Server implementation - Tivoli Storage Manager server

Integrated backup/restore scenarios

Chapter 3. Tivoli Storage Manager server

3.4 Server implementation

In this section, we explain how to load the Tivoli Storage Manager supplied sample scripts, load the redbook environment scripts, format server volumes, label tape volumes, and use the Windows NT install wizards.

3.4.1 Load sample scripts

Tivoli Storage Manager is shipped with sample command scripts that can be loaded into the database and run from a Tivoli Storage Manager administrative client, administrative Web interface, or server console. They can also be included in Tivoli Storage Manager administrative command schedules. The sample scripts, inscripts.smp, are primarily SELECT queries, but also include scripts that define volumes, extend the database and recovery log, and backup storage pools.

You can load the sample scripts into the database by using either the DSMSERV LOAD command or the ^macro administrative command. When running the administrative client, it is required that the sample scripts file be accessible from the local machine. The DSMSERV LOAD command can only be used when the server is not running, while the^macrocommand can only be used when the server is running. We recommend that you use the^macrocommand method.

On non-MVS platforms, the sample scripts file is named scripts.smpand is in the install directory for the server. On the MVS platform, the sample scripts file is a member of the Tivoli Storage Manager SAMPLIB data set named ANRSCRPT.

tsm: TSM010> set accounting on

ANR2091I Accounting parameter set to ON.

tsm: TSM010> set actlogretention 10

ANR2090I Activity log retention period set to 10 days.

In the following example, we assume that the administrative client is running in an AIX environment and the sample scripts file has been put into the directory /usr/tivoli/tsm/server/bin. You must invoke the administrative command line client with the ITEMCOMMIT parameter, otherwise the macro command will fail with a series of error messages. The commands to create the sample scripts and resulting output looks similar to this:

3.4.2 Format server volumes

The Tivoli Storage Manager database, recovery log, and storage pools consist of storage volumes. On UNIX server platforms, you have the choice of using raw logical volumes or operating system files for these volumes. On all other

platforms, you can only use operating system files. In all cases where operating system files are used for server volumes, a formatting process is required to create and prepare the file for a particular type of usage. We do not discuss using raw logical volumes for server volumes further in this book.

The process of adding a new server volume consists of two steps:

1. Format the volume for the volume type using the DSMFMT utility.

2. Define the volume to Tivoli Storage Manager using the appropriate^define command.

In a non-MVS environment, those two steps can be combined into a single process: you format the volume and immediately define it in Tivoli Storage Manager by using one single storage volume command using the FORMATSIZE option. You format and define new database volumes by using the^define dbvolumecommand, new recovery log volumes by using thedefine logvolume command, and storage pool volumes by using thedefine volume command. We recommend that you use this method. See sections 4.1, “Defining a new

database volume” on page 57, 4.2, “Defining a new recovery log volume” on page 59, and 5.8.5, “Defining storage pool volumes” on page 107 for examples.

root@ /usr/tivoli/tsm/server/webimages > dsmadmc -itemcommit Tivoli Storage Manager

Enter your user id: admin Enter your password:*****

Session established with server TSM010: AIX-RS/6000 Server Version 3, Release 7, Level 1.0

Server date/time: 02/08/00 16:33:18 Last access: 02/08/00 16:26:12

tsm: TSM010> macro /usr/tivoli/tsm/server/webimages/scripts.smp NS8000I Server command: 'del script q_locked'

ANR1455E DELETE SCRIPT: Command script Q_LOCKED does not exist.

ANS8001I Return code 11.

ANS8000I Server command: 'del script q_inv_attempt'

ANR1455E DELETE SCRIPT: Command script Q_INV_ATTEMPT does not exist.

ANS8001I Return code 11.

...

ANS8000I Server command: 'upd script fsnobackup ' backup_end is null'' ANR1456I UPDATE SCRIPT: Command script FSNOBACKUP updated.

In an MVS environment, the only way to format server volumes is to use the DSMFMT utility. This utility runs outside of the Tivoli Storage Manager server environment. Sample JCL to create and format server volumes is in the Tivoli Storage Manager SAMPLIB data set in members named ANRALLO1 and

ANRALLO2. The server volume is allocated as a VSAM linear data set. Once the volume has been formatted, it must be defined to Tivoli Storage Manager for use.

3.4.2.1 Define database volume

For database volumes, the allocated file size is always a multiple of 4MB (plus an additional 1MB for overhead). The command to format a 100MB database volume on an AIX system, and the resulting output from that command, should look like this:

The command to define the formatted database volume to Tivoli Storage Manager, and the resulting output from that command, should look like this:

