# Create a scaling configuration for Azure

Creating a scaling profile for Azure includes specifying credentials for the Azure account, a scaling manager node, and the region to scale access nodes in.

Need guidance for configuring Azure auto-scaling?

Before you configure auto-scaling in the Command Center, prepare the following Azure resources in the Azure subscription where auto-scaling nodes will be deployed.

Note

You can also use other approaches to achieve the same result, as long as you ensure proper networking between any VNets involved.

- Create an auto-scale resource group where VMs will be created.

- Provision one scale manager node. If you have an existing access node, you can use that as a scale manager node.

  - Identity: System-assigned managed identity

  - Required role assignment:

    - Role: `Commvault - Auto Scale`

    - Scope: Subscription

- Create a public IP prefix resource in each region for which auto-scaling is required.

- Create one storage account in each region for which auto-scaling is required.

- Confirm networking resources in all regions for which auto-scaling is required. Make sure that a VNet and a subnet with relevant routing/NSG rules are in place. Tag each VNet with subnet mapping details.

- If auto-scaling is configured using the Automatically discover resources based on tag setting, make sure that required tags are available on the VNet, auto-scale resource groups, and storage account.

## Start the scaling configuration wizard

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

2. Click the Scale configuration tile.

3. Click Add.

4. Select Microsoft Azure, and then click Next.

## General page

1. In the Name box, enter a name for the Azure scaling configuration.

2. In the Description box, enter a description for the Azure scaling configuration.

3. Click Next.

## Authentication and Access page

1. Specify how you want to give Commvault access to your Azure resources:

   - To authenticate the access node with Azure services, toggle the Use Managed Identity option to the right, and then enter the subscription ID.

   - To use an Azure application and a secret, move the Use Managed Identity toggle key to the left, from the Credentials list, select or create a credential.

     - If you have an existing Azure application, add a credential.

       Steps to add a new credential

       1. Beside Credential, click the add button .

       The Add credential dialog box appears.

       2. From the Account type list, verify that Cloud Account is selected.

       3. From the Vendor type list, verify that Microsoft Azure is selected.

       4. In Credential name, enter a descriptive name for the credentials.

       5. In Tenant ID, enter the tenant ID for the Azure account.

       6. In Application ID, enter application ID for the tenant.

       7. In Application secret, enter the secret key value that is generated for the application.

       Copy the values for Tenant ID, Application ID, and Application secret from Azure Cloud Shell.

       8. From the Environment list, verify that AzureCloud is selected.

       9. To view and modify Azure endpoint URLs that Commvault will use to connect to Azure during VM onboarding, enable the Show endpoints toggle key. If your environment requires custom endpoints (for example, Azure Government or other sovereign cloud environments), you can modify the following endpoints:

       - Authentication endpoint: Used to verify identity and obtain access tokens from Azure.

       - Storage endpoint: Used to access Azure storage resources.

       - Management endpoint: Used to communicate with Azure Resource Manager (ARM) for managing VM resources.

       10. In Description, enter a description of the credentials.

       11. Click Save.

     - If you want to create a new Azure application, follow the steps below.

       Steps to add a new Azure application

       1. Beside Credential, click the add button .

          The Add credential dialog box appears.

       2. From the Account type list, verify that Cloud Account is selected.

       3. From the Vendor type list, verify that Microsoft Azure is selected.

       4. In Credential name, enter a descriptive name for the credentials.

       5. Beside Application ID, click Deploy New Application.

       6. In the Deploy new application dialog box, do the following:

          1. In the information box shown at the top, click Open Azure Cloud Shell.

          2. Follow the instructions that appear and select Bash or PowerShell.

          3. Return to the Command Center window, in the Application name box, enter a name for the Azure application.

          4. In the Subscription ID box, enter your Azure subscription ID. Click Get Subscription ID if you need to get the ID using the command.

          5. Copy the PowerShell or Bash commands to deploy the application in the selected subscription and get the application details.

             If you have the application ID, tenant ID, and secret key, enter them. Otherwise, run the commands to get these details.

          6. At the Azure Cloud Shell command prompt, paste the commands.

             The commands run to create a new Azure application, and then the Tenant ID, Application ID, and Application secret for the application are displayed.

          7. Copy Tenant ID, Application ID, and Application Secret from the shell.

       7. Switch to Add credentials dialog box, and then paste the Tenant ID, Application ID, and Application secret to create the credential.

       8. From the Environment list, verify that AzureCloud is selected.

       9. To view and modify Azure endpoint URLs that Commvault will use to connect to Azure during VM onboarding, enable the Show endpoints toggle key. If your environment requires custom endpoints (for example, Azure Government or other sovereign cloud environments), you can modify the following endpoints:

          - Authentication endpoint: Used to verify identity and obtain access tokens from Azure.

          - Storage endpoint: Used to access Azure storage resources.

          - Management endpoint: Used to communicate with Azure Resource Manager (ARM) for managing VM resources.

       10. In Description, enter a description of the credentials.

       11. Click Save.

       Steps to assign required roles to the application

       For information about how Commvault uses Azure resource providers and what roles and permissions are required, see Role and Permission Requirements for Protecting Azure Resources.

       1. Click Assign role.

       2. In the Assign role dialog box, do the following:

          1. Copy the PowerShell or Bash commands into a text editor.

          2. Replace ROLE_NAME with the name of your role.

          3. In the information box shown at the top, click Open Azure Cloud Shell.

       3. Follow the instructions that appear and select Bash or PowerShell.

       4. At the Azure Cloud Shell command prompt, paste the commands.

          The commands runs to assign the required role.

       5. Switch to Assign role dialog box, and then click Close.

