none
Server 2012R2 backup fails randomly with "The specified network name is no longer available" RRS feed

  • Question

  • Folks,

    I have 2 .vhdx (Generation 2) domain controllers that randomly fail DPM 2012R2 Bare Metal backup with the following " The specified network name is no longer available"

    VM:

    * Server 2012R2, fully patched, with "windows server backup" feature installed, enough of HD space for VSS backup, Gen2 -.vhdx

    * netsh int tcp set global chimney=disabled

    * netsh int tcp set global rss=disabled

    I have also tried the following: http://goo.gl/8WTIhx

    DPM2012R2:

    Fully patched and currently Bare Metal backing up 2008R2 Gen1 VM DCs with absolutely no problem. DPM has more than enough storage to accommodate the backup job

    I am swallowing my pride and asking for help! :)

    Dmitri.

    ************************************************

    EDIT: have uninstalled the backup agent, removed the server backup feature and reinstalled everything back.

    Can reliably backup the VM locally, still have random DPM failures:

    C:\Windows\System32>wbadmin start backup -allcritical -backuptarget:e:
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2013 Microsoft Corporation. All rights reserved.

    Retrieving volume information...
    This will back up (EFI System Partition),(C:),Recovery (300.00 MB) to e:.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

    The backup operation to E: is starting.
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Windows Server Backup is updating the existing backup to remove files that hav
    been deleted from your server since the last backup.
    This might take a few minutes.
    Creating a backup of volume (EFI System Partition) (99.00 MB), copied (0%).
    The backup of volume (EFI System Partition) (99.00 MB) completed successfully.
    Creating a backup of volume (C:), copied (0%).
    Creating a backup of volume (C:), copied (4%).
    Creating a backup of volume (C:), copied (8%).
    Creating a backup of volume (C:), copied (11%).
    Creating a backup of volume (C:), copied (15%).
    Creating a backup of volume (C:), copied (18%).
    Creating a backup of volume (C:), copied (21%).
    Creating a backup of volume (C:), copied (25%).
    Creating a backup of volume (C:), copied (28%).
    Creating a backup of volume (C:), copied (31%).
    Creating a backup of volume (C:), copied (34%).
    Creating a backup of volume (C:), copied (38%).
    Creating a backup of volume (C:), copied (42%).
    Creating a backup of volume (C:), copied (45%).
    Creating a backup of volume (C:), copied (49%).
    Creating a backup of volume (C:), copied (52%).
    Creating a backup of volume (C:), copied (56%).
    Creating a backup of volume (C:), copied (59%).
    Creating a backup of volume (C:), copied (62%).
    Creating a backup of volume (C:), copied (66%).
    Creating a backup of volume (C:), copied (70%).
    Creating a backup of volume (C:), copied (73%).
    Creating a backup of volume (C:), copied (76%).
    Creating a backup of volume (C:), copied (80%).
    Creating a backup of volume (C:), copied (84%).
    Creating a backup of volume (C:), copied (87%).
    Creating a backup of volume (C:), copied (90%).
    Creating a backup of volume (C:), copied (94%).
    Creating a backup of volume (C:), copied (97%).
    Creating a backup of volume (C:), copied (99%).
    The backup of volume (C:) completed successfully.
    Creating a backup of volume Recovery (300.00 MB), copied (38%).
    Creating a backup of volume Recovery (300.00 MB), copied (100%).
    Summary of the backup operation:
    ------------------

    The backup operation successfully completed.
    The backup of volume (EFI System Partition) (99.00 MB) completed successfully.
    The backup of volume (C:) completed successfully.
    The backup of volume Recovery (300.00 MB) completed successfully.
    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-07-03-2014_21-00-01.log




    Monday, March 10, 2014 4:50 PM

