V11 SP8

Configuration for Oracle Database Application Migration to an Amazon EC2 Instance

Amazon Configuration

You must have an Amazon EC2 account that contains an Amazon Machine Instance (AMI).

The following options are available for EC2 instance creation:

  • After you create an Amazon Machine instance, you can create an EC2 instance.
  • When you perform the migration, configure the Commvault software to create the instance.

For instructions on creating the following in Amazon Web Services, see Amazon Elastic Compute Cloud Documentation.

  1. Create an Amazon account.
  2. Obtain a user access key by using AWS Identity and Access Management (IAM). For more information, see Managing Access Keys for IAM Users. You use the IAM user access keys to control access to specific AWS services and resources for an AWS account.
  3. Create an Amazon Security Group with the appropriate rules. For information, see Amazon Security Groups for Linux Instances.
  4. Create a Amazon Machine Instance for Red Hat Enterprise Linux. For information, see Creating an Instance Store-Backed Linux AMI.

    You can use an AMI available from Amazon, or create your own custom AMI. If you create a custom AMI, you must verify that it is valid before you use the Commvault software.

    This is the AMI that hosts the EC2 instance.

  5. If you do not have an Amazon key pair, you must create one. For more information, see Amazon EC2 Key Pairs.
  6. Configure the permissions to access AWS resources. When you use the access key and secret key for an IAM user, you must have appropriate permissions, which can be any of the following:
    • Amazon EC2 Full Access
    • Administrator Access
    • Custom permissions to access AWS resources

    For more information, see:

Record all of the Amazon information, for example, the user and the key pair, before you start the Commvault configuration.

Commvault Configuration

Oracle database application migration uses the File System Agent to move the Oracle application.  You must have a storage policy configured for the default file system subclient (Subclient Properties dialog box, Storage Device tab, Storage Policy) and the Oracle default subclient (Subclient Properties dialog box, Storage Device tab, Data Storage Policy). If both are administered, the software uses the file system subclient storage policy.

  1. Install the workflow engine.
  2. If you have not done so, install the Oracle Agent.

    For more information, see Getting Started with Oracle.

    Note: The instance that you want to migrate must be configured to automatically include the control file in the backup (Instance Properties dialog box, Details tab, Control File Autobackup set to On).

  3. Install the File System Agent.

    For more information, see Deployment - UNIX/Linux File System Agent.

  4. Make sure that the file system data set is accessible.
  5. Configure a storage policy, and then assign the storage policy to the file system default subclient for the default backup set.

    For more information, see Configuration - Linux File System.

  6. If the CommServe does not have a public IP address, specify the public IP address for Oracle Database Application Migration.
  7. Enable client data collection for Oracle database application migration.
  8. Configure an Amazon virtual client.

    You can install the Virtual Server Agent on the MediaAgent host.

    For more information, see Creating an Amazon Client.

    Note: When you create the client, the Commvault software creates a client group that has the same name as the virtual client.

  9. Create a VM lifecycle policy for Amazon.

    For more information, see Creating a VM Lifecycle Policy for Amazon.

  10. Configure the firewall settings for application migration. For more information, see Application Migration Firewall Overview.