You can perform the partial restore of MySQL instance from a default subclient to either the same instance or a different instance on the source client. You can also restore the instance to a different destination server.
Before partial restore of the MySQL instance, the MySQL server must be online. The data part of the backup is then restored to the staging space and recovered to data directory. The log restore and recovery take place at the destination instance.
Note
-
To perform partial restore of MySQL instance, the free space at the Staging location must be double the size of the source MySQL instance.
-
For restore without recovery, the staging location and the destination folder must have free space equal to the size of source MySQL instance.
-
During a MySQL Enterprise Backup (MEB) partial restore, the data is first recovered to a staging location. An auxiliary server is then started by using the recovered data to restore the database to the destination MySQL server. The auxiliary server startup can fail if there is a configuration mismatch between the source MySQL server and the auxiliary or destination MySQL server.
To start an auxiliary server with MySQL server parameters that differ from the source MySQL server, create a custom configuration file with the following content:
[mysqld]
<mysql server parameter1> = <value1>
<mysql server parameter2> = <value2>
Specify the path to the custom configuration file using the sAuxServerConfigFilePath parameter. For instructions about adding an additional setting, see Adding an Additional Setting from the CommCell Console.
Note
The custom configuration file must not be world-writable.