When running the Load Balance Index Servers workflow, are there any precautions to take into consideration? Should any of the services on the main CommCell be suspended? Should this be done when there is a window where there are no jobs running? What is the best practice before running this workflow?
Load Balance Index Servers: Precautions, impact to running

Best answer by Marcelo Mansano
Hi Jonathan,
Thank you for your questions, it will help us enrich our documentation with missing information .
Answering them:
- Are there any precautions to take into consideration?
The main precautions to take here is to verify that you have other Media Agents that can receive the load from overloaded ones. We also recommend that the overloaded Media Agent to have at least 5% of total disk space of index cache disk free to be used during the migration process (copy from the old to the new server).
There is no need to disabled schedules or stop any jobs during the load balance process, the index backend will take care of locking and making sure everything is protected during the migration process.
- Should any of the services on the main CommCell be suspended?
No, that's not required or recommended in this situation, the CommCell needs to be up-and-running for the workflow to succeed.
- Should this be done when there is a window where there are no jobs running?
No, that's also not required, although it can help accelerate the process, there is not need jobs to suspended during the workflow run.
- What is the best practice before running this workflow?
There are three points we should observe before running this workflow:
1. Certify that the overloaded index server's cache disk should have ~5% of free disk space.
2. Certify that the overloaded index server has shared data-path with other Media Agents, so we can use those for index migration. This can be done by verifying the primary copy of the existing Storage Policies' data-path and check if there are more than one Media Agent there.
3. Certify that the index servers are connected and ready (Commvault processes are up-and-running), and that they can communicate with themselves.
You can always check the "Index Server Load Report" to see the status and what's the recommended management steps there.
As mentioned by wgrande, we have a default schedule that runs the workflow once every month (last Sunday), but I can recommend you to create a new or change the schedule to run the workflow weekly - this way you won’t need to worry with index cache space usage.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.