Capacity usage is calculated based on the size of the latest backup jobs of each active client in the CommCell.
To view capacity calculations for the CommCell environment, see Capacity Types in the License Summary Report.
The capacity calculation includes the following data:
The application size of the latest full backup or synthetic full backup for each subclient. If the agent has multiple backup sets, the backup set with the largest backup size is counted towards capacity.
All backup copy jobs for Intellisnap backup.
Considerations for Agents
The capacity calculation includes the following data for each agent:
Command-line backups performed directly from third-party applications: The subclient with the largest backup job is used to calculate capacity. For multi-stream backups, Commvault might register these backups as parallel jobs. In this scenario, the size of the largest backup is determined by adding up the size of all parallel jobs.
DB2, DB2 Multinode: After identifying the latest backup jobs from each subclient, the subclient with the largest backup size for every backup set is used to calculate capacity.
Informix, Oracle, Oracle RAC, SAP for Oracle: After the latest backup jobs from each subclient have been identified, the subclient with the largest backup size for every instance is used to calculate capacity.
MySQL, PostgreSQL, SAP HANA, SAP for MAX DB, Sybase: the largest subclient for each backup set or instance is used to calculate capacity.
SharePoint Storage Manager: All SharePoint components configured in a SharePoint Server subclient are calculated as data backed up by the SharePoint Agent, even when other agents are configured to back up or archive some of the SharePoint components.
Virtual Server: The guest VM size is measured to calculate capacity. For more information, see Virtual Machines in the Capacity Calculation.
Capacity Usage Increase
Capacity usage can increase because of any of the following actions:
Deploying newer clients with new data.
Assigning storage policies to content of newly created subclients.
Backing up more data using a specific storage policy.
Capacity Usage Decrease
Capacity usage can decrease because of any of the following actions:
Deleting a subclient policy. Even if the backup job is retained, it won't be counted towards measurement.
Disabling backups on the subclient. For more information, see Disabling backups on the subclient.
Deleting the last full or synthetic full backup.
The following types of data are excluded from the capacity calculation:
Multiple instances of the same backup job across different copies of a storage policy.
For database agents, transaction log backup jobs are not counted.
If the same subclient policy is used in two backup sets, only the one with the largest backup is counted. This eliminates the chances of double counting when a redundant full backup job is run.
Index server backup jobs.
Indexing V2 log backup jobs.
Jobs from deconfigured clients or agents: The deconfigured client releases the license and excludes its jobs from the measurement process. However, if the client is enabled again to run new backup jobs, then the jobs start counting towards the measurement process.
Jobs from deleted subclient policies: The backup job is retained for restore but the subclient is no longer available for new backups.
Secondary, deduplicated Silo backup jobs: Only the original backup job is counted towards measurement and secondary Silo backup jobs are excluded.
Jobs from import operations: Includes jobs that are actively managed in other CommCells, or third-party jobs from the External Data Collector (these jobs qualify as read-only, deconfigured clients).
If you apply the CPU Sockets on Hypervisor Hosts license key, Virtual Server Agent jobs do not count toward capacity. For more information about this license, see CPU Sockets on Hypervisor Hosts.
If you apply the End Point User and End Point Sharing User license keys, backups performed by laptop users and Edge users do not count toward capacity. For more information about these licenses, see Endpoint Users in the License Summary Report.