Upgraded to 2017 ver. 8029 on one machine and I keep getting "Failed to create volume snapshot".
I have four computers with Acronis 2017 for Windows on them.
I upgraded one of them to 2017 ver. 8029 and did a quick backup. It seemed to work fine AFAIK, and I shutdown the machine. (I say this, because, the error message I get is very easy to miss. It will loop back after a few minutes and try to complete the backup from the start. So, it is possible I missed the message. That computer is at work right now.)
Then I upgraded another machine, and started to run the backup. That's when I noticed the second machine was in a loop with "Failed to create volume snapshot". The third machine successfully completed a backup. So, two out of three very similar machines upgraded successfully.
I started troubleshooting the issue of the failed upgrade by following the many suggesstions on this board regarding the VSS issue. I tried completely uninstalling, as well as following the instructions to clean the registry per the Acronis support KB. Nothing worked. If I leave the option for VSS on, the backup fails. If I backup with Windows Backup, it completes. If I change the settings of VSS off, and use Acronis' version of the snapshot it works. I do not see this option in version 5554.
I have finally isolated the issue/problem, but not the solution. I noticed the backup will fail at the very end of the backup. Since it is only backing up the small SSD drive and there are only two partitions C: and D: (the recovery drive), I decided to try backing up just the D: recovery drive. It would not even start. Yet, if I unchecked the D: recovery drive, the backup was successful backing up the C: drive.
Now that I've isolated the problem after a many hours, I have reverted back to the previous version 2017 5554. And everything works fine again. Which brings me to the next problem. When I tried to intall the version 5554 that I originally downloaded upon purcahse, it automatically upgraded me to 8029 again. The only way for me to revert back to 2017 5554 was by restoring a previous backup. As I type this, I'm guessing that if I turned off the Internet connection, it may have kept the older version.
Anyway, at this point I'm not real crazy about troubleshooting this any further if it requires that I install 8029 again to test anything. I've spent a whole night on it until the early hours of the morning.
I will say that all three machines are HP's that came with hdd's and were converted to SSD's (C: and D: restore), with acronis software. I have currently reverted back to 2017 5554 since it works fine.
Thanks Steve,
You might be right about that. I will try re-sizing the D: drive a bit and try again.
I checked a working computer and the available space is 1.78GB out of 12.8GB or 13%
The computer which is not working has 236MB available out of 3.68GB or 6%. I'll try bumping it up to 512MB or 13%.
It's worth a shot.
Bingo. I resized the D: drive and gave it 14% available space and 2017 build 8029 was able to backup fine. I'm glad I posted and that you responded, because I was going to just give up and stick with 2017 build 5554. Thank-You!
pl1, that's great to have the size issue confirmed in a positive way. VSS does seem to be sensitive to these space issues which is why the Acronis Snapshot alternative will work when VSS doesn't. Thank you for the feedback.
Thread readers,
Minimum size for VSS shadow copies when performing full disk image backups is 10% of total free partition space. Anything below 10% will produce the error as mentioned here. Resizing of partitions or not using VSS are the only options currently available to remedy the issue.