Skip to main content

Restore a machine to a cloud powered by VMware

You can restore a backup created with Veeam Agent from the Selectel repository to a cloud powered by VMware.

For recovery to be possible, you must have a system image with required drivers (Linux) or a boot disk (Windows) created before recovery; read more in the instructions Preparing for recovery using Veeam Recovery Media.

For recovery, you will need:

  • a machine backup created in Entire computer mode or containing the necessary partitions;

  • resources in a cloud powered by VMware:

    • a virtual data center;
    • a vApp;
    • a network with internet access.

For more information on connecting to a cloud powered by VMware, see the instructions Cloud powered by VMware: Quick Start.

After restoration, the server name, login, and root password remain the same as the original from the backup. They can be redefined using guest OS recustomization or manually.

To restore a virtual machine:

  1. Create an empty virtual machine.
  2. Optional: install VMware Remote Console.
  3. Start the empty virtual machine.
  4. Load Tools virtual device drivers (Windows only).
  5. Restore the backup to the virtual machine.
  6. Configure the network environment.
  7. Deploy a virtual machine with Windows Server (Windows only).
  8. Install VMTools.
  9. Configure backups on the restored machine.

1. Create an empty virtual machine

  1. From the control panel, open the Cloud Director panel: in the top menu, click ProductsCloud powered by VMwareCloud Director section.

  2. Open the virtual data center page.

  3. Go to the ComputevApps section.

  4. In the vApp card, click ACTIONS.

  5. Click AddAdd VM.

  6. Click Add virtual machine.

  7. In the Name field, enter a name for the virtual machine.

  8. In the Computer name field, enter the host name.

  9. In the Type field, select New.

  10. In the OS family field, select the same OS family as on the original server (the backup source).

  11. Specify the Operating System — the same OS as on the original server (the backup source).

  12. Specify the Boot image:

    • for Linux: veeam-recovery-media-5.0.2.4567_x86_64.iso;
    • for Windows: Veeam recovery media.
  13. In the Virtual CPUs field, specify the number of vCPUs.

  14. In the Memory field, specify the amount of memory.

  15. In the Storage block, remove all disks. They will be added later.

  16. To select a storage policy for the virtual machine, check the Use custom storage policy checkbox and, in the Storage Policy field, select the required policy. If you do not select a policy, the default one will be applied.

  17. In the Networking block, click CUSTOMIZE.

  18. In the Network column, select a network — default_net or another network with internet access.

  19. In the Network Adapter Type column, select VMXNET3.

  20. In the IP Mode column, select the mode appropriate for the chosen network.

  21. Click OK.

  22. Check the new VM parameters and click ADD.

  23. Open the vApp page → Virtual Machines section.

  24. Open the virtual machine page.

  25. Go to the HardwareHard Disks section.

  26. Click EDIT.

  27. Click ADD.

  28. Configure each virtual disk to match the disks on the source machine:

    • Size — volume sufficient for restoring the source data;
    • Policy — any;
    • Bus TypeParavirtual (SCSI);
    • Bus Number, Unit Number — default.
  29. Click SAVE.

2. Optional: install VMware Remote Console

VMware Remote Console is required to use the mouse in the virtual machine console.

  1. From the control panel, open the Cloud Director panel: in the top menu, click ProductsCloud powered by VMwareCloud Director section.
  2. Open the virtual data center page.
  3. Go to the ComputevApps section.
  4. Open the vApp page → Virtual Machines section.
  5. Open the virtual machine page.
  6. Click ALL ACTIONSVM ConsoleDownload VM Remote Console. You will need a VMware Customer Connect account to download it, which you can create while downloading VMware Remote Console.

