Deploy a MediaAgent on Azure

You can deploy a MediaAgent on Azure by using several deployment methods. Use vendor native deployment when possible.

Requirements

  • Verify that you have the Contributor role for the Azure subscription where you deploy the MediaAgent. For more information, see Azure role requirements.

  • Verify that the MediaAgent can communicate with the CommServe. If the CommServe is behind a firewall, open the required ports or deploy a Network Gateway.

  • For vendor native or manual deployment, have the appropriate registration information available:

  • Commvault software: CommServe host name, CommServe name, and installation authcode

  • Commvault Cloud: Commvault Gateway URL and installation authcode

Deploy the MediaAgent

Start the MediaAgent deployment in Command Center, and then use the deployment method that meets your requirements.

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

  2. Click the MediaAgents tile.

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

  4. From the Vendor list, select Microsoft Azure.

  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 Platform list, select the operating system.

    3. In the Custom Template area, click DEPLOY CUSTOM TEMPLATE, or click Copy link and paste the URL into a browser.

    4. In the Azure portal, review the deployment information.

    5. On the Basics tab, specify the resource group, region, virtual machine name, and other required deployment settings.

    6. On the Commvault Configuration tab, enter the registration information displayed for your environment:

      • Auth code: The installation authorization code used to authenticate and register the MediaAgent with the CommServe.

      • CommServe hostname: The network address used to reach the CommServe.

      • CommServe name: The name assigned to the CommServe.

      • Commvault Gateway URL: The URL of the Commvault Gateway.

      • CS firewall port: The firewall port used by the MediaAgent to communicate with the CommServe.

    7. Review the deployment settings, and then deploy the Azure Resource Manager (ARM) template.

    8. Wait for the deployment to complete.

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

    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.

      An installation authcode is not required for Auto Provision.

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

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

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

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

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

    7. 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.

    8. 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.

    Windows

    1. From the Platform list, select Windows.

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

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

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

    5. Run the installation executable as an administrator.

    6. Follow the installation wizard:

      • Select the installation language.

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

      • Specify the installation directory, if required.

      • Configure the firewall settings, if prompted.

      • Enter the CommServe host name, if prompted.

      • Enter the installation Auth code.

    7. Complete the installation.

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

    Linux

    1. From the Platform list, select Linux.

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

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

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

    5. Extract the installation package, if necessary.

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

    7. Follow the installation prompts:

      • Confirm that you want to install the MediaAgent package.

      • Specify the installation directory, if required.

      • Configure the firewall settings, if prompted.

      • Enter the CommServe host name, if prompted.

      • Enter the installation Auth code.

    8. Complete the installation.

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

×

Loading...