Hello,
I implemented my first 2016 server a few weeks ago. I've been having intermittant problems with back ups, and the cause seems to be that the log file is locked so a new back up doesn't start.
Here is my script run with a scheduled task (ip changed)
WBADMIN START BACKUP -backuptarget:\\0.0.0.0\sauvegarde\Complete1 "-include:g:,l:" -systemState -quiet >> C:\backupLogs.txtIt's the backuplogs.txt that is staying locked after backups. Then when the next run of the backup happens, it can't open the file so the backup doesn't run.
It can go 1 to many days just fine, then one day it stays locked and no more backups work (with task or manually run) until I restart the server(which unlocks the file), then they the work fine again.
Can anyone please tell me why this file is staying locked sometimes? Backing up to a synology disk station that is up to date. The VM on this same server never fails (but no system state on that backup). Server 2012 backing up to same device has no problems either.
The backup file is very useful so I'd like to keep it. I could append the date I guess to the file name but I'd rather it just work.