After you enable the cluster backup, you can perform the restore operation from the default subclient-level of the primary Commvault instance. You can run both in-place and out-of-place restores.
Restores for a Single Cluster Node
-
If you want to recover a MySQL server on a single node, run a data-only restore operation without selecting the Log check box in the MySql Restore dialog box.
-
After the MySQL server is started, run the
start group_replicationcommand to sync with the primary server.
Restores for a Complete Cluster
-
If you want to recover the complete cluster, run a data-only restore operation on all the nodes without selecting the Log check box in the MySql Restore dialog box.
-
Bootstrap the MySQL server that you want to make as the primary server and add secondary servers to the MySQL group replication.
-
After the MySQL group replication is in sync, run a log-only restore operation on the primary server by entering a point-in-time value and without selecting the Data check box in the MySql Restore dialog box.
Note
-
If you want to perform log backups and point-in-time restores, add the bEnableMEBLogBackup additional setting on the CommServe server.
-
You cannot run a point-in-time restore for a combination of incremental backups with or without selecting the Log check box in a backup cycle.
-
If a failover occurs, the backup chain is broken. To perform a point-in-time restore, use the next backup cycle.
-
For example, suppose there are two backup cycles - Full Inc1 Inc2 Inc3..., Full Inc1 Inc2...
If a failover occurs after Inc3 of the first cycle, the next backup automatically becomes a Full backup, starting the second cycle. You can perform a Point-in-Time restore at any point within the incremental backups of the first cycle. To perform a Point-in-Time restore between Inc3 of the first cycle and the Full backup of the second cycle, you must restore from the second cycle.
-
-
By default, the
service mysqldstart command is used to start the MySQL server after restoring data. If the MySQL service name is different, on the client, set the sServerStartCmd additional setting to the start command value.