> Expert > Commvault HyperScale > HyperScale X > Maintenance

Stopping and Starting the HyperScale X Cluster

You can stop and restart a Commvault HyperScale X cluster.

Caution

To maintain data integrity and to prevent data loss, it is important to follow the proper shut down and startup procedures outlined in this page, while stopping or starting the cluster.

  • If a single node needs to be shutdown for maintenance, follow the steps outlined in Stopping and Starting a Node.

  • If more than one node needs to be shutdown, make sure to shutdown the entire cluster as described in this page.

  • Improper shutdown of multiple nodes individually can lead to data integrity issues resulting in data loss and restore failures.

Stopping the Cluster

  1. Stop or suspend all running jobs associated with the MediaAgents in the cluster . For more information, see Controlling Jobs.

  2. Set the MediaAgents on maintenance mode. For more information, see Setting the MediaAgent on Maintenance Mode.

  3. Stop the Commvault services, and verify that the Commvault File System (CVFS) vdisk is unmounted on all the nodes in the cluster:

    1. Using an SSH client program, like PuTTy on Windows, login to one of the nodes using the root credentials.

    2. Get the <vdiskname> using the following command:

      <vdiskname> is the name sub-folder under /ws/hedvig.

       
      # df -h

      See the following example:

       
      127.0.0.1:/exports/CVLTBackupSMC43002153  269T -1.5T  271T   0% /ws/hedvig/CVLTBackupSMC43002153
127.0.0.1:/exports/CVLTBackupSMC43002153  269T -1.5T  271T   0% /ws/hedvig/CVLTBackupSMC43002153-r

    3. Stop the services using the following command:

      # commvault stop

    4. To verify that vdisk is unmounted, execute the mount command. The output should not display <vdiskname> in the output.

    5. Repeat the steps on the other nodes in the cluster.

  4. Start the hv_deploy mode using the following commands:

    Note

    On nodes with HyperScale 2.x installations, before you stop the nodes, switch to the admin user using the command, # su - admin. 

    # export HV_PUBKEY=1
# hv_deploy

  5. Display the cluster name and note down the name.

    # show_all_clusters

    This will display the cluster name, as shown in the following sample output:

     
    Cluster name: HV13102021054000 - owner: unowned - version: v-4.5.0.0.2.3597.00320e0ba9:06aca75bc4db06170a13ef14cbfe8446

  6. Login to the cluster.

    # login_to_cluster <cluster name>

    For example:

     
    # login_to_cluster HV13102021054000

    When prompted, type the root password.

  7. Stop the cluster.

    # stop_cluster

  8. Exit the the hv_deploy mode.

    # exit

Starting the Cluster

  1. Using an SSH client program, like PuTTy on Windows, login to one of the nodes using the root credentials.

  2. Start the hv_deploy mode using the following commands:

    Note

    On nodes with HyperScale 2.x installations, before you stop the nodes, switch to the admin user using the command, # su - admin. 

    # export HV_PUBKEY=1
# hv_deploy

  3. Display the cluster name and note down the name.

    # show_all_clusters

    This will display the cluster name, as shown in the following sample output:

     
    Cluster name: HV13102021054000 - owner: unowned - version: v-4.5.0.0.2.3597.00320e0ba9:06aca75bc4db06170a13ef14cbfe8446

  4. Login to the cluster.

    # login_to_cluster <cluster name>

    For example:

     
    # login_to_cluster HV13102021054000

    When prompted, type the root password.

  5. Start the cluster

    # start_cluster

  6. Exit the hv_deploy mode.

    # exit

  7. Start the Commvault services. (This will also mount the CVFS vdisk.)

    # commvault start

  8. Disable the maintenance mode for the MediaAgent to bring it online. For more information, see Setting the MediaAgent on Maintenance Mode.

Handling Improper Shutdowns of HyperScale Nodes or Clusters

Loading...