Skip to main content

backup file in use ?

Thread needs solution

i start a backup at a client and it keeps saying close application that is using this file.
now i am sure no other application is using that file it doesnt even exist on the location. but cant backup. first full backup worked now the first incremental backup wont .. so whats the problem and what is locking the backup file that doesnt even exist yet.  and what is al the bs_hudson stuff mean ?????? c:\bs_hudson\workspace\790\products\imager etcetcetc ?

 

error 0xfff0: Toegang geweigerd
| line: 0xbd28fdbd64edb8f1
| bestand: c:\bs_hudson\workspace\790\core\common\error.cpp:307
| functie: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\790\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070005
| $module: ti_demon_vs_17750
2023-02-23T12:29:02:713+01:00 6664 I00640000: Volledige versie schrijven naar bestand: Mijn bestanden_full_b2_s1_v1.tib
2023-02-23T12:29:08:016+01:00 6664 E01E50023: Error 0x1e50023: Sluit de toepassing die momenteel mogelijk het volgende bestand gebruikt: \\BackupNas\nasbackup\Mijn bestanden_full_b2_s1_v11.tib
| opsporingsniveau: fout
| line: 0x4d3f22948e29f19e
| bestand: c:\bs_hudson\workspace\790\products\imager\archive\impl\utils.cpp:199
| functie: `anonymous-namespace'::GenerateGuiErrorWithPath
| line: 0x4d3f22948e29f19e, c:\bs_hudson\workspace\790\products\imager\archive\impl\utils.cpp:199, `anonymous-namespace'::GenerateGuiErrorWithPath
| $module: ti_demon_vs_17750
|
| error 0x40014: Kan geen toegang krijgen tot het bestand.
| line: 0x1d8eab676a3f6aba
| bestand: c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_message_callback.cpp:1169
| functie: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6aba, c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_message_callback.cpp:1169, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: \\BackupNas\nasbackup\Mijn bestanden_full_b2_s1_v1.tib
| $module: ti_demon_vs_17750
|
| error 0x40014: Kan geen toegang krijgen tot het bestand.
| line: 0xf35f747b3b21f9e0
| bestand: c:\bs_hudson\workspace\790\core\file\windows\winnt_dir.cpp:727
| functie: winnt_dir::Remove
| line: 0xf35f747b3b21f9e0, c:\bs_hudson\workspace\790\core\file\windows\winnt_dir.cpp:727, winnt_dir::Remove
| function: DeleteFileW
| path: \\?\UNC\BackupNas\nasbackup\Mijn bestanden_full_b2_s1_v11.tib
| $module: ti_demon_vs_17750
|
| error 0xfff0: Toegang geweigerd
| line: 0xbd28fdbd64edb8f1
| bestand: c:\bs_hudson\workspace\790\core\common\error.cpp:307
| functie: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\790\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070005
| $module: ti_demon_vs_17750
2023-02-23T12:29:08:016+01:00 6664 I01E50023: Sluit de toepassing die momenteel mogelijk het volgende bestand gebruikt: \\BackupNas\nasbackup\Mijn bestanden_full_b2_s1_v11.tib 

0 Users found this helpful

John, the error shown in your log is saying that the original Full backup file for this incremental backup task cannot be accessed - 'Access denied' which suggests that perhaps the NAS credentials needed for this task may have changed?

The log also shows that your client is not running the latest / final build version #18100 for ATI 2019 that Acronis released back in January 2022 to fix some security issues.

The c:\bs_hudson\ entries in the log are internal messages intended for the Acronis developers and refer to entry points within their code, not to locations on the client PC.

I would suggest trying to create a small new task from the client PC to the same NAS, say of a single folder with a few files, i.e. a temporary folder, to confirm if the credentials being used are correct or not?

the credentials are good . so its wierd . this backup is going through a vpn. so maybe there is something wrong ? also is it possible to auto ignore files that are locked for whatever reason?

John, the use of a VPN is probably at the heart of this issue and is not something I have any experience in trying to use for my own backups.

For locked files, then the only options are those in the Options > Advanced > Error handling settings for the task, but this won't help if it is the destination image file that is locked!

Steve Smith wrote:

John, the use of a VPN is probably at the heart of this issue and is not something I have any experience in trying to use for my own backups.

For locked files, then the only options are those in the Options > Advanced > Error handling settings for the task, but this won't help if it is the destination image file that is locked!

 

didnt work and its not the destination that is locked its a source file .  any other ideas ?

 

Ich denke, das der Backuptask defekt ist und nicht weiter verwendet werden kann, ich würde einen neuen Backuptask erstellen.

"path: \\?\UNC\BackupNas\nasbackup\Mijn bestanden_full_b2_s1_v11.tib"

--------------------------------------------

I think that the backup task is broken and cannot be used further, I would create a new backup task.

"path: \\?\UNC\BackupNas\nasbackup\Mijn bestanden_full_b2_s1_v11.tib"