Onam DRM
Onam DRM is disaster recovery management for your cloud. It maps your applications and what they depend on, reads the backup and replication your cloud configuration has, predicts recovery time (RTO) and data loss (RPO) against the targets you set, composes the order in which each application comes back, and flags drift from the recovery model you approved.
It is a separate product, granted per organisation, and runs inside the same console as Onam Estate, Onam Security and Onam FinOps. It works from the platform's cloud inventory, so your accounts are connected once.
What it answers
| Question | Where in DRM |
|---|---|
| Which applications do we run, and what do they depend on? | Applications, Dependencies, Topology |
| What is protected, and by what? | Protection |
| Could we recover in time? | Recovery — readiness and objectives |
| In what order does it come back? | Recovery — plans |
| Has anything changed since we signed off? | Monitor — drift; Governance — baselines |
| Did the last drill meet the target? | Drills |
The stages
- Understand. Resources come from the platform inventory and are placed where the provider says they live — the availability zone where one is given, the region otherwise. Applications are proposed from your tags, each with the tag it came from and a confidence. Dependencies are classified as recovery order, protection (proves a copy exists) or placement (shares a failure domain).
- Protect. Backup, snapshot and replication are read from cloud configuration. A configured mechanism is reported as discovered, never as protected or tested — those are statements a person makes.
- Recover. Recovery plans are composed from approved items only. Predicted RTO is the critical path through the plan; predicted RPO is the worst replication link.
- Govern. Engines propose and people approve. The approved model is frozen as a baseline, and drift is measured against it.
What DRM does not do
- It does not execute a recovery or fail anything over.
- It does not run DR tests. Drills run with your own tools are recorded in DRM.
- It has no connectors to backup products. Protection is read from cloud configuration, which shows that a mechanism is configured — not that last night's job succeeded or that a restore works.