none
DPM is out of disk space for the replica RRS feed

  • Question

  • Trying to make a bare metal backup of a phyiscal server running 2008 R2 SP1 . I've checked im not out of space. I've uninstalled and reinstalled the agent, I've manually tried to make the disk allocation larger same error.

     DPM is out of disk space for the replica. (ID 58 Details: Internal error code: 0x809909FF)

    This is in the event log on the Client machine

    The backup operation attempted  has failed to start, error code '2155348040' (There is not enough free space on the backup storage location to back up the data.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    I have several other machines doing bare metal backups they are virtual but I can't see why that would be any different. They have no problems doing this. I have seen hacks on the internet editing xml files to get this to work changing allcritical to "C:". I'd like an actual fix for this please?

    Tuesday, February 21, 2012 9:32 PM

Answers

  • Hi,

    OK, so the solution should be to just modify the disk allocation for the BMR datasource so that the replica volume is ~110GB - after that, run a consistemcy check and see if you get a successful BMR backup.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Mike_Kubi Friday, February 24, 2012 2:30 PM
    • Unmarked as answer by Mike_Kubi Friday, February 24, 2012 2:50 PM
    • Marked as answer by Yegor StartsevModerator Thursday, October 18, 2012 11:08 AM
    Friday, February 24, 2012 12:53 AM
    Moderator

All replies

  • hi,

    could you try to increase the replica volume size manually on your dpm server?

    Tuesday, February 21, 2012 10:55 PM
  • Hi,

    Try these steps to get the absolute space required for BMR initial replica size.

    To test BMR backup outside of DPM, try this command:

    1) Set up a network share on a remote machine \\server\bmrshare

    2) From an administrative command prompt on the PS, type:

                  wbadmin.exe start backup -allcritical -backuptarget:\\server\bmrshare


    This should show you the list of volumes included in the BMR backup and ask "Do you want to start the backup operation?. - Type Y to continue..

    3) After windows backup completes, Check the disk space required for the BMR by looking at the properties of the WindowsImageBackup folder under the \\server\bmrshare then when you make the Protection Group for BMR on the DPM server be sure you allocate enought disk space for the replica volume to hold the BMR backup.  If the replica is already created, modify the disk allocation and increase the size to accomodate the size of the BMT backup based on the above test.

    NOTE: BMR backup does NOT require any disk space on the PS, DPM writes directly to the DPM Servers replica volume.



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, February 22, 2012 2:40 AM
    Moderator
  • hi,

    could you try to increase the replica volume size manually on your dpm server?


    Hi thanks, in my original post I mentioned that I've tried that already.
    Wednesday, February 22, 2012 3:40 PM
  • Ok did as instructed it didn't list the volumes when I hit Y to the question to back up or not . Here is what it says

    wbadmin start backup -allcritical -backuptarget:\\kdvh2\bmrshare
    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 Local Disk(C:) to \\kdvh2\bmrshare.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

    The backup operation to \\kdvh2\bmrshare is starting.
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    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 (0%).
    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 (0%).
    Creating a backup of volume Local Disk(C:), copied (0%).

    I navigated to the folder the backup is occuring and I see the VHD is 104 gigs . Way beyond what DPM set as the inital disk size?

    • Proposed as answer by drensta Tuesday, May 6, 2014 1:57 PM
    Wednesday, February 22, 2012 3:46 PM
  • Ok the backup needs 104 gigs, DPM is reserving 216 Gigs . Not sure why this wouldn't work ? What am I doing wrong here ?

    Wednesday, February 22, 2012 3:55 PM
  • Hi,

    If DPM has allocated the space correctly, but Windows backup fails due to space issue, then you need to work with the Windows support group to troubleshoot.  The DPM Replica is nothing more than a network share for Windows backup to write to, just like your test backup you performed earlier.   The only difference is permissions are locked down so the PS machine account can write to it.

    Replica volume has only these permissions

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

    You can list the share on the dpm server using net view \\dpmserver, then you can try backing up to the replica directly using the manual backup method by following these steps on the PS.

    1)      Download psexec.exe from www.sysinternals.com

    2)      Run PSEXEC -s cmd.exe   (this will switch window to system context)

    3)      Afterwards - type WHOAMI it should return:

                      nt authority\system

    4)      Run wbadmin and backup to \\dpmserver\replica-share


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, February 22, 2012 7:23 PM
    Moderator
  • Good idea Mike! I'll give that a try.
    Wednesday, February 22, 2012 7:44 PM
  • Mike quick question. How can I determine which share my particular server is using to backup to? Here is what I get when I try to do a DIR on the folder as system

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

    C:\Windows\system32>dir \\kdnap-util1\0ae3c77eaab54ea09b0724737a125f48
    Access is denied.

    C:\Windows\system32>dir \\kdnap-util1\12068c1992634c92addf44bfbee5cada
    Access is denied.

    I was just trying to poke around to browse the folder to see which one to back it up to . But with the access denied error this isn't helpful :)

    Here is my list of shares

    C:\Windows\system32>net view \\kdnap-util1
    Shared resources at \\kdnap-util1


    I also tried doing a DIR from a server that is backing up correctly on any of those shares listed above after running psexec and I get access denied from them as well so I guess thats normal

    Share

    name                        Type  Used as  Comment


    -------------------------------------------------------------------------------
    0ae3c77eaab54ea09b0724737a125f48  Disk           0ae3c77eaab54ea09b0724737a125f4
    8
    12068c1992634c92addf44bfbee5cada  Disk           12068c1992634c92addf44bfbee5cad
    a
    32d87ea3f0ea4570bd1ae215c818686d  Disk           32d87ea3f0ea4570bd1ae215c818686
    d
    3429bef9926347babbf20bbb258fdec0  Disk           3429bef9926347babbf20bbb258fdec
    0
    5c9c98bbc69c4f0ab75df48e89f52fc3  Disk           5c9c98bbc69c4f0ab75df48e89f52fc
    3
    600460aa29bb4f198d0d0fb6b1636068  Disk           600460aa29bb4f198d0d0fb6b163606
    8
    62abc840b38444abaa9d8dc9bd43b852  Disk           62abc840b38444abaa9d8dc9bd43b85
    2
    6833cf7dec3e4f19a3bf7961d53c5ced  Disk           6833cf7dec3e4f19a3bf7961d53c5ce
    d
    68437b942573463b9437a15056bccf7c  Disk           68437b942573463b9437a15056bccf7
    c
    805320dcb886401fa3dc6a8213b3deec  Disk           805320dcb886401fa3dc6a8213b3dee
    c
    8404f7468dea47ce9e92a99536ebe13d  Disk           8404f7468dea47ce9e92a99536ebe13
    d
    8bcbc4deae44458da77fbe59661f60fb  Disk           8bcbc4deae44458da77fbe59661f60f
    b
    9bc5182a9d6b43478b7c09062ee1c9b0  Disk           9bc5182a9d6b43478b7c09062ee1c9b
    0
    b588fc67397e4a5a81a15bb5b52dbe31  Disk           b588fc67397e4a5a81a15bb5b52dbe3
    1
    Backups                           Disk

    bf941a02f6e847a095b03d01963b8df1  Disk           bf941a02f6e847a095b03d01963b8df
    1
    bfc06209ce514b939098a9fd701e05d7  Disk           bfc06209ce514b939098a9fd701e05d
    7
    BLAZELG                           Disk

    d35de342510248a0a34dac84ecd55d08  Disk           d35de342510248a0a34dac84ecd55d0
    8
    df1658496f364923b25f615625254195  Disk           df1658496f364923b25f61562525419
    5
    dfc6d6061f314fabbed0fb144c18df7c  Disk           dfc6d6061f314fabbed0fb144c18df7
    c
    e8fcdd5155c940bb8ecddd0e7a99be7b  Disk           e8fcdd5155c940bb8ecddd0e7a99be7
    b
    ee23ec6bc709410a9cfce4759c935f8f  Disk           ee23ec6bc709410a9cfce4759c935f8
    f
    f0f1272aeab7417d82a6473b3f8b3a91  Disk           f0f1272aeab7417d82a6473b3f8b3a9
    1
    library.old                       Disk

    The command completed successfully.

    *******

    OK figured out which share it is by viewing the sharename in the shared folders snap-in (mmc) it listed my server name which access on the share. its "600460aa29bb4f198d0d0fb6b1636068"


    • Edited by Mike_Kubi Thursday, February 23, 2012 4:06 PM
    Thursday, February 23, 2012 3:57 PM
  • Here is what i get when doing a manual backup . WTF over :)

    On the DPM server I checked the volume it made and its 50 gigs .  Arfg.


    C:\pstools>wbadmin start backup -allcritical -backuptarget:\\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068
    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 Local Disk(C:) to \\kdnap-util1\600460aa29bb4f198d0d0fb
    6b1636068.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

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

    C:\pstools>


    • Edited by Mike_Kubi Thursday, February 23, 2012 4:19 PM
    Thursday, February 23, 2012 4:10 PM
  • I believe you have found the root cause of the space error.   You should not get access denied while trying to view that BMR share from the protected server.

    <snip from my test server>
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


    C:\>psexec.exe -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>net view \\mjlc-dpm01
    Shared resources at \\mjlc-dpm01

     

    Share name                        Type  Used as  Comment


    -------------------------------------------------------------------------------
    a6159995754d48358fe39b4c46abbae4  Disk           a6159995754d48358fe39b4c46abbae4

    The command completed successfully.


    C:\Windows\system32>dir \\mjlc-dpm01\a6159995754d48358fe39b4c46abbae4
     Volume in drive \\mjlc-dpm01\a6159995754d48358fe39b4c46abbae4 is DPM-vol_2af19d17-92a2-4f29-
     Volume Serial Number is 0401-A69A

     Directory of \\mjlc-dpm01\a6159995754d48358fe39b4c46abbae4

    02/23/2012  11:10 AM    <DIR>          .
    02/23/2012  11:10 AM    <DIR>          ..
    08/11/2011  05:03 PM    <DIR>          WindowsImageBackup
                   0 File(s)              0 bytes
                   3 Dir(s)  11,922,640,896 bytes free

    C:\Windows\system32>

    >snip<

    Please check the NTFS permissions on the root of the replica volume.  You can use mountvol.exe to get the volume guid based on the mountpoint path, then run icacls.

    ON DPM SERVER
    =============
    C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer>icacls \\?\Volume{fd0e3a41-be3a-11e0-9d89-00155d410
    \\?\Volume{fd0e3a41-be3a-11e0-9d89-00155d410c0c}\ BUILTIN\Administrators:(F)
                                                                                      NT AUTHORITY\SYSTEM:(F)
    Successfully processed 1 Files: failed processing 0 Files

    Please investigate permissions issue on the DPM Server.  Once the above works for you, then BMR backups will succeed.  Let me know what you find.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 23, 2012 5:40 PM
    Moderator
  • Hey Mike if you read a little deeper in my post (sorry it was so long) It was access denied because I was connecting to a share that didn't belong to that particular server. When I did connect to the right share after discovering which one it was I was able to read it just fine by mapping a drive to it. Still getting the out of space message however see below.

    :\pstools>wbadmin start backup -allcritical -backuptarget:\\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068
    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 Local Disk(C:) to \\kdnap-util1\600460aa29bb4f198d0d0fb
    6b1636068.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

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

    C:\pstools>

    Thursday, February 23, 2012 6:59 PM
  • Hi,

    Sorry I missed that.  So if you do a DIR \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068 - how much free space does it return ?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 23, 2012 7:03 PM
    Moderator
  • 53 Gigs
    Thursday, February 23, 2012 7:11 PM
  • Hi Actually, I should have asked you to do a DIR /S /A  \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068 to see how much was used and free.  We know you need a >104GB based on your manual BMR test you did to another share.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Thursday, February 23, 2012 7:21 PM
    Moderator
  • Shouldn't DPM set the volume automatically? This looks like a problem see below

    C:\pstools>dir /A \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068
     Volume in drive \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068 is DPM-vol_4e499
    231-bd2c-4f51- Volume Serial Number is 28AB-8D8A

     Directory of \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068

    02/23/2012

      11:10 AM    <DIR>          .
    02/23/2012  11:10 AM    <DIR>          ..
                   0 File(s)              0 bytes
                   2 Dir(s)  53,591,359,488 bytes free

    C:\pstools>

    Thursday, February 23, 2012 7:24 PM
  • I actually modified my post after you already read it.  I need the output of this to see used and free space. sorry.

    DIR /S /A  \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068 

    DPM does not know the size of a BMR backup, it varies widely from system to system based on roles instaled, and 9 out of 10 times DPM allocates too little space. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 23, 2012 7:30 PM
    Moderator
  • Hi,

    OK, so the solution should be to just modify the disk allocation for the BMR datasource so that the replica volume is ~110GB - after that, run a consistemcy check and see if you get a successful BMR backup.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Mike_Kubi Friday, February 24, 2012 2:30 PM
    • Unmarked as answer by Mike_Kubi Friday, February 24, 2012 2:50 PM
    • Marked as answer by Yegor StartsevModerator Thursday, October 18, 2012 11:08 AM
    Friday, February 24, 2012 12:53 AM
    Moderator
  • Ok I'll do that, and let you know. I guess my question is why isn't DPM doing this for me?
    Friday, February 24, 2012 2:11 PM
  • Hi,

    <snip>
    why isn't DPM doing this for me?
    >snip<

    Windows backup was never attempting to write the the replica, it was failing while doing it's own required space calculations.  DPM will autogrow a volume only when it receives an alert that the disk space is running low while writing to it.

    Anyhow, thanks for following directions, it makes it easier to help and I'm glad that it's resolved.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, February 24, 2012 2:52 PM
    Moderator
  • Hi Mike, seems that didn't fix it or maybe it did and now we have another problem :(

     DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 518, WSB Error Code:  0x80780017). (ID 30229 Details: Internal error code: 0x809909FB)

    After seeing this I tried to manually run a backup again got the following below:

    C:\pstools>wbadmin start backup -allcritical -backuptarget:\\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068
    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 Local Disk(C:) to \\kdnap-util1\600460aa29bb4f198d0d0fb
    6b1636068.
    Do you want to start the backup operation?
    [Y] Yes [N] No y

    Another backup or recovery operation is in progress.

    C:\pstools>dir /S /A \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068
     Volume in drive \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068 is DPM-vol_655b8
    ccc-25b2-4b77-
     Volume Serial Number is 56AE-E8D9

     Directory of \\kdnap-util1\600460aa29bb4f198d0d0fb6b1636068


    02/24/2012

      09:53 AM    <DIR>          .
    02/24/2012  09:53 AM    <DIR>          ..
                   0 File(s)              0 bytes

         Total Files Listed:
                   0 File(s)              0 bytes
                   2 Dir(s)  128,750,993,408 bytes free

    C:\pstools>

    • Edited by Mike_Kubi Friday, February 24, 2012 2:56 PM
    Friday, February 24, 2012 2:55 PM
  • Hi,

    <snip>
    why isn't DPM doing this for me?
    >snip<

    Windows backup was never attempting to write the the replica, it was failing while doing it's own required space calculations.  DPM will autogrow a volume only when it receives an alert that the disk space is running low while writing to it.

    Anyhow, thanks for following directions, it makes it easier to help and I'm glad that it's resolved.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Then I guess I should rephrase my question :) Why isn't DPM calculating the correct replica size BEFORE doing the backup when you're configuring options to do backups ?
    Friday, February 24, 2012 2:57 PM
  • ok after hunting around I found with 'wbadmin get status' there was a job that was holding up the operatation since  yesterday. I guess with all the experimenting it caused one job to hang. I canceled it and now DPM is doing a verification. I believe this time for real its going to work :)
    Friday, February 24, 2012 4:32 PM
  • This worked perfectly.

    THANKS

    Friday, January 31, 2014 6:32 PM
  • This solved it for me too - increased the replica size and the backup worked straight away.  Couldn't figure this out before!

    Thanks

    Wednesday, February 26, 2014 5:30 PM