Restoring databases that were backed up using XtraBackup utility is similar to a regular MySQL restore operation.
For full instance XtraBackup, the MySQL server is stopped. After the restore operation to the MySQL data directory is complete, the MySQL server is started. You can run a restore only from the subclient or database group level.
For instructions to perform a MySQL restore operation, see Restore - MySQL Agent.
To restore databases from the files generated from XtraBackup restore without selecting the recover option, see Applying the Logs and Database Dumps Manually for XtraBackup Utility.
Notes
-
To restore the innodb storage engine tables that were backed up using XtraBackup utility, ensure that XtraBackup is enabled at the destination server. For steps to enable XtraBackup on a server, see Configuring MySQL Instance to Enable XtraBackup.
-
The staging location must have free space with size equal to the largest database on the server.
-
You can perform a point-in-time restore, which is useful when you recover the changes made to a database object up to a given point in time. You can select and restore the database object to a state that it had previous to that point.
-
To add additional parameters to XtraBackup prepare command during a restore operation, create the additional setting sAdvancedXtraPrepareOptions, and pass the required parameters as its value. For information about creating an additional setting, see Adding or Modifying Additional Settings from the CommCell Console.
-
You must use the same path for the innodb_data_file_path and innodb_data_home_dir parameters in both the source and destination MySQL instances to ensure a successful restore operation.