VMS Help  —  RMU72  Backup  After Journal, Examples
    Example 1

    Assuming that you have enabled after-image journaling for the MF_
    PERSONNEL database, the following command causes extensible .aij
    entries to be backed up continuously until the time specified.

    $ RMU/BACKUP/AFTER_JOURNAL/CONTINUOUS/THRESHOLD=500 -
    _$          /INTERVAL=300/UNTIL="01-JUL-1996 16:15:00.00" -
    _$          MF_PERSONNEL.RDB  DISK12:[PERS_AIJ]BU_PERSONNEL.AIJ

    Every 300 seconds, the backup process tests to determine if the
    active .aij file on disk has reached the threshold size of 500
    blocks. If not, transaction processing continues normally for one
    or more 300-second intervals until the threshold test indicates
    that the active .aij file has reached a size of at least 500
    blocks. When the .aij file reaches that file size, Oracle RMU
    allows existing transactions to continue to write to the active
    .aij file but does not allow new transactions to start.

    Assuming that the active .aij file contains 550 blocks, Oracle
    Rdb moves those 550 blocks to the backup journal file and deletes
    them from the active journal file. Then, the backup process
    determines if the transactions already in progress have written
    more journal records to the active journal file during the backup
    operation. If so, Oracle RMU moves those journal records to the
    backup file.

    After Oracle Rdb completely moves the active journal file,
    it truncates the journal file to 0 blocks. Oracle Rdb then
    allows new transactions to start and the backup process resumes
    threshold testing at 300-second intervals. The backup process
    continues until the time and date specified by the Until
    qualifier.

    Example 2

    The following examples show backing up .aij files in sequence.
    Note that a number of transactions were committed to the database
    between backup operations.

    $ RMU/BACKUP/AFTER_JOURNAL/LOG MF_PERSONNEL MFPERS_BKUP_AIJ1.AIJ
    %RMU-I-AIJBCKBEG, beginning after-image journal backup operation
    %RMU-I-OPERNOTIFY, system operator notification:
     Oracle Rdb V7.2 Database DISK1:[DB]MF_PERSONNEL.RDB;1
     Event Notification AIJ backup operation started

    %RMU-I-AIJBCKSEQ, backing up after-image journal
     sequence number 0
    %RMU-I-LOGBCKAIJ, backing up after-image journal
     AIJ1 at 16:35:53.41
    %RMU-I-LOGCREBCK, created backup file
     DISK1:[DB]MFPERS_BKUP_AIJ1.AIJ;1
    %RMU-I-AIJBCKSEQ, backing up after-image journal
     sequence number 1
    %RMU-I-LOGBCKAIJ, backing up after-image journal
     AIJ2 at 16:35:54.58
    %RMU-I-QUIETPT, waiting for database quiet point
    %RMU-I-OPERNOTIFY, system operator notification:
     Oracle Rdb V7.2 Database DISK1:[DB]MF_PERSONNEL.RDB;1
     Event Notification AIJ backup operation completed

    %RMU-I-AIJBCKEND, after-image journal backup operation
     completed successfully
    %RMU-I-LOGAIJJRN, backed up 2 after-image journals
     at 16:35:56.40
    %RMU-I-LOGAIJBLK, backed up 508 after-image journal blocks
     at 16:35:56.41
       .
       .
       .
    $ More transactions committed to the database
       .
       .
       .
    $ RMU/BACKUP/AFTER_JOURNAL/LOG MF_PERSONNEL MFPERS_BKUP_AIJ2.AIJ
    %RMU-I-AIJBCKBEG, beginning after-image journal backup operation
    %RMU-I-OPERNOTIFY, system operator notification:
     Oracle Rdb V7.2 Database
     DISK1:[DB]MF_PERSONNEL.RDB;1 Event Notification
    AIJ backup operation started

    %RMU-I-AIJBCKSEQ, backing up after-image journal sequence number 2
    %RMU-I-LOGBCKAIJ, backing up after-image journal AIJ1 at 16:47:44.66
    %RMU-I-LOGCREBCK, created backup file
     DISK2:[AIJ]MFPERS_BKUP_AIJ2.AIJ;1
    %RMU-I-OPERNOTIFY, system operator notification:
     Oracle Rdb V7.2 Database
     DISK1:[DB]MF_PERSONNEL.RDB;1 Event Notification
    AIJ backup operation completed

    %RMU-I-AIJBCKEND, after-image journal backup operation completed
     successfully
    %RMU-I-LOGAIJJRN, backed up 1 after-image journal at 16:47:46.57
    %RMU-I-LOGAIJBLK, backed up 254 after-image journal blocks at
     16:47:46.57

    Example 3

    The following example uses the Edit_Filename qualifier to give
    the .aij backup file a meaningful file name. The Rename qualifier
    specifies that Oracle RMU should create the backup file by
    renaming the current .aij file and by creating a new .aij file
    with the same name as the original .aij file.

    $ RMU/BACKUP/AFTER_JOURNAL MF_PERSONNEL -
    _$ /EDIT_FILENAME=(SEQUENCE,"_",HOUR,"_",MINUTE,"_",MONTH,"_", -
    _$ DAY_OF_MONTH) AIJ2/RENAME

    $ DIR DISK1:[DB.AIJ2]*.AIJ

    Directory DISK1:[DB.AIJ_TWO]

    AIJ23_15_46_07_09.AIJ;1

    Example 4

    The following example shows the syntax to use when you want the
    .aij backup file name to default to that previously specified
    with the RMU Set After_Journal command. Note that the .aij backup
    file name used is that which corresponds to the first .aij file
    included in the backup operation.

    $ RMU/SET AFTER_JOURNAL MF_PERSONNEL /ENABLE/RESERVE=5 -
    _$ /ADD=(NAME=AIJ1, FILE=DISK1:[AIJ]AIJ_ONE, -
    _$ BACKUP_FILE=DISK4:[AIJBCK]AIJ1BCK) -
    _$ /ADD=(NAME=AIJ2, FILE=DISK2:[AIJ]AIJ_TWO, -
    _$ BACKUP_FILE=DISK4:[AIJBCK]AIJ2BCK) -
    _$ /ADD=(NAME=AIJ3, FILE=DISK3:[AIJ]AIJ_THREE, -
    _$ BACKUP_FILE=DISK4:[AIJBCK]AIJ3BCK)
    %RMU-W-DOFULLBCK, full database backup should be done to
     ensure future recovery
    $ !
    $ !Assume backup operation was performed and other database
       activity occurs.
    $ !Then back up the .aij files:
    $ !
    $ RMU/BACKUP/AFTER_JOURNAL MF_PERSONNEL.RDB ""
    $ !
    $ DIR DISK4:[AIJBCK]

    Directory DISK4:[AIJBCK]

    AIJ1BCK.AIJ;1

    Example 5

    The following example uses a density value with compression:

    RMU/BACKUP/AFTER_JOURNAL /DENSITY=(TK89,COMPACTION)/REWIND -
    /LABEL=(LABEL1,LABEL2) MF_PERSONNEL TAPE1:MFP.AIJ, TAPE2:
Close Help