IBM E16RMLL-I Implementation Guide - Page 624
DRM settings
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 624 highlights
Last Update by (administrator): ADMIN Last Update Date/Time: 02/27/2006 15:25:52 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No Reclamation Type: Threshold 19.2.3 DRM settings Now we configure the DRM settings. Most of the DRM basic settings are set using SET commands. 1. First, we need to specify a directory where the DR plans will be stored, and a prefix that will name each file. To set the prefix we use the set drmplanprefix command. You should specify the plan prefix with an absolute directory path followed by your chosen file name prefix. Using the form shown in Example 19-4, our DR plans generated by DRM will be stored in the directory C:\TSMDATA\DRM\PLANS\ and each file will be prefixed by the string LOCHNESS-DR_. If you do not set the directory and prefix, plans are created in the server's default path (the directory where the instance of the Tivoli Storage Manager server is running from) with a file name consisting only of the date and time the plan was created. Enclose the prefix in quotes if it contains metacharacters or spaces. Example 19-4 Setting the DRM plan prefix tsm: LOCHNESS_SERVER1>set drmplanprefix "c:\tsmdata\drm\plans\lochness-dr" ANR6700I SET DRMPLANPREFIX command completed successfully. 2. Next we set the prefix for where site-specific recovery instructions will be stored. The DRM prepare command will look for the instructions files in this directory if it is set. We set the instructions directory using set drminstrprefix. You should specify the instructions prefix with an absolute path. Using the syntax shown in Example 19-5 on page 595, the recovery instruction files should be located in the directory C:\TSMDATA\DRM\INSTRUCTIONS\. The prefix does not need to be specified. If you do not set the directory, instructions are searched for in the server's default path (the directory from where the instance of the Tivoli Storage Manager server is running). 594 IBM Tivoli Storage Manager Implementation Guide