Skip to main content

Yet another bug: cant finish backup because of one locked file.

Thread needs solution

Backup was running for 2 days until next bug came.
Backup: network directory -> local USB drive.
Backup didnt finish because it encountered one open/locked file.
Its your latest build 11.0.17437 and options to not show dialog boxes and ignore sector errors are enabled. Snapshot is deactivated, because source is not local drive and doesnt support this.

Failing backup because of one single locked file is a disaster to production environment.
Whats wrong with this software?

1 Information 13.07.2012 23:01:22 Befehl 'Backup' wird ausgeführt.
2 Information 13.07.2012 23:02:01 Erstelle ein inkrementelles Backup
Von: \\nas\cad\
Zu Datei: "file:F:\NAS_2012_07_09_23_01_10_204F4.TIB"
Komprimierung: Normal
Ausschluss: Durch Ausschlussmaske erfasste Dateien
Kriterium: *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...

3 Fehler 13.07.2012 23:30:29 Fehler beim Backup.

Fehlercode: 0x40019
$module = "disk_bundle_vs"
Tag: 0xCE542E14DA203B8B
Fehler beim Backup. Error in backup

Fehlercode: 0x40019
$module = "disk_bundle_vs"
Tag: 0xCE542E14DA203ACB
Zugriff auf die Datei verweigert. Access to file denied

Fehlercode: 0x40014
function = "CreateFileW",
filename = "\\?\UNC\somepath\~$Toleranzen.pptx",
$module = "disk_bundle_vs"
Tag: 0xA8A1022BD18AE057
Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird

Process cannot access file, because its used by another process.

Fehlercode: 0xFFF0
code = 2.147.942.432 (0x80070020),
$module = "disk_bundle_vs"
Tag: 0xBD28FDBD64EDB8E0
4 Fehler 13.07.2012 23:30:30 Befehl 'Backup' ist fehlgeschlagen.
Command 'Backup' failed
Zusätzliche Info:
--------------------
Fehlercode: 61
Module: 309
LineInfo: 4a8728dc8a1c94f4
Felder: $module : service_process_vs
Nachricht: Befehl 'Backup' ist fehlgeschlagen.
Command: 'Backup' failed
--------------------
Fehlercode: 3
Module: 329
LineInfo: 1cd98aae889424f9
Felder: $module : disk_bundle_vs
Nachricht: Backup ist fehlgeschlagen.
Backup failed
--------------------
Fehlercode: 1060
Module: 1
LineInfo: ba19e88dc5fea16e
Felder: $module : disk_bundle_vs
Nachricht:
--------------------
Fehlercode: 25
Module: 4
LineInfo: ce542e14da203b8b
Felder: $module : disk_bundle_vs
Nachricht: Fehler beim Backup.
Error during backup
--------------------
Fehlercode: 25
Module: 4
LineInfo: ce542e14da203acb
Felder: $module : disk_bundle_vs
Nachricht: Fehler beim Backup.
Error during backup
--------------------
Fehlercode: 20
Module: 4
LineInfo: a8a1022bd18ae057
Felder: function : CreateFileW, filename : \\?\UNC\somepath\~$Toleranzen.pptx, $module : disk_bundle_vs
Nachricht: Zugriff auf die Datei verweigert.
Access to file denied
--------------------
Fehlercode: 65520
Module: 0
LineInfo: bd28fdbd64edb8e0
Felder: code : 2147942432, $module : disk_bundle_vs
Nachricht: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird
Process cannot access file, because its used by another process.
--------------------
Task 'Inkrementelles Backup' ist fehlgeschlagen auf Maschine 'dc1.domain.com'.
Task 'Incremental Backup' failed on machine 'dc.domain.dom'.

0 Users found this helpful

As a workaround, you could exclude filenames starting with a ~ which are temporary files created by applications such as powerpoint in this case. Also you could exclude the System Volume Information folder as well ,since you probably would not need to restore it anyway.
It would be better if the backup just skipped the files it could not backup and log them for review, not have the backup just fail.

Hello Yurij,

Thanks for using Acronis Software.

It is not recommended to use file backup for a system partition of another machine. File backup always works like a copy command and cannot backup files that are open or locked by the OS or any application. It is important to remember, that an system backup done via UNC path and file backup will create a valid backup file, but there is no guarantee, that the restored file backup will ever boot again.

Please use instead an local Acronis Agent to create backups from this system.

For using folder exclusion you will find more information in this article from our Knowledge Base.

Please let me know if you have additional questions.

Thank you.

James F wrote:
... It would be better if the backup just skipped the files it could not backup and log them for review, not have the backup just fail.

I completely agree with this. i have a couple computers that fail (file) backups several times a week due to files being locked, and this is while backing up locally with an agent. My issue isnt with files starting with a ~ though, and setting exclusions for those specific files is more of a band-aid than a fix IMHO.

It would also be nice to be able to select a machine to back up and not have to worry that the backup will fail due to an empty CD drive (or another empty drive, like when machines have a multi-card reader that has 4 or 5 "drives" that are always present). Makes for a lot more manual selection when configuring backups and makes using groups to do file level backups useless.

It is not recommended to use file backup for a system partition of another machine.
Im backing up data directory located on NAS, not a partition.
File backup always works like a copy command and cannot backup files that are open or locked by the OS or any application.
So skip them, where is the problem? Completely failed backup is a disaster in case of failure, as compared to few missing files.
It is important to remember, that an system backup done via UNC path and file backup will create a valid backup file, but there is no guarantee, that the restored file backup will ever boot again.
Im not going to boot my data directory in case of failure :)

Please use instead an local Acronis Agent to create backups from this system.
NAS is driven by some customized Synology Linux OS, so no chance to install any agents.

For using folder exclusion you will find more information in this article from our Knowledge Base.
Im not going to exclude any folders from my data backups, but I will try to add exclusion for "~" and see if it helps.

Please let me know if you have additional questions.
Only one question: are you going to fix this? Option to continue backup in case of single file errors would be just fine.

Last night 2 sceduled backups failed again, because acronis_vs service was stopped for some reason.
Currently, im switching back to my robocopy script, at least for data backup. Its not incremental, but at least it always successfully finished its job without any voodo magic.

Hear your customers.
Do whatever possible to finish backups!
If file is locked, skip it.
If sector is damaged, ignore it.
If service is stopped, restart it.
If one vss service is not able to make snapshot, switch to the other.
Inconsistent backup is a lot. No backup is epic fail.