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 screen showing "(file) is missing or corrupt" or "BOOTMGR is missing"

Follow

Scope

This article describes the cause and possible solutions for the screenshot verification errors "(file) is missing or corrupt" or "BOOTMGR is missing."


Figure 1 - Example of the error "BOOTMGR is missing"

Figure 2 - Example of "BootMGR is missing or corrupt" error message

Cause

Although these types of errors can have many different catalysts, the backup agent may just need to reconcile its current backup with a new full scan of the target machine.

Solution

Manually force a differential merge for the agent (Figure 3). Note that this will force the agent to traverse the entirety of each volume being backed up, giving the appearance of a new full backup. However, a differential merge backup will only incur a cost of space on the storage array equal to a normal incremental and a minor amount of overhead.

 Figure 3 - Force a Differential Merge from the Configure Agent Settings of the web UI


Was this article helpful?

2 out of 7 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!