2. From the Scale manager node list, select the primary scale manager node.

3. From the Standby scale manager list, you can select the secondary manager node when the primary scale manager node is offline.

4. Click Next.

## Region Configuration page

Specify the regions to scale the access nodes in. You can add multiple regions, or auto discover regions based on tags.

1. From the Resource group list, select the resource group where you want to create the compute nodes in.

2. To manually add regions, do the following:

   1. Click Add.

      The Add region dialog box appears.

   2. From the Region list, select the region to the create the access nodes in.

   3. From the Virtual network list, select a virtual network (VNet) for the access nodes.

   4. From the Subnet list, select a sub network of the virtual network.

   5. Click Save.

      Note

      Deployment will be attempted only if the workload VM’s region matches a configured region.

3. To automatically discover resources, do the following:

   1. Enable the Automatically discover resources based on tag toggle key.

   2. In the Auto-detect tag box, enter a value.

   Need help understanding how Commvault discovers resources?

   Commvault discovers resources only within resource groups that have the specified tag. It then identifies required resources in the same region as the workload VMs. The following resources are identified using the specified tag:

   - Storage accounts

   - Virtual networks (VNets), the tag value must match the subnet name to be used

   - Public IP addresses

   Commvault then uses these resources to deploy access nodes.

   Note

   - Only tagged resources are considered.

   - Access node deployment is attempted only in the same region as the workload VMs.

4. Click Next.

## Node Settings page

Configure settings for the access nodes, such as identity, tags, scaling limits, and networking options.

1. Assign a public address for the scaling configuration and specify other settings, such as tags and maximum number of access nodes.

2. To assign an identity to compute nodes, from the User-assigned identity list, select the identity.

   The selected identity must have the Storage Blob Data Contributor role on the storage account used for access node deployment.

3. Add tags to organize and track resources.

4. In Maximum number of nodes, specify the maximum number of access nodes that can be created.

5. To assign a public IP address to access nodes, enable the Public IP toggle key.

   - For manual region configuration, the public IP prefix is searched in the resource group selected on the Region Configuration page and must be tagged with cv-scale:<cs guid>.

   - For automatic discovery, the public IP prefix is discovered using the specified tag, similar to other resources.

6. Click Next.

## Summary page

1. Review the summary.

2. Click Submit.

×

Loading...