Table of Contents [+/-]
- 5.1 Preparing the Backup to be Restored
- 5.2 Performing a Restore Operation
- 5.3 Point-in-Time Recovery from a Hot Backup
- 5.4 Setting Up a New Replication Slave
- 5.5 Restoring a Master Database in Replication
- 5.6 Backing Up and Restoring a Single
- 5.7 Restoring a Backup to a Different Database Version
The ultimate purpose of backup data is to help recover from a database issue, or to create a clone of the original database in another location (typically to run report queries or to create a new replication slave). This section describes the procedures to handle those various scenarios.
After a serious database issue, you might need to perform a recovery under severe time pressure. It is critical to confirm in advance:
How long the recovery will take, including any steps to transfer, unpack, and otherwise process the data.
That you have practiced and documented all steps of the recovery process, so that you can do it correctly in one try. If a hardware issue requires restoring the data to a different server, verify all privileges, storage capacity, and so on, on that server ahead of time.
That you have periodically verified the accuracy and completeness of the backup data, so that the system will be up and running properly after being recovered.