none
BMR Failing on all servers DPM 2010 RRS feed

  • General discussion

  • My system state backups are failing on all 3 servers where I have the BMR option enabled. The system state works fine with BMR disabled on these same servers. The error being generated is coming from Windows Server backup and is as follows:

    The backup operation attempted at '‎2011‎-‎09‎-‎22T20:02:53.144149800Z' has failed to start, error code '2147942405' (General access denied error). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Thursday, September 29, 2011 7:45 PM

All replies

  • Hi,

     

    Are those machines being protected using workgroup or non-trusted domain agent communications ?   If so BMR is not supported as the domain machine account is required to access the share on the DPM server.  SystemState writes to local protected server then tranferred to DPM server, DPMRA does that so it works.  BMR is written directly to the DPM replica via a network share, and Windows backup running as system account needs access to that share.  The error is "access denied" meaning windows backup cannot access the share to write the BMR backup on the replica.

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 30, 2011 4:37 AM
    Moderator
  • All of the protected machines are either members of the domain or domain controllers.

    Friday, September 30, 2011 1:17 PM
  • OK - it's still some kind of permissions issue.

    The DPM replica volume for BMR has only these permissions where machinename$ is the computer account of the PS.

    Domain\machinename$:(F)
    NT AUthority\System:(F)


    DPM is not involved with this process except to start the backup, after that. It’s hands off until the backup completes, then we get the status of the backup and if successful, we make a snapshot on the DPM replica.  If we get a non-successful status, we display the error in the failed job details and you need to look at the wbadmin event logs (Under Application and Service logs - Microsoft - Windows - backup - Operational) for details.

     


    Using administrative command prompt on PS – you will get access denied is you try to backup to the DPM share.
    ===============================================================================


    C:\Users\Administrator>wbadmin start backup -allcritical -backuptarget:\\dpm01\a6159995754d48358fe39b4c46abbae4
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.


    Note: The backed up data cannot be securely protected at this destination.
    Backups stored on a remote shared folder might be accessible by other
    people on the network. You should only save your backups to a location
    where you trust the other users who have access to the location or on a
    network that has additional security precautions in place.

    Retrieving volume information...
    This will back up volume System Reserved (100.00 MB),Local Disk(C:) to \\dpm01\a6159995754d48358fe39b4c46abbae4.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

    Access is denied.

     

    Starting an a new cmd.exe with NT Authority\System should work.
    ========================================================


    C:\Users\Administrator>cd C:\Windows\MPSReports\DPM\bin

    C:\Windows\MPSReports\DPM\bin>psexec -s cmd.exe

    PsExec v1.96 - Execute processes remotely
    Copyright (C) 2001-2009 Mark Russinovich
    Sysinternals - www.sysinternals.com


    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Windows\system32>whoami
    nt authority\system


    C:\Windows\system32>wbadmin start backup -allcritical -backuptarget:\\dpm01\a6159995754d48358fe39b4c46abbae4
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.


    Note: The backed up data cannot be securely protected at this destination.
    Backups stored on a remote shared folder might be accessible by other
    people on the network. You should only save your backups to a location
    where you trust the other users who have access to the location or on a
    network that has additional security precautions in place.

    Retrieving volume information...
    This will back up volume System Reserved (100.00 MB),Local Disk(C:) to \\dpm01\a6159995754d48358fe39b4c46abbae4.
    Do you want to start the backup operation?
    [Y] Yes [N] No y
    y

    The backup operation to \\dpm01\a6159995754d48358fe39b4c46abbae4 is starting.
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    The backup of volume System Reserved (100.00 MB) successfully completed.
    Creating a backup of volume Local Disk(C:), copied (0%).
    Creating a backup of volume Local Disk(C:), copied (0%).
    Creating a backup of volume Local Disk(C:), copied (2%).
    Creating a backup of volume Local Disk(C:), copied (2%).
    Creating a backup of volume Local Disk(C:), copied (3%).
    Creating a backup of volume Local Disk(C:), copied (4%).
    Creating a backup of volume Local Disk(C:), copied (4%).
    Creating a backup of volume Local Disk(C:), copied (5%).
    Creating a backup of volume Local Disk(C:), copied (5%).
    Creating a backup of volume Local Disk(C:), copied (6%).
    Creating a backup of volume Local Disk(C:), copied (7%).
    Creating a backup of volume Local Disk(C:), copied (8%).
    Creating a backup of volume Local Disk(C:), copied (8%).
    Creating a backup of volume Local Disk(C:), copied (9%).
    Creating a backup of volume Local Disk(C:), copied (10%).
    Creating a backup of volume Local Disk(C:), copied (11%).
    Creating a backup of volume Local Disk(C:), copied (12%).
    Creating a backup of volume Local Disk(C:), copied (12%).
    Creating a backup of volume Local Disk(C:), copied (13%).
    Creating a backup of volume Local Disk(C:), copied (14%).
    Creating a backup of volume Local Disk(C:), copied (15%).
    Creating a backup of volume Local Disk(C:), copied (15%).
    Creating a backup of volume Local Disk(C:), copied (16%).
    Creating a backup of volume Local Disk(C:), copied (16%).
    Creating a backup of volume Local Disk(C:), copied (16%).
    Creating a backup of volume Local Disk(C:), copied (17%).
    Creating a backup of volume Local Disk(C:), copied (18%).
    Creating a backup of volume Local Disk(C:), copied (19%).
    Creating a backup of volume Local Disk(C:), copied (19%).
    Creating a backup of volume Local Disk(C:), copied (20%).
    Creating a backup of volume Local Disk(C:), copied (21%).
    Creating a backup of volume Local Disk(C:), copied (22%).
    Creating a backup of volume Local Disk(C:), copied (23%).
    Creating a backup of volume Local Disk(C:), copied (24%).
    Creating a backup of volume Local Disk(C:), copied (24%).
    Creating a backup of volume Local Disk(C:), copied (25%).
    Creating a backup of volume Local Disk(C:), copied (26%).
    Creating a backup of volume Local Disk(C:), copied (27%).
    Creating a backup of volume Local Disk(C:), copied (27%).
    Creating a backup of volume Local Disk(C:), copied (28%).
    ...
    ..
    .
    Creating a backup of volume Local Disk(C:), copied (89%).
    Creating a backup of volume Local Disk(C:), copied (89%).
    Creating a backup of volume Local Disk(C:), copied (90%).
    Creating a backup of volume Local Disk(C:), copied (90%).
    Creating a backup of volume Local Disk(C:), copied (90%).
    Creating a backup of volume Local Disk(C:), copied (91%).
    Creating a backup of volume Local Disk(C:), copied (91%).
    Creating a backup of volume Local Disk(C:), copied (92%).
    Creating a backup of volume Local Disk(C:), copied (92%).
    Creating a backup of volume Local Disk(C:), copied (93%).
    Creating a backup of volume Local Disk(C:), copied (93%).
    Creating a backup of volume Local Disk(C:), copied (94%).
    Creating a backup of volume Local Disk(C:), copied (94%).
    Creating a backup of volume Local Disk(C:), copied (95%).
    Creating a backup of volume Local Disk(C:), copied (95%).
    Creating a backup of volume Local Disk(C:), copied (96%).
    Creating a backup of volume Local Disk(C:), copied (96%).
    Creating a backup of volume Local Disk(C:), copied (97%).
    Creating a backup of volume Local Disk(C:), copied (97%).
    Creating a backup of volume Local Disk(C:), copied (98%).
    Creating a backup of volume Local Disk(C:), copied (98%).
    Creating a backup of volume Local Disk(C:), copied (99%).
    Creating a backup of volume Local Disk(C:), copied (99%).
    Creating a backup of volume Local Disk(C:), copied (99%).
    Creating a backup of volume Local Disk(C:), copied (100%).
    The backup operation successfully completed.
    Summary of the backup operation:
    ------------------

    The backup of volume System Reserved (100.00 MB) successfully completed.
    The backup of volume Local Disk(C:) successfully completed.

     

    Please try the same test and see what results you get.  psexec.exe can be downloaded at www.sysinternals.com

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 30, 2011 3:35 PM
    Moderator
  • If I use a command prompt logged in as the system administrator, I get the following response:

    There is not enough free space on the back up storage location to backup the data.

     

    If I log in using the System account, I get the following response:

    The remote shared folder does not exist.

    Friday, September 30, 2011 6:31 PM
  • Correction... I typed the path wrong in the second example. The correct results are as follows:

     

    If I use a command prompt logged in as the system administrator, I get the following response:

    There is not enough free space on the back up storage location to backup the data.

     

    Access is Denied.

     

    It appears that I have two issue. One is that I have an access problem and the second, after the access is granted I still do not have enough disk space.

    Friday, September 30, 2011 6:38 PM
  • Hi,

    OK - we need to figure out the access problem first.  Is the DPMRA.EXE process running as local system account.  It starts wbadmin.exe and it in turn starts wbengine.exe  in the context of the dpmra account.   If you start task manager, and check to make sure dpmra, wbadmin, and wbengine all start in system context after you kick off a BMR backup from dpm, then they should be able to access the DPM share same as you did when running in system account.

     

    Correct, DPM has a tendancy to under estimate BMR replica volume size, and you will need to extend it to make room, or dpm will autogrow it for you.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 30, 2011 7:04 PM
    Moderator
  • DPMRA.exe, abadmin.exe and wbengine.exe are all running under the SYSTEM account on the protected server.

     

    The share folder on the DPM server is located on the primary system volume that contains the OS which is not part of the storage pool. Is that the volume that requires the space to temporarily hold the BMR backups?

    Friday, September 30, 2011 7:13 PM
  • Hi,

    The share is pointing to the relica volume that is hosted under a mountpoint on C: - no data is stored on the actual c: drive.

     

    If you open a command prompt, and cd to c:\program files\Microsoft dpm\dpm\volume\replica\Non VSS Datasource writer

    Then DIR - all those folder should be listed as <JUNCTION> - if any say <DIR> - then the mountpoint is broken and that may be your problem.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 30, 2011 7:30 PM
    Moderator
  • Here are the results. It appears to me that everything is fine.

    E:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer>dir

     Volume in drive E is Application Data
     Volume Serial Number is BEAC-5C1B

     Directory of E:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasou
    rce Writer

    10/15/2010  10:57 AM    <DIR>          .
    10/15/2010  10:57 AM    <DIR>          ..
    10/15/2010  10:57 AM    <JUNCTION>     vol_1b490419-919a-4946-b76a-3858a6eab469
    [\??\Volume{2c8f7325-d672-11df-b91a-001422211650}\]
    10/15/2010  10:55 AM    <JUNCTION>     vol_1c945617-ef75-4798-9dd7-6a1c347bfcbe
    [\??\Volume{2c8f72d7-d672-11df-b91a-001422211650}\]
    10/15/2010  10:56 AM    <JUNCTION>     vol_77f49ce6-4fdb-484a-bb6c-380082a8aecb
    [\??\Volume{2c8f72f5-d672-11df-b91a-001422211650}\]
    10/15/2010  10:56 AM    <JUNCTION>     vol_afc0f4ae-a983-41aa-99c9-915394ef7315
    [\??\Volume{2c8f7301-d672-11df-b91a-001422211650}\]
                   0 File(s)              0 bytes
                   6 Dir(s)  30,726,492,160 bytes free

    E:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer>

    Friday, September 30, 2011 7:39 PM
  • Hi,

    I agree, I'm scratching my head.....  I assume you tried stopping protection and deleting the replica and reprotect BMR to see if that fixes it.

    Just for a test, try adding one of the protected servers machine names to the administator group on DPM server.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 30, 2011 9:32 PM
    Moderator
  • I had BMR enabled upon initially installing DPM a year or so ago. When it did not work, I disabled it and removed the replica. I am now re-enabling it again for the first time.

     

    I just tried adding the computer to the local administrators group on the DPM server. Unfortunately that group will not accept computers as members, only users, etc.

     

    I don't know if this is relivant, but I want to mention that my DPM storage pool disk is located on an iSCSI drive.

    Monday, October 3, 2011 1:57 PM
  • Hi

    The iSCSI dpm storage pool shoud not any problem.   I'm out of ideas why Windows backup is getting access denied trying to write to the BMR share on the DPM server.    You can try using process monitor http://technet.microsoft.com/en-us/sysinternals/bb896645 and see if you can spot where the access denied is coming from while attempting a BMR backup.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, October 3, 2011 7:17 PM
    Moderator
  • Hoping to resurrect this thread...

    Same issue:   The backup operation attempted at has failed to start, error code '2155348081' (The remote shared folder does not exist.).Now a WIndows 2008 AD and functional but at time of installation of DPM 2010 an errant Windows 2003 DC was running and I believe was causing AD confusion.  I found the AD problem and corrected it but am thinking the rights for DPM at install time were all wrong.  

    Your thoughts please as I am still having these issues after having no issues with DPM for over a year.  I do have DPM 2012 if that's a better long term solution. 

    Thursday, February 28, 2013 4:13 AM