---
title: "Restore a machine to a VMware-based cloud"
sidebar_label: "Restore a machine to a VMware-based cloud"
sidebar_position: 7
description: "How to restore a Linux or Windows machine to a virtual machine in a VMware-based cloud and how to configure the machine after restoration"
toc_max_heading_level: 2
---

import Formbricks from '@theme/MDXComponents/Formbricks'
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'
import {TabItemLabel} from '@selectel/docux/components'

# 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](/public-cloud/about/about-public-cloud.mdx).

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](/veeam-agent/restore-from-backup/veeam-recovery-media.mdx).

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](/public-cloud/quickstart.mdx).

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](/public-cloud/manage-public-cloud/os-recustomization.mdx) or manually.

To restore a virtual machine:

1. [Create an empty virtual machine](#create-empty-virtual-machine).
2. Optional: [install VMware Remote Console](#install-vmware-remote-console).
3. [Start the empty virtual machine](#run-empty-virtual-machine).
4. [Load Tools virtual device drivers](#load-tools-virtual-device-drivers) (Windows only).
5. [Restore the backup to the virtual machine](#restore-backup-to-virtual-machine).
6. [Configure the network environment](#configure-network).
7. [Deploy a virtual machine with Windows Server](#deploy-vm-windows) (Windows only).
8. [Install VMTools](#install-vmtools).
9. [Configure backups on the restored machine](#configure-backup).

## 1. Create an empty virtual machine \{#create-empty-virtual-machine}

1. From the [control panel](https://my.selectel.ru/vmware/), open the Cloud Director panel: in the top menu, click **Products** → **Cloud powered by VMware** → **Cloud Director** section.

2. Open the virtual data center page.

3. Go to the **Compute** →  **vApps** section.

4. In the vApp card, click **ACTIONS**.

5. Click **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 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 **Hardware** → **Hard 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 Type** — `Paravirtual (SCSI)`;
    * **Bus Number**, **Unit Number** — default.

29. Click **SAVE**.

## 2. Optional: install VMware Remote Console \{#install-vmware-remote-console}

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

1. From the [control panel](https://my.selectel.ru/vmware/), open the Cloud Director panel: in the top menu, click **Products** → **Cloud powered by VMware** → **Cloud Director** section.
2. Open the virtual data center page.
3. Go to the **Compute** →  **vApps** section.
4. Open the vApp page → **Virtual Machines** section.
5. Open the virtual machine page.
6. Click **ALL ACTIONS** → **VM Console** → **Download 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 \{#run-empty-virtual-machine}

1. From the [control panel](https://my.selectel.ru/vmware/), open the Cloud Director panel: in the top menu, click **Products** → **Cloud powered by VMware** → **Cloud Director** section.
2. Open the virtual data center page.
3. Go to the **Compute** →  **vApps** section.
4. In the vApp card, click **ACTIONS**.
5. Click **Power** → **Power on**.
6. In the virtual machine menu, click **VM Console** → **Launch Remote Console** or **Launch Web Console**. The Veeam Recovery Media recovery environment will load automatically. If the environment does not load, [check the settings](#check-veeam-recovery-media-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 \{#check-veeam-recovery-media-settings}

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

1. From the [control panel](https://my.selectel.ru/vmware/), open the Cloud Director panel: in the top menu, click **Products** → **Cloud powered by VMware** → **Cloud Director** section.

2. Open the virtual data center page.

3. Go to the **Compute** →  **vApps** section.

4. Open the vApp page → **Virtual Machines** section.

5. Open the virtual machine page.

6. Go to the **Hardware** → **Removable 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) \{#load-tools-virtual-device-drivers}

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 \{#restore-backup-to-virtual-machine}

Use the [Restore a virtual machine](/veeam-agent/restore-from-backup/restore-machine.mdx) instructions for your operating system.

## 6. Configure the network environment \{#configure-network}

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 \{#deploy-vm-windows}

If you are using Windows, use the [Deploy a virtual machine with Windows Server](/public-cloud/manage-public-cloud/deploy-vm-windows.mdx) instructions.

## 8. Install VMTools \{#install-vmtools}

<Tabs queryString="os-vmtools">
  <TabItem value="ubuntu-debian" default>
    <TabItemLabel>
      Ubuntu/Debian
    </TabItemLabel>

    1. Install VMTools (Perl required):

       ```shell
       sudo apt install open-vm-tools
       ```

    2. Make sure the service is running:

       ```shell
       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](/public-cloud/manage-public-cloud/vmware-tools.mdx#install-vmware-tools) instructions.

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

       ```shell
       mount
       ```

       Command output:

       ```shell
       /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:

       ```shell
       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:

       ```shell
       ls /mnt/cdrom
       ```

    7. Extract the archive to the `/tmp:` directory:

       ```shell
       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:

       ```shell
       cd /tmp/vmware-tools-distrib
       ```

    9. Run the installation script:

       ```shell
       sudo ./vmware-install.pl
       ```

    10. Follow the installer instructions.

    11. After installation, reboot the virtual machine.
  </TabItem>

  <TabItem value="rhel-centos-fedora">
    <TabItemLabel>
      RHEL/CentOS/Fedora
    </TabItemLabel>

    1. Install VMTools (Perl required):

       ```shell
       sudo yum install open-vm-tools
       ```

    2. Make sure the service is running:

       ```shell
       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](/public-cloud/manage-public-cloud/vmware-tools.mdx#install-vmware-tools) instructions.

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

       ```shell
       mount
       ```

       Command output:

       ```shell
       /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:

       ```shell
       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:

       ```shell
       ls /mnt/cdrom
       ```

    7. Extract the archive to the `/tmp:` directory:

       ```shell
       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:

       ```shell
       cd /tmp/vmware-tools-distrib
       ```

    9. Run the installation script:

       ```shell
       sudo ./vmware-install.pl
       ```

    10. Follow the installer instructions.

    11. After installation, reboot the virtual machine.
  </TabItem>

  <TabItem value="suse">
    <TabItemLabel>
      SuSE
    </TabItemLabel>

    1. Install VMTools (Perl required):

       ```shell
       sudo zypper install open-vm-tools
       ```

    2. Make sure the service is running:

       ```shell
       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](/public-cloud/manage-public-cloud/vmware-tools.mdx#install-vmware-tools) instructions.

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

       ```shell
       mount
       ```

       Command output:

       ```shell
       /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:

       ```shell
       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:

       ```shell
       ls /mnt/cdrom
       ```

    7. Extract the archive to the `/tmp:` directory:

       ```shell
       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:

       ```shell
       cd /tmp/vmware-tools-distrib
       ```

    9. Run the installation script:

       ```shell
       sudo ./vmware-install.pl
       ```

    10. Follow the installer instructions.

    11. After installation, reboot the virtual machine.
  </TabItem>

  <TabItem value="windows">
    <TabItemLabel>
      Windows
    </TabItemLabel>

    1. From the [control panel](https://my.selectel.ru/vmware/dashboard/), open the Cloud Director panel: **Cloud powered by VMware** → **Cloud Director**.
    2. Open the virtual data center page.
    3. Go to the **Compute** → **Virtual Machines** section.
    4. On the virtual machine card, click **ACTIONS** → **Install VMware Tools** → **Install**.
    5. On the virtual machine, launch the `setup64.exe` file from the connected DVD and perform a **Typical** installation.
    6. Reboot the virtual machine.
  </TabItem>
</Tabs>

## 9. Configure backups \{#configure-backup}

The [Cloud powered by VMware backup](/public-cloud/vmware-backups/about-vmware-backup.mdx) service is available for backing up VMware virtual machines.

<Tabs queryString="os-backup">
  <TabItem value="linux" default>
    <TabItemLabel>
      Linux
    </TabItemLabel>

    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:

       ```shell
       sudo apt remove veeamma veeam
       ```

       RHEL, CentOS, Fedora:

       ```shell
       sudo yum remove veeamma veeam
       ```

       SuSE:

       ```shell
       sudo zypper remove veeamma veeam
       ```

    2. [Install the management agent](/veeam-agent/connect-veeam-agent.mdx#install-management-agent) and [backup agent](/veeam-agent/connect-veeam-agent.mdx#install-backup-agent) again.
  </TabItem>

  <TabItem value="windows">
    <TabItemLabel>
      Windows
    </TabItemLabel>

    Verify the correct operation of the management agent and backup agent for Windows using one of the following methods:

    * run an **Active Full Backup** to start a new chain of restore points;
    * to save previously created restore points, disable backup execution.
  </TabItem>
</Tabs>

<Formbricks />
