Kbase P144949: How to move a Replication Target database to a new server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/11/2010 |
|
Status: Verified
GOAL:
How to move a Replication Target database to a new server
GOAL:
Is it possible to move a Replication Target database to a new server?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
The following are steps you can use to move the target database to another system without stopping your Source (production database). Below are the steps necessary to accomplish this task. It is recommended, however, that you test with a sports database that is replication enabled:
*** sourcedb/targetdb = your database name.
****If this operation is going to take a long time, make sure there is enough free ai space/files to handle the ai notes during this operation. Otherwise, the ai files could all be in a locked status and could stop the source db.
1) Proshut the target database. This should stop the rpserver process on the source. Check the source database log file or run:
dsrutil sourcedb -C monitor.
You should get a message about no replication shared memory.
If the rpserver is still running, you can stop it using:
dsrutil sourcedb -C terminate server.
2) Move/copy the target database files to the new system. This includes the targetdb.repl.recovery and targetdb.repl.properties file...and any other file the targetdb.repl.properties might be calling.
3) Prostrct repair the targetdb if necessary (if in different path).
4) Restart the targetdb. Check log file for any errors on startup.
5) Edit the sourcedb.repl.properties file. Edit the hostname=<hostname> to have the new target server's host name. Save the file
6) Restart the replication server
dsrutil sourcedb -C restart server
The two database should be synchronized. Check both source and target using dsrutil status or monitor.