Capacity License - Capacity Calculation

Table of Contents

Usage Calculation

The usage is determined based on the Front-End Terabyte (FET) capacity, which is measured by calculating the amount of data retained in backup, archive, snapshot and replication jobs. The amount of data is measured based on a terabyte (TB) of data defined as 10244 bytes.

Data Protection (Core and Enterprise)

The usage is calculated based on the size of the latest backup jobs of each active client in the CommCell.

What is measured?

Counts 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.

For Virtual Server agents, the guest size is measured towards capacity calculation. See How is the Virtual Machine size calculated? for more information.

For the following agents, the capacity calculation is measured as follows:

  • Oracle, Oracle RAC, SAP for Oracle, Informix

    After identifying the latest backup jobs from each subclient, the license counts the subclient with the largest backup size for every instance.

  • SAP for MAXDB

    Counts the subclient where the largest backup job took place with other parallel backup jobs running along the largest job.

  • DB2, DB2 Multinode

    After identifying the latest backup jobs from each subclient, the license counts the subclient with the largest backup size for every backup set.

  • 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.

The following are license considerations for command-line backups performed directly from third-party applications:

  • The license counts the subclient with the largest backup job.
  • For multi-stream backups, SnapProtect might register these backups as parallel jobs. In this scenario, the license calculates the size of the largest backup by adding up the size of all parallel jobs.

How usage increases?

Capacity usage can increase by:
  • Deploying newer clients with new data
  • Assigning storage policies to content of newly created subclients
  • Backing up more data using a specific storage policy.

How usage decreases?

Capacity usage can decrease by:
  • Deleting a subclient policy

    Even if the backup job is retained, it won't be counted towards measurement.

  • Disabling backups on the subclient
  • Deleting the last full or synthetic full backup

What is excluded from measurement?

  • 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.
  • 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 (a CAL license), Virtual Server Agent jobs will not count towards 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 licenses (CAL licenses), backups performed by laptop users and Edge users will not count towards capacity. For more information about these licenses, see the End Point User sections in Client Access License - Usage Calculation.

Data Archiving (Core and Enterprise)

The usage is calculated based on the size of archive jobs for Simpana OnePass and classic archiver features, legal hold jobs, and Object Link jobs performed in the CommCell. Each archive job is included in the capacity consumption, though it does not include the number of copies.

What is measured?

  • Last backup cycle of each Simpana OnePass subclient

    The last backup cycle includes the latest full or synthetic full backup job, and all incremental jobs that run since the last full or synthetic full job.

    Any subclient that is configured with Simpana OnePass counts towards the capacity calculation (even if archiving rules are not enabled for stub files). For instructions on configuring a subclient with Simpana OnePass, see Enabling Simpana OnePass for your Subclient.

  • All archive jobs for Simpana OnePass for Exchange Mailbox
  • All legal hold jobs
  • All Object Link jobs
  • For traditional archiver agents, the total size of all active archive jobs is measured towards capacity calculation.
  • For Virtual Server agents, the guest size is measured towards capacity calculation. See How is the Virtual Machine size calculated? for more information.

How usage increases?

Capacity usage can increase by running new archive jobs.

How usage decreases?

Capacity usage can decrease by:
  • Deleting a subclient policy

    Even if the archive job is retained, it won't be counted towards measurement.

  • Disabling backups on the subclient
  • Configuring synthetic full backups to check for deleted stubs. This ensures that the archived data copy residing on the disk is considered towards the capacity usage. For more information, see Configuring a Check for Deleted or Moved Files.

What is excluded from measurement?

  • Multiple instances of the same archive job across different copies of a storage policy
  • Jobs from deconfigured clients that are disabled for new archive services
  • Secondary, deduplicated Silo jobs

    Only the original archive job is counted towards measurement and the secondary jobs are excluded.

  • Content Indexing jobs
  • Content Director jobs
  • 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 (a CAL license), Virtual Server Agent jobs will not count towards 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 licenses (CAL licenses), backups performed by laptop users and Edge users will not count towards capacity. For more information about these licenses, see the End Point User sections in Client Access License - Usage Calculation.

Data Protection Snapshot

The usage is calculated based on the size of all the latest SnapProtect backup jobs that have run in the CommCell for all the supported hardware storage arrays.

What is measured?

Latest full SnapProtect backup jobs.

The license measures the size of the snap job for each supported agent as follows:

  • Windows File System, UNIX File System, NAS

    Measures the used size of all snapped volumes.

  • VMware, Microsoft Hyper-V

    Measures the application size of the virtual machines configured on each subclient.

  • Oracle, Oracle RAC

    Measures the total size of all data files in each configured Oracle instance.

  • Microsoft SQL Server, Exchange Database, Notes Database

    Measures the total size of all data files.

  • DB2, DB2 MultiNode, SAP Oracle

    Measures the total size of all data files in each configured database.

How usage increases?

