Task
Create a DR plan for the VMware target cloud.
Solution
This an essential step taken in advance when planning your strategy for a possible failover of selected machines to the target cloud and eventual disaster recovery.
The DR plan is the prerequisite that regulates this sequence and specifies the primary values. It is created by accessing your Acura instance and clicking on the "Add" button in the "DR plans" section (or editing an existing one by selecting the "Edit" option).
The text of a DR plan must be configured in JSON format and pasted into the editing field on the "Expert" tab. Review and Save.
Example of a DR plan:
- {
- "devices": {
- "ubuntu-small": {
- "id": "52560751-12ca-9b0e-db00-02cb718a138a",
- "guest_id": "centos64Guest",
- "hardware_ver": "vmx-11",
-
"firmware": "EFI",
- "flavor": "1-2",
- "rank": 0,
- "ports": [
- {
- "name": "port_0",
- "subnet": "main_subnet"
- }
- ]
- }
- },
- "subnets": {
- "main_subnet":
- {"subnet_id": "VM Network"}}
- }
- }
This is a JSON list containing specific information about your instances, the ones that you wish to include into the recovery plan: their names, IDs, available hardware configuration as flavor and hardware_ver, rank (desired boot order), boot option, utilized ports, and subnet information.
- The flavor format is defined as "vCPU-RAM", so the flavour "1-2" is equivalent to 1 CPU and 2Gb RAM for a machine.
- Subnet_id is the name of a VMware network, a wide-spread template being VM Network, that is the standard default name, but make sure to check if it's relevant in your case.
- To select a boot option, add "firmware": "BIOS" or "firmware": "EFI" line to your DR plan. If not specified, BIOS will be used by default.