Kbase P182178: How to OS backup Replication Source to make changes to source that may need to be undone without tra
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/05/2011 |
|
Status: Unverified
GOAL:
How to OS backup Replication Source to make changes to source that may need to be undone without transmitting changes to target?
GOAL:
How to OS copy Replication Source to make changes to source that may need to be undone without transmitting changes to target?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
OpenEdge Replication
FIX:
In a situation where a change is to be made to a Replication source database and there is concern that the change may not be successful for whatever reason use the following steps:
1) Shutdown target database.
2) Shutdown the source database.
3) Use an operating system copy or backup program to backup the entire database (all files, .db, .d<n>, .b<n>, .a<n>, etc.) and the associated <sourcedb>.repl.recovery file to some backup location. Do not modify or use these backup files unless it is necessary to undo all future changes to the source.
4) At this point the source database can be served or used in single user mode but be aware changes will be written to the AI files. If the AI files become full then the database will shutdown (unless -aistall is used in which case the database will stall) because with replication active but the target database(s) offline no AI files can be emptied. All full AI files will stay in a locked state.
5) If changes made to the source database files need to be completely undone without ever applying the changes to the target database(s) just restore all the operating system copies or backup files of the source and <source>.repl.recovery files, made in step 3, overwriting the modified source database files.