Overview
Druva provides a strong reporting mechanism to track credit consumption at each resource level and determine the cost associated with each organization. Hybrid Workloads allows you to create a cost allocation report that provides cost allocation details specific to cost codes. The Cost Allocation Report displays credit consumption details for the created cost codes. The backup set level details of the cost codes can be seen in the Cost Allocation Details report. The Cost Allocation report is generated every day at 12:15 AM UTC. You can download the report that shows credit consumption for a quarter. You can configure Hybrid Workloads to send the Cost Allocation Report through an email on the first calendar day of every month. The report contains credit consumption details of the previous month and the cost allocation information.
Factors that affect report generation
When the cost allocation report is generated, the cost allocation of a particular resource is calculated using the credits consumed by the resource and the cost allocation rate defined for its cost code. Any change in the mapping between the cost code and the administrative group or organization during report generation affects the cost allocation for the cost code. The various factors that affect the cost allocation are listed as follows:
An administrative group is deleted from an organization: The deleted administrative group is not accounted for cost allocation during report generation for that month. The credit usage information for the deleted resources belonging to the administrative groups is displayed under the unaccounted resource details in the Details section of the report. If an administrative group associated with a cost code is deleted, the administrative group is no longer associated with the cost code.
An administrative group is removed from the cost code: The removed administrative group is not accounted for cost allocation during report generation for that month.
An administrator deletes an organization: The organization is deleted from the associated cost code and is not accounted for cost allocation during report generation for that month. If an organization associated with a cost code is deleted, the organization is no longer associated with the cost code.
An organization is removed from the cost code: The removed organization is not accounted for cost allocation during report generation for that month.
The organization is moved from one cost code to another cost code in mid-month. The organization is accounted under the latest cost code for the complete month.
A resource is deleted from the administrative group: The cost allocation for the deleted resource for the current complete month is displayed as unaccounted resource details in the Details section in the report.
A resource is moved from one administrative group to another administrative group in mid-month: The resource is accounted under the latest administrative group for the complete month. If the latest administrative group is associated with any other cost code, the resource is accounted under that cost code.
A backup set is deleted from an organization: The removed backup set is not accounted for cost allocation during report generation for that month.
A backup set is moved from one administrative group to another administrative group in mid-month: The backup set is accounted under the latest administrative group for the complete month. If the latest administrative group is associated with any other cost code, the backup set is accounted under that cost code.
A cost code is deleted: The report details for the current month are deleted. However, Hybrid Workloads maintains the reports for the previous months.
Cost objects are overlapped: If one or more cost codes are mapped to the same administrative group, organization, or backup set, the credit usage entries are duplicated for each cost code.
The following table lists the fields of the Cost Allocation report:
Field | Description |
Month | The month for which the report was generated. |
Cost Code | The entity associated with the administrative groups, organizations, and backup sets to determine the cost allocation for individual resources based on the credit usage. |
Monthly Credits Consumed | The credits consumed by the resources during the reporting month. The credits are calculated in TB Months. For AWS Marketplace customers, storage is consumed in TB Days. |
Cost Allocation Rate ($/GB/Month): | The chargeback rate defined for credit consumption of one GB storage consumed over a period of one month. The cost allocation rate is defined as $/GB/Month. For AWS Marketplace customers, the cost allocation rate is defined as $/GB/Day. |
Monthly Cost | The monthly cost incurred for the storage or credit consumption by all resources associated with each cost code.
The monthly cost is calculated as follows: Cost = Credits consumed * 1024 * Cost allocation rate For AWS Marketplace customers, the cost for the reporting period is calculated as follows: Cost = Storage consumed * 1024 * Cost allocation rate |
Quarterly Cost | The cost incurred during the current quarter for the credit consumption by all resources associated with each cost code. For AWS Marketplace customers, the cumulative cost is incurred for the current quarter for the storage by all resources associated with each cost code. |
|
|
Actions
The following actions can be performed on the Cost Allocation Report page: