Release 10.1C: OpenEdge Replication:
User Guide
Setting transition properties
Once you make the decisions outlined in the "Planning for transition" section, you must set the transition properties that support those decisions, as listed in Table 4–1. (See Table 4–3 for a complete list of all transition properties.)
Table 4–1: Setting transition properties To implement this transition planning decision . . . Do this . . . Which is the primary and which is the secondary database? Modify theresponsibility
property (currently used for informational purposes only) to identify the type of database. Possible values are: What type of transition will occur? Modify thedatabase-role
property to identify the new role of the database once it is transitioned. Possible values are:
- Reverse — The role of the database is reversed: A source database becomes a target database, and a target database becomes a source database.
- Normal — The role of the database becomes that of a normal database; the database is no longer enabled for replication once the transition is performed. This is the default value.
What type of after-imaging operations should transition perform? Modify the after-imaging propertiesauto-begin-ai
,auto-add-ai-areas
, andai-structure-file
to set AI behavior.Specify either of these values for theauto-begin-ai
property:Specify either of these values for theauto-add-ai-areas
property:
- 0 — Do not add AI areas to the database automatically (when a database is transitioned to a source database or there are currently no AI areas for the database).
- 1 — Add AI areas to the database automatically by using the structure file specified in the
ai-structure-file
property (when a database is transitioned to a source database or there are currently no AI areas for the database).Specify the name of the structure file (which contains the list of AI areas to add) in theai-structure-file
property. What types of backup do you want to perform during transition? Modify the backup propertiesbackup-method
,backup-arguments
, andincremental-backup-arguments
to set the type of backup you want to perform during transition and before AI is enabled.Specify one of these values for thebackup-method
property:rfutil
db-name
-C mark backedup
Marking the database as backed up does not allow future AI extents to be used when recovering from a disaster.The backup is performed in two steps. The first backup is a full backup, which is performed before AI is enabled for the database. The second backup is an incremental backup, which is performed after AI is enabled and after the role of the database is changed.Specify thebackup-arguments
property for the arguments required for the full online and offline backups performed for the database. Keep the following in mind:
- You must specify, at a minimum, the target file or device in these arguments for both online and offline backups.
- To avoid overwriting a backup, do not use the same target file or device for both the backup and the incremental backup.
- Do not use backup validation parameters (such as
-vp
and-vf
).- Begin the arguments with
device-name
.Specify theincremental-backup-arguments
property for the arguments required for the offline incremental backup performed after AI is enabled and the database’s role is reversed. Begin the arguments withdevice-name
. Do you want the database to restart automatically after transition? Modify the following automatic transition properties to specify whether the database should be automatically restarted after transition:Specify either of these values for therestart-after-transition
property:Specify the*-startup-arguments
property or properties:
- If the database is transitioned to a normal database, specify the
normal-startup-arguments
property. These arguments are used when the database is started. The arguments will be appended to the PROSERVE command. In most cases, the only argument specified here should be-pf
followed by a parameter file name, as shown here:-pf
db-name
.normal.pf
- If the database is transitioned to a source database, you must specify the
source-startup-arguments
property. The arguments are appended to the PROSERVE command and are used when the database is started. In most cases, the only argument specified should be-pf
followed by a parameter file name, as shown here:-pf
db-name
.source.pf
Do you want the database to restart automatically after transition?(continued) Because the database is a source, you must also specify the following argument as an indication to the broker to start the Replication server:-DBService replserv
- If the database is transitioned to a target database, you must specify the
target-startup-arguments
property.The arguments are appended to the PROSERVE command and are used when the database is started. In most cases, the only argument specified here should be-pf
followed by a parameter file name, as shown here:-pf
db-name
.target.pf
Because the database is a target, you must also specify the following arguments as an indication to the broker to start the Replication agent and listen on the TCP/IP port as specified:-DBService replagent -S
port-number
or
service-name
For additional details about thesource-
,target-
, ornormal-startup-arguments
, see the "Sample startup parameter file" section. Will transition automatically attempt to recover in the event of a failure? Modify therecovery-backup-arguments
property, which determines whether transition automatically attempts a recovery.Specify the device name, followed by any other backup arguments.
Copyright © 2008 Progress Software Corporation www.progress.com |
![]() |