Selected VMs from the Protected Domain can be customized with runbook settings and grouped into Runbook Groups, where they are recovered according to a user-specified boot sequence and delay, with customized VM and network settings.

    1. From the Runbook Settings screen, click the Create Group button to create a new runbook group.

Figure 111: Create a runbook group.

    1. Follow the guided steps of the pop-up dialog window:

Step: General

      • Enter a name for the runbook group. 
      • If needed, in the lower portion of the screen apply custom pre- and post- scripts to automatically run prior to and following operation of the runbook group.
      • Click the Next button.

Figure 112: Enter general runbook settings.

Step: Select VMs

      • Select VMs to include in the runbook group from the list.
        • Independent VMs that are not currently associated with other runbook groups will appear on the selection list.
      • Click the Next button.

Figure 113: Select VMs to include in the runbook group.

Note: When constructing a runbook group, you will only be able to select from the list of Independent VMs. VMs cannot simultaneously belong to multiple runbook groups.


Step: Edit VM Settings

      • Specify parameters for recovering the VMs, including: boot sequence, boot delay, # of CPUs, memory allocation, post-scripts, and network settings.
        • Click any displayed parameter value to edit its setting.
        • The boot sequence of a VM within the runbook group can be changed by dragging it to a new position on the list.
        • The boot delay is the number of seconds the system will pause after a VM has been booted before starting the process for the next VM of the group.
        • A post-script can be applied to each individual VM of the group and will run immediately after the VM is processed.
        • Options to Retain MAC, Power Off VMs, and Retain UUID can be applied to all VMs of the runbook group.
          • Retain MAC: preserves the existing MAC address values for each VM's virtual NICs so they will continue to use their original MAC address after they are restored.
          • Keep VMs Powered Off: keeps the recovered VMs in a powered off state. By default, VMs are powered-on automatically upon recovery.
          • Retain UUID: preserves the VM instance UUID of the protected VMs ensuring they will remain unchanged after recovery.
      • These settings will be applied to each VM when the runbook group is executed.

Figure 114: Specify runbook recovery settings for the VMs.

      • Static IP addresses can be manually configured for individual VMs of the group. 
        • Click a numbered link under the NICs column to manually configure the IP address settings of a VM.
          • The number indicates the number of NICs currently assigned to the VM.
          • A window will appear allowing you to edit the network settings of the VM.

Figure 115: Configure VM network settings.

          • Click a displayed parameter value to edit its setting.

Figure 116: VM NIC settings window.

        • To configure a static IP address for a NIC:
          • Click the Configure link under the IP column to display the Static IP Address configuration window.
          • Specify IP address details for the NIC.
          • Click the Configure button to save the NIC settings for the VM.

Figure 117: Configure static IP (optional).

Step: Summary

      • Review all entered settings on the Summary step.
        • Use the Back button to modify any settings that need to be changed.
        • If the settings are correct, click the Create button.
        • The runbook group will be created.

Figure 118: Review details and create the runbook group.

    1. The status of both failover and failback runbooks will now appear as “Configured”.
      • Failover and failback runbooks are created in pairs using the same initial group of VMs and settings.
        • If necessary, the settings of either runbook can be independently customized by clicking its respective Details link and making changes.
      • A test failover runbook can be set up independently from failover/failback runbooks using the same steps described above.

Figure 119: Runbooks are now configured.

Notes:
1) Failover and failback runbooks are always created in matched pairs, but their configuration settings can be customized individually.
2) The boot sequence of VMs is the same for both runbooks of the pair (failover and failback). Changing one automatically changes the other; they cannot be made different from one another.
3) Failback runbook settings can be customized while failover is running.