Control-M SaaS Data Backup and Retention Policy
Control-M SaaS ensures robust backup and recovery capabilities to protect customer data and maintain service continuity in case of accidental deletion, corruption, system failure, or disaster. Our backup strategy aligns with business continuity and contractual obligations.
Backup Architecture
The following architecture applies to both production and non-production environments:
| Scope / Layer | Environment | Backup Type | Frequency | Retention |
|---|---|---|---|---|
| Data Layer | Production & Non-production | Continuous backup with daily snapshots | Continuous | 5 days |
| Immutable Backup (DR & Account Termination) | Production & Non-production | Immutable Backup | Continuous | 60 days |
Security and Storage
Data security and storage practices are based on the following principles:
- Backups are stored in a separate AWS continuity account, ensuring isolation from production.
- Access is restricted via least-privilege RBAC.
- Backups are immutable and used for recovery and continuity purposes.
Recovery Objectives
Backup and retention practices have the following recovery objectives:
- Localized failure: RPO = No data loss; RTO ≤ 1 hour.
- Account compromise: RPO ≤ 1 hour; RTO ≤ 24 hours.
Monitoring and Testing
Monitoring and testing practices are based on the following principles:
- Backup jobs are monitored constantly to alert on failures.
- Annual restore tests validate recoverability within defined RTOs.
- Test results are documented and shared upon request.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*