Standby Image to Self-Hosted

Cove Data Protection (Cove) offers self-hosted Standby Image as a form of disaster recovery. It is a scheduled, automated service to recover critical devices.

Restores run after each backup session for System State, Files and Folders. After the first restore, a virtual machine is created and kept on the Recovery Locations, then with each subsequent restore the virtual machine is updated with only new data.

Restores can be performed to either a Hyper-V instance or to a Local VHDX file. Local VHDX files can be restored to either a Local Drive, or to a Network Share (NAS).

For a Virtual Machine restored to Hyper-V, 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.

There is no limit to the number of devices that can be added to a recovery location

Limitations

  • Only devices with Backup Manager version 17.4 and above are supported for Standby Images
  • Standby Images cannot be used on the RMM integrated version of Backup (Managed Online Backup)
  • Standby Images cannot be used on the N-central integrated version of Backup (Backup and Recovery)
  • Standby Image restores the following data sources:
    • System State
    • Files and Folders
    • Exchange
    • SharePoint
    • MS SQL
  • Standby Images are not available for devices with disabled ‘Virtual disaster recovery’ feature in an assigned Product
  • Standby Images do not support 32-bit architecture

  • Due to a Microsoft limitation, Hyper-V does not support FAT/FAT32/ExFAT formatted drives. For this reason, please use NTFS formatted drives for Standby Image. More information can be found in the Microsoft Documentation for Hyper-V

  • Maximum supported capacity for virtual hard disks is 64 TB per disk
  • Devices cannot be added to a Standby Image plan if already assigned to a Recovery Testing plan
  • Devices and Recovery Locations must belong to the same customer
  • Devices can only be assigned to one Recovery Location
  • 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 an environment where restores will be performed
    • Recovery service is a service which perform restores on that Recovery location