Disaster Recovery

Disaster Recovery plans define how Breeze brings your systems back online after a major incident. You organize devices into ordered recovery groups, set overall RTO and RPO targets, and rehearse the plan before you ever depend on it.

Ordered Recovery Groups

Recovery groups define which devices to recover and in what order. Groups execute sequentially, so group 1 completes before group 2 starts, and each group can be configured to depend on another finishing first. Model the order after your service dependency chain, such as domain controllers, then databases, then application and file servers.

RTO and RPO Targets

Every plan carries an RPO target, the maximum acceptable data loss in minutes, and an RTO target, the maximum acceptable recovery time in minutes. Pairing plans with SLA policies lets Breeze track day to day whether those objectives are actually achievable, giving you confidence well before a DR event.

Bare-Metal Recovery

Bare Metal Recovery restores a complete system, including OS, drivers, configuration, and data, to new or replacement hardware. It uses a one-time recovery token instead of an enrolled agent, so you can recover a machine that was never enrolled in Breeze: system state restores first, data files follow, and post-restore validation checks service status, network connectivity, and critical file presence automatically.

Coordinated Failover and Failback

Plans support three execution types. A rehearsal validates recovery steps without touching production, a failover performs the live restore during a real disaster or planned migration, and a failback returns services to the primary environment once the original site is repaired. Recovery groups execute in sequence, progress is tracked in the execution detail view, and a running execution can be aborted at any time.

Recovery Rehearsals

Rehearsals run the full plan without modifying production systems, so you can prove recovery works before relying on it for failover. Breeze recommends rehearsing at least quarterly and reviewing after each run to update device assignments, sequence orders, and targets based on what you learned.

Execution History and Audit

Each plan detail page lists past executions with their type, start and end times, status of running, completed, failed, or aborted, and per-group results. This history gives MSPs a clear, auditable record of every rehearsal and failover, making it easy to demonstrate that recovery plans are tested and current.