Kbase P122240: How to transition a database using OpenEdge Replication 10.1x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/09/2008 |
|
Status: Verified
GOAL:
How to transition a database using OpenEdge Replication 10.1x
GOAL:
Generic Steps to Perform Transition with OpenEdge Replication 10.1x
GOAL:
General Steps to perform Failure Recovery with OpenEdge Replication
GOAL:
General Steps to perform Failover with OpenEdge Replication.
GOAL:
How to transition source and target databases?
GOAL:
How to failover from target to source using OpenEdge Replication?
GOAL:
What are the steps to use target replicated database as a source database
GOAL:
How to make a target database as source database
GOAL:
How to Target transition a database
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Replication 10.1A 32-bit
OpenEdge Replication 10.1A 64-bit
OpenEdge Replication 10.1B 32-bit
OpenEdge Replication 10.1B 64-bit
OpenEdge Replication 10.1C 32-bit
OpenEdge Replication 10.1C 64-bit
FIX:
The failover process works as follows:
1. Primary replication is happening, replication server and replication agents are both running
2. Failure occurs and breaks communication between the replication server and replication agent, typically caused by a failure on the primary machine
3. Replication agent on target machine enters pretransition. If the server properties has agent-shutdown-action set as normal, the agent will shut down. When this happens, you will need to manually enter pretransition
dsrutil target -C triggertransition
at this point, try to apply all unapplied AI extents to secondary database (for manual transition only, if auto transition, could lose unapplied AI extents)
dsrutil target -C recovery
dsrutil target -C applyExtent extent_name
4. Transition target to primary
Automatic: if the properties file is configuring this as automatic, auto transition occurs
Manual: dsrutil target -C transition
5. Failover
After step 4 is successful, the secondary database can be restarted automatically if configured to do so. If primary will be down for some time, can terminate replication server on the secondary machine
dsrutil target -C terminate server
6. Secondary replication
After primary machine is available again, enable replication again between the secondary and primary machines
a: on-line backup of target
b. restore back up on primary machine and enable transition
prorest primary backup -REPLTransition
or restore and transition
prorest primary backup
proutil primary -C enableSiteReplication target
c. restart replication server on secondary machine
dsrutil secondary -C restart server
7. Failback
a. Using failover command
dsrutil secondary -C transition failover
failover command causes replication to transition both the primary and secondary databases
b. Controlled transition
* shut down and restart both databases
* verify synchronization
dsrutil source -C status -detail
if 3049 is returned, both databases are synchronized
* shut down the databases again
* dsrutil primary -C transition
this transitions primary into source
* dsrutil secondary -C transition
this transitionsn secondary into target