> Software > Manage > Storage > HyperScale > HyperScale 1.5 > Appliance > Operations

Rebuilding the CommServe VM Hosting the CommServe Server

The Virtual Machine(VM) hosting the CommServe server (along with the CommServe server) can be rebuilt, in the event of a disaster, when it becomes unusable or inaccessible.

Before You Begin

Important

A copy of the latest Disaster Recovery (DR) backup is needed to rebuild the CommServe server. Make sure to locate a copy of the latest full and the latest differential DR backup (if applicable) before you start. If your primary CommServe is available make sure to perform a DR Backup before rebuilding the CommServe VM. For more information on performing a DR Backup, see Performing a Disaster Recovery.

Do not take snapshots of the CommServe VM which is deployed on RHV (Red Hat Virtualization). This will cause the CommServe VM to run out of space and preventing the CommServe from rebooting.

  • 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

    • CommServe IP address

    • CommServe netmask

    • Windows product key

    • Virtualization Engine hostname

    If you have a 1G Management network, you will also need the following information:

    • Backup network hostname

    • IP address associated with backup network host

  • Note down the version information including the Service Pack (and hot fixes, if applicable) installed in the CommServe before rebuilding the CommServe.

Procedure

  1. Login to any one of the HyperScale nodes and create an input file containing the CommServe information as follows:

    cs_hname=mycs.company.com
cs_ip=100.01.01.01
cs_netmask=255.255.240.0
windows_productkey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
ovirt_hname=myovirt.company.com

    Provide the following additional inputs if you have a 1G Management network.

    cs_bkpnw_hname=mybkpcs.company.com
cs_bkpnw_ip=100.02.02.200

    Note

    Make sure to use the same names, IP addresses and Windows product key that was used in the original CommServe.

    Save the file in /tmp or any other appropriate location.

  2. Navigate to the following folder:

    /opt/commvault/MediaAgent

  3. Run the following command:

    ./cvcsrebuild.py /tmp/csvm.cfg

    The following prompt will be displayed:

    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

  4. Press Enter to continue.

    The following prompt will be displayed:

    Please enter Commserve OVA file path (default:/ws/ddb/ova/cvhcics.ova):

  5. Press Enter (or type the path if the OVA file is saved in a different folder and then press Enter) to continue.

    The following prompt will be displayed:

    Enter ovirt password:

  6. Enter the password associated with the OVIRT host and press Enter.

    This will create the CommServe VM and the progress, similar to the following, will be displayed:

    rw-r--r-- VMware/VMware  8057 2019-03-16 13:18 cvhcics.ovf
-rw-r--r-- VMware/VMware 60173941760 2019-03-16 13:18 cvhcics-disk1.vmdk
-rw-r--r-- VMware/VMware         129 2019-03-16 13:18 cvhcics.mf
Will connect to Red Hat Virtualization manager. Please wait ...
Connected to Red Hat Virtualization Manager successfully!
Memory needed is: 68719476736 bytes, memory avaialble is: 125870940160 bytes
              total        used        free      shared  buff/cache   available
Mem:      131244968     3617224   126967628      173416      660116   122920804
Swap:      14553084        2860    14550224
              total        used        free      shared  buff/cache   available
Mem:      131244968     3616972   127041508      173416      586488   122958132
Swap:      14553084        2860    14550224
Swap:      14553084        2860    14550224
-rw-r--r-- VMware/VMware  8057 2019-03-16 13:18 cvhcics.ovf
-rw-r--r-- VMware/VMware 60173941760 2019-03-16 13:18 cvhcics-disk1.vmdk
-rw-r--r-- VMware/VMware         129 2019-03-16 13:18 cvhcics.mf
Started instantiating CommServe from OVA file. This may take several minutes. Please wait...
CommServe has been deployed successfully
Starting post deployment operations on CommServe. Please wait...
Network interface 'virtio' added to 'cvhcics'
Made the vm cvhcics highly available
Uploading, please wait...
INFO: Start uploading /opt/commvault/Base/Temp/ovadir/config.iso
Uploading: [########################################] 100%
INFO: /opt/commvault/Base/Temp/ovadir/config.iso uploaded successfully
Attached dvd config.iso to cvhcics
Starting vm cvhcics
Waiting for vm cvhcics to reach up status...
CS Services are restarted successfully, will try to qlogin...
Ejected DVD from 'cvhcics'
Successfully restored powershell config
######   Creation of CommServe VM completed successfully   ######

  7. Run the following command using the input file created in step 1:

    ./cvcsrebuild.py input_file_name

    For example:

    ./cvcsrebuild.py ./tmp/CSInput

    This will create the CommServe server.

What to Do Next

  • Login to the CommServe server using the same credentials used in the original CommServe.

  • Verify the Service Pack version (and hot fixes, if applicable) to ensure that it matches the original CommServe. If not make sure to install the necessary Service Pack and updates to match the ones that were installed in the original CommServe, before proceeding to the next step.

  • Restore the CommServe databases using the latest DR backup. For more information about recovering the databases, see Recovering the CommServe Computer Using DR Backups.

×

Loading...