> Software > Manage > Infrastructure > MediaAgents > Deploy a MediaAgent

Deploying a MediaAgent on Amazon EC2

Deploy a MediaAgent on Amazon EC2 before you configure Amazon EC2 protection if you use your own infrastructure. Use vendor native deployment when possible.

Requirements

  • Verify that you have the permissions required to deploy the MediaAgent in the target AWS account.

  • Verify that the MediaAgent can communicate with the CommServe.

  • For vendor native deployment, configure one of the following supported authentication methods:

  • AWS STS AssumeRole

  • IAM Role

  • Access keys for IAM users

  • For manual deployment, have an installation authcode available.

Add MediaAgent

  1. From the Command Center navigation pane, go to Manage > Infrastructure.

  2. Click the MediaAgent tile.

  3. In the upper-right area of the page, click Add MediaAgent.

  4. From the Vendor list, select Amazon Web Services.

  5. Use one of the following deployment methods.

    Vendor native deployment — recommended

    1. From the Deployment type list, select Vendor native deployment.

    2. From the Authentication list, select one of the following:

      • AWS STS AssumeRole (recommended): Before launching the CloudFormation stack, verify that CommvaultAdminRole exists in your AWS account.

      • IAM Role: Before launching the CloudFormation stack, verify that CommvaultRole exists in your AWS account.

      • Access keys for IAM users: Before launching the CloudFormation stack, verify that CommvaultUserGroup exists in your AWS account.

    3. From the Platform list, select the operating system.

    4. From the Region list, select the region where you want to deploy the MediaAgent.

    5. Click Launch The CloudFormation Stack to open the AWS console.

      Note

      If AWS EBS encryption is enabled in the selected region, you must be a key user for the default encryption key to use the stack. If you are not a key user, copy the Launch The CloudFormation Stack link and share it with a key user, such as your security administrator.

    6. Sign in to the AWS console.

    7. Under Parameters, specify the following information:

      1. For EC2 Instance Type, select the EC2 instance type to use for the MediaAgent.

      2. For EC2 Key Pair, select the key pair used to access the Commvault MediaAgent.

      3. For VPC ID, select an Amazon Virtual Private Cloud (VPC).

      4. For Subnet ID, select a subnet.

      5. For VPC CIDR, select a VPC CIDR.

    8. Click Create stack.

    Kubernetes

    Kubernetes deployment is separate from the deployment types available in the Add MediaAgent dialog box.

    To deploy a MediaAgent in a Kubernetes environment, see Installing Commvault Packages in Kubernetes Using Helm.

    Auto Provision

    1. From the Deployment type list, select Auto Provision.

    2. In the Name field, enter a unique name for the MediaAgent.

    3. From the Scale profile list, select a scale profile.

    A scale profile is a predefined configuration that specifies how MediaAgents are automatically provisioned and managed. It includes settings such as the cloud environment, networking, security, and scaling behavior that Commvault uses when deploying MediaAgents.

    Note

    Before you use Auto Provision, create a scale profile. For more information, see Scaling configurations for dynamic management of AWS, Azure, and Google Cloud access nodes.

    1. From the Region list, select the AWS region where you want to deploy the MediaAgent.

    2. From the Platform list, select the operating system.

    3. From the Size list, select the instance size to use when provisioning the MediaAgent.

    4. Size options determine the CPU and memory allocated to the MediaAgent.

    5. Use the displayed values to verify that the instance meets your compute and storage requirements.

    6. From the Server group list, select the server group where the new MediaAgent will be added.

    Server groups are logical collections of MediaAgents and other servers that help you organize infrastructure and control where workloads are processed.

    1. Click Submit.
    Manual deployment — least preferred

    Use manual deployment only when your organization does not permit vendor native deployment.

    For requirements, see MediaAgent: System Requirements.

    1. From the Deployment type list, select Manual deployment.

    2. From the Platform list, select the operating system.

    3. Click Download package to download the MediaAgent installation package.

    4. Copy the installation Auth code. You will enter this code during installation.

    Windows

    1. Copy the installation package to the Windows computer where you want to install the MediaAgent.

    2. Run the installation executable as an administrator.

    3. Follow the installation wizard:

    4. Select the installation language.

    5. Verify that MediaAgent is selected as the component to install.

    6. Specify the installation directory, if required.

    7. Configure the firewall settings, if prompted.

    8. Enter the CommServe host name, if prompted.

    9. Enter the installation Auth code.

    10. Complete the installation.

    11. In Command Center, verify that the MediaAgent appears on the MediaAgents page.

    Linux

    1. Transfer the installation package to the Linux computer where you want to install the MediaAgent.

    2. Extract the installation package, if necessary.

    3. Run the installation script, such as ./cvpkgadd, as the root user or by using sudo.

    4. Follow the installation prompts:

    5. Confirm that you want to install the MediaAgent package.

    6. Specify the installation directory, if required.

    7. Configure the firewall settings, if prompted.

    8. Enter the CommServe host name, if prompted.

    9. Enter the installation Auth code.

    10. Complete the installation.

    11. In Command Center, verify that the MediaAgent appears on the MediaAgents page.

×

Loading...