> Commvault SaaS > Backup Storage > On-Premises Storage > Commvault HyperScale X > HyperScale X Upgrade

Migrating the HyperScale X Version on Existing Nodes

You can migrate HyperScale X 2.x clusters to HyperScale X 3.x clusters using the FR42.18 HyperScale X ISO image.  With this migration, the OS drive on the nodes is upgraded to Rocky Linux platform.

Review the following considerations:

  • The upgrade process is performed sequentially, and may require up to 90 minutes per node to complete. For example, a three-node cluster may require up to 4.5 hours to complete. For customers with systems configured with BIOS boot, additional time may be required.

  • The upgrade process will prompt to update the password for both the root and cvbackupadmin users.

  • The upgrade process automatically creates the cvbackupadmin user, if the user is not already present before the upgrade.

  • The upgrade process does not impact the drives that host Deduplication database (DDB) and Index Cache. The drives hosting backup data are also not modified during the upgrade.

  • Once the upgrade is complete, ransomware protection, restricted shell, and firewall are enabled by default, even if the storage pool did not have these settings enabled previously.

  • After the upgrade starts, it is not possible to rollback to the previous version.

  • To prevent a significant increase in the deduplication database and storage, avoid performing full backups and synthetic full operations during the upgrade process.

Before You Begin

  • Verify that the Server Gateway is on 11.36.22 or higher version.

  • Verify that you have maintenance release 11.36.22 or higher installed on all the nodes in the HyperScale X cluster. For more information, see Updating the Backup Gateway Software.

  • Install the HyperScale X Platform Version 2.2507 or higher on all the HyperScale X nodes.

  • Enable password-based root access only on remote cache node to run the migration related commands.

  • Verify that the nodes in the HyperScale cluster are not under maintenance mode.

  • Verify that multi-factor authentication (MFA) is enabled.

    Review the following considerations:

    • Verify that all nodes in the HyperScale cluster can access the following URLs:

      • https://api.metallic.io, which is the endpoint used for all storage pool operations.
      • https://<Saas-ring-name>.metallic.io/commandcenter, Commvault Cloud Console URL specific to your ring. For example, https://m01.metallic.io/commandcenter.

      Both the URLs are on HTTPS and can be accessed through port 443.

    • Verify that users have a local CommCell account; if SAML authentication is used, create a new Local Tenant Admin account.

    • Make a note of the following:

      • Obtain the CommCell username. The username must be the email address of the user. Do not consider username in the format of <CompanyName>/Username.
      • Obtain the PIN generated by the authenticator tool that you use for multi-factor authentication.

  • If your hardware supports booting from NVMe drives, ensure that the /ws/ddb/iso path is located on a bootable NVMe drive.

    Note: NVMe drives containing the /ws/ddb/iso path appear in the boot order menu in the BIOS.

    Before starting the migration, update the BIOS boot settings to place the bootable NVMe drive above CVLTPBBA and at the top of the boot order.

  • If a tape library is attached to the Backup Gateway, complete the following steps:

    1. Do not use the tape library for any operations like backup, restore or auxiliary copy.

      • Verify that all tape library drives are unloaded.

      • Confirm the library is in an "Idle Ready" state.

    2. Remove lin_tape Driver (if applicable)

      • If using the lin_tape driver, remove it using the following command:

        rpm -e [lin_tape_version].rpm

        Example:

        rpm -e lin_tape-1.60.0-1.x86_64.rpm

      • If a lin_tape.conf file exists under /etc/modprobe.d, remove it.

Procedure

To migrate the HyperScale X version, complete the following steps:

  1. Copy the latest HyperScale X image from Commvault Cloud store to the /ws/ddb/iso folder on the Hyperscale X remote software cache node.

  2. Using the system console (for example, using KVM, not SSH), log on to the node in which the remote cache is configured, and navigate to the /ws/ddb/iso folder.

  3. You must proceed with the migration only after the validation process is complete. If the validation fails, you must fix the issue and then rerun the validation command.

    Verify if the existing cluster meets the migration criteria using the following command: 

    #cd /opt/commvault/MediaAgent<br>
#./cvmanager.py -t Validate_Migrate_Cluster
    The validation process will prompt for the following inputs: 
    Are you registering with SaaS (y/n):

  4. Enter y.

    The following messages appear:

    Enter the SaaS backup gateway for registration:
Enter the SaaS backup gateway port for registration [443]:

    Enter the fully qualified host name and port of the existing backup gateway that you are connecting to.

  5. Enter y.

    The following messages appear:

    Authorization mode:
1) Username & Password (Non-MFA)
2) Existing Access Token
3) Username & Password + PIN (MFA)
Your Choice (1/2/3):

    Enter values for all the prompts. Authorization mode 2 - Existing Access Token is currently not supported.

  6. If your organization has MFA enabled and you selected 3 for the authorization mode, the following prompts are displayed. 

    CommCell user name with permission to register clients and edit storage pools:
