icon
Search...
icon

Restore Backup to New Virtual Machine

Definition

The Restore to New Virtual Machine feature enables users to restore a backup to a newly created Virtual Machine instance without affecting the original VM. This is useful for cloning, testing, recovery, and troubleshooting scenarios.

 

Use Cases

  • Fault Tolerance: Restore a backup into a fresh Virtual Machine when the original Virtual Machine is corrupted or inaccessible.
  • Testing & Development: Quickly spin up a replica of a production Virtual Machine to a test environment.
  • Cloning & Scaling: Create Virtual Machine clones from a known state for load testing or scaling.

 

Prerequisites

  1. User must have permission to Restore a Virtual Machines.
  2. The source Virtual Machine must have DHCP enabled to ensure correct IP configuration in the restored Virtual Machine.
  3. Restoring to a new Virtual Machine requires at least one free IP address in the same network as the original Virtual Machine.

 

Step-by-Step Guide

Step 1: Locate the Backup

  • Navigate to the Virtual Machine page > Backup tab.
  • Find the relevant backup entry in the table.

Step 2: Select "Restore to New Virtual Machine"

  • Click the 3-dots menu next to the backup.
  • Select "Restore to New Virtual Machine".

Step 3: Fill VM Details

  • In the modal, complete the following:
  •    New Virtual Machine Name (required)
  •    Description (optional)

Step 4: Review Warnings & Acknowledge

  • Read and acknowledge the two warnings:
  1.         DHCP Warning: Confirms DHCP is enabled on the original VM to avoid dual network loss.
  2.         EDR Warning: Reminds to reinstall the EDR agent post-restore.
  • Check both boxes to enable the Restore button.

Step 5: Submit

  • Click Restore.
  • Wait for the confirmation message or error notice.

Step 6: Monitor Progress

  • Go to the Request List in the header .
  • View real-time status of the restore operation.

Step 7: Post-Restore

The new VM appears in the VM list and supports all the Standard operations including Further backups

 

 

EDR Visibility Requirement

  • For proper EDR visibility and functionality, you must reinstall the EDR agent on the newly restored Virtual Machine. Follow the step-by-step instructions in the official guide:
    EDR & EPP Installation Guide

 

How to enable DHCP

For Windows:

1.Open Network Settings:

  • Go to Control PanelNetwork and Sharing CenterChange adapter settings.

2.Right-click your network adapterProperties.

3.Select Internet Protocol Version 4 (TCP/IPv4)Properties.

4.Choose:

  • Obtain an IP address automatically
  • Obtain DNS server address automatically

5.Click OK to save and restart the network adapter.


For Ubuntu - Debian (Netplan):

  • File: /etc/netplan/01-netcfg.yaml

Modify to use DHCP:

network:

  version: 2

  ethernets:

    all-interfaces:

      match:

        name: en*

      dhcp4: true

Apply the changes:

sudo netplan apply


For Red Hat - CentOS - Rocky - AlmaLinux:

Use nmcli to configure DHCP:

sudo nmcli connection add type ethernet ifname "*" con-name "default-dhcp" ipv4.method auto

sudo nmcli connection modify default-dhcp connection.autoconnect yes

sudo nmcli connection modify default-dhcp connection.multi-connect multiple

Apply the configuration:

sudo nmcli connection up default-dhcp


For Oracle - Linux:

Same procedure as Red Hat:

sudo nmcli connection add type ethernet ifname "*" con-name "default-dhcp" ipv4.method auto

sudo nmcli connection modify default-dhcp connection.autoconnect yes

sudo nmcli connection modify default-dhcp connection.multi-connect multiple

Apply the configuration:

sudo nmcli connection up default-dhcp


For SUSE - openSUSE:

If using NetworkManager:

sudo nmcli connection add type ethernet ifname "*" con-name "default-dhcp" ipv4.method auto

sudo nmcli connection modify default-dhcp connection.autoconnect yes

sudo nmcli connection modify default-dhcp connection.multi-connect multiple

Apply the configuration:

sudo nmcli connection up default-dhcp

If using wicked (older versions):

sudo vi /etc/sysconfig/network/ifcfg-eth0

Set:

BOOTPROTO='dhcp'

STARTMODE='auto'

Apply the changes:

sudo systemctl restart wicked


For Linux:

sudo nmcli connection add type ethernet ifname "*" con-name "default-dhcp" ipv4.method auto
sudo nmcli connection modify default-dhcp connection.autoconnect yes
sudo nmcli connection modify default-dhcp connection.multi-connect multiple

 

 

Additional Notes:

  • If DHCP is disabled on the original VM it will lead to unexpected behavior or network failure.
  • If the agent is not reinstalled, the restored VM EDR status may not appear accurately in your MDR monitoring system.

 

Glossary

VM (Virtual Machine): A virtual computer with its own OS and resources.

Backup: A saved copy of a VM’s state.

DHCP (Dynamic Host Configuration Protocol): Auto-assigns IP addresses to VMs.

EDR (Endpoint Detection and Response): Security tool for detecting and responding to threats.

Audit Trail: Log of user actions for tracking.

Request Log: List of user actions with status and details.

 

Updated at 2025-11-11