The Boot tab allows to immediately boot VM or DR Image backup jobs. When you boot a backup job on the CFA, files from the job are cloned, and the copy is booted, so the job remains unaltered. You can use a VNC viewer software to access the console of the booted VM.

You can boot most backups, except for those VMs and DR Images configured to use EFI BIOS.

For the clients booted on the CFA to be able to access the network, their virtual NIC must be bridged to one of the physical NICs in the CFA. CFA NICs can be set to allow this bridging by selecting Export Virtual in System > Network Adapters settings. (See Network Adapters settings.)

To prevent the booted clients from affecting the CFA performance, each CFA model has its own default limit of the simultaneously booted clients.

CFA model Simultaneous boots allowed
Current models  
550 N/A
960/965 2
1550 2
2750 4
4550 8
Legacy models  
950/955 2
1200 2

However, you can change this parameter in System > Local Boot settings.

Supported operating systems

The following operating systems support the local boot feature:

Operating system Architecture  
  x32 x64
Windows Server 2003 R2 SP2 and earlier Yes Yes
Windows Server 2008 R1 Yes Yes
Windows Server 2008 R2 SP1 Yes Yes
Windows Server 2012 R1 N/A Yes
Windows Server 2012 R2 N/A Yes
Windows SBS 2011 Yes Yes
Windows XP Yes Yes
Windows Vista Yes Yes
Windows 7 Yes Yes
Windows 8 Yes Yes
Windows 8.1 Yes Yes
Windows 10 Yes Yes

Overview subtab

The Overview subtab shows the list of VM and DR Image clients, which can be booted as a VM running on the CFA or in the cloud, grouped in categories.

Information

Information on the Overview subtab is presented in the table format with the following default columns:

Column name Column description
Client Name Name of the client
Recovery Points Number of valid recovery points, which can be used when booting the VM
VM Size Total size of the client
Boot Group Boot group, to which the client belongs

Special actions

All special actions on the Overview subtab are available via

  • the toolbar on the top left, or

  • the context menu of a client

Boot a single client

To boot a single VM or DR Image client

  1. Click Boot on the toolbar or in the context menu of a client.

    The Boot Wizard starts.

  2. Select a recovery point from the list of available points.

    infoThis step shows only if the client has multiple recovery points.
  3. Specify the boot settings, if needed.

    Setting Description
    Basic settings  
    Name Name of the VM configuration, under which it shows in the list of VMs
    Base Memory Amount of RAM to be used by the booted VM
    Processor(s) Number of processors to be used by the booted VM
    Network Type of network for the booted VM
    VNC Port Port to access the booted VM on. Sequentially picked from the list of available ports unless specified manually
    VNC Password Password to access the booted VM. Generated automatically unless specified manually
    VNC Console Keymap Keyboard mapping to be used within VNC. Default is English (United States)
    Advanced settings  
    Disk Controller Select when booting a VM with a specific set of boot devices
    Processor Model Select if the operating system of the booted VM requires a specific CPU architecture
    Pointing Device Select to match your actual pointing device
    Network Adapter Select to ensure the booted VM loads proper drivers for the NIC, with which it was backed up
    MAC Address Select to boot the VM with the same MAC address, and retain the same static IP or DHCP address

    QEMU commands

    QEMU commands allow to override any boot settings specified previously.

    notification_important These to be used preferably only if instructed by Infrascale Support.

    For the comprehensive details, see the QEMU User Documentation.

  4. Click Boot to boot the client.

    infoThe client will boot only if it does not exceed the number of simultaneously booted VMs.

Boot a group of clients

To boot a group of VM or DR Image clients, click Boot Entire Group on the toolbar or in the context menu of a client.

infoIf the number of VMs in the booted group exceeds the number of simultaneously booted VMs, none of them will boot.

If the name of a VM in the booted group is identical to the name of an already booted VM, the new VM will have an incremental number added to its name.

Active subtab

The Active tab lists VMs currently booted on the CFA.

Information

Information on the Active subtab is presented in the table format with the following default columns:

Column name Column description
Status Current status of the VM
Name Name of the VM
VNC Address VNC address to access the booted VM
VNC Password VNC password to access the booted VM
Boot Group Name of the boot group, to which the VM belongs
Preview Preview thumbnail of the booted VM

Special actions

All special actions on the Active subtab are available via

  • the toolbar on the top left, or

  • the context menu of a VM

Action name Action description
Power On Boot the VM
Power Off Shut down the VM
Reboot Restart the VM
Reset Force restart without the guest OS warning (can result in data loss). Useful is guest OS is not responding
Pull Plug Force shutdown without the guest OS warning (can result in data loss). Useful if guest OS is not responding
Wake Up  
Settings View boot settings of the VM
Create Backup Job Create a backup job from the current state of the VM 1. The job can then be restored or archived as usual
Delete Delete the current state of the VM and remove it from the tab

Interact with a booted client

You have two options to interact with a booted VM:

  • via the browser-based VNC viewer (click the thumbnail in the Preview column or the address link in the VNC Address column)

  • via a VNC client software

Orchestration subtab

The Orchestration subtab allows to configure 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.

info Changes to the DR LAN settings will cause the VPN connection to Infrascale cloud to not work properly. Please contact Infrascale Support to have the VPN settings updated in the cloud.

To test the orchestration configuration, click Run.

You can check the status of the booted VMs on the Active subtab.

  1. Backup jobs created from the Boot tab cannot be archived with the dehydrated archive option.