License editions: To understand the applicable license editions, see Plans & Pricing.

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.

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.

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.

📝 Note

To protect RDS databases and clusters using our air-gapped data protection solution, 2 credits will be consumed for 1 TB of backup data stored in Cloud per month. For more information, see RDS Airgap Data Protection.

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.

Credit consumption refers to the usage of purchased credits in accessing Druva’s Cloud based solutions such as data backup, recovery and management services.

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.

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.

📝 Note

This section provides details about the factors due to which the credit consumption is impacted.

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.

📝 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.

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.

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 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.

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.

📝 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 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.

📝 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.

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.

Druva displays credit balance on the DCP Dashboard and also on the following pages:

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:

All the credit related information is displayed on the following places:

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.