Business continuity and disaster recovery
Control-M SaaS Continuity Priorities
Control-M SaaS is intended to enable customers to automate their most business-critical processes. The priorities of our DR and BCP planning are:
- No loss of customer data
- Automatic recovery from availability zone (AZ) failures
- Recovery from corruption caused by a platform or application bug
- Recovery from customer (human) errors that generate data loss (for example, accidentally deleting folders or jobs)
Overview of DR approach
Control-M SaaS is hosted in AWS data centers in the following regions:
- US West (Oregon)
- EU West (Ireland)
- Canada (Central)
- Asia Pacific (Sydney)
These regions have at least three availability zones per region, which are independent data centers. Control-M SaaS components are replicated across all availability zones, providing an extremely high level of resiliency.
Our recovery objectives are:
Recovery point objective (RPO) | No-gap |
Recovery time objective (RTO) | <15 minutes |
Acceptable data loss | Zero |
Data persistency
All data is continuously backed up to ensure we meet recovery objectives. Apart from synchronizing data across the AZs, additional sets of persisted data are maintained using a separate, dedicated account and encrypted.
Notification of unplanned failures
Type of failure | Example impact | Notification |
|---|---|---|
Applicative - customer specific |
| BMC Support will call the affected customer and walk them through recovery steps. |
Communications |
| Through the Control-M SaaS trust page |