Skip to content
CA Disk™ Backup and Restore - 12.5
Documentation powered by DocOps

DBRECOV - Forward Recovery After Loading or Rebuilding the Index

Last update April 12, 2016

After the DBLOAD reloads DBRECOV, DBRECOV can forward recover your database. If you restored from a hot backup, perform Forward Recovery to ensure the integrity of the database. You also can run a forward recovery after rebuilding the index with the DBRETIX job.

Spill the LXX before the database is loaded and your most recent RXX recovery files are used. Data centers that use tape sometimes have a special setup for jobs that use tape. If your data center uses tape, the DBRECOV job can require more customization.

//DBRECOV  JOB (1),'CA DISK',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID

//************************************************************************

//*                                                                      *

//*  AMPLE FORWARD RECOVERY OF CA DATACOM/AD                             *

//*                                                                      *

//*  DO NOT USE FOR PRODUCTION DATA WITHOUT FIRST CALLING                *

//*  CA DATACOM/AD SUPPORT AND OPENING A SEVERITY ONE ISSUE.             *

//*                                                                      *

//*  REFER TO CA DATACOM/AD MANUALS FOR INFORMATION ON FORWARD           *

//*            RECOVERY AND OPTIONS FOR ITS USE.                         *

//*                                                                      *

//************************************************************************

//RECOVER      EXEC      PGM=DBUTLTY,REGION=0M

//STEPLIB      DD        DISP=SHR,DSN=CAI.DISK.ADRRSPNN.CUSLIB

//             DD        DISP=SHR,DSN=CAI.DISK.ADRRSPNN.CAAXLOAD

//SYSPRINT     DD        SYSOUT=*

//CXX          DD        DISP=SHR,DSN=CAI.DISK.ADRRSPNN.CXX

//RXX          DD        DISP=SHR,DSN=CAI.DISK.ADRRSPNN.RXX(-2)

//             DD           DISP=SHR,DSN=CAI.DISK.ADRRSPNN.RXX(-1)

//             DD           DISP=SHR,DSN=CAI.DISK.ADRRSPNN.RXX(-0)

//*

//SYSIN        DD   *

 RECBASE DBID=650

 RECOVERY OPTION=FORWARD,UPDATE=NO

 SET OPTION1=ON-ERROR-CONTINUE

 ACCESS STATUS=WRITE,DBID=650          ASSUMES DBLOAD OR DBRETIX

/*

Review the following customization points:

  1. Ensure CA Datacom/AD MUF is active.
  2. Ensure CA Disk is quiesced.
  3. Ensure that the RXX DD contains all the RXX data sets created since the backup job ran.
  4. Run the DBRECOV job.

The RXX recovery files contain log data for all databases in the MUF. If multiple databases were reloaded, you can recover multiple databases in one forward recovery.

  1. Identify the RXX recovery files, generally tapes or cartridges, which are needed. Include all RXX recovery files that were created since the backup job that created the restored backup.
  2. Concatenate these files in order on the RXX DD.
    Start with the oldest file first and proceed with the next oldest. Continue until the most recent RXX file is added as the last in the concatenation.

    Note: These files must be processed to restore the database .
  3. Remove the NORESTART control statement from the MUF startup parameters.
  4. Shut down the MUF and restart it.

Recovering Multiple Databases Concurrently

If you have restored multiple product databases within a MUF and you want to forward-recover these databases simultaneously, follow these steps:

  1. Retrieve and customize the DBRECOV job in the CA Disk INSTALL library.
    Add any site-specific requirements, such as a special job class or SETUP controls, because the DBRECOV is generally a tape or cartridge job.
  2. Specify an ACCESS control statement for each database you want to recover in the DBLOAD or DBRETIX job.
  3. Specify a RECBASE control statement for each database you want to recover.
  4. Identify the RXX recovery files, generally tapes or cartridges. Include all RXX recovery files that have been created since the earliest of the restored backups started processing. For example:
    You run two backups:
    1. DBID 650
      The backup of 650 started at 11:00.
    2. DBID 651
      The backup of 651 started at 11:30.
    You need all RXX tapes that are created after 11:00.
  5. Concatenate these files in order on the RXX DD.
    Start with the oldest file first and proceed with the next oldest. Continue until the most recent RXX file is added as the last in the concatenation.

    Note: These files must be processed to restore the database correctly .

Review the following customization points:

  1. Open a Severity 1 Issue with CA Datacom/AD Support before running the recovery.
  2. Ensure CA Datacom/AD MUF is active.
  3. Ensure CA Disk is quiesced.
  4. Ensure that the RXX DD contains all the RXX data sets created since the earliest backup job ran.
  5. Run the DBRECOV job.
  6. Remove the NORESTART control statement from the MUF startup parameters.
  7. Shut down the MUF and restart it.

Recovering Multiple Databases Concurrently

If you have restored multiple product databases within a MUF and wish to forward recover these databases at the same time, you can do so by following these steps:

  • Retrieve and customize the DBRECOV job in the CA Disk INSTALL library.
  • Since this will generally be a tape or cartridge job, add any site-specific requirements you may have such as a special job class or SETUP controls.
  • Specify an ACCESS control statement for each database you want to recover in the DBLOAD or DBRETIX job.
  • Specify a RECBASE control statement for each database you want to recover.
  • Identify the RXX recovery files, generally tapes or cartridges that are needed. You will need to include all RXX recovery files that have been created since the earliest of the restored backups started processing.

For example: if you ran two backups, one of DBID 650, and one of DBID 651, and the backup of 650 started at 11:00 and the backup of 651 started at 11:30, you will need all RXX tapes created after 11:00.

On the RXX DD, concatenate these files in order; the oldest file first and proceeding with the next oldest, until the most recent RXX file is added as the last in the concatenation. These files must be processed in order to correctly restore the database.

The following are the customization points:

  • Open a Severity 1 Issue with Datacom/AD Support before running the recovery.
  • Ensure Datacom/AD MUF is active
  • Ensure CA Disk is quiesced
  • Ensure the RXX DD contains all the RXX data sets created since the earliest backup job ran
  • Run the DBRECOV job

After this has completed, ensure the NORESTART control statement in the MUF startup parameters has been removed, shut the MUF down and restart it.

Was this helpful?

Please log in to post comments.