Disaster Recovery Tasks

Alteeve Wiki :: How To :: Disaster Recovery Tasks

Note: At this time, DR management is via the command line. DR management in the UI is planned.

Disaster Recovery on M3 clusters provides a way to create a copy of a server on a remote "DR Host". These are machines that generally match the capabilities of the Anvil! node the server runs on, but that's not a requirement.

Servers don't live migrate to the DR host, and the DR host itself is not a member of the subcluster. Simply speaking, the DR host has a copy of the server's virtual hard drive(s), and the hypervisor has the configuration needed to boot the server. If the production node is destroyed, you can boot the server on the DR host.

Linking DR Hosts

A DR host can be used by multiple Anvil! nodes, and multiple DR hosts can be used by a given Anvil! node. To support this, a "linkage" need to be created to connect a DR host to a subnode.

You can see the current list of Anvil! nodes, DR hosts and servers using the anvil-manage-dr --list command

anvil-manage-dr --list

Anvil! Nodes
- Node Name: [an-anvil-01], Description: [Demonstration anvil node]
 - No linked DR hosts yet.
- Node Name: [an-anvil-02], Description: [RX200 S8 Test Node]
 - No linked DR hosts yet.
- Node Name: [an-anvil-04], Description: [Test Mixed-Hardware Anvil! Node]
 - No linked DR hosts yet.

-=] DR Hosts
- Name: [an-a01dr01.alteeve.com]

-=] Servers
- Server name: [srv01-primary-dc] on Anvil! Node: [an-anvil-01]

Linking a DR host to an Anvil! node

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche!	Alteeve Enterprise Support	Community Support
© 2025 Alteeve. Intelligent Availability® is a registered trademark of Alteeve's Niche! Inc. 1997-2025
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.