Druva Phoenix extends its consumption-based pricing capabilities by allowing you to pre-purchase storage in terms of credits. With credits, you can pay only for the actual storage consumed in the Phoenix Cloud.
The Credits Balance graph on the Dashboard depicts the credit utilization based on storage consumption. The credit balance and cumulative credits consumed till date are updated based on storage consumption at 12:15 AM UTC, every day.
Note: Phoenix credits do not apply to the customers that are onboarded through the AWS Marketplace. The Phoenix Management Console does not display any credit-related information to these customers.
Credit describes the prepaid storage that is consumed as the data is stored in the Phoenix Cloud. One Phoenix credit allows you to store 1 TB of deduplicated data in the Phoenix Cloud for one month. A credit is expressed in TB-Month.
You can pre-purchase the Phoenix credits depending on the volume of your organization’s data to be stored in the Phoenix Cloud. For example, if your organization needs to store an average of 10 TB of deduplicated data in the Phoenix Cloud each month for the next one year, you need to purchase 120 credits (TB-Months) that would be consumed as data is stored in the Phoenix Cloud.
Druva Phoenix billing mechanism charges for the actual storage consumed in the Phoenix Cloud. The Phoenix Management Console displays the balance credits in TB-Months. However, for more accurate calculation, Druva Phoenix calculates the actual credits in TB-Days and then converts the value into TB-Months. Druva Phoenix converts the credits in TB-Months into a daily equivalent in TB-Days by dividing the credits by 12 and multiplying by 365.
One TB-Month = (1/12)*365 = 30.42 TB-Days
Credits are then reduced by the daily amount stored in the Phoenix Cloud, after deduplication. If the Phoenix Cloud stores 1 TB data over 30.42 days, Druva Phoenix consumes one credit. Similarly, Druva Phoenix consumes one credit if the Phoenix Cloud stores 30.42 TB data in one day as illustrated in the following diagram.
For more information about various credit consumption scenarios, see Credit consumption scenarios.
You can purchase additional credits to purchase additional storage at any point in time. If the customer type transits from the Evaluation mode to the Commercial mode, the previous balance credits are not carried over. However, if there is no change in the customer type, the previous balance credits are added to the additional credits purchased.
Example: Consider that you purchased an additional 500 GB storage on February 15, 2017, for 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
When you consume all of the pre-purchased credits, you can purchase more Phoenix credits to continue the data storage to the Phoenix Cloud. However, when the credit balance falls below zero, any further storage consumption leads to an overage. Phoenix applies on-demand pricing to the 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 example illustrates the credit consumption, carry-over, and overage scenarios for the given backup data:
- Source data: 150 TB
- Estimated cloud storage after deduplication: 100 TB
- Purchased Phoenix credits: 1200 (TB-Months)
Where 100 TB data is stored for 12 months.
The following graph illustrates the credit consumption data for a regular deployment where all the credits are consumed over 12 months.
The following graph illustrates the credit consumption data for a slow deployment. In this deployment, Druva Phoenix carries over the balance credits.
The following graph illustrates the credit consumption data for fast deployment. For such a deployment, Phoenix applies on-demand pricing to the credits consumed beyond the purchased credits.