Resilience > FailSafe > Routine Maintenance of FailSafe > Saving the Primary Database

Comment on this topic

Documentation Comments

Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.

Reality V15.0 ()

Saving the Primary Database (Resilience - FailSafe) (m646720+saveprimary.htm)

To

Reality

Version

Topic

Submitted by

Company

Location

Email address

Comment

 

 

Saving the Primary Database

This procedure enables you to save the primary database to tape. Before performing the save, tlmenu switches the clean log and gives you the option of archiving it to tape.

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.

Procedure

  1. Select the Save the Primary Database  option on the Routine Maintenance menu. A message is then displayed describing the purpose of the procedure and prompting you to confirm that you wish to continue.
  2. If Transaction Logging is inactive, tlmenu then asks if you want to continue with the save.

    • If you want to start logging before continuing with the save, enter n. This aborts the procedure. You can then start logging by selecting the Start Transaction Handling/Logging  option on the Configuration and Setup menu.
    • If you wish to continue with Transaction Logging inactive, enter y. Go to step 7.
  3. If Transaction Logging is active, 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:

    1. Automatically creates and switches to a clean log with today's date, named according to the standard naming conventions for clean logs.
    2. Automatically creates and switches to a clean log with tomorrow's date named according to the standard naming conventions for clean logs.
    3. Creates a clean log name using the standard naming conventions for the day of the week (e.g. Mon) or the date (13/06/99) that you specify and switches logging to it. This option prompts you for the day or date.
    4. Creates and switches to a clean log with any name that you specify.

    Note: It is recommended that you use the standard clean log naming conventions (for example, CLOGyymmdd-nn) when selecting a log name. Refer to the topic Naming Conventions for Clean Logs.

    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.

  4. You are then 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 7.
  5. 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.

  6. 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 required tape device.
  7. 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 and 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.

  8. If the Physical Save  or 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 12.

    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.

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

    Enter tape record block length (if other than 16000) :
  10. Next, 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 you selected multi-reel save in step 8:

    • If you selected multi-reel save, 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.

  11. You are then prompted to select the tape density (press return to use the device default) and to enter a tape label.
  12. 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.

    If Transaction Logging is inactive, go to step 16.

  13. If Transaction Logging is active, a new clean log is created and logging is switched to the new clean log. If you did not request the previous clean log to be archived, tlmenu then continues with the save as described in step 16.
  14. 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 5, 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  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.

  15. Once the archive tape is 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 disk.

    Note: If an error condition occurs during the archiving or verification of the clean log, the following message is displayed:

    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 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 local 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 save is then executed and the tape verified if this option was selected.

    You then are returned to the Routine Maintenance  menu.

RealityV15.0Comment on this topic