github protection licensing

Hey @lborek - I flagged this for one of our licensing specialists, so hoping they should get an answer for you soon.

We have escalated this to our sales team, as Commvault is just way to expensive. Of course I can't look into the wallet of others but we pay way more for a single VOI license than what other competitive solutions like cloudback and gitprotect ask. 

+1. Not a killer if you have 100 repos, but our usecase is ~ 10k. 

@Stephen Gracon  are you sure if it’s only licensing method? What if we have only capacity license available? 

We have the same situation. In case you use tools like Chef, Ansible you normally create a repo per configuration item. This will result in a huge amount of repositories while the actual amount of data in size is limited to just a few KB. So in my opinion they should treat it as unstructured data or for example use a 10 repositories to 1 VOI ratio. 

@lborek - for our customers with a capacity-only configuration without VM-based licensing, Git/Azure DevOps will consume capacity. It is only with the introduction of VM-based licensing that metering shifts to consume Virtual Operating Instances.

@Onno van den Berg  - we strongly appreciate our customers/partners feedback and will forward your comments to the Product Owner.

Received wording that the current model for customers not using capacity based licensing, so in our cases Commvault Complete for Virtualized environments, will remain intact. This effectively means Commvault calculates 1 x VOI per repository. We've relayed it back to our customers and now they are moving away to point solutions…….