none
WBADMIN blocking log file and preventing future backups server 2016 RRS feed

  • Question

  • 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.txt

    It'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.  

    Friday, September 20, 2019 8:54 AM

All replies

  • Can you try using out-file command

    WBADMIN START BACKUP -backuptarget:\\0.0.0.0\sauvegarde\Complete1  "-include:g:,l:" -systemState -quiet | Out-File C:\backupLogs.txt -Append 


    Vote or mark as answer if you think useful


    Friday, September 20, 2019 9:12 AM
  • Hi,
    Just want to confirm the current situations.
    Please feel free to let us know if you need further assistance.
    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 24, 2019 6:15 AM
    Moderator
  • Hi,

    Solved the blocked backup log by appending the date.

    Still getting the Following errors from time to time with failed backups on my two dc server 2016:

    Retrieving volume information...
    This will back up OS(C:) (Selected Files),DOCUMENTS(G:),INTRANET(L:),RECOVERY (3.00 GB) (Selected Files) to \\path\Complete1SRV5.
    Windows Backup cannot read the backup destination.

    and

    Retrieving volume information...
    This will back up OS(C:) (Selected Files),DOCUMENTS(G:),INTRANET(L:),RECOVERY (3.00 GB) (Selected Files) to \\path\Complete1SRV5.
    Provide a user name and a password for a user who has write permission to the
    remote shared folder.

    Enter the user name for '\\172.16.0.220\sauvespi\Complete1SRV5': 

    NAS is Synology disk station, joined to the AD, and completely accessible whenever I try. Again, often the task runs fine, then all the sudden it doesn't and I can't figure out why.  Synology says they have checked all my debug files and the NAS is fine.

    This is the last bit from my server change that I need to get Under control, I need to be able to count on my backups running!


    • Edited by KCSPI76 Wednesday, October 2, 2019 3:06 PM
    Wednesday, October 2, 2019 3:06 PM
  • Hi,
    According to your description, the issue seems a little strange, we are trying to involve someone more professional to look into this issue, if there's any useful information or suggestions, we'll feedback as soon as possible.
    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 7, 2019 6:03 AM
    Moderator
  • ok thank you.

    This morning both DC backups failed, and the VM worked fine.

    Monday, October 7, 2019 1:48 PM
  • Any news on this?  I keep having this problem periodically and can't figure out why.
    Monday, October 21, 2019 7:27 AM