ALERT: Datto Drive Cloud service will no longer be available as of June 1, 2019. For more information, see our end-of-life article. To learn how to download your Datto Drive Cloud data, please visit this article.

Direct to Cloud: Screenshot Verification Overview



This article explains the screenshot verification feature for endpoints protected by the Datto Direct to Cloud (DTC) solution.


  • Datto Direct to Cloud (DTC)


This article assumes that you have already installed the Datto Direct to Cloud Agent on your test machine, that the agent has begun taking backups, and that you have configured screenshot alerts for your client(s). If you have not already done so, see the Direct to Cloud: Getting Started and Direct to Cloud: Email Alert Settings articles before proceeding.


Screenshot Verification Overview

This feature validates that your protected system's backups are healthy and restorable by building virtual machines from preexisting snapshots and performing context-sensitive tests against them to evaluate whether or not they boot successfully.

Unlike screenshot verification for SIRIS and ALTO, it is not possible to change the verification schedule for a Direct to Cloud agent or to manually force verification to run. Screenshot verification automatically runs once a day against the first successful backup of the day.

Configuring Screenshot Alerts & Viewing Screenshot Results

You can configure screenshot alerts from the Email Alert Settings page of the Direct to Cloud portal.

The results of screenshot verification are reported as Agent Screenshot Verification Succeeded and Agent Screenshot Verification Failed email alerts.

Diagnosing Screenshot Verification Failures

1. If you are receiving failed screenshot notifications, but the screenshot shows that your virtual machine is booting successfully, proceed to the Contacting Support section of this article.

2. If the screenshot verification shows the virtual machine in a failed boot state, observe the full boot sequence of the restore point by virtualizing it in the cloud. Document any unusual behavior that you observe. Then, check the production machine. Many boot failures replicate from issues which are present in the production environment.

  • If the screenshot failure shows Windows updates installing, schedule a maintenance window for the production machine, reboot it, and allow its pending Windows updates to install. Then, resume backups, and observe the outcome of the next day's screenshot verification.
  • If the screenshot failure shows CHKDSK operations underway, schedule a maintenance window for the production machine, reboot it, and allow the disk operation to run. Then, resume backups, and observe the outcome of the next day's screenshot verification.
  • If, during cloud virtualization, you observe any other unusual boot behavior which you can replicate on the production machine, correct the problem in the live environment, resume backups, and observe the outcome of the next day's screenshot verification.

3. If the failed screenshot verification does not fall into the above-listed categories or if you are unable to resolve the issue via the troubleshooting methods described, proceed to the Contacting Support section of this article.

Contacting Support

1. Before contacting Datto Technical Support, gather the following information about the screenshot failure:

  • Detailed description of the problem
  • Detailed description of all troubleshooting attempted
  • Screen capture of the failed verification notice which shows the screenshot performed
  • Hostname of the impacted system
  • Direct to Cloud Agent version and short code for the affected system
  • Agent logs from the affected system

2. Attach this information to a Technical Support ticket, and then contact Datto Technical Support for assistance.

Additional Resources

Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Community Forum or get live help.