2012 R2 Full Metal Backups Fail from the 2010 DPM Server

Problem:  Server 2012 full metal backups fail from the DPM server.


Errors:
  1. DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x8078015B). (ID 30229 Details: Internal error code: 0x809909FB)
  2. The backup operation that started at '‎2015‎-‎07‎-‎28T15:32:54.838780500Z' has failed with following error code '0x8078015B' (Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
  3. C:\Windows\Logs\WindowsServerBackup\Backup.log:  Backup of volume C: has failed. Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.

Suggestions:

  1. Increase the allocated replica volume size by using the modify the disk allocation wizard from the DPM GUI.  Run a full consistency check.
  2. WSB bare metal recovery (BMR) backups use Volume Shadow Snapshots on the System Recovery and EFI PartitionsEnsure these resources have at least 320MB of free space for Volume Shadows Snapshots (VSS).
  3. Do not run WSB on the protected 2012 server -only manage backups from DPM.  Individual backups run from WSB modifies the backup catalog and VSS volume associations -DPM backups begin to fail.  Steps to correct:

      -Use Vssadmin and/or Diskshadow to delete all local snapshots on protected 2012 member.
      -Delete WSB catalog from protected 2012 server: wbadmin delete catalog
      -
      Perform consistency check from DPM.
    1. Manually increase the size of the Replica volume.  DPM does not calculate an appropriate replica size for bare metal backups.    Microsoft recommends:

           Data Source Size x 3 / 2

      However, I found this formula was insufficient.  Rather, increase storage liberally.  If Microsoft's forumla call for 50GB, try using 100GB!  Consistency checks will work after the resource has sufficient storage in DPM.    
    References:
    https://technet.microsoft.com/en-us/library/Bb795684.aspx



    0 Comments:

    Post a Comment

    My Instagram