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 Credit 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.
Credits describe 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.
Phoenix gives you an insight into the cogent lifecycle of credit utilization during the contract term of your organization. To simplify the credit management process, Phoenix displays the credit term along with the credit balance on the Phoenix Management Console. A term is a period during which the purchased credits are available for consumption. When you purchase Phoenix credits, Phoenix displays the term on the Phoenix Management Console as specified in your contract. For example, Jun 01, 2020 - May 31, 2021.
Phoenix performs an in-depth and real-time analysis of the storage consumption trend of your organization for the last 90 days. It also intelligently predicts the end date of your term based on the storage consumption and how many credits might lapse or rollover at the end of the term. Therefore, you can make informed decisions whether or not to purchase additional credits to continue backups to the Phoenix Cloud. For more information, see Credit term prediction.
Customers who have onboarded with the new contract type can view the credit term on the Dashboard page, the Analytics page, and on the My Accounts page.
Phoenix requires you to consume at least 80% of the purchased credits during the term. On the contract renewal, Phoenix allows you to carry over a maximum of 20% of the balance credits from the current term to the next term.
Note: The additional credits purchased during a term must be consumed within the same term.
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. When your purchased credits exhaust, Phoenix continues your data storage to the Phoenix Cloud and displays the excess credits consumed (below zero) in red on the dashboard. Phoenix applies on-demand pricing to the credits consumed beyond the purchased credits.
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 4.5 credits will appear in red in the Credit Balance graph.
Credit consumption scenarios
The following example illustrates the credit consumption, carry-over, and credit consumption below zero 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.
Credit term prediction
Phoenix analyzes the storage consumption of your organization. Based on the credit consumption data, Phoenix provides insights into the following details:
- Date until which credits will last based on the consumption pattern.
- Sufficiency of credits to last until the end of the term.
- Excess credits that might expire at the end of the current term.
- Shortfall of credits before the end of the current term. Phoenix also estimates the additional number of credits based on the consumption trend that you need to continue backups until the end of the current term.
Phoenix displays these projections on the Dashboard and Analytics pages, and periodically sends alerts when your organization,
- is predicted to fall short of credits before the end of the term, or
- have excess credits that may go unutilized at the end of the term.
To notify you about the excess credits projected to expire at the end of the term, Phoenix sends emails 30, 15, and 1 day before the term ends. Similarly, Phoenix sends an email to notify about the additional credits required to suffice until the end of the term.
Note: Customers who have onboarded with the new contract type can view the credit consumption predictions on the Dashboard and Analytics pages only after 30 days of storage utilization.
Phoenix intelligently analyzes credit consumption patterns based on the historical consumption of data and predicts the credit balance sufficiency for the current credit term. To record any sudden variance to the storage consumption pattern of your organization, Phoenix requires a leeway of at least 30 days and projects the term details on the Dashboard and Analytics pages. The prediction statistics displayed at any point-in-time is an estimation based on the historical data. The predictions vary for any changes in the storage consumption trend of your organization.
The following sections describe various credit consumption scenarios and how Phoenix make predictions:
For a regular deployment, where the credit consumption of your organization is on-target, the credits are expected to be sufficient enough to last until the end of the term.
The following screenshot shows sample predictions made for a regular deployment:
In a slow deployment of your organization, Phoenix predicts the excess credits that might lapse at the end of the current term. Phoenix predicts the excess credits two months before the term end date and displays it on the Analytics page.
Phoenix allows you to carry over a maximum of 20% of the purchased credits from the current term to the next term on the contract renewal. This intelligence helps you make appropriate decisions for purchasing credits during your contract renewal.
To notify you about the excess credits projected to expire at the end of the term, Phoenix sends emails 30, 15, and 1 day before the term ends.
The following screenshot shows predictions made for a slow deployment:
In a fast deployment of your organization, Phoenix projects the end date of the term based on the storage consumption trend. Phoenix projects the date until which the purchased credits can last. Phoenix also calculates the number of credits that you might fall short of for the current term two months before the predicted day of credit expiry and displays it on the Analytics page.
Phoenix sends an email notification about the additional credits that are projected to suffice the remaining term to continue seamless backups. Phoenix continues data backups to the Phoenix Cloud even after your credits exhaust.
The following screenshot shows sample predictions made for a fast deployment:
View credit balance
Phoenix displays credit balance on the following pages:
The License and Storage section displays the credit balance for all your organizations. See Dashboard.
The Storage Credit section displays the credit balance for all your organizations. See Storage details.
The Total Credits & Storage section displays the credit balance along with the storage consumed by all your resources. See Analytics.
- My Account
The Licensing Details section of the My Account page displays the credit balance along with the licensing details of your organization. See Licensing details.