3. Start the empty virtual machine

  1. From the control panel, open the Cloud Director panel: in the top menu, click ProductsCloud powered by VMwareCloud Director section.
  2. Open the virtual data center page.
  3. Go to the ComputevApps section.
  4. In the vApp card, click ACTIONS.
  5. Click PowerPower on.
  6. In the virtual machine menu, click VM ConsoleLaunch Remote Console or Launch Web Console. The Veeam Recovery Media recovery environment will load automatically. If the environment does not load, check the settings.
  7. Wait for Veeam Recovery Media to load the network configuration and SSH (if DHCP is available). If you do not require SSH, click Proceed without SSH. After 60 seconds, the parameters of the automatically configured network and access will be displayed.

Verify Veeam Recovery Media settings

If Veeam Recovery Media does not load, check the settings.

  1. From the control panel, open the Cloud Director panel: in the top menu, click ProductsCloud powered by VMwareCloud Director section.

  2. Open the virtual data center page.

  3. Go to the ComputevApps section.

  4. Open the vApp page → Virtual Machines section.

  5. Open the virtual machine page.

  6. Go to the HardwareRemovable Media section.

  7. Make sure the correct boot disk is selected in the CD/DVD drive field:

    • for Linux: veeam-recovery-media-5.0.2.4567_x86_64.iso
    • for Windows: Veeam recovery media.
  8. Go to the General section.

  9. Make sure Enabled is set in the field Enter BIOS Setup.

  10. Reboot the virtual machine.

4. Load Tools virtual device drivers (Windows)

Drivers only need to be loaded for Windows-based machines.

  1. In Veeam Recovery Media, go to the Tools section.
  2. Select Load Driver.
  3. For the SAS Controller and Ethernet Controller drivers, click Install driver.
  4. Make sure both drivers have an Online status.
  5. Check the Inject these drivers into operating system while performing bare metal recovery checkbox.
  6. Click OK.

5. Restore the backup to a virtual machine

Use the Restore a virtual machine instructions for your operating system.

6. Configure the network environment

By default, the virtual machine network adapters do not match the network adapters of the original machine. Configure the settings according to the requirements of the new network environment.

7. Deploy a virtual machine with Windows Server

If you are using Windows, use the Deploy a virtual machine with Windows Server instructions.

8. Install VMTools

  1. Install VMTools (Perl required):

    sudo apt install open-vm-tools
  2. Make sure the service is running:

    systemctl status open-vm-tools
  3. If the virtual network adapter drivers or open-vm-tools are missing, the virtual machine will not be connected to the network. In this case, complete steps 1-4 of the Install VMware Tools instructions.

  4. Verify if the disk with VMTools is mounted automatically on the virtual machine:

    mount

    Command output:

    /dev/cdrom on /mnt/cdrom
  5. If the disk is not mounted, mount it, taking into account the file device paths and mount points depending on the distribution:

    sudo mkdir /mnt/cdrom
    sudo mount /dev/cdrom /mnt/cdrom
  6. Check if an archive with the .tar.gz extension containing VMTools exists on the mounted device:

    ls /mnt/cdrom
  7. Extract the archive to the /tmp: directory:

    tar -zxpf /mnt/cdrom/<vmwaretools.tar.gz> -C /tmp

    Specify <vmwaretools.tar.gz> — the name of the VMware Tools archive, which depends on the version.

  8. Go to the directory with the extracted archive:

    cd /tmp/vmware-tools-distrib
  9. Run the installation script:

    sudo ./vmware-install.pl
  10. Follow the installer instructions.

  11. After installation, reboot the virtual machine.

9. Configure backups

The Cloud powered by VMware backup service is available for backing up VMware virtual machines.

Veeam agents use the BIOS UUID to identify machines. The restored machine has a new BIOS UUID, so existing backup chains in Veeam Agent might fail to continue.

  1. Remove the Veeam agents:

    Ubuntu, Debian:

    sudo apt remove veeamma veeam

    RHEL, CentOS, Fedora:

    sudo yum remove veeamma veeam

    SuSE:

    sudo zypper remove veeamma veeam
  2. Install the management agent and backup agent again.