Capacity usage can increase by:
  • Deploying newer clients with new data
  • Assigning storage policies to content of newly created subclients

How usage decreases?

Capacity usage can decrease by:
  • Disabling backups on the subclient
  • Deleting the last SnapProtect backup job

What is excluded from measurement?

  • Standard backup jobs
  • Backup copy jobs (movement to media operations)
  • SnapProtect backup jobs from deconfigured clients or agents
  • For database agents, transaction log backup jobs are not counted
  • If you apply the CPU Sockets on Hypervisor Hosts license (a CAL license), Virtual Server Agent jobs will not count towards capacity. For more information about this license, see CPU Sockets on Hypervisor Hosts.

Data Protection Replication

The usage is calculated based on the size of all the primary snap copies undergoing a SnapVault or SnapMirror operation, which creates a secondary copy referred to as vault/mirror copy. SnapVault and SnapMirror jobs apply only for NetApp storage arrays.

What is measured?

Latest SnapVault and SnapMirror jobs for each primary snap copy.

How usage increases?

Capacity usage can increase depending on the amount of backed up data that you want to vault or mirror.

How usage decreases?

Capacity usage can decrease by:
  • Disabling backups on the subclient
  • Deleting the last SnapVault and SnapMirror jobs

What is excluded from measurement?

Multiple vault and mirror copies in the same storage policy. Vault and mirror copies of the same primary snap copy is not counted.

Example: How the Capacity Usage for Data Protection and Data Archiving Licenses is Calculated for a Client

When you apply the license, the license is consumed by taking the latest backup (full or synthetic full). All active archive jobs are taken into consideration while consuming license.

The following table provides an example of how the capacity usage is calculated based on the amount of data being backed up.

Clients in CommCell Agents Installed Job Type Data Backed Up (in TB) Notes
Client 1 Windows File System iDataAgent Full/Synthetic Full Backup 11 yesterday The capacity consumed by Client 1 will be 5 TB as the latest data being backed up using full/synthetic full backup is 5 TB.
Windows File System iDataAgent Full/Synthetic Full Backup 5 today
    Total Data Protection Capacity for Client 1 5
Client 2 Windows File System iDataAgent Full Backup 8 yesterday For Windows File System iDataAgent, the latest consumption of 2 TB will not be consumed because data is backed up using a differential backup. The capacity is consumed for the latest data using full/synthetic full backups only.

Therefore, the capacity consumed by Client 2 is:

  • 8 TB of data for Windows File System iDataAgent
  • 10 TB of Data for SQL iDataAgent
Windows File System iDataAgent Differential Backup 2 today
SQL iDataAgent Full Backup 10 today
    Total Data Protection Capacity for Client 2 8 + 10 = 18
Client 2 File Archiver for Windows Agent Archive (active) 12 today For Client 2 that has File Archiver for Windows Agent and Exchange Mailbox Archiver Agent, the total data archive capacity is the addition of the active archive jobs, which is 14. Therefore, 14 TB of data is counted towards the usage.
Exchange Mailbox Archiver Agent Archive (active) 2 today
    Total Data Archive Capacity for Client 2 12 + 2 = 14

Addressing Over-Capacity Situations

The following table describes how the CommServe responds at various stages of the capacity usage:

Capacity Usage (in Percentages) How does the CommServe respond?
At 85% Event messages are displayed in the Event Viewer window to indicate that you are approaching your licensing limits.

The graph for the capacity license consumption in the License Administration dialog box changes from green to yellow to indicate warning.

Between 85% and 110% Event messages continue to be displayed in the Event Viewer window every time you run a backup job.

When the capacity usage reaches 95%, the graph for the capacity license consumption in the License Administration dialog box changes from yellow to red to indicate warning.

The CommServe gives you an additional 10% of capacity to allow your backup jobs to run by delaying the over-capacity status to 110%.

At 110% Backup jobs go into waiting state (restore and administration jobs are not affected).

The License Administration dialog box displays the over-capacity status.

When the capacity usage reaches 110%, use the following steps to resume the backup jobs by resetting the capacity usage:

  1. From the CommCell Console ribbon, click the Tools tab and then click License Administration.

  2. In the Capacity tab of the License Administration dialog box, do the following:
    1. Click Save to save the report as a file. Then, send the file to your software provider so you can receive a new license with an upgraded capacity.
    2. Click Reset to resume the jobs for a grace period of 72 hours.
  3. Click Close to exit the License Administration dialog box.

    If the first 72 hours have passed and the license usage continues to display 110% or more, continue to use the reset operation every 72 hours. The reset operation can be used for a total of 10 times. This gives you 30 days to obtain a new license with an upgraded capacity.

To decrease the capacity usage while you wait for the new license, you can delete the largest backup jobs and run data aging operations. If the capacity usage decreases below 110%, the CommServe resets the over-capacity condition and all jobs are resumed. The grace period counter also resets to 0, and the Reset button becomes unavailable.