If you have the TSM APIs on CD-ROM, use the following command: RSTLICPGM(5733197) DEV(device name where device-name is the name of the device for the CD-ROM that contains the Tivoli® Storage Manager Client API (TSM APIs).
If you downloaded the APIs from the Internet, use the following command: RSTLICPGM LICPGM(5733197) DEV(*SAVF) SAVF (library-name/save-file-name) where the SAVF parameter specifies the library and the save file that contain the TSM APIs.
You can find information about how to install BRMS in Installing and Initializing BRMS.
If you have more than one TSM server create a unique BRMS location for each TSM server. If you also use a BRMS network, this location will automatically be sent to other systems in the network.
To get to the Work with Storage Locations display, type WRKLOCBRM at a command line and press Enter.
Work with Storage Locations RCHAS400 Position to . . . . . . Starting characters Type options, press Enter. 1=Add 2=Change 3=Copy 4=Remove 5=Display 6=Work with media 7=Work with containers Opt Location Volumes Containers Text 1 TSMSERVER *HOME 97 1 Entry created by BRM configuration VAULT 0 0 Entry created by BRM configuration Bottom F3=Exit F5=Refresh F12=Cancel
Add Storage Location Type choices, press Enter. Storage location . . . . . . . . . TSMSERVER Name Address line 1 . . . . . . . . . . Computer room, parent location. Address line 2 . . . . . . . . . . Address line 3 . . . . . . . . . . Address line 4 . . . . . . . . . . Address line 5 . . . . . . . . . . Contact name . . . . . . . . . . . Jennie Doe Contact telephone number. . . . . . Retrieval time . . . . . . . . . . .0 Hours Allow volumes to expire . . . . . . *NO *YES, *NO Media slotting . . . . . . . . . . *NO *YES, *NO Text . . . . . . . . . . . . . . . TSM server location F3=Exit F12=Cancel
BRMS media policies used with TSM servers determine how long the objects stored on the TSM server are maintained in BRMS history. When the retention period expires, and the object will be deleted from the TSM server and BRMS history the next time maintenance is run. It is important to always explicitly specify the location when using the media policy for TSM servers.
Take the following steps to create a media policy for your TSM server:
Create Media Policy Type choices, press Enter. Media policy . . . . . . . . . . . TSM Name Retention type . . . . . . . . . . 2 1=Date, 2=Days, 3=Versions, 4=Permanent Retain media . . . . . . . . . . 35 Date, Number Deleted library retention. . . . *NONE Number, *NONE Move policy . . . . . . . . . . . *ADSM Name, *NONE, *ADSM, F4 Media class . . . . . . . . . . . *ADSM Name, *SYSPCY, *ADSM, F4 Storage location . . . . . . . . . TSMSERVER Name, *ANY, F4 for list Save to save file . . . . . . . . *NO *YES, *NO ASP for save files . . . . . . . *SYSTEM Name, *SYSTEM, 1-32 Save file retention type . . . . 4 1=Date, 2=Days, 3=Permanent, 4=None Retain save files . . . . . . *NONE Date, Number, *NONE ASP storage limit . . . . . . . *SYS *SYS, 1-99 Secure media . . . . . . . . . . . *ADSM *YES, *NO, *ADSM More... F3=Exit F4=Prompt F5=Refresh F12=Cancel
Create Media Policy Type choices, press Enter. Required volumes . . . . . . . . . *NONE *NONE, 1-9999 Mark volumes for duplication . . . *NO *NO, *YES Mark history for duplication . . . *NO *NO, *YES Text . . . . . . . . . . . . . . . *NONE More... F3=Exit F5=Refresh F12=Cancel
Create Media Policy Type choices, press Enter. Encrypt Data . . . . . . . . . . . *NO *NO, *YES TSM management class . . . . . . . STANDARD TSM transfer size. . . . . . . . . 1024 1-9999999 TSM transfer ASP . . . . . . . . . *SYSTEM Name, *SYSTEM, 1-32 TSM security: TSM node . . . . . . . . . . . . APPN.REESES TSM password . . . . . . . . . . *NONE Bottom F3=Exit F5=Refresh F12=Cancel
You need to create a unique BRMS device for each TSM server you intend to use. BRMS devices are not networked so you will need to create these devices on each system which will use the TSM servers. You can create a TSM device at the Work with Devices (WRKDEVBRM) display. To get there, type WRKDEVBRM at a command line and press Enter. At the Work with Devices display, take the following steps:
Work with Devices RCHAS400 Position to . . . . . . Starting characters Type options, press Enter. 1=Add 2=Change 4=Remove 5=Display 8=Work with status Opt Device Category Type/Model Text TAPMLBBRM *TAPMLB 3575/018 Entry created by BRM configuration 1 TSMSERVER *NET More... F3=Exit F5=Refresh F12=Cancel
Add Net Device Net device . . . . . . . . . . . : TSMSERVER Type choices, press Enter. Text . . . . . . . . . . . . . . . TSM Server Location . . . . . . . . . . . . . TSMSERVER Name, F4 for list TSM file space . . . . . . . . . . *LCL Buffer size . . . . . . . . . . . . *DEVTYPE *DEVTYPE, 1-512 KB Retention protection . . . . . . . *NO *NO, *YES Internet address . . . . . . . . . 123.345.567.890 Internet port . . . . . . . . . . . 1500 1-65534 F3=Exit F4=Prompt F12=Cancel
You can easily change an existing control group which uses local devices to use TSM devices provided that the data specified in the control group meets the criteria for user data allowed to be saved on TSM servers. Take the following steps to change an existing control group:
Change Backup Control Group Attributes Group . . . . . . . . . . . . . . . . : SAMPLE Type information, press Enter. Media policy for: Full backups . . . . . . . . . . . . . TSM Name, F4 for list Incremental backups . . . . . . . . . TSM Name, F4 for list Backup devices . . . . . . . . . . . . . TSMSERVER Name, F4 for list Parallel device resources: Minimum resources . . . . . . . . . . *NONE 1-32, *NONE, *AVAIL Maximum resources . . . . . . . . . . 1-32, *AVAIL, *MIN Sign off interactive users . . . . . . . *BKUPCY *YES, *NO, *BKUPCY Sign off limit . . . . . . . . . . . . . *BKUPCY 0-999 minutes, *BKUPCY Default weekly activity . . . . . . . . *BKUPCY SMTWTFS(F/I), *BKUPCY Incremental type . . . . . . . . . . . . *BKUPCY *CUML, *INCR, *BKUPCY Force full backup days . . . . . . . . . *BKUPCY 0-365, *NOMAX, *BKUPCY More... F3=Exit F4=Prompt F12=Cancel
You are now ready to perform saves to a TSM server while using this control group. You can use the locations, media policies, and devices you just created with other backup or archive control groups.