Creating or Rebuilding the CommServe VM

You can build the CommServe VM in an existing HyperScale X Appliance node to address one of the following situations:

Create a standby CommServe host in one of the nodes, to implement the CommServe LiveSync For High Availability Disaster Recovery.
To rebuild the CommServe host in one of the nodes, after a node failure.

Before You Begin

The CommServe server must be rebuilt using the same names, IP addresses and Windows product key that was used in the original CommServe server. Collect the following information associated with the original CommServe server before you start:
- CommServe hostname (FQDN )
- CommServe IP address
- CommServe netmask
- Windows product key
If you are rebuilding a CommServe in a CommServe Livesync setup, make sure to failover to a standby CommServe host, if the VM hosts the production CommServe host. For more information, see Unplanned Failovers.

Procedure

Download one of the following files, depending on your model, from the Commvault Store.
- HS2300 HyperScale Appliance CommServe OVA
- HS4300 HyperScale Appliance CommServe OVA
Rename the file to cvhcics.ova.
Login to the node and copy cvhcics.ova to the /ws/ddb/ova folder.

Create a configuration file (using a text editor like vi) with the following entries:

windows_productkey=windows_product_key cshname=FQDN of CommServe being deployed cs_ip=IP address of the CommServe being deployed and should resolve to Commserve FQDN provided. cs_netmask=Netmask of the CommServe being deployed

For example:

windows_productkey=A1B2C-3D4E5-F6G7H-8I9K0-L1M2O
cshname=smchs2300-pcs2.company.com 
cs_ip=111.11.11.111
cs_netmask=255.255.240.0

Navigate to the following folder:
```
# cd /opt/commvault/MediaAgent
```

Deploy the CommServe VM using the following command:

#./cvcsrebuild.py --config=path_to_config_file

For example:

# ./cvcsrebuild.py --config=/root/standbycs.cfg

Output similar to the following will be displayed. Enter appropriate information where needed.

######    Rebuilding CommServe    ######
Recreating CommServe Virtual Machine ...
After successfully creating CommServe VM, please recover from DR backup to rebuild the CS completely.
Please confirm if you want to proceed at this time (y/n): y
Please enter Commserve OVA file path (default:/ws/ddb/ova/cvhcics.ova):
Enter windows password: 
Pool cvcommserve refreshed
Domain cvcsdomain_prim defined from /tmp/v2vlibvirt944ba0.xml
[ 253.3] Finishing off
Device attached successfully
Device attached successfully
Device detached successfully
               Successfully restored powershell config
######   Creation of  CommServe VM completed successfully   ######

Once the CommServe VM is successfully deployed, login to the CommServe server using the same credentials provided as input while running cvcsrebuild.py.
Uninstall the Commvault software in the VM. You will find 2 instances (Instance001 and Instance002) installed in the VM.

Use the following command to uninstall the instances:
```
C:\ProgramData\Package Cache\GUIID]\Setup.exe" /uninstall /quiet /instance Instance001
C:\ProgramData\Package Cache\GUIID]\Setup.exe" /uninstall /quiet /instance Instance002
```
GUID can be found in the Windows registry in the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\CommVaultSystems\Galaxy\InstanceNNN\InstalledPackages\BundleProviderKey

Note

Uninstall each instance one-by-one.
Install the CommServe server using one of the following procedures, depending on your setup:
- To create a standby CommServe host, see Installing the Standby CommServe Host.
- To re-install a CommServe server, see Installing the CommServe Server.
OPTIONAL: If you have a CommServe Livesync setup, perform a test failover to ensure successful failovers. For more information, see Verifying Disaster Readiness.