Deploying standalone Commvault images from the Azure Marketplace

Deploy a standalone CommServe, Web Server, or Command Center image from the Azure Marketplace when you want to deploy these Commvault components on separate Azure VMs.

Requirements

Access to the Azure Marketplace and permission to deploy virtual machines in your Azure subscription.
A standalone image selection for the Commvault component that you want to deploy: CommServe, Web Server, or Command Center.
The User Data JSON content for the component that you're deploying:
- Commvault CommServer BYOL
  
  Required fields: cvidUser, cvidPassword, cvidEmail, clienthost, and clientname.
- Commvault WebServer BYOL
  
  Required fields: cshost, commcelluser, commcellpassword, clienthost, and clientname.
- Commvault CommandCenter BYOL
  
  Required fields: cshost, commcelluser, commcellpassword, clienthost, and clientname. wsclientname is optional.
For Web Server and Command Center deployments, an existing reachable CommServe and valid CommCell credentials are required.

User Data values

cvidUser: Commvault username used during CommServe configuration.
cvidPassword: Password for the CommServe configuration.
cvidEmail: Email address associated with the CommServe configuration.
cshost: Host name or IP address of the CommServe that the Web Server or Command Center connects to.
commcelluser: Valid CommCell user name for the existing CommServe.
commcellpassword: Password for the specified CommCell user.
clienthost: Host name of the VM being deployed.
clientname: Client name used to register the component in the CommCell.
wsclientname: Optional Web Server client name to associate with the Command Center deployment.

Deploy the standalone image

In the Azure VM deployment workflow, provide the User Data for the Commvault component that you're deploying.

Cross-reference with BYOL procedure

Reuse only the Azure portal VM workflow mechanics from Deploying Commvault (Windows/Linux BYOL) from the Azure Marketplace. Always use the standalone image selection in step 1 of this procedure.

Ignore BYOL-specific steps for standalone deployments, including the All-in-One disk layout guidance and the Complete the CommServe Configuration section. For standalone images, use the component-specific User Data JSON in step 4 of this procedure.

Procedure

In the Azure Marketplace, select the standalone Commvault image that you want to deploy.
Configure the required Azure VM settings.
Go to the Advanced tab.
In User Data, copy and paste the contents of the JSON file for the component that you're deploying:
- Commvault CommServer BYOL
- Commvault WebServer BYOL
- Commvault CommandCenter BYOL
  
  For Web Server and Command Center, cshost, commcelluser, and commcellpassword connect the deployment to the existing CommServe.
  
  For Command Center, wsclientname is optional. Specify it only when you want to associate the deployment with a specific Web Server.
Complete the Azure VM deployment.

After Azure finishes deploying the VM, Commvault software configuration starts automatically by using the values provided in User Data.

Verify the deployment

After the Azure VM finishes deploying, setup and configuration start automatically based on the User Data values that you entered.

For a standalone CommServe deployment, after the Commvault software configuration is complete, open the Command Center and sign in using the account configured during deployment. When the user account is configured through the deployment User Data, the Registration page does not appear.
For a standalone Web Server, verify that the Web Server is registered in the existing CommCell with the specified clientname and is connected to the CommServe specified by cshost.
For a standalone Command Center, verify that Command Center is registered in the existing CommCell with the specified clientname and is connected to the CommServe specified by cshost. If you specified wsclientname, verify that it is associated with the expected Web Server.

Use the following checks:

In Azure portal, confirm that the VM deployment shows as successful and the VM is running.
Sign in to Command Center for the CommCell that you used during setup.
Check that the new VM appears in the CommCell for the component that you deployed.
Confirm that the component is usable:
- For CommServe, confirm that you can sign in to the new CommServe.
- For Web Server and Command Center, confirm that the component is connected to the existing CommServe that you entered in User Data.
- For Command Center with wsclientname, confirm that it is linked to the expected Web Server.