Overview

Druva 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 Druva 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: Druva credits do not apply to the customers that are onboarded through the AWS Marketplace. The Hybrid Workloads Management Console does not display any credit-related information to these customers.

Credits

Credits describe the prepaid storage that is consumed as the data is stored in the Druva Cloud. One Druva credit allows you to store 1 TB of deduplicated data in the Druva Cloud for one month. A credit is expressed in TB-Month.

You can pre-purchase the Druva credits depending on the volume of your organization’s data to be stored in the Druva Cloud. For example, if your organization needs to store an average of 10 TB of deduplicated data in the Druva 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 Druva Cloud.

Credit term

Druva gives you an insight into the cogent lifecycle of credit utilization during the contract term of your organization. To simplify the credit management process, Druva displays the credit term along with the credit balance on the Hybrid Workloads Management Console. A term is a period during which the purchased credits are available for consumption. When you purchase Druva credits, Druva displays the term on the Hybrid Workloads Management Console as specified in your contract. For example, Jun 01, 2020 - May 31, 2021. 

Druva performs an in-depth and real-time analysis of the storage consumption trend of your organization for the last 90 days. 

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. 

Druva requires you to consume at least 80% of the purchased credits during the term. On the contract renewal, Druva allows you to carry over a maximum of 20% of the purchased credits from the current term to the next term.

Note: The additional credits purchased during a term must be consumed within the same term.

Credit consumption

Druva billing mechanism charges for the actual storage consumed in the Druva Cloud. The Hybrid Workloads Management Console displays the balance credits in TB-Months. However, for more accurate calculation, Druva calculates the actual credits in TB-Days and then converts the value into TB-Months. Druva 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 Druva Cloud, after deduplication. If the Druva Cloud stores 1 TB data over 30.42 days, Druva consumes one credit. Similarly, Druva consumes one credit if the Druva 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.

Credit balance

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 Druva credits to continue the data storage to the Druva Cloud. When your purchased credits exhaust, Druva continues your data storage to the Druva Cloud and displays the excess credits consumed (below zero) in red on the dashboard. Druva 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 Druva credits: 1200 (TB-Months)
  Where 100 TB data is stored for 12 months.