To implement this transition planning decision . . .
|
Do this . . .
|
Which is the primary and which is the secondary database?
|
Modify the responsibility property (currently used for informational purposes only) to identify the type of database. Possible values are:
![]() ![]() |
What type of transition will occur?
|
Modify the database-role property to identify the new role of the database once it is transitioned. Possible values are:
![]() ![]() |
What type of after-imaging operations should transition perform?
|
Modify the after-imaging properties auto-begin-ai, auto-add-ai-areas, and ai-structure-file to set AI behavior.
Specify either of these values for the auto-begin-ai property:
![]() ![]()
Specify either of these values for the auto-add-ai-areas property:
![]() ![]()
Specify the name of the structure file (which contains the list of AI areas to add) in the ai-structure-file property.
|
What types of backup do you want to perform during transition?
|
Modify the backup properties backup-method, backup-arguments, and incremental-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 the backup-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 the backup-arguments property for the arguments required for the full online and offline backups performed for the database. Keep the following in mind:
![]() ![]() ![]() ![]()
Specify the incremental-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 with device-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 the restart-after-transition property:
![]() ![]()
Specify either of these values for the start-secondary-broker property:
![]() ![]()
Specify the *-startup-arguments property or properties:
![]()
-pf db-name.normal.pf
![]()
-pf db-name.source.pf
Because the database is a source, you must also specify the following argument, which is case-sensitive, as an indication to the broker to start the Replication server:
-DBService replserv
![]()
-pf db-name.target.pf
Because the database is a target, you must also specify the following arguments (note that -DBService is case-sensitive)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 service-name
![]()
For additional details about the source-, target-, or normal-startup-arguments, see Sample of a startup parameter file used by transition.
|
Will transition automatically attempt to recover in the event of a failure?
|
Modify the recovery-backup-arguments property, which determines whether transition automatically attempts a recovery.
Specify the device name, followed by any other backup arguments.
|