HP RISS Components manual How Riss configures TSM, Policy domain structure

are first stored after they are backed up or archived. A copy group is used to define how many versions of a file are kept and how long client data is retained.

The figure below shows how these categories are related.

Figure 26 Policy domain structure

How RISS configures TSM

The RISS backup server is initially configured with the script /usr/local/tsmBackup/configTiv init from the PCC machine.

This script uses the TSM administrative command line interface to connect to TSM, and sends TSM commands that create the TSM objects and configurations that are necessary for backing up RISS data.

The TSM objects that are created are always preceded with an appropriate prefix to make it easier to remember and recognize the object names. The association of prefixes and objects is as follows:

•LIB: Libraries

•DC: Device Classes

•DR: Drives

•SP: Storage Pools

The details of the configTiv script are not required for day-to-day operation, but might be useful for TSM administrators who are interested in customizing their systems.

The process of setting up the initial Tivoli configuration is divided into three phases:

1.Establishing general backup server settings.

•The default password expiration time is the maximum available (27 years).

•The password for the administrator is set to never expire.

•To prevent clients from creating unexpected nodes, the client registration is set to closed. Only the administrator can register client nodes. (See the Tivoli Administration Guide on “Closed Registration” at http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/ com.ibm.itsmcw.doc/anrwgd53393.htm.)

•An administrator account is created with the name INTERNAL_ADMIN. The granted privilege class is system.

•A database volume of 1000 MB is allocated on the backup server, if one does not already exist under C:\WINNT\SYSTEM32\DB.2.

2.Initializing the library, storage paths, drives, device classes, and labeling of all of the media. The following steps represent an example configuration and can vary from system to system.

Administrator Guide 101