All replies

  • Try

    Command to Move VSS Snapshot on Map Drive while Backup is in Progress: http://technet.microsoft.com/en-us/library/cc788051.aspx#BKMK_examples

    vssadmin add shadowstorage /for=d: /on=z: /maxsize=unbounded

    To limit snapshot max size

    vssadmin add shadowstorage /for=d: /on=z: /maxsize=40%

    To revert back the above command: http://technet.microsoft.com/en-us/magazine/2006.01.rapidrecovery.aspx

    VSSAdmin Create Shadow /For=D: /AutoRetry=2

    from

    http://social.technet.microsoft.com/Forums/en-US/7373a7b8-01c8-4e2b-aaaa-513b7dad56f4/windows-server-2012-r2-vm-back-up-fails-with-insufficient-storage-available-to-create-either-the?forum=windowsbackup


    Have a nice day !!!

    Wednesday, March 12, 2014 10:30 AM
  • also try

    shrink C drive down by 512MBs and created a new partition and added Shadow Storage to it with the following command, S being mapped to the recovery volume
    vssadmin Add ShadowStorage /For=S: /On=F: /MaxSize=UNBOUNDED


    Have a nice day !!!

    Wednesday, March 12, 2014 10:31 AM
  • 1.  Disable WinRE (Open elevated command prompt and Run: “reagentc /disable”)
    2.  Take system image backup
    3.  Enable WinRE (Open elevated command prompt and Run: “reagentc /enable”)

    This solved the issue for me.

    Automate

    Use a DPM pre-backup and post-backup script to disable WINRE before the BMR backup is taken and Re-enable WINRE after the BMR backup completes.

    Using pre-backup and post-backup scripts

    a) On the Windows 2012 R2 protected server (hyper-V guest) replace the ScriptingConfig.xml file with the new one below.


    LOCATION:  C:\Program Files\Microsoft Data Protection Manager\DPM\Scripting\ScriptingConfig.xml

    CONTENT OF NEW ScriptingConfig.xml.  Note the trailing space in "System Protection " <--must be trailing space.


    < ?xml version="1.0" encoding="utf-8"?>
    < ScriptConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.microsoft.com/2003/dls/ScriptingConfig.xsd">
    < DatasourceScriptConfig DataSourceName="System Protection ">
    < PreBackupScript>C:\temp\Disable-WINRE.cmd</PreBackupScript>
    < PostBackupScript>C:\temp\Enable-WINRE.cmd</PostBackupScript>
    < TimeOut>5</TimeOut>
    < /DatasourceScriptConfig>
    < /ScriptConfiguration>


    b) Make the following two batch files (disable-winre.cmd and enable-winre.cmd) and save them in c:\temp folder on the protected server.

    Disable-WINRE.cmd content.

    reagentc /disable


    Enable-WINRE.cmd content.

    reagentc /enable


    Have a nice day !!!

    Wednesday, March 12, 2014 10:38 AM
  • thanks Eugene Leitan.

    We are running pre and post commands

    <?xml version="1.0" encoding="utf-8"?>
    <ScriptConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.microsoft.com/2003/dls/ScriptingConfig.xsd">
    <DatasourceScriptConfig DataSourceName="System Protection ">
    <PreBackupScript>C:\scripts\Disable-WINRE.cmd</PreBackupScript>
    <PostBackupScript>C:\scripts\Enable-WINRE.cmd</PostBackupScript>
    <TimeOut>5</TimeOut>
    </DatasourceScriptConfig>
    </ScriptConfiguration>

    We believe that the whole thing is related to DPM/type (Generation) of the VM. We run multiple 2012R2 (Gen1) Domain Controllers on 2008R2 Hyper-V, backed up by the same DPM server, and BMR and System state backup is rock solid.

    As I said before, can dump a local wbadmin backup reliably, however, it randomly fails if the backup is started by DPM.

    thanks!

    Wednesday, March 12, 2014 6:14 PM
  • As said Mike Jacquet

    "The Windows product group has determined that this is a code defect and are working on a fix.  In the meantime, you can use one of the following workarounds so DPM initiated BMR backups succeed."

    That's why i think that pre and post scripts for DPM are temporary solution.


    Have a nice day !!!

    Thursday, March 13, 2014 5:04 AM
  • thanks Mike!

    Seems like only affected Generation 2 VMs , correct? 

    Friday, March 14, 2014 4:54 PM