Recovering from data loss or system outages

You can use Tivoli® Storage Manager to recover data that was lost when a disaster or system outage occurred. You can recover directory-container storage pools, client data, and databases.

Before you begin

Schedule client and server workloads to achieve the best performance for your storage environment. Issue the PROTECT STGPOOL and REPLICATE NODE commands as part of the schedule. Protect the storage pool before you replicate the client node. When node replication is started, the data extents that are already replicated through storage pool protection are skipped, which reduces replication processing time.

Procedure

Use the following recovery methods based on the component that you must recover.

Component to recover	Procedure	More information
Directory-container storage pool	To recover directory-container storage pools, complete the following steps: Scan for damaged data extents in the directory-container storage pool by using the AUDIT CONTAINER command and specifying the ACTION=SCANALL parameter. Repair damaged data extents in the directory-container storage pool by using the REPAIR STGPOOL command. Restriction: You can repair a storage pool only if the storage pool is protected. Remove damaged data extents by using the AUDIT CONTAINER command and specifying the ACTION=REMOVEDAMAGED parameter.	Repairing storage pools
Client data	Prerequisites: The source replication server, the target replication server, and the client must be at the V7.1 level or later. If any of the servers are at an earlier level, automatic failover is disabled and you must rely on manual failover. Manually configure the client to automatically fail over to the target server for data recovery. If you enabled the client for automated client failover, you can recover the data by using automatic failover function. You can verify that the usereplicationfailover option is either not in the client options file or is set to `yes`. Recover data from the target server when the source server is unavailable due to an outage by using automatic failover. Tip: Use the SET FAILOVERHLADDRESS command to specify the IP address for the replication server during failover, if the address is different from the IP address that is specified for the replication process.	Recovering damaged data from a replicated copy SET FAILOVERHLADDRESS (Set a failover high level address)
Database	Prerequisites: To restore the database after a disaster, you must have a copy of the current device configuration file. The device configuration file cannot be recreated. Ensure that you have a backed up version of the database. Restore the Tivoli Storage Manager database to the most current state or to a specific point in time by using the DSMSERV RESTORE DB server utility.	DSMSERV RESTORE DB (Restore the database)