Shadow Database Recovery
This topic describes procedures carried out from the the tlmenu Database Recovery menu to recover a database protected by Shadow Database software. If, on a database configured for Rapid Recovery, the automatic recovery is unsuccessful ? for example because of a hardware problem on that disk ? Shadow Database then provides an extra level of resilience. The procedures described in this topic include:
- Making the Current Database Live and Restoring the Latest Clean Logs.
- Rebuilding and Restoring the Shadow Database.
- Restoring Clean Logs onto the Shadow Database.
Overview
Recovery of a database in a Shadow configuration, after a system or application has crashed, is carried out from the tlmenu Database Recovery menu, displayed by selecting option 3 on the main administration menu. Refer to tlmenu for an overview.
The procedures executed from this menu are detailed in this topic. Each procedure, started by selecting a sub-menu option, comprises a sequence of message prompts to guide you through the process. Refer to Replies to Prompts for a description of the required responses.
Recovery is carried out in three stages which correspond to options 1 to 3 on the Database Recovery menu. They are:
- Reconfigure the current Shadow Database as the live database and enable users to logon while the failed database is being recovered.
- Remake the failed database and restore the last backup of the database.
- Restore all clean logs made since the last save, onto the new Shadow Database so as to synchronise it with the live database, except for recent updates in the active clean log.
Transaction Logging Menu System Mon Jul 31 1999
Database name : dbase2 Host name : payroll
State : Shadowing enabled, live database
Database Recovery
=================
1. Make this the Live Database and Restore the Latest Clean Log(s)
2. Rebuild and Restore the Shadow Database
3. Restore Clean Log(s) onto the Shadow Database
Enter option (1-3) : _