This article explains the Screenshot Verification feature of SIRIS and ALTO devices and gives resources to troubleshoot failed screenshot errors.
Screenshot Verification verifies that the 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.
As a way to let a partner know the state, the screenshot verification is sent in email form as an alert detailing the results of the recently taken screenshot(s).
This article focuses on common problems that can be resolved through these configurable options.
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.
In efforts to diagnose a failed screenshot, there can be times where the captured image is not displaying the correct error or state which caused screenshot verification to fail. To check, boot the virtual machine manually through the Datto Remote Web to observe its behavior.
To spin up a virtual machine manually, see the following steps (Figure 1):
1. Log in to the device's web interface.
2. Click on 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 Virtualization.
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 more information about the different options, check out Remote Web - Local Virtualization - Local Options.
Figure 1 - Setting up a local virtualization
Figure 2 - Local virtualization settings
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
Note: By default, screenshots for 32-bit virtual machines use 1 CPU core and 2GB (2048MB) of RAM, and screenshots for 64-bit systems use 2 CPU cores and 3GB (3072MB) of RAM
The screenshot verification process will use whichever storage controller is 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.
Screenshot Error Resources
If you need to solve an error with screenshot verification, click on the article that pertains to the error that you are seeing:
- 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