> Commvault Cloud > Backup Storage > On-Premises Storage > Commvault HyperScale X

Migrating the HyperScale X Version on Existing Nodes

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

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

The migration process does not impact the drives that host Deduplication database (DDB) and Index Cache.

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

  • The migration script does not support nodes with legacy BIOS and NVMe drives. To migrate these nodes, contact Commvault support.

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. 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: 
    root@smchsx2 MediaAgent]# ./cvmanager.py -t Validate_Migrate_Cluster        
:      Initializing HyperScale Task Manager.        
:      Commvault HyperScale Task Manager Initialized.
Are you registering with Metallic (y/n): n
CommServe fully qualified hostname: (smchsx11.company.com)
CommCell's user name with permissions to register new clients: admin
CommCell's user password with permissions to register new clients:
[Re-Enter to Confirm] - CommCell's user password with permissions to register new clients:
    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.

  4. To start the migration, run the following commands: 

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

  5. 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:
Are you registering with Metallic (y/n): n
CommServe fully qualified hostname: (server1.company.com)
Commcell's user name with permissions for registering new clients: 
Commcell's user password with permissions for registering new clients: 
Enter the users password:
[Re-Enter to Confirm] - Commcell's user password with permissions for registering new clients:

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

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

Loading...