After a Tivoli Storage Manager Server restore to a previous point in time, it is necessary to ensure that the storage pool

volumes are consistent with the Tivoli Storage Manager database which has been restored The following steps should be performed prior to returning the Tivoli Storage Manager server to normal use: 1. Immediately after the Tivoli Storage Manager server database is restored, place the following options into the dsmserv.opt file: !MI"##$%& '(revents migration and reclamation from )ic)ing off when the server is started* +ISA,&$S%-$+ .$S 'prevents any schedules from starting when the server is started* $/(I T 0 'prevents e1piration from running when the server is started* If set to something other than 0, change the setting to 0 and record the original setting. In step 2 we will remove or reset this option bac) to the original setting.

3. Start the server in the foreground '+SMS$#4*

5. 6hen the Tivoli Storage Manager server prompt comes up, enter the command +ISA,&$ S$SSI! S so that clients will be unable to connect to the Tivoli Storage Manager Server. while these cleanup steps are being performed.

7. #eview the saved volume history file, and locate se8uential tape or 9I&$ volumes mar)ed as :ST"+$&$T$: and :ST"#$;S$: in the list. .ou will need to audit only these types of volumes created after the date of the database bac)up that had been restored. If the volume history file is lost or unrecoverable, then all se8uential volumes should be audited, for the sa)e of caution. The audit command is performed as follows: A;+IT 4!&;M$ <volume=name> 9I/?.$S ote that this command will verify the data on the volume against the entries in the Tivoli Storage Manager Server database. Any items that are not found will be removed from the Tivoli Storage Manager Server.

@. It will also necessary to audit all volumes in randomAaccess dis) storage pool volumes with the same command above. These are volumes belonging to storage pools whose device class name is +ISB.

C. !nce all applicable volume audits have been completed, the data on the volumes should be synchroniDed with the Tivoli Storage Manager +atabase at the point in time of the last restored database bac)up.

2. -alt the server and remove the following two options added in step one: nomigrrecl, :disablescheds yes:E and set the e1pinterval bac) to its original setting 'or comment it out if it had not previously been set*.

F. #estart the server as normal. %onnect to the running Tivoli Storage Manager server and Issue the command $ A,&$ S$SSI! S to allow clients to connect to the server again.