Skip to main content

 

Druva Documentation

Phoenix Credits

Overview of credits

Phoenix introduces "Credits" to extend its consumption-based pricing capabilities. It allows you to pre-purchase Phoenix storage using credits and in-effect pay only for the storage that you consume. The Dashboard provides various credits and consumption-related graphs to track the purchased credits and storage consumption on the Phoenix Portal. The credit balance and cumulative credits consumed till date are updated based on the storage consumption at 12:15 AM UTC, everyday.

NotePhoenix credits are not applicable to customers onboarded through the AWS Marketplace . No credits-related information will be available to these customers on the Phoenix Management Console.

How storage purchase translates into credit allocation?

Phoenix allows you to purchase storage in terms of credits. One credit is defined as an average usage of 1 TB storage over a period of a calendar month. Credits are purchased in TB months.

Credits purchased = Storage purchased in TB * Duration for which the storage is purchased in months

The average usage of credits in a month can be calculated as the total credit consumption in that month divided by the total number of days in that calendar month.

Average credit usage in a month = (Credit utilized on day 1 + Credit utilized on day 2 +.....+ Credit utilized on day N)/N 

where, "N" denotes the number of days in that calendar month.

Example:

Consider that you purchase a 10 TB Phoenix storage for a contract term of one year, for example, on January 1, 2017.

For the initial purchase, 

  • Storage duration = Contract duration = 365 days
  • Credits purchased (TB months) = 10*storage duration*12/365 = 10*365*12/365 =120 TB months

When you purchase a 10 TB storage for one year, 120 credits (TB months) are credited to your account.

You can calculate the credits utilized until a particular day during the contract term.

For example, to calculate the total credits consumed up to December 20, 

  • Credits purchased up to November 30 = 10*365*11/365 = 110  TB months
  • Credits purchased from December 1 through December 20 =  10*20*12/365 = 6.5  TB months
  • Credits purchased for partial month January 1 through December 20 = 110 + 6.5 = 116.5 TB months

How storage usage translate into credit consumption?

The credit consumption is calculated at the end of each day, at 12:15 AM UTC everyday. It signifies the difference between the credit utilized on the previous day and the credit consumed at the end of that particular day. Based on the credit consumption calculation, the credit balance is updated. This updated credit balance reflects on the Phoenix Dashboard at the end of each day.

Balance credits at the end of a particular day = [Balance credit on the previous day - Credit consumed in that day]

Credit consumed in that day (TB months) = Phoenix storage usage at the end of the day *12/365 

Example:

Consider that the storage used on January 1, 2017 and January 2, 2017 are 1 TB and 1.5 TB, respectively.

  • Credits consumed on January 1, 2017 = 1*12/365 = 0.03 

Similarly,

  • Credits consumed (TB months) on January 2, 2017 = 1.5*12/365 = 0.05
  • Credit Balance at the end of January 2, 2017 = 120-(0.03+0.05)= 119.92

For more information about various credit consumption scenarios, see Credit consumption scenarios.

How additional storage purchase translate to new credit balance?

You can purchase additional credits to purchase additional storage at any point of time. If the customer type transits from the Evaluation mode to the Commercial mode, the previous balance credits are not carried forward. However, if there is no change in the customer type, the previous balance credits are added to the additional credits purchased.

Additional credits  (TB months)= Storage purchased (TB days) * Duration for which the storage is purchased (days) * 12/365

Revised Balance Credits = Credits Balance + Additional purchased credits

Example:

Consider that you purchased an additional 500 GB storage on February 15, 2017 for a duration of two years. 

Storage purchase duration from February 15, 2017 through February 14, 2019 = 730 days

Let's assume that the Credit Balance on February 15, 2017, is 110.

  • Additional Credits Purchased =  [(500/1024)*730]*12/365=11.71
  • Revised Credit Balance = 110+11.71 = 121.71

How is overage calculated?

When the credit balance falls below zero, any further storage consumption leads to an overage.

Example:

Consider that the Credit Balance on a particular day, for example, February 15, 2017, is 2, and consumes additional 2.5 and 4 credits during the next consecutive days, respectively.

  • Credit Balance on February 15, 2017 = 2
  • Credit Consumed on February 16, 2017 = 2.5
  • Credit Consumed on February 17, 2017 = 4
  • Ending Credit Balance on February 16, 2017 = 2-2.5 = -0.5
  • Ending Credit Balance on February 17, 2017 = -0.5-4 = -4.5

Therefore, the additional utilization of credits result in an overage of 4.5 credits.

Credit consumption scenarios

The following section describes various credit consumption scenarios.

Purchased credits are all consumed mid-contract

If you consume all the credits before end of the contract, you can do the following:

  • Purchase additional credits
    You can purchase additional credits to purchase additional storage. The revised credit balance will be calculated as the addition of the current balance and the additional credits purchased. 
  • Pay for overage at the end of each month
    The credit consumption leads to an overage, if credits consumed for a particular days are greater than the ending credit balance of the previous day. In case of an overage, when you renew contract and purchase additional storage, the unbilled overage from the previous contact period is deducted from the additional credits purchased.

Purchased credits are not completely consumed at the end of contract period and customer renews the contract

The balance credits from the previous contract period are added to the credits purchased in the new contract period.

Purchased credits are not completely consumed at the end of contract period and customer terminates the services

Phoenix stops data backup as soon as the contract period is over, however, it continues to restore data for a grace period of 90 days after the expiry date. Credits continue to be consumed for these 90 days after which the account is deleted. In case of an overage, you are charged for the additional credits consumed during these 90 days.