Backup to NAS fails to clean up old versions
I take weekly full image backups to a share on my Unraid NAS. Unraid's architecture is such that files are actually allocated on a single drive in the NAS, so to reduce the possibility that mt backup image is too large for the available space on the selected drive, I break up the image into 100GB chunks.
I have the backup set to keep two versions, so after each successful completion, it tries to delete the oldest (now third) version... and there it fails.
Every time, it successfully deletes all but one of the files, then gives an error that another process has the v1 file open, fails to delete it, and flags the backup as failed.
If I subsequently select "Recover Files", I get an error saying it cannot find the version files that it *did* successfully delete, and I need to click "Ignore this version".
I'm wondering if the "other process" is its own verification process, because I know for a fact that nothing else except True Image accesses this area of the NAS. Perhaps I'll try turning off verification and see if that allows it to properly clean up after itself, and I'll just run a manual verify. Of course, that is a sub-optimal solution, because if the verify were to fail, then I wouldn't necessarily want to delete the oldest version. It would be nice if the product would simply work correctly in the first place.
Trying to turn off validation is a good test.
Try also a smaller backup size without segmenting. Trying to see whether this is dependent on the backup settings.
Sure enough, turning off "Validate backup when it's created" appears to resolve the problem. I have that option enabled for a separate backup to a local eSATA drive, which I also split into 100GB chunks, and it works fine there. So it appears that it's the combination of NAS destination, splitting, and validation at backup time, that's causing problems.
I will report this thread to Acronis as it seems that the validation is keeping some handle open on the file.
Hello Jon,
could you please check if the issue reproduces on your system with the latest build 6673?
Thank you.