CommCell's user password with permissions to register new clients:
[Re-Enter to Confirm] - CommCell's user password with permissions to register new clients:
PIN:
    Enter the values.

    • The username must be the email address of the user. Do not enter username in the format of <CompanyName>/Username.
    • Enter the PIN generated by the authenticator tool that you use for multi-factor authentication

  7. If your organization does not have MFA enabled and you selected option 1 for the authorization mode, the following prompts are displayed. 

    CommCell user name with permission to register clients and edit storage pools:
CommCell's user password with permissions to register new clients:
[Re-Enter to Confirm] - CommCell's user password with permissions to register new clients:
    Enter the values.

  8. After successful validation, to proceed with the migration, run the following commands: 

    # cd /opt/commvault/MediaAgent/
#./cvmanager.py -t Migrate_Cluster

  9. The migration script prompts you to input the following values: 

    Root password of existing cluster:
[Re-Enter to Confirm] - Root password of existing cluster:
Restricted shell user (cvbackupadmin) password:
[Re-Enter to Confirm] - Restricted shell user (cvbackupadmin) password:

  10. Enter the root password which was added during the initial HyperScale node configuration. (This root password would be the same root password used in the other nodes.)

    The following message appears: 

    Are you registering with SaaS (y/n):

  11. Enter y.

    The following messages appear:

    Enter the SaaS backup gateway for registration:
Enter the SaaS backup gateway port for registration [443]:

    Enter the fully qualified host name and port of the existing backup gateway that you are connecting to.

  12. Enter y.

    The following message appears:

    Authorization mode:
1) Username & Password (Non-MFA)
2) Existing Access Token
3) Username & Password + PIN (MFA)
Your Choice (1/2/3):

    Select an authorization mode. Authorization mode 2 - Existing Access Token is currently not supported.

  13. If your organization has MFA enabled and you selected 3 for the authorization mode, the following prompts are displayed. 

    CommCell user name with permission to register clients and edit storage pools:
CommCell's user password with permissions to register new clients:
[Re-Enter to Confirm] - CommCell's user password with permissions to register new clients:
PIN:
    Enter the values.

    • The username must be the email address of the user. Do not enter username in the format of <CompanyName>/Username.
    • Enter the PIN generated by the authenticator tool that you use for multi-factor authentication

  14. If your organization does not have MFA enabled and you selected option 1 for the authorization mode, the following prompts are displayed. 

    CommCell user name with permission to register clients and edit storage pools:
CommCell's user password with permissions to register new clients:
[Re-Enter to Confirm] - CommCell's user password with permissions to register new clients:
    Enter the values.

  15. The migration process migrates and reboots each node in the cluster from RHEL7 to Rocky8 sequentially. This process may take several hours to complete.

  16. To verify whether the node was migrated successfully, run the following command and make sure the output is displayed as follows:

    # commvault reg | grep sRHELtoRockyMigrationCompleted

    Output:
    sRHELtoRockyMigrationCompleted yes

What to Do Next

Perform the following post-migration tasks:

  • Install the latest Commvault Cloud updates

    The Backup Gateway on the migrated node may have an older version of the Commvault Cloud software. To view the Backup Gateway version in the new nodes, see View the HyperScale X Backup Gateway version.

    If necessary, update the software to the latest maintenance release version. For more information, see Updating the Backup Gateway Software.

  • Install the latest HyperScale X platform version

    After the migration, the CVFS version is updated. However, the node may not be fully up-to-date with the Operating System updates. To view the HyperScale X platform version, see Viewing the HyperScale X Platform Version.

    If necessary, install the latest platform version to make sure that the node has the latest security fixes. For more information, see Installing Operating System Updates on HyperScale X.

  • After the migration, root user login is automatically disabled on the HyperScale X cluster nodes. SSH and console login will be prohibited, and only the cvbackupadmin user can log on and access the nodes. If required, you can enable the root access. For more information, see Enabling or Disabling Root Access.

  • If firewall was enabled on the HyperScale cluster before the migration, then you must re-enable firewall manually after the migration is complete. For more information, see Enabling Firewall.

  • If a tape library is attached to the Backup Gateway, complete the following steps:

    1. From the Command Center navigation pane, go to Storage > Tape.

      The Tape page appears.

    2. In the upper-right corner of the page, click Add to add a tape storage.

      The Add tape dialog box appears.

    3. From the MediaAgent list, select the Backup Gateway to which the tape library is attached.

    4. Click Scan hardware.

      Tail the cvd.log file on the Backup Gateway or Node to monitor progress. The output of CVMACScsi::DetectDevices() will display the access paths.

      Once the scan is complete, close the Add tape dialog box.

    5. From the Command Center navigation pane, go to Storage > Tape.

      The Tape page appears.

    6. For the tape_storage, click the Actions button, and then click Reset library.

    7. Click Yes in the Confirm reset library prompt.

      The reset is complete when CVMA.log shows details on slots, drives, and IE ports, concluding with: WORKER [ ] libHandlerError = 0, bStatus = 1

×

Loading...