Skip to main content

 

Druva Documentation

About virtual machine restore

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Overview

As a Phoenix administrator, you can restore virtual machines anytime back to your virtual infrastructure.

Phoenix provides the following types of restores for virtual machines:

What you should know before restoring a virtual machine?

  • Hot snapshots reside on Phoenix CloudCache for a period that you specified at the time of configuring Phoenix CloudCache
  • If you are a group administrator, you can only restore data to a virtual machine that belongs to a server group that you manage. Cloud administrators can restore virtual machines across server groups. 
  • In the event of a network connection failure at the time of restores, backup proxies attempt to connect to Phoenix Cloud. After the restoration of connectivity, backup proxies restart restores from the state in which they were interrupted. 
  • If you restart or reboot  backup proxy during a restore, the restore operation changes to scheduled state and will resume after power on.
  • The snapshot timestamps are displayed according to the virtual machine time zone. 
  • Although Phoenix backs up VMX files along with the VMDK files, you can restore the VMDK files only.
  • The Restore Points follow the backup proxy time zone.
  • If you choose to restore the complete virtual machine, Phoenix creates a new virtual machine with the same configuration as the original virtual machine using the following naming syntax:

    <Name of the original virtual machine>_<counter>

    The <counter> increments by 1 for subsequent restores of the virtual machine.

    Example:
    • For the first restore of a virtual machine named Test Virtual Machine, Phoenix creates a virtual machine called Test Virtual Machine_1.
    • For the second restore, Phoenix creates a virtual machine called Test Virtual Machine_2.
  • If you choose to restore a virtual disk, Phoenix creates a new virtual machine with minimum configuration and associates the VMDK files that you selected to it.
  • Phoenix supports restore of virtual machines to a different ESXi hypervisor, as well as the source hypervisor associated with a vCenter Server on which you installed backup proxy.
    However, if you deployed backup proxy for a standalone ESXi, you can restore a virtual machine from this ESXi to the source ESXi only.
  • A Thick Provisioned Lazy Zeroed disk is restored as a Thick Provisioned Lazy Zeroed disk.
  • A Thick Provisioned Eager Zeroed disk is restored as a Thick Provisioned Eager Zeroed disk.
  • Thin provisioned VMDK files are restored as Thin disks.
  • CBT is always disabled on a restored virtual machine, even if CBT was enabled on the original virtual machine.
  • Phoenix supports restore of RDM virtual mode disks (vRDM) as VMDK files.
  • If a virtual machine is associated with disks that are configured in different modes, for example, Independent Persistent, Phoenix restores only those disks for which the mode is supported.
  • In case of virtual machine restore to the original location, Phoenix restores the virtual machine to its original network configuration. However, for a virtual disk restore or restore to an alternate location, Phoenix restores the virtual to the default network configuration of the ESXi where it is restored.
  • If a restore fails, the newly created virtual machine is deleted.
  • After a restore, the virtual machine is always powered off. You must manually power on the virtual machine.
  • During an ongoing restore and scheduled backup, if the client machine is restarted then jobs request may not be resent to the client machine.
  • In case of virtual machine restore to the original location, as a backup and restore cannot run in parallel on the same virtual machine, you can cancel the ongoing backup and trigger the restore request. For more information, see Restore virtual machine to original location.
  • In case of virtual machine restore to the original location, two restore requests cannot run in parallel on the same virtual machine.
  • In case of virtual machine restore to the original location, if a backup is triggered while a restore is in progress, the backup will be queued until the restore is complete.

As an Phoenix administrator, you can restore virtual machines as per your requirement. 

The following types of restores are supported for virtual machines,

Restore virtual machine to original location workflow

 

 

Step Operations

Step 1

Phoenix administrator initiates virtual machine restore. Phoenix forwards the restore request to backup proxy pool.

  • Based on the load balancing algorithm, Phoenix automatically identifies the backup proxy that will fulfill the restore request.
  • If the identified backup proxy is busy, the restore request is queued and initiated when the backup proxy becomes free.

Step 2

Phoenix performs a check to ensure that the restore location is not a Network-attached Storage (NAS).

  • In an environment where virtual machines are deployed on ESXi hosts managed by vCenter Server, backup proxy contacts vCenter server to locate the virtual machine.
  • In an environment where virtual machines are deployed on standalone ESXi hosts, backup proxy contacts ESXi host and locate the virtual machine.

Step 3

VDDK connection is established with the virtual machine with SSL transport mode.

Step 4

Backup proxy checks if it is a full virtual machine restore or a VMDK file restore. Backup proxy contacts the virtual machine and establishes a write connection to restore virtual machine data.

  • For a full virtual machine restore, Phoenix creates a new virtual machine with an identical configuration (that is, the configuration of the virtual machine at the time of backup) at the similar location, with the following syntax: 
    <Name of the original virtual machine>_<counter>
  • For a disk restore, Phoenix creates a new virtual machine with minimum configuration (100 MB RAM, 1 CPU, 1 video card, and the disk to be restored) at the location specified, with the following syntax: 
    <Name of the original virtual machine>_<counter>.
