This article goes over the cause and solution when a file restore fails to mount on a volume.
If a file restore is unable to mount a volume for restore after selecting a point from the web interface. There are several issues that could cause this:
- The backup clone for the file restore needs to be fixed.
- The backup image may have some form of corruption.
- The protected machine may have NTFS corruption that is preventing writing clean images to the backup files.
Please see the following possible solutions of this issue:
- Should the file restore fail in this fashion, contact Datto Technical Support who should be able to remedy this situation manually to get the data needed.
- Ensure that the latest version of the ShadowSnap agent is installed (3.2.0 at the time of writing. A reboot may be required for changes to take effect if ShadowProtect is upgraded in the process.)
- If after the new agent is installed and issues with mounting file restores persist, force a differential merge on the agent from the Advanced Options tab of that agent in the Remote Web. This will allow the image to repair itself.
- Should this persist further, on any volume that fails to mount for file restore, schedule time for a chkdsk /r on the protected volume.
Note: This backup will be a large incremental because of the possible changed data due to the chkdsk. Because there is no indication for how large the snapshot is going to be, assume that it is going to be taking a full backup.