The Credit Overage suspension feature in the credit lifecycle management is designed to protect against unintended costs while ensuring your existing data remains fully accessible and recoverable at all times.
📝 Note
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.
Credit overage
Your backup operations will be automatically suspended when your credit consumption exceeds 110% of your available credits for the current term.
Workflow
The system checks the credit consumption once every 24 hours to determine if the suspension should be applied.
Alerts are triggered at 70%, 80%, 90% thresholds before suspension. At 110%, a dedicated suspension alert is triggered.
You will receive a notification banner on the Management Console and an email alert fromcredit.alerts@druva.com.All the new backup jobs are suspended after your credit consumption exceeds 110% of your purchased credits.
The backup operations that gets suspended are:On-demand backups
Scheduled backups
API-triggered backups
When suspension is active, backup jobs move into a queued state. The running jobs are completed successfully.
Any attempt to trigger a backup will produce an error message.
When credits are replenished (purchased mid-term), the consumption percentage recalculates, suspension is lifted, and backups automatically resume.
Credit overage behaviour
Credit overage is a mid-term cost control mechanism. The following table describes additional capabilities.
Restores | Warm, LTR, Archive are fully operational |
DR operations | Restore, Failover, and failback are unaffected |
Management Console | All management console capabilities such as configuration changes to backup sets and backup policies, consumption analytics, reporting, RBAC, etc. are accessible |
Data | Existing backup up data is preserved |
Compaction | Continues per retention policies |
Running jobs | Complete before suspension takes place |