After you enable Private Metrics and data collection completes, you can access and configure your Chargeback Details report. The Chargeback Details report is slightly more detailed than the Chargeback report, and enables you to categorize tenant data consumption based on a Service Plan (such as Essential, Standard, or Premium).
Procedure
-
Log on to the Command Center.
-
From the navigation pane, go to Web Console.
-
Click Reports.
-
In the search box in the upper-right area of the page, enter Chargeback.
-
Click the Chargeback Details report.
-
To generate a Chargeback report for a specific tenant:
-
Select the time range for the report (day, week, or month).
-
Select the client group (tenant) by searching for the tenant name.
Select all client groups for the tenant.
-
Click Apply.
-
Results
The Chargeback Summary includes the following information:
|
Features |
Definition |
|---|---|
|
Front End Backup Size |
The amount of data in the largest full backup job from each VM group (subclient) during the specified time period. If no full backup job completed during the specified time period, then it is the amount of data in the largest full backup job from the previous time period. For VMs, this is the largest guest size in the last full backup cycle for the selected time period. For clients that have both VSA and other agents installed, the report displays only the front end size for VSA subclients. Jobs that run on a VM are counted only once, regardless of the number of VM groups that are used to back up the virtual machine. This is Front End data measured at the client prior to compression or deduplication. |
|
Front End Archive Size |
Total Front End tenant data that was archived during the specified time period. This will be 0 for the catalog configured. |
|
Primary App Size |
The amount of application data that was written to primary copies before compression and deduplication, including aged data and pruned data, during the specified time period. For VMs, the application size is the backup size. |
|
Protected App Size |
The size of application data before compression and deduplication, for all active jobs that ran during the specified time period, and in all storage policy copies, including aged data and pruned data. |
|
Media Size |
The amount of data that was saved on storage media during the specified time period, including aged and pruned data. For storage policy copies with deduplication enabled, the media size for each job is calculated based on the average deduplication ratio of the copy, where media size = (application size) * (average deduplication ratio per copy). The average deduplication ratio of a destination copy is calculated by (total size on disk)/(total protected app size) for the destination copy. |
|
Total Protected App Size |
The size of application data before compression and deduplication, for all active jobs that ran at any time, and in all storage policy copies, excluding aged data. For VMs, the application size is the backup size. |
|
Total Media Size |
The amount of all active data that is saved on storage media, including all storage policy copies on all media types, and excluding aged data. For storage policy copies with deduplication enabled, the media size for each job is calculated based on the average deduplication ratio of the copy, where media size = (application size) * (average deduplication ratio per copy). The average deduplication ratio of a destination copy is calculated by (total size on disk)/(total protected app size) for the destination copy. |
As a best practice, use Front End Backup Size be used as the only metric for customer metering and billing. Using any metric that includes media size in deduplication environments is discouraged, because deduplication factors can create inaccurate reporting.
Customers are typically able to manage the consumed storage (or Front End TB) on their infrastructure. This metric is the most commonly adopted and understood metric for Backup as a Service (BaaS) offerings.