Skip to main content

Single Version Backups with True Image 2016 - Acronis won't delete old backup files

Thread needs solution

Greetings,

I'm using Acronis True Image 2016, and use Single Version backup scheme, which is supposed to delete the old backup file(s) before creating the newest version.  A few months ago Acronis started occasionally skipping the delete action, which quickly uses up available space on the backup drive.  Now it never deletes, which is a constant nuisance.  I've looked everywhere in settings, but find no options other than Backup Scheme, which is already set for "Single Version."

Acronis no longer offers any support for True Image 2016, so I need to lean on you gurus out there for help. 

Any thoughts as to where the problem might be?

Thanks,

Todd

 

0 Users found this helpful

Todd, files are only deleted with all Acronis backup schemes, including Single Version, when a new backup has been created successfully, so the first check-point here is to look at your backup file names.  Are you seeing any files being created with such as _v1-2.tib or similar, which would indicate that Acronis hit a problem during the process of writing the file to your backup drive?

If you do see such file names, then do a CHKDSK /R for your backup drive in case it is developing any bad sectors.  Check cable connections to the drive etc.

If there are no drive issues, then consider using the option to 'Clone settings' for your backup task to duplicate the task, then remove the original task (keeping the files if needed and space allows), then rename the Cloned task but ideally using a unique name that hasn't been used before, then run the new backup task.

Hi Steve,

Thanks for the quick reply.  Most appreciated.

The drives are both fine (I use two drives and alternate, and the problem applies to both). 

Acronis states that the Single Version scheme "creates a single full backup version, and overwrites it every time."  Upon closer look at the scheme description, the additional explanatory text contradicts that basic description (as you outlined). The problem becomes clear:  One would need a backup drive with twice the capacity of the source drive in order to perform even a "single version" backup.  Unfortunately, the initial description in the software is wrong, in that it does not "overwrite," but rather writes new, then deletes old.  With respect to your thoughtful answer, such a method renders the single version scheme much less useful (but admittedly safer). 

Guess I'll need to get larger backup drives or consider another option, although it doesn't look as though there is a scheme which will allow automatic deletion of old backups while using backup drives which are the same size as source.

This all makes sense now, as the problem began when my source drive began accumulating more data and went beyond 50% full.

Thanks again,

Todd

Todd, glad to have helped to clarify how Acronis works here.

The only method around the backup drive size issue would be to use a Pre Command for your backup task that would delete the .tib files on the backup drive before creating a new one.  This would leave you at risk of having no backup unless you have other backups stored on different drives or locations.

The Pre Command batch file could be as simple as 2 lines:

@echo off
del L:\Test\Win*.tib > NUL 2>&1

where you would need to change the detail of what to delete.