# Manual Migration of Systems Without NVMe Boot Support

Some hardware vendors do not support booting from NVMe drives where the `/ws/ddb/iso` path resides. In such cases, NVMe drives do not appear in the BIOS boot order menu. A manual mode migration is required.

## Before You Begin

- 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 thecvbackupadminuser, 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.

- If a tape library is attached to the MediaAgent, 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 upgrade the Commvault Grid version, complete the following steps:

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

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

3. Configure BIOS boot settings.

   1. Edit the BIOS boot settings for each node to boot from the attached DVD.

      Do not reboot the node at this point.

   2. Exit the IPMI settings.

      Alternatively, as each node auto-reboots, enter the boot menu and manually select the DVD as the boot device.

4. To verify if the existing cluster meets the upgrade criteria, run the following command:

       #./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 upgrade only after the validation process is complete. If the validation fails, you must fix the issue and then rerun the validation command.

5. From the Remote Cache Node, run the following command:

       cd /opt/commvault/MediaAgent/task_manager

       ./cvmanager.py -t Migrate_Cluster manual_iso=True

   To migrate a single node, run the following command:

       ./cvmanager.py -t Migrate_Cluster manual_iso=True node=nodename

6. When prompted during the upgrade process, follow these steps:

   1. Open IPMI console on the node `node1.company.com` and keep it active throughout the migration.

      Press 'y' to proceed (y|n): y

   2. Attach the migration ISO:

      `/ws/ddb/cvmanager/share/dvd_02132025_084957.iso` via IPMI console.

      Press 'y' to proceed (y|n): y

   3. Update the BIOS boot order to boot from the ISO.

      Do NOT reboot the node at this point.

      Press 'y' to proceed (y|n): y

   4. The upgrade will sequentially update the OS and reboot each node.

      Note

      This process may take several hours to complete.

7. The upgrade 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 process upgrades the operating system and reboots each node in the cluster, sequentially. This process may take several hours to complete.

   Caution

   Do not attempt to manually upgrade any node in the cluster while migration is in progress.

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

   `# commvault reg | grep MigrationCompleted`

   Output:
   `sRHELToRockyMigrationCompleted yes`

9. To resume a upgrade job automatically when there are incomplete tasks, start the upgrade using the following command:

       #./cvmanager.py -t Migrate_Cluster --resume

   When you run the upgrade without the `resume` parameter, the upgrade job detects the existing migrate_cluster task and offers options to resume the task.

10. If the upgrade fails after authentication:

    1. Retrieve the last task:

       `/opt/commvault/MediaAgent/task_manager/cvmanager.py --unfinished_task_check Migrate_Cluster`

       This will generate a .yaml file, for example:

       /ws/ddb/cvmanager/catalog/status/Task_6554744226181603181/cvmanager_jJV8X7.yaml

    2. Resume the upgrade using the YAML file:

       `/opt/commvault/MediaAgent/task_manager/cvmanager.py <filepath.yaml>`

       You do not need to re-verify the upgrade criteria before resuming.

## What to Do Next

If a tape library is attached to the MediaAgent, complete the following steps:

1. From the Command Center navigation pane, go to Manage > 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 MediaAgent to which the tape library is attached.

4. Click Scan hardware.

   Tail the cvd.log file on the MediaAgent 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.

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

   The Tape page appears.

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

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