Capacity License - FAQ
- Are Synthetic Full and Incremental backups calculated in the License Summary report?
- Do Backup Copy jobs count towards capacity usage?
- Do I need additional licenses after upgrading from a previous version?
- Do SnapProtect operations count towards capacity usage?
- How do I exclude unnecessary backups from being counted against the capacity usage calculation?
- How do I use this license if I have upgraded from a previous version?
- How can I track license expiration?
- How can I track the capacity usage?
- How can I decrease the capacity usage?
- How is my data calculated?
- Why is the application size for my backup different than my used disk space?
- What factors influence application size?
- How is the Virtual Machine size calculated?
- How much data growth should I anticipate?
- I see the Snapshot and Replication license in my License Details, am I being charged for them?
- What do I do when the capacity usage exceeds the available capacity?
- What happens when the capacity is exceeded?
- What is measured and excluded from backup and archiving jobs?
- What is the difference between Traditional and Capacity License?
- What should I do when the license expires?
- Why is the capacity information different between the License Summary Report and the License Usage by Capacity graph?
- Why is the Reset button not available?
Yes. The License Summary Report measures synthetic full and incremental backup along with full backups to calculate the total backup job size of a client.
Yes. Backup copy jobs count towards the capacity usage. Backup copy jobs are measured by the Backup license.
No, it is not required.
Yes. SnapProtect operations are measured by the Snapshot and Replication licenses. The availability of these licenses do not change the current capacity calculation done by the Backup license.
If you perform SnapProtect operations in your CommCell environment, you must contact your software provider to obtain the snapshot and replication licenses based on your current capacity usage. See Calculating the Capacity Usage for more information.
To exclude unnecessary backups, disable backup operations at the subclient level.
- Right-click the <Subclient> and click Properties.
- Click the Activity Control tab
- Clear the Enable Backup check box and click OK.
There are two ways to use capacity based licensing:
- If you already have capacity licenses, contact your software provider and obtain new licenses.
- If you do not have capacity licenses, contact your software provider to obtain and apply new licenses.
You configure an alert to track the expiration of your CommServe license. See Capacity License - Reports for Monitoring Capacity for more information.
You can check the status of the capacity usage in the CommCell from the capacity dashboard displayed in the Licensing and Registration (Capacity) dialog box. See Capacity License - Capacity Dashboard for more information.
See the How usage decreases? sections in Capacity Calculation - Capacity Calculation.
- Backup jobs are calculated by determining the last full or synthetic full job for each client. The jobs are counted once, regardless of the number of copies the job could exist in.
- Archive jobs are calculated by determining the total number of running jobs and completed jobs in your CommCell environment.
- Oracle backup jobs are calculated based on the following:
- If data and logs are included in the backup for the same subclient, the application size used for capacity calculation includes both data and logs.
- If multiple jobs are run on the same subclient, the size of the latest full backup is considered.
- If there are backups from many subclients, the latest backup with the largest application size is considered.
For example, assume you have subclient01 with two full backups (8GB and 6GB respectively), and subclient02 with one full backup (7GB).
subclient02 is considered for data usage because the application size from the latest backup of subclient01 is lesser than the backup from subclient02.
In SnapProtect software, application size is the amount of data being protected. File deletion and file versioning settings tend to make application size for a file different from the disk space that file consumes on a backed-up disk. The retention rules you set for a subclient directly affect the application size for that subclient by controlling how long a locally deleted file continues to be backed up before ultimately being erased from backup (deletion), and how many versions of a file are retained before the oldest version is erased from backup (versioning).
Application size is determined by the size of data being backed up, and subclient-level retention rules. These are the four retention settings and their effects:
- Type 1: Retention of deleted items.
The Subclient Properties (Retention) dialog box provides three rules for controlling how long each of the following deleted item types is carried forward through successive synthetic full backups based on time, before finally being erased:
- For files deleted by user. This is when a user deletes a file directly from disk.
- For stubs deleted by user (OnePass only). This is when a user deletes archived data by deleting its stub from the disk.
- For files deleted by archiving jobs (OnePass only). This is when retention rules result in the system deleting a file.
The longer files are kept, the larger the application size is, because more files are being retained (carried forward into successive backups) at any point in time.
- Type 2: Retention of a number of versions.
The number of versions of a file that are kept is controlled by the Versions setting for the subclient. Each version that is kept adds to the application size because each version adds to the amount of data in the backup.
For further details on these settings, see Subclient Properties (Retention).
Virtual machine backup job data for capacity licensing usage is calculated as follows:
- For streaming backups and backup copy jobs, the capacity usage is based on the guest size for all virtual machines being backed up.
- For SnapProtect backups, the capacity usage is based on the application size for the virtual machines being backed up.
In the License Summary Report, the Job Size column lists guest sizes for virtual machines included in full or synthetic full streaming backups (including backup copy jobs) and application sizes for snapshots.
Capacity usage is summarized as follows:
- Virtual machine streaming backups are included in the Backup license count (depending on the storage policy configuration).
- Backup copy operations are included in the Backup license count.
- Archived VMs are included in the Archive license count.
- SnapProtect backups are included in the Snapshot count.
When the same virtual machine is included in multiple backup jobs, only one of the jobs counts against capacity usage. If a virtual machine is included in multiple subclients, the latest backup provides the size included in overall capacity usage. If a virtual machine is included in both backups and archiving jobs, the guest size for the VM counts toward the Backup license.
Logical volume manager (LVM) metadata processing for volumes encrypted using BitLocker is currently not supported. Decrypting contents of such volumes may not be feasible during backup because decryption requires a recovery password or a decryption key. Because metadata collection for the volume fails, the reported guest size for virtual machines with encrypted volumes may be incorrect and a file-level browse operation for the encrypted volume cannot display file information.
When capacity licensing is used, the used space as reported by the guest OS for the virtual machine is reported against licensed capacity. For example, if the guest OS shows 20 GB used on a 100 GB disk, 20 GB is what counts against the licensed capacity. This is the case even if a different figure is reported for VM disks on the datastore, and is not affected by deduplication or compression.
For more information about virtual machine sizes, see Size Measures for Virtual Machines.
Verifying Backup Job Data for Virtual Machines
To review backup information for virtual machines, generate a VM Backup Report.
Alternatively, you can log in to the CommServe host using qlogin and run the following stored procedure on the CommServe database:
qoperation execscript -sn QS_CLAGetVSADetails –cs commserve_host_name –file file_name -format csv
The resulting output shows the size of the latest backup job for each virtual machine. The size value is the guest size for the VM, or the used space if guest size is unavailable; the size value for all VMs is used in the overall capacity licensing calculation.
The output also shows which license category each VM counts against, and provides instance, backup set, subclient, and job information for each VM.
Surveys of numerous customer sites reveal that production data increases incrementally at an annual rate of 20 to 30 percent. When the available free capacity nears zero or if the capacity reached is almost 100% of the allocated capacity, then it becomes necessary to purchase additional capacity to satisfy the needs.
If the data size increases over time due to new data growth, then the size of protection jobs and the usage measure increase at a similar rate. However, if data is deleted, or filters are used to constrain the amount of protected data, then the usage measurement will decline over time.
Yes. If you see the Snapshot and Replication licenses listed on the License Details tab of Licensing and Registration dialog box, then it means you have purchased and applied the licenses to the CommCell.
SnapProtect backups and SnapVault/SnapMirror jobs are measured by the Snapshot and Replication licenses.
If you have exceeded the available capacity, reset the capacity usage from the Licensing and Registration dialog box to reactivate the CommCell for 96 hours. For more information, see Addressing Over-Capacity Situations.
When the license usage reaches 110%, backup jobs go into waiting state. However, you can resume the jobs by resetting the license usage. The CommServe will display a message in the Event Viewer when no more resets can be performed.
- For backup jobs, refer to Capacity Calculation - Backup usage for more information.
- For archiving jobs, refer to Capacity Calculation - Archive usage for more information.
The capacity-based licensing provides more flexibility than the traditional agent-based licensing by allowing you to focus on how to best protect your data, regardless of:
- What client/agent is used, and
- Where the data is stored (deduplication, tape drives, etc)
The following table compares the benefits of the two licensing mechanisms.
|Traditional Agent-Based Licensing||Capacity-Based Licensing|
Contains modular components licensed by client, agent, and back-end storage policy capacity or feature enablers. Requires the individual purchase of each component.
Allows you to purchase licenses based on the amount of data you backed up or archived. Consolidates and simplifies your licensing needs.
Licensing is dependent on agent types, client quantities and copy of store pools (deduplication, tape drives, etc). Exact number of licenses need to be purchased to meet individual deployment and configuration needs.
|Freedom to configure as per Needs
Each capacity license includes a wide variety of supported agents and features, and no physical limits are imposed on the quantity of clients used or the number of copies managed.
Bundled licenses are available for advanced solutions that need a combination of agents and options to be configured. This requires purchasing the exact license bundles to use the advanced solutions.
|Single Capacity License
The following capacity licenses offer the full feature set of SnapProtect to fit your configuration needs, and gives you the flexibility to change it at any time.
When you change the operating system, the CommCell license key needs to be updated as well. The existing license types might need to be swapped or a new license needs to be purchased.
The unlimited client options encoded in a capacity license allow the redeployment of new agents without the need to change the license key.
|More number of Licenses required
Back-end capacity licensing can become expensive as multiple copies are deployed in a storage policy. For example, an active deduplicated recovery copy and secondary DASH copy recovering the same data will use two times the deduplication database licensing requirements.
|Front End Capacity Size is counted
A capacity license measures the front-end capacity size. Front-end capacity allows unlimited quantities of secondary copies (deduplicated recovery copies, etc.) and eliminates licensing costs on the managed data sets.
Additional clients, back-end/storage policy capacity (such as Advanced Deduplication Option Store capacity, or tape drives), or other advanced options might be required as the environment and setup grows. This can be more complicated depending on the configuration.
When the amount of front-end capacity is fully consumed, an additional capacity license can be purchased to satisfy upcoming demands. This can be done without the need to change the license type.
When a capacity license expires, data management jobs will not run (which can be backup, archive, snap, or replication - based on the license type). You must contact your software provider to obtain a new license.
Why is the capacity information different between the License Summary Report and the License Usage by Capacity graph?
Because the capacity information was captured at different times by each report.
- The License Summary Report displays the current capacity usage (at the time you generated the report)
- The License Usage by Capacity graph in the License Summary dialog box is updated every 24 hours, unless a data aging job runs or if the CommServe services are restarted.
You can reset the capacity usage from the Licensing and Registration dialog box. The Reset button is not be available in the following scenarios:
- If you performed the reset operation 8 times.
- If you performed data aging operations to decrease the capacity below 110% of the total used capacity.