Steps at the TSM Server

Ask your TSM administrator to perform the following tasks:

• Register your system node name and assign it to a TSM domain that does not perform scheduled backups.
  Note:

  When you register the system as a node with the TSM server, make sure you use COMPression=Client or COMPression=No, and BACKDELete=Yes on the REGister Node command.
• Provide the management class name if that name is different from STANDARD.
• Provide the communications protocol that you will use to connect to the TSM server.
• Provide a name that indicates the communications category (for example, *APPC or *NET) you need to use.
• The TSM STANDARD management class does not provide the most efficient use of TSM server storage when used with the BRMS TSM Client. You need to consider using the following TSM administrative commands to create and enable a new TSM domain and TSM management class, and registering nodes for BRMS use.

  For IBM® Tivoli® Storage Manager servers

  DEFINE DOMAIN BRMS DESCRIPTION="Domain for BRMS TSM
  Clients" BACKRETENTION=nnnnn ARCHRETENTION=0
  
  DEFINE POLICYSET BRMS BRMS DESCRIPTION="Policy set for BRMS
  TSM Clients"
  
  DEFINE MGMTCLASS BRMS BRMS BRMS DESCRIPTION="Management
  class for BRMS TSM Clients"
  
  DEFINE COPYGROUP BRMS BRMS BRMS STANDARD TYPE=BACKUP
  DESTINATION=storage pool name
  VEREXISTS=1 VERDELETED=0 RETEXTRA=0 RETONLY=0
  
  ASSIGN DEFMGMTCLASS BRMS BRMS BRMS
  
  ACTIVATE POLICYSET BRMS BRMS
  
  REGISTER NODE node-name password DOMAIN=BRMS COMPRESSION=N0 BACKDELETE=YES
  

  For IBM Data Retention 450 (DR450) and DR550 servers

  DEFINE DOMAIN BRMS DESCRIPTION="Domain for BRMS TSM
  Clients" BACKRETENTION=0 ARCHRETENTION=nnnnn
  
  DEFINE POLICYSET BRMS BRMS DESCRIPTION="Policy set for BRMS
  TSM Clients"
  
  DEFINE MGMTCLASS BRMS BRMS BRMS DESCRIPTION="Management
  class for BRMS TSM Clients"
  
  DEFINE COPYGROUP BRMS BRMS BRMS STANDARD TYPE=ARCHIVE 
  RETVER=nnnnn RETINIT=CREATION
  
  DESTINATION=storage pool name
  
  ASSIGN DEFMGMTCLASS BRMS BRMS BRMS
  
  ACTIVATE POLICYSET BRMS BRMS
  
  REGISTER NODE node-name password DOMAIN=BRMS COMPRESSION=N0 ARCHDELETE=YES
  

• BRMS will be the management class name that is used by the BRMS TSM Client.

• If the management class you are using for the BRMS TSM Client uses a sequential access storage pool, you need to be aware that each library saved by the client starts and ends within a client session. If the device class used by the sequential storage pool has a mount retention of 0 minutes, the tape volume is mounted at the start of a session and dismounted at the end of a session. If you are seeing a lot of tape mounts and dismounts during the backup, review the mount retention attribute on the TSM server and change it as required to improve your response time.
• If the management class you are using for the BRMS TSM Client uses a disk storage pool, you need to be aware that TSM servers require a client to provide the size of the saved object in order to allocate storage from the disk pool for receiving the saved object. BRMS estimates the saved object size because the true size of any saved object is not available from the operating system until after the object has been saved. If you are running multiple concurrent backup jobs to a TSM server, the cumulative disk pool storage requirements due to these estimated object sizes may cause some BRMS client sessions to be ended by the TSM for insufficient storage. The following defines the estimates BRMS uses for saving objects to TSM servers.

  Libraries and objects:

  Use the size of each library.

  Folders and documents:

  Use the size of library QDOC.

  Directories and files:

  *LINK save or calculated size or size specified in QUSRBRM/Q1ATSMSIZE data area, then maximum of that size or 128 megabytes.

  Spooled files

  Use 512 megabytes.

  The estimated size is then increased another 5% to allow for descriptors and check sums inserted into the save data stream by the operating system.

Using estimated saved object sizes provides better save performance than determining the actual saved object. The BRMS estimated size tends to be over estimated. Over estimating objects sizes may impact TSM client operations if the target disk storage pool is not of sufficient size. If you run multiple BRMS clients sessions to the same disk storage pool, other client sessions using the same disk storage pool could be ended due to lack of storage.