unixadmin.free.fr Handy Unix Plumbing Tips and Tricks

Recommended Tivoli Storage Manager Server Post-Database Restore Processing Steps

Question

After a DSMSERV RESTORE DB is completed, are there any additional steps that should be taken before resuming normal operations of the Tivoli Storage Manager Server?

Cause

Restore of the Tivoli Storage Manager server database to an earlier point in time can cause Tivoli Storage Manager to encounter data on disk and tapes for which it has no record, or records in its database for which the data in question no longer exists (whether at all or in its original location), resulting in ANR1330E and ANR1331E errors and/or ANR0340E messages for 6.3+ level servers using node replication.

Answer

NOTE: It is important to save a copy of the volume history file (volhist.out, captured by running the BACKUP VOLHIST command) on a regular basis. The information in this file can be used to reduce the amount of volume auditing that is necessary for step 4 below.

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:

NOMIGRRECL (Prevents migration and reclamation from kicking off when the server is started)
DISABLESCHED YES (prevents any schedules from starting when the server is started)
EXPINT 0 (prevents expiration 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 7 we will remove or reset this option back to the original setting.

2. Start the server in the foreground (DSMSERV)

3. When the Tivoli Storage Manager server prompt comes up, enter the command DISABLE SESSIONS so that clients will be unable to connect to the Tivoli Storage Manager Server. while these cleanup steps are being performed.

4. Review the saved volume history file, and locate sequential tape or FILE volumes marked as "STGDELETE" and "STGREUSE" in the list. You will need to audit only these types of volumes created after the date of the database backup that had been restored. If the volume history file is lost or unrecoverable, then all sequential volumes should be audited, for the sake of caution. The audit command is performed as follows:

AUDIT VOLUME FIX=YES

Note 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.

5. It will also necessary to audit all volumes in random-access disk storage pool volumes with the same command above. These are volumes belonging to storage pools whose device class name is DISK.

6. Once all applicable volume audits have been completed, the data on the volumes should be synchronized with the Tivoli Storage Manager Database at the point in time of the last restored database backup.

7. Halt the server and remove the following two options added in step one: nomigrrecl, "disablescheds yes"; and set the expinterval back to its original setting (or comment it out if it had not previously been set).

8. Restart the server as normal. Connect to the running Tivoli Storage Manager server and Issue the command ENABLE SESSIONS to allow clients to connect to the server again.

9. For TSM Server 6.3 or higher, if using node replication between servers, resync replication. Reference the steps from the messages manual for message ANR0340E (Link below)