Skip to main content

ATI 2019 Automatic Cleanup is not working like expected - which user and password is used to do the cleanup

Thread needs solution

Hello,

I use ATI 2019 with a NAS to backup my data.
To prevent writing access to my backup files, I have created a folder on the NAS on which I as user from Windows only have read access.
ATI 2019 has its own credentials which were configured inside ATI with write access to this folder.
For me it seems that the automatic and manual cleanup of the Backup is using my local windows account to do the job instead of using the credentials entered inside of ATI 2019.
The issue which I see is that my backup storage is growing and older versions will not get deleted.

I hope you got the point and can verify it in your lab and fix it in an update.

It would be very helpful to not manually delete these files.

Thank you.

Regards Jochen

0 Users found this helpful

Jochen, if you want Acronis development to get involved in investigating this issue you will need to open a Support Ticket directly with Acronis Support.  It is highly unlikely that any such action will arise from just posting in these forums.

I also have ATI 2019 and use this with my own Synology NAS where the only credentials used are those assigned specifically for Acronis to perform the backup task and any associated actions such as automatic cleanup.  I have no Windows type user access to the NAS and no assigned drive letter mapping, so ATI is definitely using the only Acronis credentials given to the task and is cleaning up old versions as the cleanup rule are applied.

This is shown clearly in both the ATI 2019 GUI Activity page entries and in the backup task log file.

17/12/2018 08:30:07 :488  The following backups have been successfully created: nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_full_b6_s1_v1.tib
17/12/2018 08:30:09 :922  Consolidate Backup Archive Location: nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_full_b6_s1_v1.tib Destination: nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_full_b6_s1_v1_9D4899BC-7F73-432E-9050-91A47C94D195.tib
17/12/2018 08:30:13 :074  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s8_v1.tib.
17/12/2018 08:30:13 :408  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s7_v1.tib.
17/12/2018 08:30:13 :905  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s6_v1.tib.
17/12/2018 08:30:15 :182  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s5_v1.tib.
17/12/2018 08:30:15 :861  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s4_v1.tib.
17/12/2018 08:30:16 :103  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s3_v1.tib.
17/12/2018 08:30:16 :524  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_inc_b4_s2_v1.tib.
17/12/2018 08:30:16 :787  Deleting backup file with path nas://DROYLS3TB/Backup/Dell Studio 1545/Win 10-1-2 Synology_full_b4_s1_v1.tib.
17/12/2018 08:30:29 :556  Operation has succeeded.
 

I use the same approach as that taken by Steve and have had the same experience. I have a different model Synology NAS so it is unlikely to be model specific issue; indeed I would not expect there to be such a variation.

Ian

PS Only NAS related problem I have had was with continuous backup task that got corrupted when installing Windows October update.

Hi Steve, hi Ian,

thank you both for your answers.

In general I don´t know what to think about this issue. You both have from your computer directly via Windows no access with your use to your NAS.
So you use only the credentials inside Acronis True Image.
I have two credentials, one with my Windows Account and second one inside Acronis.
Don´ know if this make any differences?
And by the way, I use a Thecus NAS.
After your posts, I have checked my logfiles about some errors and found some.
In the end the Job says it was successful and freed up some GB but it was failing.

Don´ know if you can help me with this logentries or if I should open a ticket directly by Acronis?

Here is the output of the logfile:

