I’m deploying a 2 node grid pair (local storage shared using dataserver IP), these servers also have the virtual server agent deployed and are both defined in the pseudo client.
When I take node 1 offline (which is the top node in the VSA Proxy order) simulate a failure the VSA backups go to a waiting state with “14:201” Index from previous job was not found on MediaAgent, When I take node 2 offline the MediaAgent resources failover as you’d expect
The current VMware pseudo client is V1 indexing, if I create a new pseudo client and upgrade it to V2 indexing will this resolve the issue and allow jobs to continue to run if the primary VSA proxy/MediaAgent is offline?
Also, I know that you need to disable the existing pseudo client, create a new one, run the workflows to update / import configs, but can I get away with just creating a new pseudo client and running the upgrade to v2 workflow (i’ll happily re-create the configuration) and leaving the old pseudo client running the legacy environment until I cut it over?
Best answer by NunoS
The VSA v1 backup job that goes into waiting should then go ahead and kick off an index restore from the backup media to restore the index to the MA that is online and proceeded the back up from there, as long as the second MA has access to the data path that the backups jobs were written to. If this not working, a support case is best to then investigate.
Migrating to v2 indexing, would not solve this challenge. v2 indexing still needs to be housed on one of the MAs and will be known as the Index Cache Server for this client. If that MA is down, the same would need to happen; the new MA would have an index restore kicked off to bring back the index from backup media.
For more information on VSA with Indexing v2, we do have a comparison chart as indexing v2 does have some differences in current capabilities between v1 and v2- Comparison of VSA Features with Indexing Version 1 and Indexing Version 2 - https://documentation.commvault.com/commvault/v11_sp20/article?p=114107.htm