Performing SQL Database Application Migration to an Amazon EC2 Instance

When you migrate the application, you specify both the AMI and the Amazon EC2 instance.

You can use an existing EC2 instance, or you can specify a new EC2 instance name and the Commvault software creates the instance in the Amazon cloud.

If you need additional storage for the data, you can add a new storage device for the new or existing instance.

Before You Begin


  1. From the CommCell Browser, expand Client Computers > client > SQL.
  2. Right-click the instance, point to All Tasks, and then click Migrate to cloud.

    The Migrate to cloud wizard appears.

  3. On the Application Information page, specify the cloud destination information.
    1. From the Cloud Type list, select Amazon.
    2. From the Policy Name list, select the VM lifecycle policy that you created.
    3. In the Compute Node box, type the instance name.

      If you enter a new instance name, the Commvault software creates a new VM in the Amazon cloud.

    4. From the Client Group list, select the client group that the software created for the virtual client.

      This client group name matches the virtual client name.

  4. Click Next.
  5. On the Machine Configuration page, specify the AMI information.

    If you chose to use an existing EC2 instance, and do not want to modify the instance storage, then you do not need to take any action on this page.

    • If you chose to use a new EC2 instance, specify the instance information.

      Note: The software makes the AMI list and the Instance type list unavailable when you use an existing instance.

      • From the AMI list, select the Amazon Machine Image that will host the instance.
      • From the Instance Type list, select the type of Amazon instance to create.

        For information about Amazon EC2 Windows instance types, go to the AWS article, "Instance Types", Amazon Elastic Compute Cloud Documentation.

    • Optional: Add additional storage volumes.
      1. Click Add.

        The Add Storage Device dialog box appears.

      2. In the Mount Point box, type the full path for the mount point.
      3. In the Size(GB) box, type the volume size in gigabytes.
      4. From the Volume Type list, select the volume type, for example Standard.
      5. In the IOPS limit box, type the number of shares for the VM.
      6. In the Volume Description box, type a description.
      7. Click OK.
  6. Click Next.
  7. On the Firewall Configuration page, specify the firewall options.
    1. Select the There is a firewall between Client machine and CommServe check box.
    2. Select CommServe is reachable only through proxy.
    3. In the Local HTTP/HTTPS tunnel box, type the port that you configured for the firewall, for example, 443.
    4. From the Proxy Client Name list, select the proxy server.
  8. Click Next.
  9. On the Migration Options page, specify the migration options.
    1. In the Migration area, select One time to run migration as a one-time operation.
    2. In the Baseline area, select the backup to use for migration
      • To use the latest full backup, select Use most recent full backup.
      • To run a new backup, select Run a new full backup.
    3. Change the physical path of data and log files by completing the following steps:
      1. Click Advanced.

        The Advanced Restore Options dialog box appears.

      2. On the Redirect tab, change the physical path of data and log files.
      3. Click OK.
    4. To have the destination database come up in standby mode, select Stand by.
    5. In the Post migration area, in the Validation Script box, type the full path and script name for the script that you use to validate the SQL database.
  10. Click Finish.


The production SQL database and application are in the Amazon cloud.

Last modified: 3/30/2021 3:43:58 PM