I am working with a client and they are frustrated with one particular aspect of CommVault: the subclient selection under a VM backup set that is based on discovery by affinity (in this case data store) creates a significant labor in making multiple sub clients in order to backup the affinity in a load-balanced fashion.
For a detailed example, the company wishes to backup 1 VM per data store at the same time. They've created their backupset based off of the data store affinity. The subclient can have multiple data readers set. However, by setting it to more than 1, it is currently possible that more than one VM will be backed up on the same data store during the discovery process. They would like it to do the following:
1. Contact VCenter for VMs on each data store through a discovery process
2. Notify CommVault of the VMs discovered
3. PER DATA STORE, initiate 1 VM backup concurrently until completion.
My thoughts were creating a checkbox near the data reader part of the subclient that would allow you to "load-balance across all discovered affinities" or something of the sort. Right now CommVault PS is telling them they need to create a subclient per data store and then set the reader to 1, which means alot of work on the customer's behalf with the amount of data stores that they maintain.