Aller au contenu principal

Unable to create volume snapshot

Thread needs solution

Recent backups have run but failed to complete, instead generating an error message "unable to create volume snapshot".

Have checked I have the latest build - Acronis 2016, Build 6571, which it says is up to date. 

The backup is to an external hard drive with 1 TB free space. The drive has been checked for system errors (d/properties/error checking) and is reported fault free.

Backups to the same drive have been working fine for the past year.

I have checked services and Volume Shadow Drive is set to manual.

Two other scheduled backups of document folders and files are working fine. Only the backup of the system SSD drive is failing.

Maybe it is coincidence, but trouble seemed to have started after the last Windows 10 update.

 

0 Users found this helpful

Colin, welcome to these user forums.

There can be a number of different causes for this problem, so the starting point is to gather further information from the log files that Acronis produces for each backup task activity.

Please download the Log File Viewer app from the link in my signature below and use this to check for more meaningful messages in the logs.

Volume Snapshots are created by the Microsoft Volume Shadow Copy Service (VSS) which Acronis uses under the covers to backup system data including OS files and programs etc.  There is a method of telling Acronis not to use VSS and revert back to its own snapshot utility as used in earlier versions. See post: https://forum.acronis.com/forum/45832#comment-346558 for details of how to do this.

Problem can also be caused by problems on the source drive where the snapshot will be created - so look for any messages suggesting that you may have hit any bad sectors in the logs.  Run CHKDSK /F /R against the drives if you see any such messages.

One last suggestion, if you only normally do a Shutdown of Windows 10 and have Windows Fast Start enabled, then you are in essence putting your system into hibernation - try doing a Restart instead and then retry the backup to see if a full shutdown and restart of Windows will clean up this issue with VSS.