Single version scheme does not delete previous file. ATI 2018
I run a weekly backup every day so I have 7 days of tib files in separate folders, enabling me to go back 7 days for recovery.
The single version backup scheme is supposed to delete the previous tib file but does not do so. The PC is not shutting down after the backup.


- Log in to post comments

Hi Steve,
Yes, you are right in deducing that I have 7 separate backup jobs, each going to a different folder. This means that the existing tib file is one week old by the time the next one appears in that folder. Perhaps that's why it doesn't delete it?
I will run the log tool and check the results over the next couple of days and report back with results and screen shots of settings.
- Log in to post comments

Have just checked the log - output below. Shows the old file is being deleted, but the delete is not actually happening. When I manually delete the file using windows explorer, Acronis shield blocks the attempt to remove the file unless I authorise it in the popup.
So I suspect Acronis Shield is preventing the delete. I will place trueimage.exe in the trusted list to see if that does the trick.
10/04/2018 6:00:02 PM: 00 8328 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/04/2018 6:00:02 PM: 00 8328 I00640002: Operation HP600 Tuesday started by schedule.
10/04/2018 6:00:07 PM: 00 8328 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/04/2018 6:00:07 PM: 00 8328 I013C0000: Operation: Backup
10/04/2018 6:00:07 PM: 00 8328 I0064000B: Priority changed to Low.
10/04/2018 6:00:07 PM: 00 8328 I000B03F0: Create Backup Archive From: Disk 1 To file: D:\Backups\HP600 Tuesday\HP600 Tuesday.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, *.db3-journal, C:\Users\gerhard\AppData\Local\Temp, C:\Users\gerhard\AppData\Local\Microsoft\Windows\INetCache, C:\Users\gerhard\AppData\Local\Google\Chrome\User Data, C:\Users\gerhard\AppData\Local\Opera Software, C:\Users\gerhard\AppData\Roaming\Opera\Opera, C:\Users\gerhard\AppData\Local\Mozilla\Firefox\Profiles, C:\WINDOWS\CSC
10/04/2018 6:00:07 PM: 00 8328 I000101F8: Pending operation 173 started: 'Creating partition image'.
10/04/2018 6:00:07 PM: 00 3744 I00640000: Writing full version to file: HP600 Tuesday_full_b3_s1_v1.tib
10/04/2018 6:00:10 PM: 00 8328 I000101F8: Pending operation 173 started: 'Creating partition image'.
10/04/2018 6:00:10 PM: 00 8328 I000101F8: Pending operation 173 started: 'Creating partition image'.
10/04/2018 6:04:08 PM: 00 8328 I000101F8: Pending operation 173 started: 'Creating partition image'.
10/04/2018 6:04:08 PM: 00 8328 I000B0000: Deleting backup file with path D:\Backups\HP600 Tuesday\HP600 Tuesday_full_b2_s1_v1.tib.
10/04/2018 6:04:08 PM: 00 8328 I00640000: The following backups have been successfully created: D:\Backups\HP600 Tuesday\HP600 Tuesday_full_b3_s1_v1.tib
10/04/2018 6:04:08 PM: 00 8328 I013C0006: Operation has succeeded.
Start: 10/04/2018 6:00:02 PM
Stop: 10/04/2018 6:04:08 PM
Total Time: 00:04:06
- Log in to post comments

Placing trueimage.exe in the trusted list has allowed successful deletion of previous backup.
Seems the Shield module programmers are not inherently trusting of the Backup module programmers.
- Log in to post comments

Thank you for your findings here. Interesting that this apparently only effects single version backup schemes.
- Log in to post comments