Awanio Disaster Recovery Manager

docs.awan.io

Free trial WebSelf-hosted

Spec score 8.5 #3 of 25 in Disaster Recovery Software

What it is

Awanio Disaster Recovery Manager (DRM) coordinates virtual-machine recovery across paired Awanio Cockpit sites. Administrators enroll VMs for scheduled disk replication and set the recovery site, datastore, RPO, recovery-point retention, and traffic compression. The initial sync copies the full disk; later syncs transfer changed blocks. Recovery plans arrange workloads into ordered runbooks with priority groups and boot delays, then replicate as read-only copies to the recovery site. DRM supports isolated test failover, planned migration, emergency failover, reprotection, and failback. During a test, a workload copy boots in an isolated network while production remains untouched. Emergency failover uses the latest completed recovery point, so newer data may be lost. A deployment needs two sites, each with Cockpit and at least one Vapor host, administrator access to both, and connectivity on ports 7770, 7771, and 7772. Orchestrated recovery also requires the Disaster Recovery entitlement at both sites and a DRM license or active trial. Pricing is on request; the time-limited trial permits a small number of protected workloads.

Spec sheet

Purpose: DRM orchestrates virtual-machine disaster recovery across paired Awanio Cockpit sites.Read 7 Oct 2026 · docs.awan.io
Intended users: The documentation describes a site-level tool for administrators protecting and recovering virtual machines across paired sites.Read 7 Oct 2026 · docs.awan.io
Integrations: DRM manages its local site through Cockpit, while Vapor performs disk replication and boots recovered virtual machines.Read 7 Oct 2026 · docs.awan.io
Headquarters: Jakarta, IndonesiaRead 28 Sep 2026 · docs.awan.io
Maker: Awanio describes itself as an enterprise virtualization and cloud orchestration technology company engineered in Indonesia and deployed globally.Read 7 Oct 2026 · awan.io
Deployment prerequisites: A deployment requires two sites, each running Cockpit and at least one Vapor host, plus administrator access to both sites.Read 7 Oct 2026 · docs.awan.io
Deployment requirements: A deployment requires two sites, each running Cockpit and at least one Vapor host, administrator access to both DRM consoles, and inter-site connectivity on ports 7770, 7771, and 7772.Read 7 Oct 2026 · docs.awan.io
Failback: After failover, DRM can reverse replication toward the original site and later return the workload there through planned failback.Read 7 Oct 2026 · docs.awan.io
Failover limitation: Emergency failover uses the latest completed recovery point, so data written after that point can be lost.Read 7 Oct 2026 · docs.awan.io
Failover modes: DRM supports non-disruptive test failover, planned migration, and emergency failover from the latest completed recovery point.Read 7 Oct 2026 · docs.awan.io
Failover rehearsal: Test failover boots a workload copy in an isolated network while leaving the production VM untouched.Read 7 Oct 2026 · docs.awan.io
Incremental sync: The initial replication is a full disk copy and later syncs transfer only changed blocks.Read 7 Oct 2026 · docs.awan.io
Integration: DRM connects to each site's Cockpit console, while Cockpit coordinates replication performed directly between Vapor hosts.Read 7 Oct 2026 · docs.awan.io
Intended use: Awanio describes DRM as useful for protecting many workloads and recovering them as ordered groups, while Cockpit's Replication tab can manage a single VM directly.Read 7 Oct 2026 · docs.awan.io
Licensing: Orchestrated recovery requires the Disaster Recovery entitlement enabled on Cockpit at both sites and a DRM license or active trial.Read 7 Oct 2026 · docs.awan.io
Monitoring: The DRM Overview reports aggregate recovery health while the Workloads view shows per-workload replication status and recovery-point age.Read 7 Oct 2026 · docs.awan.io
Network requirements: The guide specifies inter-site connectivity on ports 7770 for Vapor replication, 7771 for Cockpit pairing and orchestration, and 7772 for DRM recovery-plan replication.Read 7 Oct 2026 · docs.awan.io
Notable limitation: To move a workload to a different recovery site or datastore, replication must be disabled and the workload re-enrolled with the new target.Read 7 Oct 2026 · docs.awan.io
Plan replication: A plan authored at the primary site is replicated as a read-only copy to the paired recovery site's DRM so it can run if the primary is lost.Read 7 Oct 2026 · docs.awan.io
Recovery lifecycle: From one console, DRM coordinates test failover, planned migration, emergency failover, reprotect, and failback.Read 7 Oct 2026 · docs.awan.io
Recovery plans: Plans group workloads into ordered runbooks with priority groups and boot delays for coordinated recovery.Read 7 Oct 2026 · docs.awan.io
Recovery site execution: A recovery site's DRM can execute a replicated read-only recovery plan if the primary site is lost.Read 7 Oct 2026 · docs.awan.io
Replication: It enrolls VMs for scheduled disk replication from a primary site to a recovery site, with configurable RPO, recovery-point retention, and traffic compression.Read 7 Oct 2026 · docs.awan.io
Replication settings: Workload enrollment lets administrators choose a recovery site and datastore, an RPO, retained recovery points, and traffic compression.Read 7 Oct 2026 · docs.awan.io
Trial limit: A fresh DRM starts with a time-limited trial that permits a small number of protected workloads; the page does not state the trial duration or workload count.Read 7 Oct 2026 · docs.awan.io

Plans and prices

Time-limited trial Free Small number of protected workloads; trial duration not stated Read 7 Oct 2026 · docs.awan.io

Every Awanio Disaster Recovery Manager plan and price →

Strong points and limits

Strong points

Coordinates recovery runbooks across workloads
Supports isolated test failover
Can orchestrate failback and reprotection
Reports aggregate health and per-workload replication status

Limits

Requires two sites with Cockpit and Vapor
Orchestrated recovery needs entitlements at both sites
Emergency failover may lose data after the latest recovery point
Moving a workload requires disabling and re-enrolling replication

Who it suits

DRM suits administrators protecting virtual machines across paired sites, especially when workloads need to recover in ordered groups. It requires a two-site Cockpit and Vapor deployment.

Verdict

DRM provides an ordered recovery workflow for virtual machines across paired sites, with test failover and failback support. Deployment prerequisites and the possible loss of data newer than the last completed recovery point warrant attention.