Onam
4 · Recover · Onam DRMProtection

What does our cloud configuration say is actually backed up or replicated?

Onam DRM reads backup plans, snapshots, replicas and replication from your cloud configuration and reports each one as discovered — never as protected or tested, because those are statements a person makes.

Request a demo Read the docs
app.onamsecurity.com/drm/protection
Onam DRM Protection Overview: protection, backup and replication record counts, coverage bars for backup, replication, storage and traffic each measured against its own population, and protection by resource type.
Onam DRM console — demo tenant data.
The problem

In your words

Everyone assumes the important databases are backed up and replicated. Some are; some had their replica removed in a cost review; some were created after the backup policy was written. The only list of what is protected is a spreadsheet that was right when it was made. A protection report that overstates is worse than none, because it is the one people will trust during an outage.
What you see

What Protection shows you

Described from the product documentation — what the view holds, not what we hope it will.

  • Protection read from configuration

    Backup plans and retention, database automated backups and multi-zone deployments, snapshots, read replicas and storage replication, including cross-region replication.

  • Discovered, not protected

    A configured mechanism is reported as discovered. Configuration does not show whether a job succeeded, whether a restore has worked or whether a copy is complete, and DRM does not pretend it does.

  • Per resource, grouped or not

    Protection is a property of a resource, so a database nobody has tagged into an application still shows the backup its configuration has.

  • Per application, pairing by pairing

    A resource used by two applications gets one pairing for each — the same replica can be critical to one and incidental to another, and approving it for one is not approving it for the other.

  • Coverage by resource type

    Protection broken down by resource type, counted over resources so a type with no protection record at all still appears. Gaps in the model are shown as gaps, not as a score of zero.

How it works

The mechanism, step by step

What Protection does, in the order it does it.

  1. 1
    Read the control plane

    Protection is read from cloud configuration through the platform's read-only connection. Which mechanisms are recognised varies by cloud and resource type.

  2. 2
    Record it per resource

    Every mechanism found is attached to the resource it protects, whether or not that resource belongs to an application yet.

  3. 3
    Pair it with applications

    Where a resource belongs to an application, a protection pairing is proposed for that application and goes to the Approval Center.

  4. 4
    Feed plans, RPO and drift

    Recovery plans use only approved pairings, predicted RPO comes from replication links, and drift reports protection that changed since the baseline was approved.

Limits, said plainly

What it does not do

Knowing where a capability stops is part of deciding whether to buy it.

  • It has no connectors to backup products

    Protection is read from cloud configuration and reported as discovered, not protected. Configuration shows a mechanism is set up — not that last night's job succeeded or that a restore works.

  • It cannot see inside a server

    DRM reads the cloud provider's control plane. A database dump or backup job scheduled inside a virtual machine is invisible to it, so a resource with no visible mechanism is a question for its owner, not a verdict.

Onam AIOps

The DR Agent

Onam AIOps agents investigate with evidence on every claim and propose changes a person approves. Nothing changes your cloud without that approval.

DR Agent

On the roadmap

On the roadmap: the DR Agent is designed to find backup coverage for a business service and separate protection that exists from recovery that was validated.

On the roadmap: Designed, not offered. No date is promised.

Read the DR Agent docs About Onam AIOps
FAQ

Questions about Protection

No. There are no connectors to backup products. DRM reads protection from cloud configuration, which shows that a mechanism is configured — not the job history of a third-party backup tool.

Part of Onam DRM

More in Onam DRM

Back to Onam DRM

Applications & dependencies

Which applications do we actually recover, and what does each one depend on?

Explore Applications & dependencies

RTO, RPO & drills

Could we recover in time — and how do we know the number is right?

Explore RTO, RPO & drills

Baselines & drift

Has anything changed since we signed off the recovery plan?

Explore Baselines & drift

Onam DRM

Disaster recovery management — applications and dependencies mapped, protection read from cloud configuration, predicted RTO and RPO against your targets, and drift from the plan you approved.

The whole product
4 · Recover · Onam DRM

See Protection on your own cloud.

Onam DRM runs in the same console and login as the rest of Onam, with read-only access to your cloud.

Request a demo Read the docs