> Expert > Commvault HyperScale > HyperScale X > Reference Architecture > Maintenance

Re-Imaging HyperScale X Reference Architecture

HyperScale X Reference Architecture nodes can be re-imaged when there is no backup data available in the node. For example, after a failed or incorrect installation. (When there are hardware failures in one of the nodes in an existing storage pool, such as disk issues or corrupted operating system, you can refresh the node as described in Refreshing HyperScale X Reference Architecture Nodes.)

Before You Begin

  • Download the most recent version of the HyperScale software from the Commvault Store.

    Note

    Hyperscale ISO 2.2212 is the current most recent version.

  • Copy the ISO to a virtual drive accessible to the node or create an USB Boot Media.

  • Disconnect any cables that are attached to FC HBA's before imaging.

Procedure

  1. Setup the virtual drive or the USB device as the boot media on the server.

    You can do this using either the hardware vendor's remote console interface such as iLO, iRMC, or iDRAC, or using a KVM device, Local Crash Kart, etc. UEFI boot mode is recommended. Disable UEFI secure boot if it is enabled. Refer to the documentation associated with your server for more information.

  2. Restart the node using the ISO media.

    Note

    It may take several minutes for the ISO to boot, and a blank screen may be displayed for some time, approximately up to 5 minutes.

    The main menu will be displayed.

  3. Select the Next button to proceed to the selection menu.

  4. When prompted, choose the Reinitialize drives option.

    The imaging will start automatically and this process may take some time, approximately 45 minutes, to complete.

    A 'completed successfully' message will be displayed when the imaging process is finished.

  5. If necessary unmount the ISO from the node.

  6. Restart the node.

  7. After the restart, verify the Commvault Distributed Storage (CDS) RPM version using the following command:

    # /usr/local/hedvig/scripts/whichCommit.sh

    The resulting output will display the RPM version in the Branch: section, as shown in the following sample output:

    Manifest-Version: 1.0
Created-By: Hedvig
Main-Class: com.simontuffs.onejar.Boot
One-Jar-Main-Class: com.quexascale.quexablock.pages.QuexaBlockPagesService
CommitId: QBD[c92d97c476bdedb194b895589f3665c42ce09914: 1.94: 2021-03-15T22:34Z] 
Duro[4e4ba99cb77552ee56f7f7edf19112f3b3d64b86: 1.1: 2021-03-15T22:31Z] 
Common[d353c7e277802aaa15d01e47c3d7e40aefa19237: 2021-03-15T22:28Z] 
GMS[fce7026009692b7188876c35227ff1a36a09e734: 2021-03-15T22:29Z]
HPOD[0162c6263f7a647a05be8698b6b17f8863c09dd3:2021-03-15T22:30Z] 
Thrift[5dc0e4f06d8c5f1a58785da64538d41e9a2d5082:2021-03-15T22:29Z]
Branch: QBD[v-4.2.3] Duro[v-4.2.3] Common[v-4.2.3] GMS[v-4.2.3] HPOD[v-4.2.3] Thrift[v-4.2]

    In the above example, v-4.2.3 is the RPM version.

  8. Verify the minor version of the RPM using the following command:

    # rpm -qa | grep hedvig

    The resulting output will display the minor RPM version, as shown in the following sample output:

    hedvig-cluster-1.0.0_3564_2484803ffb-1.x86_64
hedvig-common-1.0.0_3564_2484803ffb-1.x86_64

    In the above example, 3564 is the minor RPM version.

What to Do Next

  • Important: Verify and ensure that all nodes have the same time and timezone settings.

Deploy the re-imaged node, choosing a deployment method based on your network topology. For more information, see Setting up the Network.

Loading...