HP Reference Information Storage System Version 1.6 Administration Guide revision 2 (T3559-90809, September 2007)
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 dom ain s truc ture
How RISS co
nfigures TSM
The RISS ba
ckup server is initially configured with the script /usr/local/tsmBackup/configTiv
init from t
he 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 prefixtomakeiteasierto
remember
and recognize the object names. The association of prefixesandobjectsisasfollows:
• LIB: Libraries
• DC: Device Classes
• DR: Drive
s
• 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. Establi
shing general backup ser ver settings.
• The default password expiration time is the maximum available (27 years) .
• The password for the administrator is set to never expire.
•Toprev
ent clients from creating unexpected nodes, the client registration is set to closed. Only
the administrator can reg ister client nodes. (See the Tivoli Admi nistration Guide on “Closed
Registration” at h
ttp://publib.boulder.ibm.com/info center/tivihelp/ v1r1/index.jsp?topic=/
com.ibm.itsmcw.doc/anrwgd53393.htm.)
• An administrator acco unt is created with the name INTERNAL_ADMIN. The granted
privi
lege 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. Init
ializing the library, storage paths, d rives, device classes, and labeling of all of the media.
The f
ollowing steps represent an example configuration and can vary from system to system.
Administrator Guide
101