Effective July 27th, Druva will automatically suspend backup operations when a customer's credit consumption exceeds 110% of their available credits for the current term. This change provides better cost control and transparency, protecting customers from unintended overage costs.
📝 Note
Existing accounts that have crossed the 110% threshold before July 27th are exempt from immediate suspension. For these accounts, backup suspension will take effect only after the next credit purchase or contract renewal.
What is the impact
Here is a breakdown of which backup operations get suspended and what remains functional.
🚫 Suspended (After 110%)
Scheduled backups
On-demand backups
API-triggered backups
✅ Not Affected (Remains functional)
Restores (Warm, LTR, and Archive)
DR operations (Restores, failback, and failover)
All Management Console capabilities such as configuration changes to backup sets and backup policies, consumption analytics, reporting, RBAC, etc.
Existing backed-up data
Supported workloads
Backups suspension applies to the following Enterprise Workloads:
Hybrid Workloads: VMware, Disaster Recovery, Hyper-V, Nutanix AHV, Proxmox, File Servers, NAS, MS SQL, Oracle PBS, Oracle DTC, and SAP HANA.
Cloud-native Workloads: Azure Virtual Machines, Azure SQL, Azure Blob Storage, Azure Files, Amazon EC2, Amazon EBS, Amazon S3 Buckets, and Amazon Elastic File Systems.
❗ Important
These changes are not applicable for Dell, MSP, AWS GovCloud (US), FedRAMP-compliant GovCloud, or Marketplace customers.
What this means for you
Let’s understand how the suspension process works in practice.
When your credit consumption crosses 110%, the system will check the threshold once every 24 hours and suspend all backup jobs.
Once backup suspension takes effect, no new backup jobs will be triggered until backups are resumed.
You will receive a notification banner on the Management Console and an email alert from credit.alerts@druva.com.
All backup jobs will resume within 24 hours automatically once credits are replenished.
What action is required
Perform the following to avoid backup disruption.
Before July 27th — Review your current credit consumption on the Analytics > Consumption Insights page.
If you are close to running out of credits, purchase additional credits or renew your contract to stay below the 110% threshold.
If backups are suspended and you're in the process of purchasing credits, contact your CSM or Account Manager.
Once credits are replenished, backups resume automatically.
Why does this change help you
Cost protection: Prevents runaway overage costs by pausing backups beyond your entitlement.
Proactive alerting: Dedicated email and portal notifications regarding credit consumption at different thresholds (70%, 80%, 90% and so on) ensure clear, timely awareness.
Zero impact on recovery: Restores and archive restores remain fully operational.
Automatic resumption: Backups restart on their own once credits are replenished.
Support flexibility: Temporary suspension lift is available during active credit purchases.
If no action is taken
After July 27th, if consumption exceeds 110% and credits are not replenished:
All backup operations will be suspended.
Any data changes occurring during the suspension period will not be protected until backups resume.
What has changed
A quick comparison of how credit overage behavior differs before and after July 27th.
Area | Until July 27 | Starting July 27 |
Backup behavior after credits are exhausted | Backups continue running | Backups are automatically suspended when credit utilization reaches 110%. |
Credit overage notification | No dedicated overage alert for 110% | When credit utilization reaches 110%, a banner appears in the Management Console and an email notification is sent. |