Aller au contenu principal

Clean up backup version "Full" <102bytes backup listed but unable to delete

Thread needs solution

I've noticed when attempting to use the interface "Clean up backup versions" there's sometimes a small "Full" version listed as <102 bytes in size and any attempt at attempting to select this "Full" version prevents Acronis from successfully deleting any of the other actual versions selected with it. Even if it is the only "Full" version listed Acronis stays in the "Cleanup up..." state and never actually delete anything. While in this "Cleaning up..." state I can close the main application window, but when attempting to reopen Acronis True Image it will not open, I can only either restart the machine, or force kill the app from Windows Task Manager. Only after that am I able to reopen the Acronis True Image application.

Drive where backups are stored are Windows mounted linux folders. This has happened on previous version of Acronis True Image and previous builds of Windows 10.

Version: Acronis True Image 2020 Release 4

Windows 10 Pro 20H2 OS Build 19042.928

 

0 Users found this helpful

Ryan, welcome to these public User Forums.

Sorry but probably more questions than answers to offer to you at this point!

Please can you expand on "Drive where backups are stored are Windows mounted linux folders."  What filesystem is being used for these Linux folders?  Is this on a NAS?  How being accessed - is this using SMB?

What are the actual file types involved here?  .tibx or .tib files?
What are the actual file sizes and naming convention being used?

If dealing with .tibx files, then the 12kb first .tibx file should not be deleted unless deleting the whole backup chain - these files contain important metadata about the backup files.

The files system being used is an ext4 file system being shared with windows over SMB.

The file types normally saved by Acronis are .tib files.

The cleanup version dialog shows this as a file dated of 3/27/2015 type of "Full" and a size of "< 102 bytes" see attached image. 

If I open that same folder in windows with "Show Hidden Files" selected it doesn't indicate a file with that date at all, see other attachment.

If I navigate to that folder in linux and do an ls -lart on the folder there's no file with that date or size in the same directory Acronis stores that data. 

 

 

 

Ryan, the only explanation that I can offer here is that ATI has an old / stale reference to the 2015 vintage file in its internal database.

See KB 60915: Acronis True Image: repairing program settings - for details of how to force the internal database to be rebuilt to see if this resolves this strange issue?