SARDBASE RESTORE

Select the correct procedure below
view
Select the correct procedure below
Contents
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
      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.
SARDBASE RESTORE without Forward Recovery Data
If the database is lost or damaged, and all attempts to recover it have failed, it can be recovered from backup tapes as follows:
  1. Run the SARDBASE utility ADDDS function to create a new database.
    In cases where the old database has to be deleted due to insufficient disk requirements for the new database, provide an alternate means of backup for the database, such as FDR or DFDSS.
  2. Run the SARDBASE RESTORE function.
    If you have specified the 'ASYNCH' keyword on the RESTORE statement, the SARDBR17 console message notifies you when the preliminary phase has completed. You can now bring up the
    View
    started task to resume archival. An alternative is to restore only the master index, and then use SARRSP and/or SARTDR TLOAD to restore the SYSOUT data.
    The SARDBASE RESTORE JCL must specify a SARRECV or SARTAPE DD statement for purposes of locating the backup tapes.
    Note:
     Perform the RESTORE operation against a newly created, empty database. It is not necessary to reinstate any initialization parameters because these parameters are recovered during the restore process.
  3. Run SARDBASE BLOAD to load the banner pages into the new database.
  4. Run SARDBASE OLOAD to load the panel, message, and skeleton JCL online members into the new database.
  5. If the old database was not used in the restore process, run either SARRSP or SARTDR TLOAD to load the SYSOUT data; you can:
    • Use SARTDR TLOAD to load one or two generations of data.
    • Restart the
      View
      archival task and resume operation.
    • Run SARRSP to restore the remaining data.