Screenshot Verification for Datto Endpoint Backup with Disaster Recovery

Topic

This article discuses the screenshot verification feature of the Datto Endpoint Backup with Disaster Recovery product.

Environment

  • Datto Endpoint Backup with Disaster Recovery

Description

Screenshot Verification confirms that your Datto backups are healthy and working. This feature automatically builds and boots virtual machines from preexisting backups and performs context-sensitive tests against the virtual machine's output to evaluate a pass or fail state.

The screenshots run daily according to a predefined schedule. Currently the schedule is not customizable.

IMPORTANT  Screenshot verification confirms the ability of a virtualization to boot the operating system of the protected system. It does not test the viability of non-boot volumes. You can use a manual virtualization to check non-boot volumes.

Limitations

Due to a limitation of the libvirt virtualization API, if an agent-based protected system's hostname is 50 characters in length or more screenshot verification will fail.

Diagnosing Screenshot Verification failures

If the screenshot verification process does not detect a successful boot, it will simply capture an image of the screen after a preset amount of time.

You can view the results of the most recent screenshot verification for a protected machine in the Partner Portal under Status > BCDR Status by hovering the time listed for the agent in the Latest Screenshot column.

When diagnosing a failed screenshot, the captured image may not display the correct error or state that caused the failure. To check, create a virtual machine manually for testing to see the error and any messaging on startup.

A virtual machine can be made with similar resources for the selected backup point to re-run the test, so the results can be view live and interacted with. This can assist in troubleshooting potential screenshot failures.

For instructions on setting up a virtualization, refer to: Performing an Instant Virtualization

NOTE  Make sure the check box is selected for Test Virtualization and networking is disconnected to avoid any conflict with the production machine.

To replicate the exact behavior of the virtual machine during screenshotting, select the same amount of virtualization resources and the same storage controller used by the screenshot verification process. By default, screenshots for 32-bit virtual machines use 1 CPU core and 2 GB (2048MB) of RAM, and screenshots for 64-bit systems use 2 CPU cores and 3 GB (3072MB) of RAM.

After testing, stop and unmount the virtual machine. Automated screenshots will not occur if a virtual machine is already mounted.

Additional Resources