Saving a Secondary Database

Note: This procedure must be carried out from the primary database.

This procedure enables you to save the secondary database to tape while maintaining an active primary, with logging continuing on both the primary and secondary databases.

Caution

tlmenu does not support archiving of multiple clean logs. The clean log archive procedure only dumps one clean log per tape. A separate tape must be used to archive each log file.

Before performing the save, tlmenu switches the clean log and gives you the option to archive the previous clean log to tape. It also gives you the option to pause updates to the secondary database while the save is being carried out. When the save has completed, it resumes updates to the secondary.

Procedure

  1. Select the Save the Secondary Database  option on the Routine Maintenance menu. A message is displayed describing the purpose of the procedure and prompting you to confirm that you wish to continue.
  2. You are asked to specify the clean log to switch to, before performing the save. A menu similar to the following is displayed:

    Switching to:
    
    1.  Another Clean Log for today (CLOG990731-01)
    2.  Next day's Clean Log (CLOG990801-01)
    3.  Clean Log for named day or date
    4.  A named Clean Log
    
    Enter option (1-4) : _
    Select the option you require:

    Having selected the clean log name, you are asked to confirm that you want to switch to the specified clean log. Enter y  to continue with the clean log switch.

  3. Next you are asked:

    Do you want to archive previous Clean Log (y/n/q) ? :
    • Enter y  to archive the previous clean log.
    • If you enter n,  the archive procedure is omitted. Go to step 6.
  4. You are then asked:

    Do you want to run the archive on the Secondary (y/n/q)? :

    Enter y  to archive the clean log on the secondary or n  to archive it on the primary.

  5. A list of tape units configured on the selected database is then displayed, showing their status, and you are prompted to select one to carry out the archive. Enter the number of the required tape device.
  6. You are then prompted to set up tape parameters for the save. First you are asked:

    Do you want to suppress the VERIFY-SAVE following 
    the Save (y/n/q) ? :

    Caution

    The integrity of the save tape cannot be guaranteed if you suppress VERIFY-SAVE.

    Enter n  to verify the tape or y  to omit the verification step. If you enter y, a warning prompt is displayed asking you to confirm that you wish to carry out the save without verifying it.

  7. If the dbsave  option was selected when defining the backup method used by tlmenu, you are then prompted to specify the time for the save to start. Go to step 15.
  8. If the Choose at time of save  option was selected when defining the backup method used by tlmenu, you are then prompted to choose the type of save. Enter the required option.
  9. If Physical Save  is selected, you are then asked whether to use the default list of tape units. Enter y  or n  as appropriate. If you entered y, continue with step 14; otherwise go to step 12.
  10. If the FILE-SAVE  method was selected, you are first prompted to set up tape parameters for the FILE-SAVE. First you are prompted:

    Will FILE-SAVE be multi-reel, if unsure select yes (y/n/q) ? : 

    Note: If you enter y, you will be prompted for multiple tape units during this FILE-SAVE setup sequence.

  11. Then you are asked to specify the tape record block length:

    Enter tape record block length (if other than 16000) :
  12. The tapes that are available on the local database are listed and you are prompted to select the required tape unit(s). The prompt depends on whether multi-reel save is selected:

    • If multi-reel save is selected, you are prompted

      Enter LOCAL tape unit number for Save (tape_unit), in sequence, separated by commas :

      Enter a comma-separated list of tape unit numbers.

    • Otherwise, you are prompted

      Enter LOCAL tape unit number for Save (tape_unit) :

      Enter the number of the required tape unit.

  13. Except if Physical Save  is selected, you are then prompted to select the tape density (press return to use the device default).
  14. You are then prompted to enter a tape label, if required.
  15. Then you are prompted to enter the start time for the save:

    Enter start time for save (hh:mm) or return for immediate start :

    Enter the time at which you want the save to start in the format hh:mm or press return to start immediately.

  16. Except if Physical Save  is selected or you are running Heartbeat, you are then asked if you want to suspend updating of the secondary database while the save is being carried out:

    Do you want to pause updates to the secondary database(y/n/q)?:
    • If you enter y  the update process for the secondary database is suspended, maintaining the secondary database in an inactive state while the save is being carried out. Note, however, that if an autoswitch occurs while updates are paused, further transaction updates will be suspended. A prompt warns you of this and you are asked if you want to continue with the save.
    • If you enter n, all updates to the primary are applied to the secondary while the secondary save is being carried out. Note that in this case, if the currently active clean log is restored, reject images will be logged to the TL-REJECT file.
  17. A new clean log is then created and logging is switched to the new clean log. The secondary update process is paused, if selected and no further updates are made to the secondary database. This whole process may take up to 2 minutes to complete.

    Once the clean log switch is complete, if you did not request the previous clean log to be archived, tlmenu continues with the save as described in step 21.

  18. If you specified that the previous clean log should be archived, you are prompted to mount the tape for the archive.

    Mount write enabled tape on LOCAL [or REMOTE] tape unit for Clean Log archive.
    
    Are you ready to continue (y/n/q) ?

    Note: If you selected archive on the secondary in step 4, the tape must be mounted on the secondary system.

    Ensure that the tape is loaded and the tape unit is on-line. Then enter y  to continue.

    tlmenu logs on to the selected database and executes tape operations to archive the clean log and, if requested, verify the archived log.

  19. Once the archive tape has been verified you are asked if you want to remove the clean log from disk:

    Delete Clean Log clog_name from Disk (y/n/q) ? :

    Enter y  to remove the archived clean log from both primary and secondary databases.

    Note: An error condition occurring during the archiving or verification of the clean log will display the message:

    Warning : Clean Log archive / verify failed.
    Do you want to retry (y/n/q)?:

    Enter y  to retry the archive/verify procedure, or n  to return to the Routine Maintenance  menu.

    If the secondary is paused, you are prompted:

    Resume secondary updates before verifying Save (y/n/q) ? :

    Enter y  if you wish to resume updating the secondary database immediately after the save is completed and before it is verified.

    If you enter n, updating of the secondary remains paused until the save is verified.

  20. You are now asked to confirm that you want to start the save.

    • For a FILE-SAVE , a message similar to the following is displayed, specifying the tape setup parameters:

      About to start the FILE-SAVE on remote tape unit(s) n,
       using tape record block length nnnnn,
      tape density DEFAULT, tape label file-save,
      with a start time of hh:mm.
      
      Are you ready to start the Save (y/n/q) ? :
    • For a dbsave the following message is displayed:
    About to start dbsave with a start time of hh:mm
    
    Are you ready to start the Save (y/n/q) ? :

    Enter y  to start the save. The remote save is then executed and verified.

    Note: If the save is not completed successfully, a warning is displayed:

    WARNING : Save did not complete successfully.

    Also if the secondary is paused and you chose to resume secondary updates after the VERIFY-SAVE (by entering n  at step 20), then the following message is also displayed:

    Secondary database remains paused.
    
    Do you wish to resume secondary updates now (y/n/q) ? :

    Enter y  to resume updating the secondary; otherwise the secondary database will remain paused.

    Once the save is successfully completed, the verification procedure continues automatically. If the secondary is paused, updates are resumed before or after the save is verified, depending on what you selected in step 20.

  21. If the secondary was paused and updates have now been resumed, the procedure finishes with the message:

    [CTL4007] Failsafe operation resumed

    You then are returned to the Routine Maintenance  menu.

    If, however, the secondary was not paused, you are now prompted to switch the clean log again in order to provide a suitable reference point for database recovery:

    Switching to:
    
    1.  Another Clean Log for today (CLOG990731-01)
    2.  Next day's Clean Log (CLOG990801-01)
    3.  Clean Log for named day or date
    4.  A named Clean Log
    
    Enter option (1-4) : _
    Select the option you require:

    Having selected the clean log name, you are asked to confirm that you want to switch to the specified clean log. Enter y  to continue with the clean log switch.

  22. You are then given the option to archive the previous clean log with the prompt:

    Do you want to archive a Clean Log (y/n/q) :
    • If you want to archive the previous clean log, enter y.
    • If you want to switch to a new clean log, but not archive the previous clean log to tape, enter n. A new clean log is created and switched on both the primary and secondary databases. The previous clean logs are retained on disk and you are returned to the Routine Maintenance  menu. You should archive the clean logs at a later date.
  23. You are then asked:

    Do you want to run the archive on the Secondary (y/n/q)? :

    Enter y  to archive the clean log on the secondary, or n  to archive it on the primary.

  24. A list of tape units configured on the selected database is then displayed and you are prompted to select one to carry out the archive. Enter the number of the tape device that you want to use for the archive. The new clean log is then created and logging is switched to it.
  25. You are then prompted:

    Mount write enabled tape on LOCAL tape unit for Clean Log archive.
    
    Are you ready to continue (y/n/q) ?

    Note: If you selected archive on the secondary in step 4, the tape must be mounted on the secondary machine.

    Ensure that the tape is loaded and the tape unit is on-line, then enter y. tlmenu logs on to the selected database and executes tape operations to archive the clean log and verify the archived log, if selected.

  26. Once the archive tape has been verified you are asked if you want to remove the clean log from disk:

    Delete Clean Log clog_name from Disk (y/n/q) ? :

    Enter y  to remove the archived clean log from both primary and secondary databases.

    Note: An error condition occurring during the archiving or verification of the clean log, will display the message:

    Warning : Clean Log archive / verify failed.
    Do you want to retry (y/n/q)?:

    Enter y  to retry the archive/verify procedure, or n  to return to the Routine Maintenance  menu.

    You are then returned to the Routine Maintenance menu.

Go to top button