Skip to main content
Restore a machine to a Cloud powered by VMware
Last update:

Restore a machine to a Cloud powered by VMware

You can restore a backup created with Veeam Agent from the Selectel repository to Public Cloud powered by VMware. For more information about recovery via Veeam Recovery Media, see Recovery with Veeam Recovery Media.

For recovery to be possible, you must have a system image with required drivers (Linux) or a boot disk (Windows) created before recovery, see Recovery with Veeam Recovery Media.

You'll need:

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

  • resources in a Public Cloud powered by VMware:

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

For more information about connecting a public cloud, see Public Cloud powered by VMware: Quick Start.

After the restore, the server name, root login and password match the original ones from the backup. They can be overridden 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 an empty virtual machine.
  4. Load Tools virtual device drivers (Windows only).
  5. Restore backup to virtual machine.
  6. Configure the network environment.
  7. Deploy a virtual machine with Windows Server (Windows only).
  8. Install VMTools.
  9. Configure backup on the restored machine.

1. Create an empty virtual machine⁠

  1. From Control Panel, open the Cloud Director panel: Cloud powered by VMware → Cloud Director.

  2. Open the virtual data center page.

  3. Go to Compute → vApps.

  4. In the vApp card, click ACTIONS.

  5. Press Add → Add 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 OS family as on the original server (backup source).

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

  12. Specify 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 CPUs.

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

  15. In the Storage block, delete all disks. These will be added at a later date.

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

  17. In the Networking block, click CUSTOMIZE.

  18. In the Network column, select the 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 appropriate mode for the selected network.

  21. Press OK.

  22. Check the parameters of the new VM and press ADD.

  23. Open the vApp page → section Virtual Machines.

  24. Open the virtual machine page.

  25. Go to Hardware → Hard Disks.

  26. Press EDIT.

  27. Press ADD.

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

    • Size — the volume sufficient to restore the original data;
    • Policy — any;
    • Bus Type — Paravirtual (SCSI);
    • Bus Number, Unit Number — default.

  29. Press SAVE.

2. Optional: Install VMware Remote Console⁠

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

  1. From Control Panel, open the Cloud Director panel: Cloud powered by VMware → Cloud Director.
  2. Open the virtual data center page.
  3. Go to Compute → vApps.
  4. Open the vApp page → section Virtual Machines.
  5. Open the virtual machine page.
  6. Click ALL ACTIONS → VM Console → Download VM Remote Console. A VMware Customer Connect account will be required for downloading, and can be registered when downloading VMware Remote Console.

3. Start an empty virtual machine⁠

  1. From Control Panel, open the Cloud Director panel: Cloud powered by VMware → Cloud Director.
  2. Open the virtual data center page.
  3. Go to Compute → vApps.
  4. In the vApp card, click ACTIONS.
  5. Press Power → Power on.
  6. From the virtual machine menu, click VM Console → Launch Remote Console or Launch Web Console. The Veeam Recovery Media will be loaded automatically. If the environment does not boot, check the settings.
  7. Wait for Veeam Recovery Media to load the network and SSH configuration (if DHCP is available). If SSH is not required, click Proceed without SSH. After 60 seconds, the automatically configured network and access parameters will be displayed.

Check Veeam Recovery Media settings⁠

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

  1. From Control Panel, open the Cloud Director panel: Cloud powered by VMware → Cloud Director.

  2. Open the virtual data center page.

  3. Go to Compute → vApps.

  4. Open the vApp page → section Virtual Machines.

  5. Open the virtual machine page.

  6. Go to Hardware → Removable Media.

  7. Make sure that 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 General.

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

  10. Reboot the virtual machine.

4. Download Tools Virtual Device Drivers (Windows)⁠

Driver downloads are only needed for Windows machines.

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

5. Restore backup to virtual machine⁠

Use the Restore Virtual Machine instructions for the desired OS.

6. Configure the network environment⁠

By default, the virtual machine's network adapters do not match the network adapters of the original machine. Configure the settings according to the conditions 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 connect to the network. In this case, follow steps 1-4 of the Install VMware Tools instructions.

  4. On the virtual machine, check to see if the VMTools disk is mounted automatically:

    mount

    Command output:

    /dev/cdrom on /mnt/cdrom

  5. If the disk is unmounted, mount it with device file paths and mount points depending on the distribution:

    sudo mkdir /mnt/cdrom
    sudo mount /dev/cdrom /mnt/cdrom

  6. Check if there is an archive with .tar.gz extension with VMTools 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 archive with VMware Tools, depends on the version.

  8. Navigate to the directory with the unzipped archive:

    cd /tmp/vmware-tools-distrib

  9. Run the installation script:

    sudo ./vmware-install.pl

  10. Follow the installer's instructions.

  11. After installation, reboot the virtual machine.

9. Configure backup⁠

The Cloud powered by VMware backup service is available for VMware virtual machine backups.

Veeam agents use BIOS UUIDs to identify machines. The restored machine has a new BIOS UUID, so continuing existing Veeam Agent backup chains may not be possible.

  1. Uninstall 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.