Page created: 4 Feb 2020 |
Page updated: 22 Jul 2020
Part of any disaster recovery involves the restoration of the user database from one server to another. You should have a well-defined backup plan that takes into account whether or not your data is replicated among a set of servers. The plan is the best insurance against significant downtime or data loss in the event of unrecoverable database issue.
Note: The server root directory should never be restored from a file system backup or snapshot. External backup methods (for example, VM snapshots) are not recommended, especially if data was corrupted during a transaction.
Keep in mind the following general points about database recovery:
- Regular Backup from Local Replicated Directory Server . Take a backup from a local replicated directory server and restore to the failed server. This will be more recent than any other backup you have.
- Restore the Most Recent Backup. Restore the most recent backup from a local server. In some cases, this may be preferred over taking a new backup if that would adversely impact performance of the server being backed up although it will take longer for replication to play back changes.
- Contact Support. If all else fails, contact your authorized support provider and they can work with you (and possibly in cooperation with the Oracle Berkeley DB JE engineers) to try a low-level recovery, including tools that attempt to salvage whatever data they can obtain from the database.