Skip to main content
commvault.com commvault.com
Question

Migrating Tape Library to HyperScale Edge and Retiring Old MediaAgent - Best Practices & Known Issues

  • May 17, 2026
  • 2 replies
  • 38 views
J
Explorer
Forum|alt.badge.img+7

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:

  1. Re-zone the FC tape library to the new HyperScale Edge node.

  2. Validate OS-level hardware detection on the Edge node.

  3. Use Expert Storage Configuration to perform Exhaustive Detection, adding the new Edge MA to the library while keeping the existing configuration intact.

  4. Execute "Change Data Path" on the relevant Storage Policy Copies to point to the new Edge MA.

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

2 replies

K
Vaulter
Forum|alt.badge.img+6
  • kkarthikkVaulter
  • Vaulter
  • May 28, 2026

Hi ​@Jean-Paul ,

Please find the details on migrating the tape library to hyperscale edge node.

  • HyperScale Edge supports FC-attached tape libraries if the hardware is compatible; please ensure proper FC zoning, HBA recognition, and that both the tape drives and medium changer are visible at the OS level
  • The OS must detect both the tape drives and the medium changer. For FC, ensure zoning is correct and the HBA is recognized by the OS.
  • HyperScale Edge uses Linux inbox drivers for tape devices (sg for drives, ch for medium changer).
  • For IBM tape drives, if you require the lin_tape driver, it must be custom-built for your kernel. Would request you to contact Commvault Support for a pre-built package if needed. 
  • Below is Tape Library Support for HyperScale X Reference Architecture. 

https://documentation.commvault.com/v11/software/tape_library_support_for_hyperscale_x.html

  • As a best practice it recommended to have separate disk and tape traffic by using different physical FC ports or HBAs, confirm OS-level visibility before proceeding with Commvault configuration, and ensure that only one MediaAgent controls the tape library at a time to avoid conflicts
  • During the migration, add the new MediaAgent to the correct Drive Pool and Master Drive Pool (if applicable), and avoid deconfiguring the tape library as this can break storage policies or lead to orphaned media, run Exhaustive Detection, add the new MediaAgent to the library
  • Update the Storage Policy Copy data paths to point to the new MediaAgent and ensure both backup and restore operations are tested successfully after the change


Before running Exhaustive Detection, you can verify SCSI device visibility using:


lsscsi -g | grep tape
lsscsi -g | grep medium

and confirm FC HBA visibility using:
cat /sys/class/fc_host/host*/port_name

to ensure all tape drives, the medium changer, and FC HBA ports are properly detected at the OS level.


Please let me know in case of any queries.

Regards,
Karthik

J
Explorer
Forum|alt.badge.img+7
  • Jean-PaulExplorer
  • Author
  • Explorer
  • May 28, 2026

Hello,

 

I appreciate your help. Additionally, I thought this command was helpful.
​​​​​​​/bin/rescan-scsi-bus.sh -a

Readiverse Academy Certifications Tier

description of image
Terms & ConditionsAccessibility statement