I am planning an infrastructure refresh where I need to retire an existing MediaAgent and migrate its FC-attached tape library to a newly deployed Commvault HyperScale Edge node.
My main focus is ensuring data path consistency, avoiding any library deconfiguration, and maintaining restore capabilities. The planned high-level workflow is:
-
Re-zone the FC tape library to the new HyperScale Edge node.
-
Validate OS-level hardware detection on the Edge node.
-
Use Expert Storage Configuration to perform Exhaustive Detection, adding the new Edge MA to the library while keeping the existing configuration intact.
-
Execute "Change Data Path" on the relevant Storage Policy Copies to point to the new Edge MA.
-
Perform standard MediaAgent Retirement on the old node.
I am looking for technical validation of this workflow. Specifically:
-
Are there any HyperScale Edge-specific prerequisites or limitations regarding direct-attached or FC-switched tape libraries?
-
What are the known issues regarding existing Drive Pools/Master Drive Pools during the Data Path change in this specific scenario?
-
Are there any specific CLI commands recommended for verifying the SCSI paths natively on the HyperScale Edge Linux OS before triggering the Exhaustive Detection?
I am looking for validated field experience and references to official Commvault documentation.
