# Post-Upgrade Readiness Check for Commvault Grid Upgrade

After the upgrade is complete, the Commvault Grid Upgrade Readiness workflow helps to perform several post-upgrade tasks.

To deploy and execute the workflow, contact Commvault Support.

## Procedure

1. Execute the Commvault Grid Upgrade Readiness workflow.

2. Select Post-Upgrade.

3. Select the Commvault Grid storage pool from the list.

4. A post-upgrade check will email a report of the post-upgrade validation and identify any issues that need to be resolved.

5. Perform an end-to-end test of backup and recovery operations, with a focus on the following areas:

   1. Verify business critical workloads can be protected and recovered

   2. Verify workloads that leverage one or more access nodes to verify communication

   3. Verify operations that rely on specific network configurations such as network topologies, backup interfaces, static routes, HTTP Proxies, or tagged VLAN interfaces

   4. Verify workloads that rely on direct storage connections such as IntelliSnap, VSA SAN/NAS modes, or direct attach tape/disk libraries.

   As a best practice Commvault recommends refraining from performing any major system updates to the CommCell or Commvault Grid Storage Pools for 30 days post upgrade, unless directed by a Commvault representative.

6. If ICMP/PING requests were disabled prior to the HyperScale Platform pre-check, the network settings may be updated to disallow ICMP/PING at the conclusion of the Platform upgrade.

7. If your environment uses an external iSCSI-based storage array, run the following commands on each Commvault Grid node to discover and log on to the iSCSI targets. This step is required to re-establish iSCSI sessions from the Commvault Grid nodes to the storage array.

   1. Discover the iSCSI target on the array:

      `iscsiadm -m discovery -t st -p <ISCSI target IP address>`

   2. List the available iSCSI target nodes:

      `iscsiadm -m node`

   3. Log on to the iSCSI target node:

      `iscsiadm -m node -T $[target_node_iqn] -l`

8. LVM configurations are not automatically restored during the upgrade process due to changes between the Linux OS versions (RHEL 7 and Rocky Linux 8). If you have any Logical Volumes (LVs) created on 2.X, complete the following steps to bring back the LVs after migration to 3.x:

   1. Retrieve the `lvm.conf` backup from `/ws/ddb/cvmanager/share/<hostname>/cv_backup_data.tgz`file on the remote cache node.

   2. Apply the required filter changes in the current `lvm.conf` file.

   3. To bring back the LVs online, run the following commands:

          pvscan
          vgscan
          lvscan
          vgchange -ay <vgname>

×

Loading...