We use a consumption-based pricing model designed to align costs directly with your actual data protected in the cloud. Instead of complex licensing, the system uses Credits to provide a predictable and scalable way to manage backup costs.
Understand Credit Terminology
Review the credit terminology to better understand usage, plan consumption effectively, and avoid unexpected surprises.
Credits
Credits
A credit is the unit of measurement across all Enterprise Workloads such as servers, VMs, databases, and cloud-native workloads.
1 Credit = 1 TB of deduplicated, compressed backup data stored in the Cloud for 1 month (1 TB-Month)
Credits are calculated on post-deduplication, post-compression data and not on the source data size. A server with 10 TB data might produce only 8 TB of unique, compressed backup data, consuming 8 credits per month and not 10. For more information, see Calculate credit consumption.
Credit allocation at purchase
Credits are purchased as part of your subscription agreement. Druva’s Sales team helps you determine the appropriate initial credit allocation based on your estimated data protection and storage requirements.
Sizing and capacity planning
Before contract execution, total credit requirements are calculated based on the following core parameters:
Total Source Data Volume: Total data volume of all targeted workload types (File Servers, Databases, VMs).
Deduplication Rate: Workload-specific deduplication ratios (for example., File Servers deduplicate differently than database backups).
Backup Frequency: Change-rate capture frequency across daily and intra-day backup cycles.
Retention Policies: Duration for which recovery points must be maintained in Druva Cloud storage.
When you purchase a contract, your required capacity is converted into a total credit allocation for the full contract term. These credits form a shared pool and are consumed daily as backup data is stored in the cloud.
Examples:
Purchasing 10 TB for 12 months allocates approximately 120 credits for a one-year term.
Purchasing 50 TB for 24 months allocates approximately 1,200 credits for a two-year term.
Your available credits are displayed as the Credit Balance on the Consumption Insights tab.
If you need additional capacity during your contract period, contact your Account Executive to purchase more credits. The newly purchased credits are added to your existing credit balance.
What happens when credits are exhausted
Druva starts sending credit utilization alerts when you use 70% of your purchased credits. Additional alerts are sent when you reach 80%, 90%, and 100%. To avoid any impact on backup operations, contact your Account Executive to purchase additional credits before your credit balance is exhausted.
Any usage beyond your purchased credits is highlighted in red on the Credits and Storage Consumption graph.
If your account has transitioned from Evaluation to Commercial mode, unused evaluation credits do not carry over.
Best practices:
To lower costs: Optimize your total data volume by excluding unnecessary files, shorten your retention duration to meet only essential compliance needs, or investigate and stabilize high change rates.
To increase savings: Improve deduplication efficiency by excluding non-deduplicable data types from backup content (like encrypted or compressed files) and maximize tier optimization by utilizing Long Term Retention (LTR) or Archive tiers for long-term data.
Credit term
Credit term
The Credit Term is the duration of your active contract, typically 12 or 24 months. All purchased credits must be consumed within this term.
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.
If consumption is below 80%, the excess rollover above 20% is forfeited making slow consumption a financial risk, not just an operational one.
Example: You have purchased 1,200 credits for 12 months.
Minimum consumption = 960 credits (80%).
If only 800 are used, 400 credits are forfeited.
What happens when credit term expires
Druva begins sending renewal reminders 90 days before your credit contract expires and continues to send alerts until the contract term ends. When your credit contract expires, Druva temporarily suspends all automated, manual, and API-triggered backup operations, regardless of your remaining credit balance. Your existing backup data is retained and remains available for restore operations according to your configured retention policies. To avoid backup interruptions, renew your license to extend your credit term before it expires. Contact your Account Executive if you need assistance with renewal.
Backup protection automatically resumes after your license is renewed and your credit contract term is extended. For more information, see Backup Suspension on Term Expiry.
Credit balance
Credit balance
Credit balance represents the number of unused credits remaining in your account at any given time.
The balance is updated daily at 12:15 AM UTC after deducting that day’s credit consumption from the previous balance.
It is displayed on both the Dashboard and the Consumption Insights tab on the Analytics page.
If all credits are consumed, the balance is shown as a negative value in red.
In the Backup Data widget on the Dashboard, the balance is separated into:
Current Term Credit Balance
Future Term Credit Balance
Credit Balance (today) = Credit Balance (end of yesterday) − Credits consumed today
Daily consumption: Credits consumed = (TB of deduped data stored that day × 12) ÷ 365 |
Credits baseline
Credits baseline
The Credit Baseline is the planned, contracted rate of consumption. It is represented by a line showing how credits should be consumed if usage tracks exactly with the contracted plan.
Displayed as a black dashed line on the Credits and Storage Consumption graph on the Consumption Insights tab.
Comparing actual balance to the baseline instantly shows whether your consumption is on track, slow, or fast.
For more information, see Credits Baseline section.
Credits projection
Credits projection
Credit Projection provides visibility into when your credits may run out and whether you are likely to end your contract term with a surplus or deficit.
Druva analyzes your historical consumption patterns and current trends to forecast your future credit balance and estimate the credit expiry date.
This projected expiry date serves as an early indication, helping you plan ahead and avoid unexpected disruptions.
For more information, see Credits Projection section.
Credit limit
Credit limit
A Credit Limit is a configurable governance cap set per organization. It prevents any single organization from consuming more than an allocated share of the company's credit pool. Administrators can set a predefined limit on credits for each organization and configure actions, such as sending alerts or disabling backups, when usage reaches thresholds like 80%, 90%, or 100%.
You can configure credit limits from Analytics > Credit Limits > Manage Credit Limits.
Druva offers intelligent recommendations based on the past 30 days of usage to support more accurate and cost-effective planning.
From the Management Console, you can view, modify, and manage credit limits, including setting validity periods and usage thresholds, and can apply these limits across multiple organizations.
If a limit is exceeded and backups are paused, increasing the credit limit allows backup operations to resume without disrupting in-progress jobs.
For more information, see Credit Limits.
Cost allocation
Cost allocation
Cost Allocation is a built-in chargeback framework that helps you simplify cost management, track department-specific storage usage, generate detailed cost and usage reports, and improve budget planning and forecasting.
You can categorize protected resources into the following entities:
Organizations
Administrative groups
Backup sets
These resources can then be mapped to specific cost codes for usage tracking and billing. Example: If all Finance servers are mapped to the cost code FINANCE-2026 with an allocation rate of $0.03/GB/Month, Druva automatically calculates Finance’s monthly data protection cost.
Key components:
Cost codes are unique identifiers assigned to departments or resource groups. They act as billing buckets for aggregating storage usage and calculating total costs for specific business units.
Cost Allocation Rate defines the storage cost, measured in $/GB/Month.
Global Rate: A default rate applied across all cost codes.
Custom Rate: A specific rate assigned to individual cost codes when separate billing structures are required.
You can subscribe to the Cost Allocation Report to receive detailed usage insights for specific cost codes and their associated organizational resources.
For more information, see Cost Allocation for Enterprise Workloads.
How credit consumption works
Credit consumption refers to how your purchased credits are used when accessing Druva’s cloud-based services such as data backup, recovery, and management.
Druva follows a usage-based pricing model. Credits are consumed based on the actual storage used to protect deduplicated backup data after compression and deduplication.
Click here to learn how credit consumption is calculated
Click here to learn how credit consumption is calculated
To ensure accurate billing, Druva calculates daily credit consumption based on the amount of protected data on a given day and converts it into credits.
Daily credit consumption formula
In TB:
Credit consumed per day = (Dedupe backup data in TB × 12) / 365
In GB:
Credit consumed per day = (Dedupe backup data in GB × 12) / (1024 × 365)
Example:
If your organization backs up 1 TB of deduplicated data in a day:
Credit consumed = (1 × 12) / 365 = 0.032 credits/day
Daily credit consumption cycle
The consumption of credits follows a sequential, daily process, summarized by the following four key steps:
Backup execution: Scheduled backup jobs run to protect your diverse workloads, including servers, VMs, and databases, in accordance with your backup policy.
Global deduplication: Global deduplication ensures that backed-up data is deduplicated and compressed before storage, so only unique and changed data blocks are stored. This reduces overall storage consumption, and credit usage is calculated based on the deduplicated data actually stored in the cloud.
Credit draw-down: The deduplicated storage consumed is used to determine your credit consumption for that day. The number of credits consumed for the day is then calculated, using the formula:
Credit consumed per day = (Dedupe backup data in TB × 12) / 365
This calculated amount is then subtracted from your available credit balance.
Credit balance update: The credit balance is then updated on the Enterprise Workloads Dashboard and the Consumption Insights tab of the Analytics page. Your new credit balance is reflected, and all consumption projection dates are updated based on the new daily usage.
Credit consumption scenarios
Let us assume your organization needs to protect 100 TB of deduplicated backup data in the Cloud each month for one year, without using Long-Term Retention (LTR) or Archive tiers. In this case, the total credit requirement would be:
Total credits required = 100 TB × 12 months = 1200 credits (TB-months)
This represents the total credits needed to protect your deduplicated backup data on the cloud for one year. Note that this is an approximate estimation and the amount would change based on the workloads you configure, your retention policies and your consumption behaviour.
Based on your organization’s credit usage patterns, your consumption will align with one of the following three scenarios: on target, slower than the baselined consumption, or faster than the baselined consumption.
On-target credit consumption
On-target credit consumption
When credits are consumed at the planned rate throughout the contract term, it is considered on-target credit consumption. This is an ideal scenario where the projected credit expiry date closely aligns with the contract term end date.
Slow credit consumption
Slow credit consumption
When credits are consumed at a slower pace than the anticipated rate over the contract term, it is considered slow credit consumption. Druva requires that at least 80% of the purchased credits be consumed within the contract term. At renewal, you can carry over up to 20% of the purchased credits from the current term to the next contract term.
The following graph illustrates slow credit consumption, where usage lags behind the expected rate, leaving a significant balance of unused credits toward the end of the contract term.
Fast credit consumption
Fast credit consumption
When credits are consumed at a faster pace than the anticipated rate over the contract term, it is considered fast credit consumption.
The following graph illustrates fast credit consumption, where credits are used more quickly than planned, resulting in early depletion before the end of the contract term.
Purchase additional credits
If your credits are being consumed faster than expected and you are at risk of exhausting them before your contract term ends, you can purchase additional credits within your existing contract. To determine how many credits you will need to maintain data protection for the remainder of your term, contact your Account Executive.
📝 Note
If your account moves from Evaluation to Commercial, existing credits are not carried forward. If there is no change in account type, the remaining credits are added to the newly purchased credits.
Excess credits consumption
If you run out of credits during the contract term, Druva continues to back up your data for the next six months. You must contact your Account Executive to purchase any additional credits required to continue backing up your data. Any extra usage appears as negative credits (in red) on the Dashboard.For example, if your balance is 7 credits and you consume 2.5, 5, 2, and 3 credits over the next few days, the extra 5.5 credits used beyond your balance will be shown in red in the Backup Data graph on the Dashboard.
The following table shows how additional credit usage is calculated after your purchased credits are exhausted.
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 |
📝 Notes
Druva continues to protect your data in the cloud for up to 6 months even after your purchased credits are exhausted.
For more information on estimating the number of credits required for the year, you can contact your Account Executive or Support.
Factors impacting credit consumption
This section explains the key factors that can affect how your credits are consumed.
Early delete fee for Long Term Retention data
Early delete fee for Long Term Retention data
Long Term Retention (LTR) data lets you store backup data in a low-cost cold tier for 1 year or more, reducing storage costs. Druva protects the backup data 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.
Credit consumption formula:
Credit Consumption = Data (TB) × Rate per TB per month × Retention (months)
If data is deleted before 1 year, an early delete fee applies:
Early delete fee = 0.35 × (12 − months stored) × data deleted (TB)
📝 Note
No early delete fee is charged for data deleted from the warm tier before it moves to the cold tier.
Early delete fee for Archive data
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 footage, 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.
Credit consumption formula:
Credit Consumption = Data (TB) × Rate per TB per month × Retention (months)
If data is deleted early:
Early delete fee = 0.35 × (12 − months stored) × data deleted (TB)
Restore fee for Archive data
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 up to 1% of archived data (source + changes) per day for free. Any restore beyond this limit is charged at 1 credit per 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
Change rate measures how much new or modified data is backed up to the cloud each day. It tells you how much your storage is growing or shrinking day by day.
Druva calculates this by comparing the total amount of backup data from two days in a row.
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
Retention
Druva’s retention 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 and potentially more resources to protect and manage the backup data. Conversely, less credits are consumed if the retention period for the deduplicated backup data is lower.
Druva provides a default backup policy with the retention settings as shown in the following screenshot.
Now let us consider that your organization requires the backup data to be retained for 7 years instead of 3 years and hence you create 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 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 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 a risk of losing important data if a disaster or data loss occurs outside of that retention period.
Deduplication rate
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.
Media files such as MP3, MP4, JPEG, and PST have a low dedupe rate as most of the redundancy is already removed and are stored in compressed format. Similarly, database dumps, encrypted files, and compressed files deduplicate poorly because their contents are either compressed, encrypted, or regenerated, resulting in minimal data similarity across backups. In addition, 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.
Monitor credit health
Monitoring credit health regularly is critical to maintaining control over storage consumption and costs. Reviewing credit utilization on a weekly basis helps you detect anomalies early, control and optimize costs, stay aligned with expected usage trends and improve forecasting accuracy.
The management console provides the following modules to help you track, analyze, and optimize credit usage across your resources.
Enterprise Workloads Dashboard
Enterprise Workloads Dashboard
The Backup Data widget on the Enterprise Workloads Dashboard provides a high-level view of credit health across all organizations, including:
Credit balance that shows remaining credits and cumulative credits consumed
Credit utilization trend graph that visualizes how credits have been consumed over the past 90 days based on storage usage
Storage details such as total storage consumed, source data (Source + Changes, Current Source), and deduplication savings to give context to credit usage.
For more information, see Dashboard.
To access the dashboard, click Enterprise Workloads on the main menu.
Analytics page
Analytics page
The Analytics feature provides you with comprehensive visibility into credit and storage consumption through detailed visualizations and audit trails. By leveraging cost allocation and credit limit tools, organizations can accurately forecast budgets, investigate usage anomalies, and automate guardrails to ensure a cost-effective deployment. To know more, see Analytics.
To access the analytics data, click Analytics on the menu bar. It provides the following three tabs:
Consumption Insights
The Consumption Insights tab is the most powerful credit visibility screen. it is accessible only to Cloud Administrators and DCP Administrators.
The top summary widgets provide a snapshot of credit balance, usage trends, storage metrics, and savings, along with projections based on recent consumption patterns. Detailed visualizations and tabs, such as credits and storage graphs, source data trends, backup set views, and drill-down panels, help analyze usage, track changes, and identify optimization opportunities across workloads. For more information see, View Consumption Insights.
Credit Limits
Credit limits help organizations control consumption by setting usage caps and defining actions like alerts or disabling backups when limits are reached. They also enable proactive monitoring by notifying administrators at key usage thresholds, ensuring better cost management.
Table of all organizations with current credit limit, Limit Used %, and configured action.
Manage Credit Limits button: Configure limit value and action (alerts / disable at 80%, 90%, 100%).
Druva's AI Recommended Credit Limit shown alongside the configured limit for each org.
For more information see, Credit Limits for Enterprise Workloads.
Cost Allocation
With cost allocation, you can automate chargeback reporting by tracking storage and credit consumption across departments, allowing your administrators to assign costs and forecast budgets effectively. Using entities like administrative groups, organizations, and backup sets along with cost codes, teams can map resource usage to credit consumption and gain detailed cost insights at multiple levels.
All cost codes across organizations, with Cost Object Type, mapped resources, and $/GB/Month rate.
Monthly Cost Allocation Reports auto-generated and emailed to Cloud Admins, DPOs, and designated non-admins.
For more information see, Cost Allocation for Enterprise Workloads.
Reports
Reports
Druva provides the following reports to monitor organizational credit trends and burn rates over time, alongside granular resource-level tracking.
Credit Consumption Report: It provides a high-level view of credit usage and utilization trends over time, including monthly consumption, balance changes, and savings. This helps administrators monitor overall credit usage, forecast future capacity needs, avoid unexpected credit exhaustion, and proactively plan renewals or additional credit purchases. For more information, see Credit Consumption Report for Hybrid Workloads.
Credit Consumption by Backup Set Report: It provides a granular breakdown of credit consumption at the backup set level, enabling administrators to identify which backup sets and workloads are driving usage. This helps quickly detect anomalies, optimize backup policies, right-size storage consumption, and control costs before they escalate. For more information, see Credit Consumption by Backup Set Report.
To access the reports, go to the Global Navigation Panel and click Reports > Hybrid Workloads.
📝 Note
The credit details are not available for customers onboarded through the AWS Marketplace and Managed Service Partners.
Account Details page
Account Details page
The Account Details page displays the credit balance along with the licensing details of your organization.
To view account details, go to the Global Navigation Panel and click Account Details.
Credit details 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.
Best practices for optimal credit utilization
Efficient credit management helps you control costs, avoid unexpected overages, and ensure optimal use of your backup environment.
Review the following best practices for configuring backups, proactively monitoring early credit utilization, and implementing governance for optimal consumption.
Configure backups efficiently
Configure backups efficiently
Maximizing your credit efficiency begins with your initial backup configuration. By strategically tailoring your backup sets and retention policies, you can prevent unnecessary drain on your resources from day one.
To optimize your credit consumption, you must carefully define these key settings:
Backup content: Use include and exclude rules to filter out large, low-deduped files such as encrypted data, videos, or compressed archives. These files consume significant credits without benefiting from our deduplication engine.
Duplicate backups: Ensure you are not backing up the same data twice. For instance, if you use a native SQL agent for database backups, exclude those specific disks from your VMware-level backup policies.
Optimize retention settings: Retention settings significantly impact credit usage. We recommend you to:
Reduce defining long-term monthly retention where not required.
Align retention policies with business and compliance needs.
Move older data to cold or archive storage tiers.
Ensure data meets age thresholds required for tiering.
Leverage storage tiering: Move aging compliance data to Long-Term Retention or Archive tiers. Ensure data stays in these tiers long enough to meet age thresholds, helping you avoid early deletion fees.
Monitor credit consumption
Monitor credit consumption
You can use the Consumption Insights tab on the Analytics page to identify high-consumption resources, monitor usage trends, and implement recommended corrective actions.
Indicator | How to monitor | Recommendations |
Actual Credit Balance vs. Baseline Credit Balance deviation | Credits and Storage Consumption graph: Look for the solid line (Actual Credit Balance) dropping below the dashed line (Baseline Credit Balance). | Contact your Account Executive or Support to purchase more credits or reassess retention policies to bring credit usage back to the baseline. |
High change rate | Backup Sets tab: Review backup sets with high change rates. | Optimize workloads for high change rates. Example:
|
Rapid storage growth | Current Source Data graph: Watch for a steep upward trend in the Shaded Area. | Identify the growth source:
|
Low dedupe savings | Dedupe Savings ratio: Monitor for a ratio lower than the historical average for that workload. | Check data type: Ensure you aren't backing up encrypted or compressed data that prevents effective deduplication, such as encrypted files, compressed files, database dumps, audio files, video files, and image files, unless required for your business or compliance needs. |
Source + changes spikes | Source + Changes graph: Look for sudden vertical spikes on specific dates. | Audit events: Click the green event markers to see any addition or removal of backup sets. |
Credit Balance depletion | Summary widget for Total Credit Balance: Monitor the Current Term Credit Balance vs. Current Term Credit Balance. | Plan your credit purchase or term renewal: If your credit utilization reaches 80% or your credit contract is 90 days from expiration, contact your Account Executive to purchase additional credits or renew your contract. This helps prevent backup service interruptions or credit overages. |
High growth rate | All Backup Sets tabular view: Sort by Average Annual Growth rate percentage. | Review retention: For fast-growing backup sets, consider shorter retention periods or enable Long term Retention (LTR) setting in your backup policy. |
Proactive governance
Proactive governance
The following are key recommendations to help you proactively manage and maintain your credit consumption health:
Identify and optimize high-consumption workloads, as those with frequent changes drive significantly higher credit usage.
For example, if you want to protect MS SQL workloads,
Enable application-aware backups.
Ensure log truncation is working correctly.
Avoid inefficient methods:
Do not back up .bak files using a NAS backup proxy.
Use the native MS SQL agent for better efficiency.
To keep costs down, it is essential to understand how specific actions drive credit usage and identify where consumption can be minimized.
Disabling backups does not stop credit usage.
To fully stop consumption:
Delete backup sets or recovery points.
Allow time for compaction/cleanup processes to complete.
Review the Credit Consumption Report to analyze usage trends, enabling more effective budget planning and accurate forecasting.
Subscribe to relevant reports, such Credit Consumption Report, Credit Consumption by Backup Set Report, Cost Allocation Report on the Druva Cloud Platform Console.
Assign proper administrator roles and permissions for viewing all reports.
Subscribe Cloud administrators and relevant stakeholders to receive Credit Consumption Report every month for consistent visibility into credit usage, consumption trends, and drive timely decisions around retention, backup policies, and infrastructure efficiency.
Review Credits Consumed due to Early Deletion of LTR data/Archive data columns in the Credit Consumption Report monthly. Recurring fees mean retention policies are being shortened without a retention plan.
Establish governance practices such as conducting monthly credit usage reviews, tracking changes to retention and backup configurations, and defining formal approval workflows for backup deletions and policy updates.
Proactively manage credit limits or expiration and engage with your Account Executive or Support 90 days before your term ends to review usage predictions, right-size your next credit purchase, and reassess retention periods or high-consumption backup sets for better forecasting.