I’m planning to use the workflow to migrate the media agent role from Windows 2012 to Windows 2019.
The maglib has 4 mount paths, 17TB in total. The mount paths are different sizes (see screenshot below). Do i need to give my new mount paths the same size storage or can i provision 4x4.5TB mount paths? Is Commvault smart enough to distribute the data evenly over the new mount paths?
I’ve used the workflow successfully already but always on servers with 1 mount path in the maglib.
Thanks in advance
Regards
Fergus
Best answer by Mike Struening
Hi @Fergus !
The Workflow will keep asking for connections from source to destination if there’s multiple paths.
For everyone following along, here’s the Workflow link:
If the old MediaAgent has any disk mount path configured, then the Move Mount Path dialog box appears.
From the Source Path list, select the path that you want to migrate.
From the Destination Path Type list, select a type.
In the Destination Path box, enter the path to which you want to migrate the selected source path.
If you selected Network Path as the Destination Path Type, then from the Network Path Credential list, select a credential.
Click Next.
If the old MediaAgent has more than one disk mount path configured, then the Move Mount Path dialog box appears again till you configure destination path for all the source mount paths.
If the old MediaAgent has any disk mount path configured, then the Move Mount Path dialog box appears.
From the Source Path list, select the path that you want to migrate.
From the Destination Path Type list, select a type.
In the Destination Path box, enter the path to which you want to migrate the selected source path.
If you selected Network Path as the Destination Path Type, then from the Network Path Credential list, select a credential.
Click Next.
If the old MediaAgent has more than one disk mount path configured, then the Move Mount Path dialog box appears again till you configure destination path for all the source mount paths.
We're currently using the Replace MediaAgent workflow, and while it functions correctly, we've noticed performance limitations.
Both the old and new MediaAgents are Windows-based and connected via a 10 Gb network. However, during the workflow execution, the data transfer rate remains between 3.5 to 4.5 Mbps. For large data sets, it has taken up to 65 hours to complete the migration from the old MA to the new one.
When performing a basic file copy via Windows Explorer, we observe similar speeds, likely due to the large number of small files involved. However, when using Robocopy with 30–50 threads, we can achieve transfer speeds close to 10 Mbps, which is a significant improvement.
Given this, we have a few questions:
Is there any way to improve the data copy speed within the Replace MediaAgent workflow?
Are there newer versions of the workflow that address copy performance?
Does the current workflow use a single-threaded/streamed approach, and is it possible to configure it for multiple streams?
Can any part of the workflow's code be modified to enhance performance or enable parallel processing?
We’re exploring whether this bottleneck is workflow-related or something we can optimize with configuration or scripting changes.
Any guidance or suggestions would be greatly appreciated.
