This article explains the Screenshot Verification feature of SIRIS and ALTO devices and gives resources to troubleshoot failed screenshot errors. For more information about the mechanics of virtualizations on Datto appliances, and how they relate to screenshot verification, see the How Virtualizations Work article.
- Datto SIRIS
- Datto ALTO
Screenshot Verification verifies that your Datto device's 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. You can configure Screenshot Verification on the Configure Agent Settings page of the Datto appliance GUI.
This article focuses on common problems that you can resolve through these configurable options.
Your Datto device can be configured to send email alerts detailing the results of the Screenshot Verification process.
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 a Screenshot Verification, by logging into the Datto GUI and clicking the PROTECT tab then clicking Manage Recovery Points. Place your cursor over the circle under the Screenshot Verification column for the date and time you wish to view.
When diagnosing a failed screenshot, there can be times when the captured image is not displaying the correct error or state that caused screenshot verification to fail. To check, create a virtual machine manually through the Datto device GUI to observe its behavior.
To create a virtual machine manually, follow the steps below:
1. Log in to the Datto device GUI.
2. Click Restore.
3. Select the protected machine to be virtualized by clicking the corresponding button under Start a Restore.
4. Under Choose Recovery Type, select Local Virtualization.
5. Under Choose a Recovery Point, select the same point in time for which the screenshot failed.
6. Finally, after confirming the information is correct, click START RESTORE.
7. In the Local Virtualization screen (Figure 2), select the number of CPU cores, the amount of RAM, the boot disk, the storage controller, and the networking options for the virtual machine. For testing purposes, set Network Options to Disconnected and uncheck the box labeled Create Rescue Agent. For more information about the different options, check out Remote Web - Local Virtualization - Local Options.
Testing The Screenshot
1. 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.
The screenshot verification process will use whichever storage controller you set in the Configure Agent Settings screen for the desired agent.
2. After confirming the resources and storage controller, start the virtual machine: Start VM.
3. Observe its behavior by downloading the automatically-generated RDP link.
- Failed screenshot with "BOOTMGR is compressed"
- Failed screenshot with "FATAL: No bootable medium found! System halted."
- Failed screenshot with screen showing "(file) is missing or corrupt" or "BOOTMGR is missing"
- Failed screenshot with customized login screen
- Failed screenshot with blank image or image of Windows loading
- Failed screenshot showing Windows desktop
- Failed screenshot with blue screen stop code 0x0000007b
- Failed screenshot with "The system is pending an update."