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:
-
Create a Secondary Copy on the existing Storage Policies.
-
Set the Target Library as the new HyperScale Storage Pool.
-
Run Auxiliary Copy to sync all data.
-
Once synced, Promote the Secondary Copy to Primary.
-
Decommission the old MA.
My Questions:
-
Is this the recommended workflow for migrating to HyperScale?
-
When creating the Secondary Copy, should I expect any specific behavior regarding the DDB association, since the target is a Storage Pool?
-
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!
