Backup job hangs on open file
We have a Win 10 Pro PC set up as a dedicated backup server running Backup4all 9.9.994. It has administrator access to all PCs and servers in our facility and runs a nightly backup on all of them.
I understand that Backup4all won't back up open files on remote machines and I'm fine with that. Occasionally a user will leave their Outlook open overnight and I'll get a warning that the .pst file could not be backed up, but the rest of the backup job proceeds and completes normally. Again, I'm fine with this.
Here's the problem - we have a SysLog server that receives and records log messages from our firewall and other devices. It is just another dedicated Win 10 Pro device. Normally the .log files (just text files) are opened just long enough for the SysLog process to write the record and then are closed again. Occasionally, if there is heavy activity, one of those files will be open at the exact moment that Backup4all tries to grab it. Instead of bypassing it and giving me a warning, however, the backup job hangs in a running status, showing the file it is trying to access. One of the processor cores on the backup server is pegged at 100%. The last entry in the B4A job log is "[Date Time] Files found to backup: ## (### KB)" (with actual values).
Looking at the SysLog server, the file is indeed open in Read mode. Forcing that file closed has no effect on the backup job. Trying to Cancel the backup job only causes it to hang again displaying "36% Aborting backup", and the processor core is still pegged. The only way to recover is to completely shut down the Backup4All app and any of its running processes and restart it.
Any thoughts?
Russ
I understand that Backup4all won't back up open files on remote machines and I'm fine with that. Occasionally a user will leave their Outlook open overnight and I'll get a warning that the .pst file could not be backed up, but the rest of the backup job proceeds and completes normally. Again, I'm fine with this.
Here's the problem - we have a SysLog server that receives and records log messages from our firewall and other devices. It is just another dedicated Win 10 Pro device. Normally the .log files (just text files) are opened just long enough for the SysLog process to write the record and then are closed again. Occasionally, if there is heavy activity, one of those files will be open at the exact moment that Backup4all tries to grab it. Instead of bypassing it and giving me a warning, however, the backup job hangs in a running status, showing the file it is trying to access. One of the processor cores on the backup server is pegged at 100%. The last entry in the B4A job log is "[Date Time] Files found to backup: ## (### KB)" (with actual values).
Looking at the SysLog server, the file is indeed open in Read mode. Forcing that file closed has no effect on the backup job. Trying to Cancel the backup job only causes it to hang again displaying "36% Aborting backup", and the processor core is still pegged. The only way to recover is to completely shut down the Backup4All app and any of its running processes and restart it.
Any thoughts?
Russ