Loading...

Instant Clone Recovery for MySQL Server

You can duplicate a source server by cloning the snapshots created during backup. This operation, referred as cloning, utilizes the cloning capability of the storage array hardware, which enables you to duplicate large servers within a short period of time. Clones can be used for multiple purposes, such as:

  • As test environments to troubleshoot issues found in the production server.
  • Quick data retrieval without running resource intensive restores on the production environment and without requiring additional space on destination server.
  • Alleviate load from the production servers for running reports and queries.

Currently, clone restore is supported on Linux platform only. A clone can be created from an existing IntelliSnap or a block-level full backup job. During the clone creation, a reservation period is specified by the user. At the end of the period, the system automatically shuts down the clone server and frees up all resources, including snapshot clones on the storage array. The cloning operation can also be scheduled to run periodically to allow the clones to get refreshed from the latest backups on a regular basis.

About This Task

Aside from the restore job, multiple extent recoveries are submitted to the Job Controller as one job called Persistent Recovery job. The default timeout for a persistent recovery job is 24 hours. However, when the restore job completes, the persistent recovery job also ends and the Job Controller displays the job as Completed.

Prerequisites

  • The MySQL server version on the destination client must be the same as the one in the source client.
  • The MySQL user in both the source and destination database servers must have the same user ID.
  • The MySQL Agent and the MediaAgent must be installed on the destination client.
  • On the destination client where you plan to create the clone database, create a directory to be used as the mount path for the database clone files. This directory must be writable by the MySQL user.
  • The clone working directory should have minimum space for the cloned server.

Procedure

Use the following steps to create a clone environment from existing snapshots:

  1. From the CommCell Browser navigate to the Client Computers | client | MySQL | instance.
  2. Right-click a subclient, and then click Clone.
  3. From the Clone Options dialog box, click View Content.
  4. From the browse window, click Clone.

    Note: By default, the entire server is selected. You cannot select individual databases here.

    The MySQL Clone Options dialog box is displayed.

  5. Under the Clone Options tab, from the Destination Client list, select a client where you want to clone the server.
  6. From the Instance Name list, you can either select an instance or <Custom> from the list.
    • Select an instance to use its Binary Directory and Unix UserName for the new clone server that you are creating.
    • Select <Custom> to type the location for Binary Directory and Unix UserName for the new clone server that you are creating.
  7. Type or select a port number that the selected instance will use for communication purpose. Verify that the selected port number is not in use.
  8. Type or browse a location for the Clone working directory. The selected instance will be cloned at this location.
  9. Specify the Reservation Period for which you would like to retain the test environment.

    By default, the clone environment will be retained for 24 hours. Once the specified reservation period expires, the clone server is dismounted and the mount point is deleted.

  10. Optional: Select the Overwrite if clone exists check box if you want to overwrite an existing clone instance that uses the same port number as the new clone that you want to create.
  11. From the Restore Time box, select a date and a time. From the Time Zone list, select the time zone of the destination client that you have selected.
  12. Click OK.

Notes:

  • If Commvault services are restarted on the client computer, the clone server becomes unavailable, even if the reservation period of the clone server is not over.
  • The file permissions for the clone working directory must be set to 777.
  • Do not use root directory as a clone working directory.

List of Supported Kernel Versions

If your kernel version is not listed in the following table, you can opt for on-demand kernel version support. Please contact Commvault Support to get on-demand kernel version support.

Kernel Version

Operating System

3.16.0-4-amd64

Linux

3.10.0-229.el7.x86_64

Linux

3.10.0-123.el7.x86_64

Linux

3.8.13-16.2.1.el6uek.x86_64

Linux

3.2.0-4-amd64

Linux

2.6.39-400.209.1.el5uek

Linux

2.6.39-400.17.1.el6uek.x86_64

Linux

2.6.39-300.26.1.el5uek

Linux

2.6.32-431.el6.x86_64

Linux

2.6.32-358.el6.x86_64

Linux

2.6.32-71.el6.x86_64

Linux

2.6.32-5-amd64

Linux

2.6.26-2-amd64

Linux

2.6.26-1-amd64

Linux

2.6.18-371.el5xen

Linux

2.6.18-371.el5

Linux

2.6.18-348.el5xen

Linux

2.6.18-348.el5

Linux

2.6.18-194.17.1.el5_lustre.1.8.5

Linux

2.6.18-164.el5xen

Linux

2.6.18-164.el5

Linux

2.6.18-128.el5xen

Linux

2.6.18-128.el5

Linux

2.6.18-92.el5xen

Linux

2.6.18-92.el5

Linux

2.6.18-53.el5xen

Linux

2.6.18-53.el5

Linux

2.6.9-55.ELlargesmp

Linux

2.6.9-55.ELsmp

Linux

2.6.9-55.EL

Linux

Last modified: 8/30/2018 6:02:40 AM