In the event of a catastrophic failure, you may find that you need to restore a source database from backup. Before you can restore a database that is enabled for OpenEdge Replication, you must first disable replication.
Note: Restore a database only when you are sure you must do so. Restoring should be used as a last resort, since you will lose the data for any activity performed after you backed up the database.
To restore a Replication-enabled source database:
1. Disable OpenEdge Replication on the source database.
Be sure you delete the db-name.repl.recovery file any time you restore.You can find the .recovery file in the source database directory.
If the database you are restoring was previously enabled for OpenEdge Replication, the database is again enabled for OpenEdge Replication after the restore. You cannot restart OpenEdge Replication for this database until OpenEdge Replication is disabled and then re-enabled. The target database must be resourced after the restore, disable, and enable have been performed.
You can restore a database enabled as a target database once you disable OpenEdge Replication. This is not a recommended practice, however, because the target database should always be created from a source database, not from a backup of itself.
If something happens to your target database and you need a new copy of it, take the latest backup of your source database. This guarantees that the databases can be synchronized. The latest backup of your source database can be from a full online backup or a full offline backup. It cannot be an incremental backup. Be sure to delete the recovery file before restarting OpenEdge Replication.
Once a database is enabled for OpenEdge Replication, information about the state of OpenEdge Replication is kept in the database itself. This information is not restored when the database is restored. The only way to recover this information is to re-enable the database for OpenEdge Replication.
