- Home
- Disaster Recovery Software
- Awanio Disaster Recovery Manager
Awanio Disaster Recovery Manager
Jakarta, Indonesia
What it is
Awanio Disaster Recovery Manager coordinates virtual-machine recovery across paired Awanio Cockpit sites. Administrators can enroll VMs for scheduled disk replication and set a recovery site and datastore, RPO, recovery-point retention, and traffic compression. The initial sync copies the full disk, with later syncs transferring changed blocks. Recovery plans organize workloads into ordered runbooks with priority groups and boot delays; a primary-site plan is replicated as a read-only copy for execution at the recovery site. DRM supports isolated test failover, planned migration, emergency failover, reprotection, and failback. Test failover boots a copy in an isolated network while production remains untouched. Emergency failover uses the latest completed recovery point, so data written afterward may be lost. Deployment requires two sites, each with Cockpit and at least one Vapor host, administrator access to both, and inter-site 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 trial is time-limited and covers a small number of workloads.
For and against
For
- Coordinates test failover, migration, emergency recovery, and failback
- Recovery plans group workloads into ordered runbooks
- Test failover uses an isolated network
- Overview and Workloads views report recovery status
Against
- Requires Cockpit and a Vapor host at each of two sites
- Requires connectivity on ports 7770, 7771, and 7772
- Emergency failover may lose data after the latest recovery point
- Changing a recovery target requires disabling replication and re-enrolling
The verdict
DRM provides coordinated recovery workflows for virtual machines across paired Awanio sites. The two-site setup, entitlement, licensing, and network requirements should be checked before deployment.
Who it suits
DRM is intended for administrators protecting virtual machines across paired sites, particularly those recovering workloads as ordered groups. Its deployment prerequisites make it a fit for organizations able to operate the required two-site setup.
Plans and prices
Time-limited trial
Small number of protected workloads; trial duration not stated
Read 7 Oct 2026 · docs.awan.io
On the record
- Deployment prerequisites
- A deployment requires two sites, each running Cockpit and at least one Vapor host, plus administrator access to both sites.docs.awan.io · read 7 Oct 2026
- 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.docs.awan.io · read 7 Oct 2026
- Failback
- After failover, DRM can reverse replication toward the original site and later return the workload there through planned failback.docs.awan.io · read 7 Oct 2026
- Failover limitation
- Emergency failover uses the latest completed recovery point, so data written after that point can be lost.docs.awan.io · read 7 Oct 2026
- Failover modes
- DRM supports non-disruptive test failover, planned migration, and emergency failover from the latest completed recovery point.docs.awan.io · read 7 Oct 2026
- Failover rehearsal
- Test failover boots a workload copy in an isolated network while leaving the production VM untouched.docs.awan.io · read 7 Oct 2026
- Incremental sync
- The initial replication is a full disk copy and later syncs transfer only changed blocks.docs.awan.io · read 7 Oct 2026
- Integration
- DRM connects to each site's Cockpit console, while Cockpit coordinates replication performed directly between Vapor hosts.docs.awan.io · read 7 Oct 2026
- Integrations
- DRM manages its local site through Cockpit, while Vapor performs disk replication and boots recovered virtual machines.docs.awan.io · read 7 Oct 2026
- 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.docs.awan.io · read 7 Oct 2026
- Intended users
- The documentation describes a site-level tool for administrators protecting and recovering virtual machines across paired sites.docs.awan.io · read 7 Oct 2026
- Licensing
- Orchestrated recovery requires the Disaster Recovery entitlement enabled on Cockpit at both sites and a DRM license or active trial.docs.awan.io · read 7 Oct 2026
- Maker
- Awanio describes itself as an enterprise virtualization and cloud orchestration technology company engineered in Indonesia and deployed globally.awan.io · read 7 Oct 2026
- Monitoring
- The DRM Overview reports aggregate recovery health while the Workloads view shows per-workload replication status and recovery-point age.docs.awan.io · read 7 Oct 2026
- 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.docs.awan.io · read 7 Oct 2026
- 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.docs.awan.io · read 7 Oct 2026
- 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.docs.awan.io · read 7 Oct 2026
- Purpose
- DRM orchestrates virtual-machine disaster recovery across paired Awanio Cockpit sites.docs.awan.io · read 7 Oct 2026
