MySQL Enterprise Backup 8.4 Release Notes
Table of Contents
- 5.1 Performing a Restore Operation
- 5.1.1 Restoring a Compressed Backup
- 5.1.2 Restoring an Encrypted Backup Image
- 5.1.3 Restoring an Incremental Backup
- 5.1.4 Table-Level Recovery (TLR)
- 5.1.5 Restoring Backups Created with the
--use-ttsOption - 5.1.6 Restoring External InnoDB Tablespaces to Different Locations
- 5.1.7 Advanced: Preparing and Restoring a Directory Backup
- 5.2 Restoring a Backup from Cloud Storage to a MySQL Server
- 5.3 Point-in-Time Recovery
- 5.4 Restoring a Backup with a Database Server Upgrade or Downgrade
The ultimate purpose of backup data is to help recover from a database issue or to create a clone of the original database server in another location (typically, to run report queries or to create a new replica). This section describes the procedures to handle those 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 soon after being recovered.