License editions: To understand the applicable license editions, see Plans & Pricing.
Overview
Druva's pricing model includes scalability, flexibility, predictability, cost savings, and security which help businesses of all sizes to manage and protect their backup data effectively and efficiently. Druva utilizes a consumption-based pricing model that is measured in terms of Druva credits thereby allowing you to pay only for the storage that is consumed to protect compressed and deduplicated backup data on Cloud. With Druva credits you can protect data in different storage tiers depending on the frequency of access and data retention requirements.
📝 Note
Druva credits do not apply to the customers that are onboarded through the AWS Marketplace and Managed Service Partners. Druva doesn’t display credit-related information for these customers on the Management Console or Managed Services Center Portal.
What is Druva credit
Druva credit is the unit used within Druva’s Enterprise Workloads ecosystem that calculates the amount of storage that is consumed to protect compressed and deduplicated backup data on Cloud. One Druva credit allows you to protect 1 TB of compressed and deduplicated backup data on Cloud for one month duration.
How are credits calculated
A credit is calculated in TB-Months. One TB Month (1 credit) allows you to protect 1 TB of dedupe backup data on Cloud for one month duration.
Credits purchased = (Dedupe backup data protected in TB) * (Duration in months)
Let us consider your organization needs to protect an average of 10 TB of dedupe backup data for each month for the next one year on Cloud.
So, to protect 10 TB of dedupe backup data in one month, 10 credits are utilized in that particular month. Hence, you need to purchase (10 TB * 12 months) = 120 credits (TB-Months) to protect dedupe backup data on Cloud for one year.
What is credit term
A credit term refers to the duration during which the purchased credits are available for consumption. When you purchase Druva credits, Druva displays the credit term on the Credit Consumption Report page of the Management Console as specified in your contract. For more information, see Credit Consumption Report.
What is credit consumption
Credit consumption refers to the usage of purchased credits in accessing Druva’s Cloud based solutions such as data backup, recovery and management services.
How credit consumption is calculated
Druva’s pricing model charges for the actual storage that is consumed to protect backup data on Cloud after compression and deduplication. However, for more accurate calculation, Druva calculates the daily credit consumption by evaluating the amount of storage consumed to protect dedupe backup data on a particular day and converts this to an equivalent credit consumption value.
The credit consumption in one day is calculated by the below given formula:
Credit consumed in one day = (Dedupe backup data protected in TB in one day * 12) / 365
Alternatively, if the credit consumption is in gigabytes, then the credit consumption in one day is calculated as:
Credit consumed in one day = (Dedupe backup data protected in one day in gigabytes * 12) / (1024 * 365)
Let us consider your organization protects 1 TB of dedupe backup data in one day. So credits consumed on that particular day can be calculated as:
Credit consumed in one day = (1 TB * 12) / 365 = 0.032 credits consumed in one day
Take a look at the following comparison between the backup data protected in one day to the equivalent credits consumed in one day.
Backup data protected/day | Credit conversion | Equivalent credits consumed/day |
1 GB i.e., 1 / 1024 TB | (1 * 12) / (1024 * 365) | 0.000032 credits |
1 TB | 1 * (12 / 365) | 0.032 credits |
10 TB | 10 * (12 / 365) | 0.32 credits |
Credit consumption scenarios
Let us consider your organization requires 100TB of dedupe backup data to be protected on Cloud each month for one year. So, your organization requires (100 TB * 12 months) = 1200 credits (TB-Months) to protect dedupe backup data on Cloud for one year. The following graph illustrates the credit consumption scenarios based on the credit consumption rate of your organization.
On-target credit consumption
On-target credit consumption
When the credits are consumed at the anticipated credit consumption rate for the contract term, it is considered as On-target credit consumption.
Slow credit consumption
Slow credit consumption
When the credits are consumed at a slower rate than that of the anticipated credit consumption rate for the contract term, it is considered as slow credit consumption.
Druva requires you to consume at least 80% of the purchased credits during the contract term. On the contract renewal, Druva allows you to carry over a maximum of 20% of the purchased credits from the current contract term to the next contract term.
Fast credit consumption
Fast credit consumption
When the credits are consumed at a faster rate than that of the anticipated credit consumption rate for the contract term, it is considered as fast credit consumption.
Purchase additional credits
During the contract term, if you are about to use up all the credits you purchased, Druva allows you to purchase additional credits as a part of the current contract term.
Consider if your organization has consumed the purchased credits at a faster rate than that of the anticipated credit consumption rate and is left with a credit balance of 110 credits.
Now your organization estimates to protect an additional 2 TB of dedupe backup data each month for the next two years and plans to purchase additional credits for the same. So the organization needs to purchase additional credits that is calculated as below:
Additional credits purchased = (Additional dedupe backup data protected in TB) * (Duration in months)
i.e., (2 TB * 24 months) = 48 creditsThe revised credits balance after the purchase of additional credits is:
Revised credit balance = (Credit balance) + (Additional credits) i.e., (110 + 48) = 158 credits.
📝 Note
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.
Excess credits consumption
During the contract term, if your purchased credits exhaust, Druva continues to protect your backup data on Cloud for a specific duration and displays the excess credits consumed (below zero) in red on the dashboard.
Consider that the credit balance on a particular day, for example, February 15, 2023, is 7, and consumes additional 2.5, 5, 2, and 3 credits during the next consecutive days, respectively. Therefore, the additional utilization of 5.5 credits will appear in red in the Credit Balance graph. Take a look at the following table that shows the additional credit usage that occurs after the pre-purchased credits are utilized.
Days | Credits consumed | Credit balance |
February 15, 2023 | - | 7 |
February 16, 2023 | 2.5 | (7 - 2.5) = 4.5 |
February 17, 2023 | 5 | (4.5 - 5) = -0.5 |
February 18, 2023 | 2 | (-0.5 - 2) = -2.5 |
February 19, 2023 | 3 | (-2.5 - 3) = -5.5 |
📝 Note
Druva continues to protect your data on Cloud even after your purchased credits are exhausted for a duration of 6 months.
For more information on estimating the number of credits required for the year, you can contact your Sales representative or Support.
What factors impact credit consumption
This section provides details about the factors due to which the credit consumption is impacted.
Early delete fee for LTR data
The Long Term Retention (LTR) feature allows you to retain dedupe backup data having higher RTO value i.e., higher tolerable recovery time with low-maintenance cost. The backup data is protected in Amazon Glacier Deep Archive (GDA as cold tier) for a retention period of one year or longer and reduces the overall data protection cost by 20%. For more information, see About Long Term Retention.
Expand to see formula along with an example
Expand to see formula along with an example
The credit consumption for LTR is calculated by below formula:
Credit Consumption = (Dedupe backup data size in TB) * (Credit consumption rate per TB per month) * (Number of months the data is retained for)
However, If you delete your backup data before the one year retention period completes, Druva charges an early delete fee depending on the size of the data deleted from the cold tier. The early delete fee is recorded in your billing and is calculated by below formula:
Early Delete Fee (in credits) = 0.35 * (12 - Number of months in cold tier) * (Data deleted in TB)
Example: Let us consider if your organization identifies 50 TB of LTR data to be retained for one year duration in cold tier. Now, say after 7 months, your organization identifies 14 TB of data to be deleted from the cold tier. Druva charges an early delete fee for this data that is deleted early from the cold tier and is calculated as:
Early Delete Fee (in credits) = 0.35 * (12 months - 7 months) * (14 TB) i.e., (0.35 * 5 * 14) = 24.5 credits.
📝 Note
Druva does not charge an early delete fee for LTR data that is deleted from warm tier which was intended to be moved to cold tier.
Early delete fee for Archive data
Druva archive is an ultra-low-cost storage tier that protects large files such as large engineering files, images, media, CCTV footages, etc. that are rarely accessed and restored. The backup data is protected in the Archive storage tier for a retention period of one year or longer and reduces the overall data protection cost by 50%. For more information, see About Druva Archive storage tier.
Expand to see formula along with example
Expand to see formula along with example
The credit consumption for Archive data is calculated by below formula:
Credit Consumption = (Dedupe backup data size in TB) * (Credit consumption rate per TB per month) * (Number of months the data is retained for)
However, If you delete your backup data before the one year retention period completes, Druva charges an early delete fee depending on the size of the data deleted from the archive storage tier. The early delete fee is recorded in your billing and is calculated by below formula:
Early Delete Fee (in credits) = 0.35 * (12 - Number of months in archive storage tier) * (Data deleted in TB)
Example: Let us consider if your organization identifies 100 TB of archive data to be retained for one year duration in archive storage tier. Now, say after 9 months, your organization identifies 40 TB of backup data to be deleted from the archive storage tier. Druva charges an early delete fee for this backup data that is deleted early from the archive storage tier and is calculated as:
Early Delete Fee (in credits) = 0.35 * (12 months - 9 months) * (40 TB) i.e., (0.35 * 3 * 40) = 42 credits.
Additional restore fee for Archive data
Druva provides a free restore tier and a paid restore tier that allows you to restore dedupe backup data that is protected in the archive storage tier. You can restore 1% of the archived data (source + changes) for free one-time in a day. Data restored for more than 1% of the archived data (source + changes), will be charged at 1 credit/TB. The unused free data restore capacity is rolled over to the next day. If you restore data more than the available free restore capacity, the restore capacity is reset to zero and again starts to accumulate as the new data is backed up. For more information, Restore fee.
Change rate
Change rate is the change in the storage consumed per day to protect dedupe backup data on Cloud and is expressed as the difference between the Source + Changes data of two consecutive days. Druva calculates change rate in percentage on a daily basis as the change rate between two consecutive days with respect to the current source data of the previous day.
Expand to see formula along with an example
Expand to see formula along with an example
The change rate and change rate percentage are calculated as:
Change rate = (Source + Changes data for current day) - (Source + Changes data for previous day)
Change rate percentage = (Change rate / Current source data of previous day) * 100
The credit consumption is directly proportional to the change rate, i.e., higher the change rate, more is the credit consumption and vice versa.
Example: The below graph depicts the Change Rate trend and Daily Data Change, for a backup set. The change rate on April 26, 2023 is (15.75 GB - 18.71 GB) / 4.35 GB = -68% shows that the Source + Changes data was less as compared to that on April 25, 2023 and hence the credits consumed on April 26, 2023 were less as compared to that on April 25, 2023. Similarly, credits consumed on April 29, 2023 will be more as compared to that on April 28, 2023.
Retention
Druva’s retention feature allows you to keep important data for future access, depending on the value and criticality of data and compliance requirements. The retention period defines the duration for which your dedupe backup data is retained on Cloud. Druva's pricing plans are based on the amount of data being protected, which is determined by the retention period and the frequency of backups that ultimately impacts the credit consumption.
The amount of credit consumption is directly proportional to the retention period. More credits are consumed if the retention period for the deduped back data is higher as Druva requires more storage space, more backup frequency, and potentially more resources to protect and manage the backup data. Conversely, less credits are consumed if the retention period for the dedupe backup data is lower.
Expand to see formula along with an example
Expand to see formula along with an example
Druva provides a default backup policy with the retention settings as shown in the below screenshot.
Now let us consider that your organization requires the backup data to be retained for 7 years instead of 3 years and hence creates a new backup policy with the below settings:
Daily recovery points to be retained for 14 days
Weekly recovery points to be retained for 4 weeks
Monthly recovery point to be retained for 3 months
Yearly recovery points to be retained for 7 years
With these settings, Druva is required to protect and manage backup data for 7 years, this ultimately means that Druva requires more storage space, more backup frequency, and potentially more resources to protect and manage the backup data, which could result in increased credit consumption and hence increased cost to protect and retain data.
📝 Note
The retention period is also an important factor in ensuring that the backup data is properly protected and available when required. If you choose a shorter retention period, there is risk of losing important data if a disaster or data loss occurs outside of that retention period.
Deduplication rate
Deduplication identifies and efficiently eliminates redundant data from the source data ensuring reduced storage space, low credit consumption, and hence lower storage cost.
Dedupe rate has a significant impact on the number of Druva credits required for data protection. A higher dedupe rate means that more duplicate data can be identified and removed, resulting in a greater reduction in storage requirements and, ultimately, lower costs. Conversely, a lower dedupe rate means that less duplicate data can be removed, resulting in higher storage requirements and potentially higher costs in terms of Druva credits.
Expand to see formula along with an example
Expand to see formula along with an example
Let us consider your organization has 150 TB of source data to be protected on Cloud for one year. This 150 TB source data consists of 50 TB of media files (MP3, MP4, JPEG files). Now let us assume that the dedupe rate for the 100 TB of source data is 2.5X and the dedupe rate for the remaining 50 TB of source data (media files) is 1X (considering low dedupe rate for media files as they are stored in compressed format).
Credits consumed for 100TB source data with 2.5X dedupe can be calculated as:
Credits consumed = (Source data) / (Dedupe rate) i.e., 100 TB / 2.5 = 40 credits
Credits consumed for the remaining 50 TB source data (media files) with 1X dedupe can be calculated as:
Credits consumed = (Source data) / (Dedupe rate) i.e., 50 TB / 1 = 50 credits
So, to protect 150 TB of source data with 2.5X dedupe rate, your organization consumes (40 credits + 50 credits) = 90 credits.
📝 Note
Media files such as MP3, MP4, JPEG, PST etc. have a low dedupe rate as most of the redundancy is already removed and are stored in compressed format. Also, CAD files such as STEP, IGES, DWG, etc. have a low dedupe rate as these files rewrite while saving file data which further reduces the chances of deduplication.
What is credit balance
Credit balance is the number of unutilized credits at the end of the day. The credit balance at the end of a day is the difference between the ending balance of the previous day and the credits consumed in the current day. The Credit Balance graph on the Dashboard represents the remainder of the credit utilization based on storage consumption. The credit balance and cumulative credits consumed till date are updated at 12:15 AM UTC, every day.
📝 Note
Druva does not display the Credit Balance field for AWS Marketplace customers and Managed Service Partners.
Where can you view credit balance on console
Druva displays credit balance on the DCP Dashboard and also on the following pages:
Enterprise Workloads Dashboard
Enterprise Workloads Dashboard
The Backup Data section of Dashboard displays the credit balance across all your organizations. See Dashboard.
Analytics page
Analytics page
The Total Credits and Storage section displays the credit balance along with the storage consumed by all your resources. See Analytics.
Account Details page
Account Details page
The Account Details page displays the credit balance along with the licensing details of your organization. You can view the accounts details information on Dashboard > Accounts Details.
Credit consumption Report page
Credit consumption Report page
The Credit Consumption report page displays the credit balance along with the credit consumption summary of all your organizations.
Management Console > Reports > Credit Consumption
You can access the Credit Consumption report for workloads deployed in Druva's Public Cloud at the following locations:Druva Cloud Platform > Management Console > Reports > Credit
Management Console > Reports > Credit Consumption
You can access the Credit Consumption report for workloads deployed in Druva's GovCloud at the following location:
What are credit limits
Credit limit is the pre-defined limit of credit consumption for an organization. The administrators will be notified if the credits are consumed beyond this limit.
You can view credit limits defined for your organizations on the Credit Limits page. To navigate to the Credit Limits page, go to Management Console > Billing > Credit Limits. For more information on Credit limits, see Credit limits.
Druva enables you to configure the number of credits that an organization can consume and define appropriate actions when the credit limit is reached. You can choose to disable the backups for an organization or alert you when the credit limit reaches a defined limit. This feature benefits you to create a cost-effective environment and track the credit consumption for each organization.
Druva actively tracks credit consumption for each organization and sends notifications to administrators when:
The credit usage reaches 80%, 90%, and 100% of the defined credit limit.
And, thereafter at every 10% increase. To view the alerts generated, see Alerts.
Where can you view credit information
All the credit related information is displayed on the following places:
Credit Consumption Report
The Credit Consumption Report shows the monthly credit consumption of credits for a specified period (default period is 12 months), credit savings, credit balance and credit term details. It also shows the breakdown of the credits consumption based on the storage, early deletion of LTR data, early deletion of archive data and additional restore of archive data.
Dashboard
The Credit Balance graph in the Backup Data section of Dashboard displays the credit utilization based on storage consumption. The credit balance and cumulative credits consumed till date are updated at 12:15 AM UTC, every day.
Credits for AWS Marketplace customers and Managed Service Partners
Druva credits do not apply to the customers that are onboarded through the AWS Marketplace or Managed Service Partners. The Management Console does not display any credit-related information to these customers.