Backing Up and Recovering the Database › SARDBASE RESTORE Using Forward Recovery Data

SARDBASE RESTORE Using Forward Recovery Data

If you have implemented forward recovery data set, you can add any data written to the forward recovery data sets to your newly restored database.

1. Use SARDBASE RENAME to rename the damaged database to a new name.

   Note: The RDSs do not get renamed, so they can be used in the SARDBASE RESTORE.

2. Use SARDBASE ADDDS to create a new target database with the original name.

   The high-level prefix name of the RDSs must correspond to the high-level prefix name of the target database.

3. Use SARDBASE RESTORE to restore the database index to the new target database (forward recovery data sets only are accessed if the most current backup is used); the following results occur:
   • The MCR, TCR, PCR, ECR, and UCR are restored from the backup tape.
   • The MCR and TCR are restored from the RDS.
   • The MCR is marked so that no backups can occur and a new RDS is created.
   • If you have specified the 'ASYNCH' keyword on the RESTORE statement, message SARDBR17 informs you that the index has been restored. You can now start the CA View archival started task and create the new RDS.
4. Run SARDBASE BLOAD to load the banner pages into the new database.
5. Run SARDBASE OLOAD to load the panel, message, and skeleton JCL online members into the new database. Online viewing can now resume and the following results occur:
   • SYSOUTs which are intact from the damaged database are copied to the new target database and each GCR is restored followed by its SYSOUT data.
   • SYSOUTs are copied from the RDSs to the new target database and each GCR is restored followed by its SYSOUT data. When all RDSs have been processed, the MCR is marked so that normal backups can occur.
6. Use the SARRSP recovery utility program to copy any SYSOUTs still missing from the new target disk database from backup tapes.