Skip to main content


Druva Documentation


If you are a central IT organization and provide backup and restore capabilities to several internal groups, Phoenix allows you to charge back to the internal groups for the credits consumed by the individual servers. Phoenix Cost Allocation feature provides the following cost object entities to organize servers 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.

After associating servers in your departments to administrative groups or organizations, you can create cost code to define credit consumption rate and determine the cumulative storage expenditures for individual administrative groups and organizations.

The Billing tab on the global dashboard provides the following capabilities:

  • Cost Allocation: Phoenix allows administrators to create and allocate cost codes to administrative groups and organizations. The mapping between cost codes and servers enable administrators to determine the cumulative cost of credit consumption by servers in a specified duration. For more information about the Phoenix Cost Allocation feature, see Cost Allocation.
  • Reports: Phoenix provides a powerful cost allocation reporting mechanism to record credit consumption at each server level. The Cost Allocation Report provides the aggregate usage of the credits consumed by individual servers and determines the cost allocation amount for the consumed credits. For more information about reports, see Billing Reports.