Salta al contenuto principale

ATI 2017 not removing older chains

Thread needs solution

I have a custom incremental backup scheme defined to create a full backup after six incrementals and to keep no more than 2 chains.

Looking in my NAS today I see four chains when I expected only two.

I've attached a screenshot of the custom scheme.

ATI is build 5554 backing up to a Synology NAS. I'm using the IP address workaround for the NAS due to the authentication issues with ATI and Windows.

Any ideas why ATi is not removing the older chains?

Thanks!

 

Allegato Dimensione
untitled.jpg 47.37 KB
0 Users found this helpful

Steve, what do your logs say about any attempts by automatic cleanup (shown as consolidation in the logs) for your task creating these backups.

There is a known issue with 5554 that can perform the backup to the NAS with no problem but then encounter credential issues when trying to perform the consolidation actions.  I suspect that you may have hit this same issue!

I have this issue on one of my computers running Windows 7 and ATIH 2017 build 5554 backing up to my own Synology DS215 NAS where I have to manually delete the oldest version chain via the ATIH option to 'Open backup location' and then run a Validation for the task to reconcile the Acronis database files, after which the task log shows no problem until the next time it needs to cleanup the oldest version chain again.

I am waiting for ATIH 2017 on that computer to offer the upgrade to the ATIH 2017 build 6116 NG standard version, which per other updates from Slava in this forum is due in around a month.

PS. Download and use the Log File Viewer app from the link in my signature for easier access to the logs.

Thanks Steve!

This is happening on all three Windows 7 machines at my office by the way.

Those logs are gnarley but I do see an error message of "Failed to perform consolidation. Ensure that the credentials are correct" in relation to the Synology NAS so I think you nailed it.

I manually deleted the older chains and tried a file restore telling ATI to ignore the errors. It seemed to work OK.

I'm also holding for the official new build for ATI 2017.

Steve, glad that the workaround worked for you too - there have been suggestions of other ways around this issue but I would rather wait for a proper fix than start having to use IP address for my NAS or apply temporary patches etc.

The trouble with the chains is on my business network with unpatched ATI 2017.

I did patch the installations on my home network to build 5555 when first trying to resolve the NAS authentication problem and the chains for those machines are automatically removed as expected. I just didn't want to patch the installations on my business network. The PCs at home are all Wndows 10 as well.

I'm hoping the next ATI 2017 resolves the issues. I'm working around three issues at this point.

Steve, the new build 6116 which is currently only available for the 2017 NG Premium (subscription version) should contain fixes for most of the key problems identifed with 5554 - I have it on a laptop at present but not on the Windows 7 system with this problem (didn't want to put the Premium on all my systems as my personal preference is to stay with perpetual licenses, not subscription - the latter is from being an MVP for testing).

Automatic clean-up (consolidation) on the NAS is working properly with ATI 2017 build 8029

Steve, thanks for your confirmation, I have found the same myself since upgrading to build 8029.