We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Backup

Booting a Hyper-V Virtual Machine with a Non-Primary Boot Disk in Cloud LiveBoot

  • Last updated on

This article refers to the Barracuda Backup firmware version 6.3.04 and higher, and supported versions of VMWare and Microsoft Hyper-V.

Cloud LiveBoot is available to all Barracuda Backup customers with Instant Replacement and a Cloud storage subscription, and is available to all customers excluding those in Japan.

Barracuda Cloud LiveBoot supports a maximum of four virtual disks per guest VM.

In cases where a Hyper-V VM boot disk is not the first (primary) disk, there is an additional step that must be completed to boot the VM. Use the following steps to complete the boot process:

Before getting started, verify you have added a Hyper-V virtual machine on the Restore > Cloud LiveBoot page, have clicked the Start button, and that the virtual machine has a status of Running.

  1. Open the VNC client of your choice, for example, RealVNC or TightVNC.
  2. In your VNC client, enter the IP Address and password for the affected Hyper-V VM found in the VNC column of the Cloud LiveBoot page:
    IPAddressPassword.png
  3. Once successfully connected to your Hyper-V VM with your VNC client, select your boot device:
    SelectBootDevice.png
  4. The Hyper-V VM should continue booting as normal.

    If the wrong disk is selected, the error message No bootable device displays:
    NoBootableDevice.png

    If this occurs, restart the VM and retry the boot process.

 

 

Last updated on