Recovering and Restoring
This section describes the following restoration/recovery procedures:
-
Restoring a corrupted or lost database to the most recent backup
-
Restoring a corrupted or lost database to a specified date and time
-
Recovering from a disk failure
-
Disaster recovery for a failed server
-
Recovering from a specific backup file
-
Restoring non-database, ACSLS control files
Most of these procedures use the rdb.acsss
utility, which provides options for restoring a database from the most recent backup, or from a specified date and time; disaster recovery using a backup created by bdb.acsss
; and restoring ACSLS control files created by bdb.acsss
. For more information about these options, see rdb.acsss.
Note:
If the home cell of a cartridge changes from its last location after a backup, then the restored database will not be up-to-date. To avoid cartridge movement on dismounts: each LSM must be the only LSM in its ACS (true in most SCSI libraries), or the Extended Store Feature must be enabled for all LSMs that are connected to other LSMs through a pass-thru-port.For more information, see Using the Extended Store Feature. If the Extended Store Feature is not enabled for all connected LSMs or cartridges have been entered or ejected, audit the library after the restoration to make the database current, and enable all LSMs that are connected to other LSMs through a pass-thru-port.
Note:
Do not specify the-f
option as a general option for the rdb.acsss
utility. If you backed up your database to an external network file or to an alternate tape device, use the -f
option only after entering rdb.acsss.
Choose the third recovery option. When prompted, enter -f
and the path name to your external network file or an alternate tape device. See "6" for more information.