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. Verify that you have performed all the configuration procedures that are specified in Configuration for SQL Database Application Migration to an Amazon EC2 Instance.

  2. Perform a full backup that includes the logs.

  3. Have the backup administrator configure the system for Database Application Migration to an Amazon EC2 instance.

  4. Make sure that you have the following information:

    • The Amazon account information.

    • The Amazon machine instance name.

    • The VM lifecycle policy.

Procedure

  1. From the navigation page, click Administration > Servers > SQL server >SQL server. Then, in the Actions column for the instance, click the action button action_button, and then click Migrate to cloud.

    The Server configuration page appears.

  2. Specify the cloud destination information.

    1. From the Cloud type list, select Amazon.

    2. From the Provisioning Policy list, select the lifecycle policy.

    3. From the Compute node list, select or type the instance.

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

  3. Click Next.

    The Content Selection page appears.

  4. Select the content that you want to migrate. In the box, select the check box for each database that you want to migrate.

  5. Optional: Redirect the databases. Click Redirect.

    The Restore Options dialog box appears.

    1. In the Physical File name box, type the new path or browse to the new path, and then click OK.
  6. Click Next.

    The Cloud compute configuration page appears.

  7. Specify the AMI information.

    If you chose to use an existing EC2 instance, and do not want to modify the instance storage, then in the User name and Password boxes, type the credentials for the AMI instance.

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

    • From the Image list, select the Amazon Machine Image that will host the instance.

    • From the Shape list, select the type of Amazon instance to create.

      For information on Amazon EC2 instance types, go to the Amazon EC2 documentation website, Instance Types.

    • In the User name and Password boxes, type the credentials for the AMI instance.

  8. Optional: add storage. Click Add storage.

    The Add storage dialog box appears.

    1. In the Mount points box, type a unique name for the mount point.

    2. From the Size(GB) box, type the mount point size.

    3. From the Volume type list, select the volume type.

    4. In the IOPS limit box, type the input and output limit.

    5. In the Description box ,type the name or phrase to describe the mount point.

    6. Click OK.

  9. Optional: modify the mount points. In the row for the mount point, click the edit edit button.

    The Edit storage dialog box appears.

    1. In the Mount points box, type a unique name for the mount point.

    2. From the Size(GB) box, type the mount point size.

    3. From the Volume type list, select the volume type.

    4. In the IOPS limit box, type the input and output limit.

    5. In the Description box ,type the name or phrase to describe the mount point.

    6. Click OK.

  10. Click Next.

    The Software Configuration page appears.

  11. On the , specify the Oracle application location.

    • To clone the Oracle Home directory from the source machine, select Clone from source.

      Note

      This option is not available when the migration source database is on an AIX or Solaris configuration.

    • To use the Oracle Home directory that exists on the destination, select Use installed on the target.

      Note

      You can select this option when you created the compute node that has Oracle preinstalled, and you know the Oracle Home directory.

    • Optional: Specify a new install directory. In the Install directory on cloud box, type the full path to the Oracle Home directory.

      Use this option when you want to use a different Oracle Home path from the source, or when you want to specify the pre-installed AMI Oracle Home path.

  12. Click Next.

    The Firewall configuration page appears.

  13. Specify the firewall options.

    • Select the There is a firewall between client machine and CommServe check box.

    • If you use have a proxy server, then select the following options:

      • Select CommServe is reachable only through proxy.

      • In the Local HTTP/HTTPS tunnel box, type the port that you configured for the firewall, for example, 443.

      • From the Proxy Client Name list, select the proxy server.

    • If you have a one-way firewall topology, then select Client machines can open connection to CommServe on tunnel port.

  14. Click Next.

    The Migration Options page appears.

  15. Specify the migration options.

    1. In the Migration area, select whether this operation is a one-time operation, or continuous.

      • To have this be a one-time operation, select One time.

      • To have this a continuous operation that uses the Live Sync feature, select Continuous (Live Sync).

    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 for the Live Sync operation, select Run a new full backup.

    3. In the Recovery types and undo path section, select the recovery type.

      Note

      If you select the Stand by option, then in the Undo file path, type the full path to the undo file.

    4. To migrate from a copy precedence, select the Copy precedence check box, and then in the box, type the copy precedence number.

    5. In the Destination instance name box, type the AMI instance name.

  16. Click Submit.

Result

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

Loading...