Save and restore data transfer performance between the BRMS TSM client and Tivoli® Storage Manager (TSM) is dependent upon several factors which include the current activity on the system, the availability of computing resources on the system, the available network bandwidth, and the TSM server. BRMS does not communicate directly with TSM servers. BRMS uses functions provided by the TSM APIs. The TSM APIs handle all communication with the TSM server.
For save operations, BRMS receives a pointer to the save data and length from the operating system. BRMS passes the pointer and length to the TSM API. The TSM API transfers the save data to the TSM server. The save performance is directly related to the ability of the operating system and BRMS to collect the blocks of save data and the TSM API to send the save data across the network to the TSM server. The slower rate of the save and send rates determines the performance of the save operation.
For restore operations, the BRMS receives requests for blocks of restore data from the operating system. BRMS passes the request to the TSM API. The TSM API manages the transfers of restore data from the TSM server. The restore performance is directly related to the ability of the TSM API to receive blocks of restore data from the TSM server across network, and BRMS and the operating system to restore the objects. The slower rate of the receive and restore rates determines the performance of the restore operation.
You can have BRMS analyze and report recent TSM performance. To do so:
Specify Report Criteria Type choices, press Enter. Select dates: From date . . . . . . . . . . . : *BEGIN Date, *BEGIN, *CURRENT To date . . . . . . . . . . . . : *END Date, *END, *CURRENT Job number . . . . . . . . . . . : *ALL 1-999999, *ALL Job user . . . . . . . . . . . . : *ALL Name, *ALL Minimum blocks . . . . . . . . . : *NONE 1-999999, *NONE F3=Exit F12=Cancel