Skip to main content
Druva Documentation

Overview of cost allocation

Druva Phoenix helps IT organizations to automate the process of chargeback reporting when server backup and restore services are provided to various internal departments. This feature allows IT administrators to quickly determine how much storage is being consumed by specific teams, departments, or remote offices. The IT administrator can immediately assign a dollar value to this storage usage and forecast a budget accordingly. 

Phoenix Cost Allocation feature provides the following cost object entities to organize resources in the internal groups:

  • Administrative groups: Servers that belong to a particular department can be grouped into one administrative group.
  • Organizations: Servers that belong to a particular department can be organized into administrative groups belonging to one organization.
  • Backup sets: Data sets belonging to a particular workload, content rule, or backup policy can be organized into one backup set.

After associating resources in your departments to administrative groups, organizations, or backup sets, you can create cost code to define credit consumption rate. The mapping between cost codes and resources enable administrators to determine the cost of credit consumption by the resources in a specified duration. For more information about the Phoenix Cost Allocation feature, see Cost Allocation.

  • Was this article helpful?