DPM 2010 backup of bare metal recovery and system state of DC failing due to missing remote shared folder RRS feed

  • Question

  • A DPM 2010 backup of a 2008 R2 DC keeps failing, although the single other file server within that Protection Group succeeds. The protection status is perpetually 'replica is inconsistent', and the error on the DPM server is ' Creation of recovery points for Non VSS Datasource Writer on DCNAME.Domain.rootdomain have failed. The last recovery point creation failed for the following reason: (ID: 3114) DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 0x9563F0). (ID: 30229)

       On the DC there are plenty of errors pertaining to the Windows backup service including:

        The backup operation that started at '‎2016‎-‎06‎-‎14T14:44:09.190508100Z' 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.

    In Windows Server Backup it says 'operation failed. Retry the operation. If the issue persists, delete and recreate the scheduled backup settings. The remote shared folder does not exist

    I have checked the backup path and it goes to a share on the DPM 2010 server which indeed does not exist, although lots of others do. These are all mounted volumes distributed accross several physical disks, so I do not wish to just create a share with the same name manually as I doubt very much I can get all the configuration to be the same as it should be. How can I get DPM 2010 to create this share again? I have removed this DC from the Protection Group, and then created a new Protection Group in which I added this DC, but the problem remains the same.


    Thursday, June 23, 2016 12:42 PM


  • If anyone is interested in the end I fixed it myself. The log referring to Windows Backup failures referred to a share with an automatically created name that was meant to exist on the DPM server but did not. I manually created the share on the DPM server, and gave the DC local system account full permissions. After forcing a consistency recheck it went green and then it started backing up successfully.
    Thursday, July 7, 2016 3:37 PM