Note: For disk restore, create a minimum configuration virtual machine because VMware does not allow to create a disk without creating the virtual machine.

Step 5

Backup proxy obtains the virtual machine data from Phoenix Cloud.

Step 6

Restore operations starts.

Phoenix checks if the restore completes successfully. 

  • If the restore completes successfully, a new virtual machine is available.
  • If the restore fails, Phoenix deletes the newly-created virtual machine.

Restore virtual machine to alternate location workflow

Step Operations

Step 1

Phoenix administrator initiates virtual machine restore. Phoenix forwards the restore request to backup proxy pool.

  • Based on the load balancing algorithm, Phoenix automatically identifies the backup proxy that will fulfill the restore request.
  • If the identified backup proxy is busy, the restore request is queued and initiated when the backup proxy becomes free.

Step 2 

Phoenix performs a check to ensure that the restore location is not a Network-attached Storage (NAS).

  • In an environment where virtual machines are deployed on ESXi hosts managed by vCenter Server, backup proxy contacts vCenter server to locate the virtual machine.
  • In an environment where virtual machines are deployed on standalone ESXi hosts, backup proxy contacts ESXi host and locate the virtual machine.

Step 3

Backup proxy checks if it is a full virtual machine restore or a VMDK file restore.

Backup proxy creates the virtual machine at specified alternate location.

  • For a full virtual machine restore, Phoenix creates a new virtual machine with an identical configuration (that is, the configuration of the virtual machine at the time of backup) at the specified alternate location, with the following syntax: 
    <Name of the original virtual machine>_<counter>
  • For a disk restore, Phoenix creates a new virtual machine with minimum configuration (100 MB RAM, 1 CPU, 1 video card, and the disk to be restored) at the specified alternate location, with the following syntax: 
    <Name of the original virtual machine>_<counter>.
Note: For disk restore , create a minimum configuration virtual machine because VMware does not allow to create a disk without creating the virtual machine.

Step 4

VDDK connection is established with the virtual machine with SSL transport mode.

Step 5

Backup proxy contacts the virtual machine and establishes a write connection to restore virtual machine data.

Step 6

Backup proxy obtains the virtual machine data from Phoenix Cloud.

Step 7

Restore operations starts.

Phoenix checks if the restore completes successfully. 

  • If the restore completes successfully, a new virtual machine is available.
  • If the restore fails, Phoenix deletes the newly-created virtual machine.

Types of snapshot restores 

Phoenix provides you 3 types of snapshot restores for a virtual machine,

Hot snapshot restore

Hot snapshot restores are created only if you have Phoenix CloudCache deployed and configured in your virtual infrastructure.

A restore of hot snapshots is an on-demand restore of virtual machine data that resides on Phoenix CloudCache. Hot snapshots are point-in-time images of backup data stored on Phoenix CloudCache. Such a restore operation continues till your data is restored to the location that you specified.

You can locate hot snapshots in the Restore Data window under Snapshots,

Warm snapshot restore

Restores of warm snapshots are on-demand restores of virtual machine data dating back to 90 days in time. Warm snapshots are point-in-time images of data dating back to 90 days in time that are stored in warm storage. Restores of warm snapshots continue till the data is restored to the location that you specified. 

To locate warm snapshots, expand Warm on the Restore Data window. 

Cold snapshot restore

Restores of cold snapshots are on-request restores of virtual machine data dating back to more than 90 days in time. Such data, known as cold snapshots, is stored in cold storage. In the event of loss or corruption of this data, you can perform a restore by using the cold snapshots. To start a restore of cold snapshots, you must first initiate a defreeze operation, during which Phoenix retrieves your data from cold storage. This retrieved data is considered as thawed and is available for restore. After your data is thawed, Phoenix sends an email informing you about the availability of your data, and also the duration for which your data remains available. After you receive this email, you can restore this thawed data. 

To locate cold snapshots, expand Cold on the Restore Data window. 

In order to restore data from cold snapshots, you must first place a request to defreeze cold snapshots which are stored in cold storage. Phoenix then retrieves your data from cold storage. This retrieved data is considered as thawed and is available for restore. After your data is thawed, Phoenix sends an email informing you about the availability of your data, and also the duration for which your data remains available. After you receive this email, you can restore this thawed data.

To defreeze cold snapshots

  1. On the Phoenix Management Console menu bar, click All Organizations, and then select the required organization from the drop-down list.
  2. On the Phoenix Management Console menu bar, click VMware. List of all the registered VMware vCenter Servers and ESXi Hypervisors appear.
  3. Click the desired vCenter Server or ESXi Hypervisor under which the virtual machine is managed. Details appear.
  4. Under Configured Virtual Machines tab, search and select the virtual machine for which you want to defreeze the cold snapshots.
  5. Click Restore.
  6. In the left pane, expand Cold, and click the snapshot that you want to defreeze.
  7. Under Home, click Defreeze.

The defreeze operation is completed in 4 hours. After completion, Phoenix sends an email informing you that your data is thawed. This data stays thawed for the duration specified in the email. You must perform a restore of your thawed data within this duration. ​ 

To locate thawed snapshots, expand Thawed on the Restore Data window.