2018-12-20T01:34:08:506+01:00 7520 E01E50017: Error 0x1e50017: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| Ablaufverfolgungsebene: Fehler
| line: 0x6d5b4dcc0ba149e7
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:3049
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::TryTakeSourceExclusiveAccess
| line: 0x6d5b4dcc0ba149e7, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:3049, TrueImage::Archive::CloneArchiveOperationImpl::TryTakeSourceExclusiveAccess
| $module: ti_demon_vs_14690
|
| error 0x40014: Der Zugriff auf die Datei wird verweigert.
| line: 0xf35f747b3b21f907
| Datei: c:\bs_hudson\workspace\646\core\file\windows\winnt_dir.cpp:510
| Funktion: winnt_dir::OpenFile
| line: 0xf35f747b3b21f907, c:\bs_hudson\workspace\646\core\file\windows\winnt_dir.cpp:510, winnt_dir::OpenFile
| function: OpenFileW
| path: \\?\UNC\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib
| $module: ti_demon_vs_14690
|
| error 0xfff0: Zugriff verweigert
| line: 0xbd28fdbd64edb8f1
| Datei: c:\bs_hudson\workspace\646\core\common\error.cpp:307
| Funktion: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\646\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070005
| $module: ti_demon_vs_14690
2018-12-20T01:34:08:506+01:00 7520 E000B03E9: Error 0xb03e9: Öffnen des Daten-Streams fehlgeschlagen. Versuchen Sie das Backup aus der Liste zu entfernen, es dann durch Klicken auf 'Vorhandenes Backup hinzufügen' neu aufzunehmen und anschließend die Backup-Einstellungen neu zu erstellen.
| Ablaufverfolgungsebene: Fehler
| line: 0x6d5b4dcc0ba14815
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2583
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::SwitchToArchive
| line: 0x6d5b4dcc0ba14815, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2583, TrueImage::Archive::CloneArchiveOperationImpl::SwitchToArchive
| $module: ti_demon_vs_14690
|
| error 0x1e50006: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| line: 0x6d5b4dcc0ba14650
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2130
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::PrepareReadStream
| line: 0x6d5b4dcc0ba14650, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2130, TrueImage::Archive::CloneArchiveOperationImpl::PrepareReadStream
| $module: ti_demon_vs_14690
|
| error 0x1e50017: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| line: 0x6d5b4dcc0ba149e7
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:3049
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::TryTakeSourceExclusiveAccess
| line: 0x6d5b4dcc0ba149e7, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:3049, TrueImage::Archive::CloneArchiveOperationImpl::TryTakeSourceExclusiveAccess
| $module: ti_demon_vs_14690
|
| error 0x40014: Der Zugriff auf die Datei wird verweigert.
| line: 0xf35f747b3b21f907
| Datei: c:\bs_hudson\workspace\646\core\file\windows\winnt_dir.cpp:510
| Funktion: winnt_dir::OpenFile
| line: 0xf35f747b3b21f907, c:\bs_hudson\workspace\646\core\file\windows\winnt_dir.cpp:510, winnt_dir::OpenFile
| function: OpenFileW
| path: \\?\UNC\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib
| $module: ti_demon_vs_14690
|
| error 0xfff0: Zugriff verweigert
| line: 0xbd28fdbd64edb8f1
| Datei: c:\bs_hudson\workspace\646\core\common\error.cpp:307
| Funktion: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\646\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070005
| $module: ti_demon_vs_14690
2018-12-20T01:34:08:507+01:00 7520 E01EF0029: Error 0x1ef0029: Während der Backup-Konsolidierung ist ein Fehler aufgetreten.
| Ablaufverfolgungsebene: Fehler
| line: 0x6d5b4dcc0ba13fd5
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:471
| Funktion: `anonymous-namespace'::BaseExecutor::Start
| line: 0x6d5b4dcc0ba13fd5, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:471, `anonymous-namespace'::BaseExecutor::Start
| $module: ti_demon_vs_14690
|
| error 0x1e50001: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| line: 0x6d5b4dcc0ba13fba
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:444
| Funktion: `anonymous-namespace'::BaseExecutor::Start
| line: 0x6d5b4dcc0ba13fba, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:444, `anonymous-namespace'::BaseExecutor::Start
| $module: ti_demon_vs_14690
|
| error 0x1e5001f: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| line: 0x6d5b4dcc0ba14839
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2619
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::SelectNextArchiveForConsolidation
| line: 0x6d5b4dcc0ba14839, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2619, TrueImage::Archive::CloneArchiveOperationImpl::SelectNextArchiveForConsolidation
| $module: ti_demon_vs_14690
|
| error 0x1e50006: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| line: 0x6d5b4dcc0ba14650
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2130
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::PrepareReadStream
| line: 0x6d5b4dcc0ba14650, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:2130, TrueImage::Archive::CloneArchiveOperationImpl::PrepareReadStream
| $module: ti_demon_vs_14690
|
| error 0x1e50017: Exklusiver Zugriff auf Backup \\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib während der Konsolidierung ist fehlgeschlagen. Stellen Sie sicher, dass die Backup-Datei nicht in einer anderen Anwendung geöffnet ist.
| line: 0x6d5b4dcc0ba149e7
| Datei: c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:3049
| Funktion: TrueImage::Archive::CloneArchiveOperationImpl::TryTakeSourceExclusiveAccess
| line: 0x6d5b4dcc0ba149e7, c:\bs_hudson\workspace\646\products\imager\archive\impl\operations\archive_operation_clone.cpp:3049, TrueImage::Archive::CloneArchiveOperationImpl::TryTakeSourceExclusiveAccess
| $module: ti_demon_vs_14690
|
| error 0x40014: Der Zugriff auf die Datei wird verweigert.
| line: 0xf35f747b3b21f907
| Datei: c:\bs_hudson\workspace\646\core\file\windows\winnt_dir.cpp:510
| Funktion: winnt_dir::OpenFile
| line: 0xf35f747b3b21f907, c:\bs_hudson\workspace\646\core\file\windows\winnt_dir.cpp:510, winnt_dir::OpenFile
| function: OpenFileW
| path: \\?\UNC\N5550\Acronis\Killerjoe-PC\SanDisk SDSSDXPS480G_inc_b5_s5_v1.tib
| $module: ti_demon_vs_14690
|
| error 0xfff0: Zugriff verweigert
| line: 0xbd28fdbd64edb8f1
| Datei: c:\bs_hudson\workspace\646\core\common\error.cpp:307
| Funktion: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\646\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070005
| $module: ti_demon_vs_14690
2018-12-20T01:34:08:654+01:00 7520 I013C0006: Aktion erfolgreich.

As you can see there are a lot of access denied messages (in german: "Der Zugriff auf die Datei wird verweigert").

I have tried to access the NAS with another system and used the credentials out of Acronis to get a Login there.
I´m able to delete and rename the file, so I have write access with that user, but Acronis for whatever reason cannot delete it.
I don´ think that an app on the NAS is preventing the file to be deleted. I don´t have apps like Antivirus or equal on it running.

Thank you for your help!
Regards,
Jochen

Jochen, I believe there is an issue when you are mixing Windows and Acronis credentials for accessing your NAS.

See KB  58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials - which although written for an earlier version is still relevant for later versions too.

Ideally, can you test your Acronis task when you have no open connections to the NAS to see if this makes a difference.