Capacity report displayed incorrect data when both SQL and Hyper-V roles were enabled on protected Windows servers.
Capacity report displayed incorrect data when both SQL and Hyper-V roles were enabled on single protected Windows server.
To resolve this issue, upgrade your appliance to version 10.1.1-3.
The concurrent use of Hyper-V role and other windows roles are not officially supproted by Microsoft and no test condition was thus created for those configurations.
A defect was present in code that would itemize only SQL or only Hyper-V backups of assets protected on such a single host preventing some units from properly listing their capacity. Under-reported capacity could lead to more limited retention and potentially backup failures.
Notes: If a condition exists where both SQL and Hyper-V co-exist on a single server, after updating to release 10.1.1-3 or higher, the capacity will then be properly calculated to it's correct larger value. This may result in appliance license overages on local UB or physical appliances and may also result in cloud capacity appearing to have increased as well. The correction of this issue does not change how we calculate capacity, nor does it change the amount of data protected; it eliminates an issue that was prior preventing a proper calculation from being realized on systems running unsupported Microsoft configurations.