Introduction
The Orchestration subtab allows configuring bootable backups to be a push-button failover to the Infrascale cloud.
Orchestration scenario is built using the following three components:
| Component name | Component description |
|---|---|
| Group | Allows to create a group of devices. All devices in the group are booted simultaneously |
| Wait | Allows to set a time delay (in seconds) between the booted VMs or groups. This can be useful to make sure your AD server starts before your Exchange server |
| Devices | List of all available VMs that can be included in the scenario |
To add a component to the scenario, drag and drop it to the configuration area on the right.
To rename a Group, click the pencil icon, enter the desired Group name, and then click Apply.
To edit a Wait value, click the pencil icon, enter the desired value in seconds, and then click Apply.
To remove a Group or a Wait from the scenario, click X.
To remove a client from the scenario, hover over the client, click the three dots, and then click Remove from Orchestration.
Special actions
All special actions on the Orchestration subtab are available via the toolbar.
| Action name | Action description |
|---|---|
 | Save the current orchestration configuration |
 | Start the current orchestration process |
 | Configure DR LAN used by orchestration to set the subnet, in which the VMs will run |
Configuring DR LAN
With DR LAN you are able to set whether or not your VMs are able to have access outside the Infrascale cloud. You are also able to specify the subnet mask and the default gateway.
Enable DHCP and IP Restore will attempt to boot the VM with the MAC address it was up with and restore a static IP. If the client was backed up with a DHCP address, it will assign the boot with an address inside the DHCP range.
Note
To test the orchestration configuration, click Run.
You can check the status of the booted VMs on the Active subtab.
