Loading...

Stopping and Starting All Nodes

When all the nodes have to be shut-down for maintenance, it is important to follow the proper shut down and startup procedures to prevent data loss.

Before You Begin

Login to Command Center and verify that the disks and storage pool are online and functioning properly .

  • To verify the Storage Pool:
    1. From the navigation pane, click Storage > HyperScale.

      The HyperScale page appears.

    2. Verify that the Status of the storage pool is displayed as Online.
  • To verify the Disks:
    1. In the HyperScale page, click the name of the <Storage pool>.

      The <Storage pool> page appears.

    2. Verify that the Status of the Nodes ia displayed as Online.
    3. Click each node and verify that the Disk Status is displayed as Ready.

Procedure

  1. Using RDP, shutdown the Windows Operating System on the VM hosting the CommServe.
  2. Set the hosted engine in the maintenance mode as follows:

    Using the Virtualization Manager:

    1. Access the Virtualization Manager by typing the following URL in a Web Browser:

      https://<Control Host Name>/ovirt-engine

      For example: http://mycontrolhost.mydomian.com/ovirt-engine

    2. Click Administration Portal.
    3. Type the login credentials to access the Virtualization Manager.

      Tip: Type admin as the user name and the root password provided for the CommServe Server during the setup.

      The Dashboard will be displayed in the Red Hat Virtualization window.

    4. Navigate to System > Data Centers > Clusters > Hosts.
    5. Right-click the appropriate host on the right-pane, and click Management > Global.

    From the Command Line:

    Login to any MediaAgent node and set the hosted engine in the maintenance mode.

    hosted-engine --set-maintenance --mode=global

    Note: You can use an SSH client program, like PuTTy on Windows, to login to the MediaAgent nodes.

  3. Shut down the hosted engine as follows:
    1. View the MediaAgent node in which the hosted engine is running using the following command:

      hosted-engine --vm-status

    2. Login to the MediaAgent node and shut down the hosted engine using the following command:

      hosted-engine –-vm-shutdown

  4. Login to each HyperScale node as root and run the following command to stop services:

    commvault stop

  5. When the services are stopped, type the following command to view the deduplication processes that may be running.

    commvault list

    If the SIDB_Engine_<ID> process is found running, wait until the process is complete.

    Note: Depending on the size of the DDB, this process might take as long as 30 minutes to complete.

    Repeat this step to confirm that the processes are no longer running before restarting the computer.

  6. Login to any one of the HyperScale nodes and stop the gluster volumes on all the nodes using the following commands:
    • List the volumes to identify the volume names using the following command:

      gluster volume list

    • Stop the volumes using the following command:

      gluster volume stop <volume_name>

      Note: The above command will stop the volumes in all the nodes - it is not necessary to repeat the command in the other nodes.

      Make sure that the volumes are stopped in the following order:

      1. Storage Pool volume
      2. Volume associated with the CommServe VM
      3. Volume associated with the Control Host

        Tip: Storage Pool volume name is the same as the Storage Pool name. The default name for the volume associated with the CommServe VM is dav_vm_vol and the default name for the volume associated with the Control Host is dav_he_vol.

  7. Shut down the nodes to perform the necessary maintenance.

    Tip: Use the reboot or shutdown –h now commands to stop the node.

  8. After restarting the nodes, start the following volumes:

    gluster volume start dav_he_vol
    gluster volume start dav_vm_vol

  9. Verify that the /ws/glus folder is mounted in each of the nodes using the following command:

    df -h

    If the folder is not mounted, wait for Commvault Services to automatically mount the folder. This may take a maximum of 30 minutes and is the recommended method. Alternatively, you can also restart the Commvault Services on the node using the following command:

    commvault -all restart

    For more information on restarting Commvault Services, see Commands to Control Services on UNIX Clients.

  10. Verify that the gluster is online using the following command:

    hosted-engine --vm-status

  11. Start the virtualization host using the following command:

    hosted-engine --vm-start

  12. Reset the hosted engine mode as follows:

    Using the Virtualization Manager:

    1. Access the Virtualization Manager by typing the following URL in a Web Browser:

      https://<Control Host Name>/ovirt-engine

      For example: http://mycontrolhost.mydomian.com/ovirt-engine

    2. Click Administration Portal.
    3. Type the login credentials to access the Virtualization Manager.

      Tip: Type admin as the user name and the root password provided for the CommServe Server during the setup.

      The Dashboard will be displayed in the Red Hat Virtualization window.

    4. Navigate to System > Data Centers > Clusters > Hosts.
    5. Right-click the appropriate host on the right-pane, and click Management > None.

    From the Command Line:

    Login to any MediaAgent node and reset the hosted engine as follows:

    hosted-engine --set-maintenance --mode=none

  13. Access the Virtualization Manager and manually restart the virtual machine hosting the CommServe.

    You can access the Virtualization Manager by typing the following URL in a Web Browser:

    https://<Control Host Name>/ovirt-engine

    For example: http://mycontrolhost.mydomain.com/ovirt-engine

  14. Open the Command Center and make sure that the Storage Pool and Disks are online and functioning properly as described in Before You Begin.

Last modified: 12/9/2020 11:03:34 AM