Aller au contenu principal

Acronis TI2019 not deleting old backups

Thread solved

For some reason Acronis does not delete my old backups. To my knowledge it should with my settings, but for some reason it doesn't. Does someone have an idea what the problem could be?

 

OS: Win10 Pro 1809

Acronis True Image 2019 Version:  Build 17750

Settings:

https://i.imgur.com/PTURtc6.png

Not deleting, though:

https://i.imgur.com/fnbXgar.png

It also always says it's freeing up space after every backup, but doesn't. At least not in the backup location:

https://i.imgur.com/cLDIOaB.png

Hope someone can help me. If more info is needed, please tell me what you need.

0 Users found this helpful

Please download the MVP Log Viewer tool (link below) and use this to capture some of the logs where the ATI GUI is saying that it has freed up space, this should then give further information to help with this issue.

Thanks. Here are the logs from the latest operation:

 

08.05.2019 19:00:00: 00 1648 I00000000: -----
08.05.2019 19:00:00: 00 1648 I00000000: ATI Demon started. Version: 23.5.1.17750.
08.05.2019 19:00:00: 00 1648 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
08.05.2019 19:00:00: 00 1648 I00640002: Operation JOBNAME started by schedule.
08.05.2019 19:00:01: 00 1648 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
08.05.2019 19:00:01: 00 1648 I013C0000: Operation: Backup
08.05.2019 19:00:01: 00 1648 I0064000B: Priority changed to Low.
08.05.2019 19:00:14: 00 1648 I000B03F0: Create Backup Archive Password Protected From: To file: \\redacted\Backup\Acronis\JOBNAME.tib Compression: High Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\---\AppData\Local\Temp, C:\Users\---\AppData\Local\Temp, C:\Users\---\AppData\Local\Microsoft\Windows\INetCache, C:\Users\---\AppData\Local\Microsoft\Windows\INetCache, C:\Users\---\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\---\AppData\Local\Opera Software, C:\Users\---\AppData\Local\Mozilla\Firefox\Profiles, C:\Users\---\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\---\AppData\Local\Opera Software, C:\Users\---\AppData\Local\Mozilla\Firefox\Profiles, C:\Windows\CSC, D:\Users\---\Documents\Monero\Blockchain\
08.05.2019 19:00:16: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:00:34: 00 1648 I00100000: Volume Tracker has failed to find changes on volume 'D:'.
08.05.2019 19:00:35: 00 6548 I00640000: Writing incremental version to file: JOBNAME_inc_b12_s3_v1.tib
08.05.2019 19:01:00: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:01:00: 00 1648 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{02531fa0-4951-4d5e-9508-a72369428e32}\'.
08.05.2019 19:01:00: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:01:00: 00 1648 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{1a0f347e-b7af-4200-9228-a697e3da200b}\'.
08.05.2019 19:01:00: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:01:35: 00 1648 I00100000: Volume Tracker has failed to find changes on volume 'C:'.
08.05.2019 19:02:30: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:02:30: 00 1648 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{2abd67b9-3b1b-48eb-956b-1f57a10083e6}\'.
08.05.2019 19:02:30: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:02:30: 00 1648 I000101F8: Pending operation 173 started: 'Creating partition image'.
08.05.2019 19:02:30: 00 1648 I00640000: The following backups have been successfully created: \\redacted\Backup\Acronis\JOBNAME_inc_b12_s3_v1.tib
08.05.2019 19:02:30: 00 1648 I000B0000: Consolidate Backup Archive Location: \\redacted\Backup\Acronis\JOBNAME_inc_b12_s3_v1.tib Destination: \\redacted\Backup\Acronis\JOBNAME_inc_b12_s3_v1_1B84B6D0-5D57-426B-A4DA-C89312D621AB.tib
08.05.2019 19:02:30: 00 1648 E01EF0024: Error 0x1ef0024: Failed to open folder Y:\Backup\Acronis\ during consolidation. Ensure that the device containing the backup is properly connected.
08.05.2019 19:02:30: 00 1648 E000B03E9: Error 0xb03e9: Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Add existing backup' and recreate the backup settings.
08.05.2019 19:02:30: 00 1648 E01EF0029: Error 0x1ef0029: An error occurred during the backup consolidation.
08.05.2019 19:02:30: 00 1648 I013C0006: Operation has succeeded.

Start: 08.05.2019 19:00:00
Stop: 08.05.2019 19:02:30
Total Time: 00:02:30

 

What's weird to me is that it says to make sure the device is connected properly, but was successful in backing up prior to that... Any idea?

It appears that the app is looking into folder Y:\Backup\Acronis\ whereas the backup is pointed to \\redacted\Backup\Acronis\

I assume that "redacted" may be an IP address?  whereas the app thinks the backup is held in a mapped drive letter Y:\

The error log is telling you to remove(Delete) the backup task from the list of backups but only remove the task from the list while retaining the backup files themselves.  After that you need to select Add existing backup, navigate to the backup file(s) location, then reconfigure the backup settings for the task.

Not sure why or how this happened but the app is confused as to the location of the backup files.

See section 4.7.6 of the documentation for instructions on adding an existing backup.

True Image Documentation

\\redacted\ is the UNC path to the mapped folder. I didn't expect it to cause problems, as it results in the same location... I'll try re-adding the existing backup and see if that helps.

It seems to be working now. I'm still confused as of why it failed before, but I'm fine with it working now :)

 

Thank you very much!

Glad to hear that it is working.  This is an issue I have seen before when using mapped drive letters.  I have no idea what happens to cause the issue.  I have seen mapped drives not connect in Windows File Explorer in Win 10 frequently however so, I have discontinued using mapped drives in favor of establishing Network Locations to network shares instead.  I have found them much more reliable.