Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Failed screenshot with blank image or image of Windows loading

Follow

Topic

This article describes the cause and possible solution for screenshot failures with a completely or partially blank screen.

Environment

  • Datto SIRIS

Cause

  • The operating system is not waiting long enough to load before attempting to capture a screenshot.
  • The operating system is waiting too long to load before attempting to capture a screenshot, and the virtualization's GUI is going into a power-saving state.
  • The operating system's screensaver is turning on, preventing a capture of the operating system in a ready state.

Figure 1Example of partial black screen boot

Solution

1. Mount a local virtualization of the affected server from the Datto appliance's GUI. Set the virtualization's resource allocation to 1 CPU core and 2 GB of RAM. Start the virtualization, and observe the amount of time the VM takes to boot to the Windows login screen.

2. If the production machine has a screensaver configured, observe the amount of time it takes for the screensaver to turn on in the VM.

3. Stop and unmount the virtualization. Navigate to the Protect → Configure Agent Settings tab of the Datto GUI. Adjust the amount of time the virtual machine needs to wait before taking a screenshot using the Screenshot Verification drop-down shown in Figure 2.

Figure 2: Screenshot Verification Schedule Options

4. Adjust the screensaver wait time on the production machine to allow enough time for the virtualization to boot, and for the Datto appliance to capture a screenshot.

5. Start a backup for the production machine. Wait for the backup to complete.

6. Force a new screenshot verification, and observe the results.

Further Troubleshooting

Verification Time

If adjusting the verification and screensaver times does not resolve the issue, you can change the Virtualization Video Controller to the 'Cirrus' setting. This setting is found on the Remote Web, at Protect → Configure Agent Settings → Advanced, as shown in Figure 3.

Figure 3: Virtualization Video Controller selector

Windows Updates

If the production machine has pending Windows updates, this state will be replicated to all snapshots taken of it from the time the updates became available until the time that they are installed. This can cause screenshots of the protected system to appear blank, because the pending Windows updates are attempting to install in the virtual environment, causing the boot process of the screenshot VM to take longer than normal to complete.

To correct this issue, you can install the pending Windows updates on the production machine and take a new backup. Alternatively, you can increase the Additional Wait Time setting for the protected system to allow the agent more time to boot fully before your Datto appliance attempts screenshot verification.

Dell Data Protection

Dell Data Protection (external link) may cause failed screenshots showing a blank screen and a cursor. If this service is enabled on the production machine, attempt another backup after disabling it.


Was this article helpful?

3 out of 4 found this helpful

You must sign in before voting on this article.

Calling all Partners! We want to hear your feedback! Please participate in this quick survey and help us build a better, more-relevant Knowledge Base!

Want to talk about it? Head on over to our Community Forum!