Standby Image to ESXi

Cove Data Protection (Cove)'s Standby Image to ESXi service runs a continuous restore of your data to VMWare ESXi or to a Local VMDK file, and boots based on the frequency set during configuration of the plan.

Devices can be assigned to multiple Standby Image plans at once, i.e. Standby Image to Hyper-V and Standby Image to Azure and Standby Image to ESXi.

Restores can be performed to either a VMWare ESXi instance or to a Local VMDK file. Local VMDK files can be restored to either a Local Drive, or to a Network Share (NAS).

Standby Image Data Restored:

The following data sources are supported and restored to the ESXi recovery location given that they are selected for backup in the Product, or data source selection:

  • System State
  • Files and Folders
  • Exchange
  • SharePoint
  • MS SQL


  • Backup Manager version 17.4 and newer
  • Devices and Recovery Locations must belong to the same Customer
  • A Cove Data Protection (Cove) SuperUser or Manager account
  • Recovery Locations must be added to the Management Console and the Recovery service must be installed on the recovery location before Standby Image recovery can occur
    • Recovery Location is a machine with the recovery service installed
    • Recovery service is a service which orchestrates all the recovery jobs for Standby Images


  • Standby Image cannot be used on the RMM integrated version of Backup (Managed Online Backup) or on the N-central integrated version of Backup (Backup and Recovery)
  • Standby Image is not available for devices with disabled ‘Virtual disaster recovery’ feature in an assigned Product
  • 32-bit architecture is not supported
  • Restores run after each backup session for System State and Files and Folders. After the first restore, a virtual machine is created and kept on the selected host/storage, then with each subsequent restore the virtual machine is updated with only new data
  • For a Virtual Machine restored to ESXi host, there is an option to automatically boot it and create a screenshot to check that the Virtual Machine is bootable, then send this screenshot to the Management Console so that users can check it
  • Maximum supported capacity for virtual hard disks is 64 TB per disk
  • Devices can only be assigned to one Recovery Location

What's inside: