Validation request: MediaAgent Hardware Refresh (Same Hostname/IP) with SAN-attached Hitachi Library

Hello everyone,

I am planning a MediaAgent hardware refresh in an enterprise environment. The backend storage is a SAN-attached Hitachi array (Disk Library) connected via Cisco MDS. The Hitachi storage remains unchanged; only the MA server hardware is being replaced.

Environment & Requirements:

• The new MA must retain the exact same Hostname, IP address, and Commvault Client Name.

• DDB and Index Cache are currently on local NVMe/SSD drives and need to be migrated to local NVMe drives on the new server.

• Operating System: Windows Server.

• Commvault environment matches the same Feature Release (FR) and Maintenance Release (MR).

Proposed Execution Plan:

1. Staging: Build the new MA with a temporary Hostname and IP. Install MPIO, HBA firmware, and drivers matching the Hitachi/Cisco Support Matrix.

2. Freeze State: Suspend all jobs, disable Backup/Restore activity on the old MA, and completely stop all Commvault services to prevent DDB corruption.

3. Local Data Copy: Robocopy the DDB and Index Cache folders from the old MA to the new MA over the network.

4. Network Cutover: Shut down the old MA. Swap the temporary IP and Hostname on the new MA to match the old MA's original IP and Hostname. Handle Active Directory Computer Object reset to avoid Trust Relationship failures. Reboot.

5. SAN Cutover: Update Cisco MDS zoning with the new WWPNs. In the Hitachi management interface, swap the WWPNs in the existing Host Group, strictly maintaining the original Host LUN IDs (HLUs).

6. OS Rescan: Rescan disks on the new MA. Verify MPIO paths. Mount the LUNs using the exact same Drive Letters / Mount Points. (Strictly no initialization/formatting).

7. Commvault Installation: Run the Commvault installer. When the existing Client Name is detected, select the Re-Install (Recover) option to generate new certificates and link the existing DB entities to the new hardware hash.

8. Validation: Verify Library Mount Paths, ensure DDB partitions are Online, and run Test Backup/Restore (Out of Place).

Questions for the community:

1. Are there any known bugs or undocumented behaviors with the "Re-Install" method regarding Certificate generation or DDB engine recognition in recent Feature Releases?

2. Regarding MPIO on Windows with Hitachi SAN—are there any specific gotchas or MPIO thrashing issues when bringing these existing LUNs online on a new host before the CV services start?

3. Is there any additional validation required for the Index Cache offline copy before resuming production jobs?

Appreciate direct, technical feedback.