Skip to main content
commvault.com commvault.com
Question

Best practice for migrating data from Legacy MA to HyperScale Edge (Side-by-Side)

  • January 1, 2026
  • 1 reply
  • 23 views
J
Apprentice
Forum|alt.badge.img+7

Hi everyone,

I am currently performing a hardware refresh/migration from a legacy Media Agent to a new Commvault HyperScale Edge (Single Node).

Current Setup:

  • CommServe is on a separate dedicated server.

  • Legacy MA: Windows Server with local disk libraries (NTFS).

New Setup:

  • HyperScale Edge (Single Node).

  • Already joined to the CommCell, and the HyperScale Storage Pool is created.

Proposed Migration Plan: Since I cannot simply move the DDB/Disk (due to the architecture change to HS Storage Pool), I plan to do a Side-by-Side migration:

  1. Create a Secondary Copy on the existing Storage Policies.

  2. Set the Target Library as the new HyperScale Storage Pool.

  3. Run Auxiliary Copy to sync all data.

  4. Once synced, Promote the Secondary Copy to Primary.

  5. Decommission the old MA.

My Questions:

  1. Is this the recommended workflow for migrating to HyperScale?

  2. When creating the Secondary Copy, should I expect any specific behavior regarding the DDB association, since the target is a Storage Pool?

  3. Are there any specific "gotchas" or performance settings I should be aware of during the Aux Copy phase (e.g., Scalable Resource Allocation)?

Thanks in advance!

1 reply

Bronco
Vaulter
Forum|alt.badge.img+3
  • BroncoVaulter
  • Vaulter
  • January 3, 2026

​@Jean-Paul,

Your migration plan is on the right track and follows Commvault-recommended best practices for moving from a legacy MediaAgent with local disk libraries to a HyperScale Edge (single-node) environment. Here’s a clearer breakdown of your questions and what to expect.

 

[1] Is this the recommended workflow for migrating to HyperScale?

Yes, your plan aligns with Commvault best practices. Creating a secondary copy to the HyperScale Storage Pool, running Aux Copy to sync data, validating restores, then promoting the copy to Primary before retiring the old MediaAgent is the correct and supported approach. It ensures data integrity and gives you a safe rollback path during migration.

 

[2] What happens to the DDB when the target is a Storage Pool?

When you create a secondary copy to the HyperScale Storage Pool, a new DDB is automatically created and associated with that pool. Deduplication must already be enabled on the storage pool, and the new DDB starts a fresh dedupe baseline. Data copied via Aux Copy is rehydrated and then deduplicated again on HyperScale, so initial storage usage may be slightly higher until dedupe savings accumulate. Moving the old DDB is not supported due to architecture differences.

 

[3] Are there any gotchas or performance settings to consider during Aux Copy?

Enable Scalable Resource Allocation to make better use of parallel streams and improve copy performance. Monitor network, disk, and CPU on both MediaAgents, and tune streams gradually if required. Validate test restores from the HyperScale copy before decommissioning the old MA, and avoid deleting or aging data from the old copy until you fully confirm restore coverage and retention behavior.

 

Regards,

Siddharth Gandhi

Terms & ConditionsCookie settingsAccessibility statement