> Expert > Commvault HyperScale > HyperScale X > Maintenance

Stopping and Starting a HyperScale X Node

You can stop and restart a single node in a HyperScale 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 a node.

  • Use the steps outlined in this page to shutdown and restart a single node, for maintenance purposes.

  • If more than one node needs to be shutdown, make sure to shutdown the entire cluster as described in Stopping and Starting the Cluster.

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

Before You Begin

  • If you have setup a Primary and Standby CommServe server, verify whether the CommServe server is currently active on the node that you want to stop. Use the following steps to identify the currently active and passive nodes:

    1. Login to the Command Center. For more information on logging in to the Command Center, see Accessing the Command Center.

    2. From the navigation pane, expand Administration > System, and then click CommServe LiveSync.

      The CommServe LiveSync page appears.

    3. Under Nodes, verify the Node Information which displays the currently active and passive nodes.

    4. If the CommServe server is currently active on the node that you want to stop, failover the CommServe server to the standby node. For more information on failover over a node, see Planned Failovers.

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

  • Stop or suspend all running jobs that are associated with the MediaAgent installed in the node that you plan to shut-down. For more information, see Controlling Jobs.

Stopping a Node using Restricted Shell

Note

Only on nodes with HyperScale 3.x installations or upgraded to the latest patch.

  1. Stop the Commvault services, and verify that the Commvault File System (CVFS) vdisk is unmounted on the node: :

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

    2. Stop the services using the following command:

      # hs_node --commvault stop

    3. To verify that the vdisk is unmounted successfully, run the following command:

      # hs_node --df
      The output should not include the exports/CVLTBackup* :

      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

  2. Stop the nodes using the following commands:

    #hs_node --cds stop

    For example:

    /opt/hedvig/bin/hv_deploy --stop_node hs2300m5.company.com --cluster_name HV13102021054000
... provisioning as a hsx cluster. details: ApplianceType HS2300
... logged into commvault cluster
Ensuring password-less SSH connections have been added for all cluster machines.
RUNNING: stop_node *************************************************************
RUNNING PLAY 1 [stop hedvig hblock] ********************************************
RUNNING PLAY 2 [stop hedvig pages] *********************************************
RUNNING PLAY 3 [stop hedvig hpod] **********************************************
COMPLETED PLAY 3 ***************************************************************
ACTION RECAP: ******************************************************************
hs2300m5.company.com : ok=9    changed=0    unreachable=0    failed=0

Starting a Node After a Reboot using Restricted Shell

  1. Reboot the node using the following command:

    # hs_node --reboot

    After a reboot all the services will be automatically restarted and the CVFS vdisk will be mounted.

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

  3. Verify the node is up and running using the command and ensure the node that was rebooted is listed: # hs_node --cds showmembers

  4. Verify that the vdisk is mounted successfully, run the following command:

    #hs_node --df

Stopping a Node

  1. Stop the Commvault services, and verify that the Commvault File System (CVFS) vdisk is unmounted on the node: :

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

    2. Stop the services using the following command:

      # commvault stop

    3. To verify that the vdisk is unmounted successfully, run the following command:

      # df -h
      The output should not appear like below:

      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

  2. Stop the nodes 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
/opt/hedvig/bin/hv_deploy --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

    Use the cluster name to stop the node using the following command:

    /opt/hedvig/bin/hv_deploy --stop_node <fqdn hostname> --cluster_name <Clustername>

    For example:

    /opt/hedvig/bin/hv_deploy --stop_node hs2300m5.company.com --cluster_name HV13102021054000
... provisioning as a hsx cluster. details: ApplianceType HS2300
... logged into commvault cluster
Ensuring password-less SSH connections have been added for all cluster machines.
RUNNING: stop_node *************************************************************
RUNNING PLAY 1 [stop hedvig hblock] ********************************************
RUNNING PLAY 2 [stop hedvig pages] *********************************************
RUNNING PLAY 3 [stop hedvig hpod] **********************************************
COMPLETED PLAY 3 ***************************************************************
ACTION RECAP: ******************************************************************
hs2300m5.company.com : ok=9    changed=0    unreachable=0    failed=0

Starting a Node After a Reboot

  1. Reboot the node using the following command:

    # reboot

    After a reboot all the services will be automatically restarted and the CVFS vdisk will be mounted.

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

Starting a Node Manually

  1. Using an SSH client program, like PuTTy on Windows, login to a node using the root credentials.

  2. Start the nodes using the following commands:

    Note

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

    export HV_PUBKEY=1
/opt/hedvig/bin/hv_deploy --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

    Use the cluster name to start the node using the following command:

    /opt/hedvig/bin/hv_deploy --start_node <fqdn hostname> --cluster_name <Clustername>

    For example:

    /opt/hedvig/bin/hv_deploy --start_node hs2300m5.company.com --cluster_name HV13102021054000
... provisioning as a hsx cluster. details: ApplianceType HS2300
... logged into commvault cluster
Ensuring password-less SSH connections have been added for all cluster machines.
RUNNING: start_node ************************************************************
RUNNING PLAY 1 [collect deploy server facts] ***********************************
RUNNING PLAY 2 [start node] ****************************************************
COMPLETED PLAY 2 ***************************************************************
ACTION RECAP: ******************************************************************
hs2300m5-1a.company.com : ok=16   changed=10   unreachable=0    failed=0
localhost                 : ok=2    changed=0    unreachable=0    failed=0

  3. Exit the admin user mode. (Skip this step for HyperScale 3.x installations.)

    exit

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

    # commvault start

  5. 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...