The Term Expiry 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.
Term expiry
When your contract term expires, backups are suspended until the contract is renewed.
Workflow
When your credit term or contract date is reached without renewal, the system automatically suspends backups for all workloads.
The system identifies the contract has expired based on the term or end date stored in the system.
Alerts are triggered as the term end date approaches, notifying an impending suspension.
If the credit term is expiring in 90 or 60 or 30 or 15 days, a warning alert is sent.
If the credit term is expiring in 7 days, critical alerts are sent on daily basis.
Alert is also sent when the credit term is expired.
You will receive a notification banner on the Management Console and an email alert from
credit.alerts@druva.com.All the new backup jobs are suspended. The running jobs are completed successfully. The backup operations that gets suspended are:
On-demand backups
Scheduled backups
API-triggered backups
Any attempt to trigger a backup will produce an error message.
After you renew your term or contact agreement, suspension is lifted and backup operations resume.
Term expiry behaviour
Term expiry is an end-of-contract enforcement 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 |