There are two RMU Server Backup_Journal commands, as follows:
o The RMU Server Backup_Journal Suspend command suspends .aij
backup operations
o The RMU Server Backup_Journal Resume command allows .aij
backup operations to resume after they have been suspended.
1 – Resume
Allows you to reinstate the ability to perform AIJ backup
operations after they have been manually suspended with the RMU
Server Backup_Journal Suspend command.
1.1 – Description
When you issue the RMU Server Backup_Journal Suspend command,
after-image journal (AIJ) backup operations are temporarily
suspended. Use the RMU Server Backup_Journal Resume command to
reinstate the ability to backup .aij files.
The RMU Server Backup_Journal Resume command must be issued from
the same node from which AIJ backup operations were originally
suspended. If you attempt to resume AIJ backup operations from
another database node, the following errors are returned:
%RDMS-F-CANTRESUMEABS, error resuming AIJ backup operations
-RDMS-F-ABSNSUSPENDED, AIJ backup operations not suspended
%RMU-F-FATALRDB, Fatal error while accessing Oracle Rdb.
1.2 – Format
(B)0[mRMU/Server Backup_Journal Resume root-file-spec
[4mCommand[m [4mQualifiers[m x [4mDefaults[m
x
/[No]Log x Current DCL verify value
1.3 – Parameters
1.3.1 – root-file-spec
Specifies the database root file for which you want to resume AIJ
backup operations.
1.4 – Command Qualifiers
1.4.1 – Log
Log
Nolog
Specifies whether the processing of the command is reported to
SYS$OUTPUT. Specify the Log qualifier to request log output and
the Nolog qualifier to prevent it. If you specify neither, the
default is the current setting of the DCL verify switch. (The DCL
SET VERIFY command controls the DCL verify switch.)
1.5 – Usage Notes
o To use the RMU Server Backup_Journal Resume command for a
database, you must have RMU$OPEN privilege in the root file
access control list (ACL) for the database or the OpenVMS
WORLD privilege.
o To determine whether AIJ backup operations have been
suspended, use the RMU Show Users command.
1.6 – Examples
Example 1
The following example demonstrates how to reinstate the ability
to perform backup operations.
$ RMU/SERVER BACKUP_JOURNAL RESUME MF_PERSONNEL.RDB
2 – Suspend
Allows you to temporarily suspend .aij backup operations on all
database nodes. While suspended, you cannot back up .aij files
manually (with the RMU Backup After_Journal command) nor will the
AIJ backup server (ABS) perform .aij backup operations.
2.1 – Description
When you issue the RMU Server Backup_Journal Suspend command,
after-image journal (AIJ) backup operations are temporarily
suspended. However, the suspended state is not stored in the
database root file. Thus, if the node from which the AIJ backup
operations were suspended fails, then AIJ backup operations by
the AIJ Backup Server (ABS) are automatically resumed (assuming
the ABS was running prior to the suspension).
The purpose of RMU Server Backup_Journal Suspend command is to
temporarily suspend AIJ backup operations during a period of
time when backing up .aij files would prevent subsequent commands
from operating properly. For example, if you have a Hot Standby
database, the time from when the master database is backed up
to the time that database replication could commence might be
long. During this period, .aij backup operations would prevent
the replication from starting. (See the Oracle Rdb7 and Oracle
CODASYL DBMS: Guide to Hot Standby Databases for information on
Hot Standby databases.)
The solution to this problem is to use the RMU Server Backup_
Journal Suspend command to suspend AIJ backups from the time
just prior to beginning the database backup until after database
replication commences.
AIJ backup operations are suspended until any of the following
events occur:
o The database is closed on the node from which AIJ backup
operations were suspended.
o The node fails from which AIJ backup operations were
suspended.
o Database replication is started on the node from which AIJ
backup operations were suspended, as a master database.
o AIJ backup operations are explicitly resumed on the node from
which AIJ backup operations were suspended. (This occurs when
you issue the RMU Server Backup_Journal Resume command. See
the Server_Backup_Journal help entry for details.)
2.2 – Format
(B)0[mRMU/Server Backup_Journal Suspend root-file-spec
[4mCommand[m [4mQualifiers[m x [4mDefault[m
x
/[No]Log x Current DCL verify value
2.3 – Parameters
2.3.1 – root-file-spec
Specifies the database root file for which you want to suspend
AIJ backup operations.
2.4 – Command Qualifiers
2.4.1 – Log
Log
Nolog
Specifies whether the processing of the command is reported to
SYS$OUTPUT. Specify the Log qualifier to request log output and
the Nolog qualifier to prevent it. If you specify neither, the
default is the current setting of the DCL verify switch. (The DCL
SET VERIFY command controls the DCL verify switch.)
2.5 – Usage Notes
o To use the RMU Server Backup_Journal Suspend command for a
database, you must have RMU$OPEN privilege in the root file
access control list (ACL) for the database or the OpenVMS
WORLD privilege.
o To determine whether AIJ backup operations have been
suspended, use the RMU Show Users command.
2.6 – Examples
Example 1
The following example first suspends .aij backup operations, then
issues the RMU Show Users command to confirm that suspension has
occurred. If you attempt an .aij backup operation, you receive
the %RMU-F-LCKCNFLCT error message.
$ RMU/SERVER BACKUP_JOURNAL SUSPEND MF_PERSONNEL.RDB
$ RMU/SHOW USERS MF_PERSONNEL.RDB
. . .
* After-image backup operations temporarily suspended
from this node
. . .
$ RMU/BACKUP/AFTER_JOURNAL MF_PERSONNEL.RDB AIJ_BACKUP.AIJ
%RMU-F-LCKCNFLCT, lock conflict on AIJ backup