Axcient Help Center

Failover VM (Local)

Axcient's Failover Virtual Machine (VM) allows you to start a virtual machine on the local Axcient appliance in the event a protected device is lost or fails. Although the Failover VM can run indefinitely, it is not intended as a long-term replacement for a permanent server. The server functions should be transferred back to a primary device as soon as possible.

Test VM Screen Shot Validation

Screen shot validations are automatically performed after the successful completion of replication jobs to ensure that replicated devices can be virtualized in the event of a disaster situation.

To ensure that screen shot validations can be successfully performed, please set the Screen Sleep Timeout option to 30 minutes or longer. When a Test VM is being deployed, minimal resources are allocated to the deployment so that they can be used by other processes on the appliance, resulting in a longer deployment process. If the Test VM enters sleep mode during the deployment, a screen shot created during this validation will depict a black screen and will result in a failed validation.

Be advised that the longer deployment process does not reflect the actual deployment time for a Production Failover VM.

Recovery Steps

Warning

When protecting a device with the Windows Server 2008 SP1 operating system, you must confirm that the 955430 package has been installed on the target device before performing the recovery. Please refer to the Microsoft KB955430 article for more information and to download the package.

Without the 955430 package, WS2008 will be unable to install GPLPV drivers due to Windows not trusting the certificates used to sign drivers.

This will mean that you will not be able to deploy a local failover VM for the device if it has more than 4 drives.

  1. On the Axcient Web Application Dashboard, click the Sites tab.

    BRC_Sites.png
  2. On the Sites page, click the Details button for the desired Site.

    ace-brc-sites-page.png
  3. On the Site Details page, click the Recover button.

    ace-brc-click-recover-1024x571.png
  4. On the Recover Something screen, select the Make it Virtual option.

    select-make-it-virtual.png
  5. On the Virtualize a Device screen, select the Start a Virtual Machine option.

    select-start-a-virtual-machine-locally.png
  6. Select the type of local virtualization to deploy:

    1. Select the Make it a Test option to test the virtualization process and verify the availability of recovery points in case of an emergency.

    2. Select the Put it in Production option in the event of a disaster. This local failover VM can be used to temporarily replace production devices until a permanent replacement is ready.

      select-type-of-virtualization.png
  7. Select the device to virtualize and click Let's Do It!.

    select-device-to-virtualize.png
  8. If this is a test, configure the Test VM:

    1. In the Recovery Point drop-down menu, select the recovery point time.

    2. Using the RAM slider, allocate virtual RAM.

    3. Using the CPU slider, allocate virtual CPU cores.

    4. In the Use Current Address field, enable or disable the option to use the device IP address.

    5. In the VNC field, enable or disable the option to allow a VNC connection (this option is only available when manually configuring the IP address).

    6. In the VNC Password field, enter the VNC password (only if the VNC connection is enabled).

    7. In the IP Address field, enter the IP address (only if the Use Current Address field is disabled).

    8. Click the Looks Good button to continue. Please note that a Test Failover VM cannot communicate with any other device. A Test VM cannot be accessed through RDP.

      vm-config-local.png
  9. If this is production, configure the production VM:

    1. In the Recovery Point drop-down menu, select the recovery point time.

    2. Using the RAM slider, allocate virtual RAM.

    3. Using the CPU slider, allocate virtual CPU cores.

    4. In the Use Current Address field, enable or disable the option to use the device IP address.

    5. In the VNC field, enable or disable the option to allow a VNC connection (this option is only available when manually configuring the IP address).

    6. In the VNC Password field, enter the VNC password (only if the VNC connection is enabled).

    7. In the IP Address field, enter the IP address (only if the Use Current Address field is disabled).

    8. Click the Looks Good button to deploy the local Production VM failover.

      vm-config-production.png

     

Viewing the Local Failover Details

You can view the local failover information for the device after the failover VM is running.

  1. On the Web Application Dashboard, expand the Activities of Interest section, click Local Virtualizations, and then click the Manage VMs link.

    local-vm-activities.png
  2. The Local VMs section of the Client's Device List page displays. Click to expand the device and view information about the failover VM, including:

    • Recovery Point - The recovery point selected

      in the failover deployment.

    • VNC - Whether VNC is enabled or disabled.

    • VNC Password - The configured VNC

      password.

    • Duration - Length of time the failover VM has been running.

    • RAM - The amount of RAM allocated in the failover deployment.

    • IP - The IP address or domain name of the failed over VM.

      local-vm-device-list.png
  3. The following administrative buttons can also be used to manage the device:

    • Click the View Device button to visit the Device Details page for the specified device.

    • Click the Stop VM button to change the VM status from Running to Ready.

    • Click the Discard VM button to completely discard the local failover VM.

Accessing the Local Failover VM

The local failover VM can be accessed in two different ways: VNC and Remote Desktop Protocol.

Warning

When failing over a device with 5 drives or more in either a test or production environment, you might see an extra disk displayed in the Disk Management/Device Manager after launching. This extra disk will not show up in My Computer, and you will receive an Incorrect Function error when attempting to bring the disk online. This extra disk will not affect the failover or any other recovery-related process associated with the failover VM.

5-disk-error.png
Method 1: VNC

A VNC agent can be used to connect to both Test and Production failover VMs. Axcient recommends using the UltraVNC Viewer.

For a single local failover VM:

  1. Open the VNC agent.

  2. In the VNC Server field, enter the IP address of the appliance.

  3. Enter the VNC password if configured.

For multiple failover VMs:

  1. Open the VNC agent.

  2. In the VNC Server field, enter the IP address of the appliance, along with the port number of the failover VM.

    VM ports are numbered in sequential order of when they were deployed, starting with 5901.

    Example: 192.168.99.234:59001

  3. Enter the VNC password if configured.

    vnc-img.png
Method 2: Remote Desktop Protocol

Use the Remote Desktop Protocol (RDP) tool to connect to the local failover VM. RDP can only be used to connect to Production failover VMs.

To access the failover VM using an RDP agent:

  1. Open the RDP agent.

  2. Create a new RDP connection using the production

    IP address and the administrator login credentials.

  3. Connect to the local failover VM.

    rdp-img.png