3.4.2.2 Define recovery log volume

For recovery log volumes, the allocated file size is always a multiple of 4MB (plus an additional 1MB for overhead). The command to format a 24MB recovery log volume on an AIX system, and the resulting output from those commands, should look like this:

The command to define the formatted recovery log volume to Tivoli Storage Manager, and the resulting output from that command, should look like this:

root@ / > dsmfmt -db /tsm/database/file07.db 101 AIX Server DSMFMT Extent/Volume Formatting Program Licensed Materials - Property of IBM

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

Allocated space for /tsm/database/file07.db: 105906176 bytes

tsm: TSM010> define dbvol /tsm/database/file07.db ANR2240I Database volume /tsm/database/file07.db defined.

root@ / > dsmfmt -m -log /tsm/log/file02 25 AIX Server DSMFMT Extent/Volume Formatting Program Licensed Materials - Property of IBM

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

Allocated space for /tsm/log/file02: 26214400 bytes

tsm: TSM010> define logvol /tsm/log/file02

ANR2260I Recovery log volume /tsm/log/file02 defined.

3.4.2.3 Define storage pool volume

The command to format a 200MB storage pool volume on an AIX system, and the resulting output from that command, should look like this:

The command to define the formatted storage pool volume in the storage pool namedDISKDATA, and the resulting output from that command, should look like this:

3.4.3 Label tape volumes

Tapes used by the Tivoli Storage Manager server must have labels written at the start of each volume. Labels are internal records that uniquely identify the tape volume. In an MVS environment, the use of standard labelled tape volumes provides the label information. In non-MVS environments, Tivoli Storage Manager must write the labels.

In an MVS environment, any tapes used by Tivoli Storage Manager must have MVS standard labels. Tivoli Storage Manager does not write those labels; they must be generated by some other method. The remainder of this section does not apply to MVS environments.

In non-MVS environments, you provide the unique labels on tape volumes by using either the DSMLABEL utility or thelabel libvolumeadministrative command. The DSMLABEL utility is run outside the Tivoli Storage Manager environment, while thelabel libvolumecommand is run inside the Tivoli Storage Manager environment. Both methods work with all tape drives, whether they are stand-alone units or are in libraries. We recommend that you use the

administrative command label libvolumeto label volumes because it writes the labels, does not require removing a drive from Tivoli Storage Manager control, and, in the case of a tape library, registers the volume with the server.

See 12.4.1, “Labeling tapes” on page 252 for examples of using thelabel libvolumecommand for both manual and automatic libraries.

3.4.4 Windows NT configuration wizards

This section applies to the Windows NT Tivoli Storage Manager server only.

root@ / > dsmfmt -m -data /tsm/stgpool/backup1 200 AIX Server DSMFMT Extent/Volume Formatting Program Licensed Materials - Property of IBM

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

Allocated space for /tsm/stgpool/backup1: 209715200 bytes

tsm: TSM010> define vol diskdata /tsm/stgpool/backup1

ANR2206I Volume /tsm/stgpool/backup1 defined in storage pool DISKDATA (device class DISK).

The Tivoli Storage Manager server utilities are available through theTivoli Storage Manager program group. It provides access to various configuration wizards, an administrative interface, a server console, Web sites, and other useful utilities. In particular, the initial configuration wizards provide a structured way to implement a Tivoli Storage Manager environment. Each of the

configuration wizards is also available independently within the Server Utilities.

Documentation on the use of the initial configuration wizards is in the chapter titled, Performing the Initial Configuration, of the bookTivoli Storage Manager for Windows NT Quick Start,GC35-0379.

The wizards provide a good front end to some steps of the Tivoli Storage Manager configuration. They are especially useful in the areas of licensing, services configuration, device configuration, volume formatting and media preparation. The configuration wizards are easier to use than the equivalent administrative interfaces. The wizards hide the details of the command interface and provide good help. However, you still need some Tivoli Storage Manager knowledge to create a good working environment.

The wizards and server utilities do not cover all aspects of an implementation and give potentially unexpected results in other areas. The wizards do not cover definition of items such as administrative schedules, client option sets, or administrators. The node configuration wizard can easily generate multiple domains, the names of which you have no control in specifying.

The wizards are not suited to bulk entry of definitions. This task is better handled through the use of administrative macros or scripts. A good example of this is the definition of our redbook administrative schedules. The definitions require one administrative command or dozens of window interactions. Our recommendation is to use the wizards with care.

In document Getting Started with Tivoli Storage Manager: (Page 72-77)