none
DPM Child partition snapshot backup fails. RRS feed

  • Question

  • I've been successfully backing up our SBS2003 VM with DPM2010 for the past couple months now.  I recently got the follow error message in DPM and continue to get it every time I attempt to backup this VM.  I have 3 other VM's in this protection group and on the same Hyper-V host that are currently being backed up successfully with no problem.

     

    Type: Recovery point

    Status: Failed

    Description: DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried,

    the error may not reoccur.

     (0x800423F3))

    More information

    End time: 12/11/2010 12:22:12 PM

    Start time: 12/11/2010 12:20:17 PM

    Time elapsed: 00:01:54

    Data transferred: 0 MB

    Cluster node -

    Recovery Point Type Express Full

    Source details: \Backup Using Child Partition Snapshot\SERVER

    Protection group: Virtual Machines


    I have check the event logs on the SBS server and I see the following error message.

    Event ID 9607  Source: MSExchangeIS   Category: Exchange VSS Writer
    Description:
    Error code 0x8004010f when preparing for backup

    I have researched this error message and have done the following in an attempt to resolve this issue but they have had no effect.

    1. Restarted the Server - Retried backup and failed.
    2. Restarted the Exchange Store Service - Retried backup and it failed.
    3. Dismounted the Exchange Store - Retried backup and it failed. 
    3. Installed KB838864 VSS update package - Retried backup and it failed.

    Can you help me out?

    Thanks in advance,

    Saturday, December 11, 2010 8:37 PM

Answers

  • At this point I would suggest that you open a Microsoft support incident so that someone from our DPM support team can assist and help resolve your issue.
    Cheers, Tyler F [MSFT] - This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, January 7, 2011 2:39 PM
    Moderator

All replies

  • Hi Caleb_S

    Try running vssadmin list writers on the SBS server in an elevated command prompt. What is the state of the Exchange VSS Writer?

    Are you running out of space on the VM's (SBS) hard drive?

    I know you said the other VM's are being backed up fine but have you tried restarting the Hyper-V host?

    Monday, December 13, 2010 6:14 AM
    Moderator
  • Hi Caleb,

                  Hope every thing going fine at your end. please Run "vssadmin list writers" in an administrive comand prompt meanwhile you can do the following:

    - First Upgrade the Version of your Integration Service on your VM

    Hyper-V Management Console.

    • Login to the Hper-V server and open Hyper-V Manager
    • On the top menu, click Action – Insert Integration Services Setup Disk

    - Then Restart your VM
    - Go back to the Hyper-V Host and restart the VMMS from elevated CMD run "net stop VMMS" then "net start VMMS"

    also please make sure that there is available Disk Space on your Hyper-V Server as System Center Data Protection Manager cannot create a shadow copy if there is no space available for it to do.

    also please refer to the following thread as it talk about similar issue hope it help you
    http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/306039ec-b929-4851-a671-b5c01c04f316/


    check those Hot Fixes
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;965230
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;968447

    Regards

    Monday, December 13, 2010 11:41 AM
  • Hi, thank you for your replies.

     

    • The SBS Box has 7GB free on the C: drive and 13GB free on the D: drive.
    • I have tried restarting the Hyper-V host.  Unfortunately, this did not change anything.  
    • The state of the exchange writer is "Stable", however, the state of other writers is "Failed".  I have posted the results of the command below.
    • I will update the integration services tonight and reboot, however, I believe they are up to date.

    I have realized several other things that are relevant.
    • This started after repairing the Hyper-V host boot files.  I had to replace a motherboard on this box and after doing so it wouldn't boot.  I subsequently ran X:\Sources\Recovery\StartRep.exe from the recovery console, and realized last week that the active partition was set to the E: Drive on the Hyper-V host.  I repaired that this weekend and all is well now, however, this may have affected the backup is some way.
    • How much disk space is needed in order to create a shadow copy?.  On the Hyper-V host there is 91GB on the C: Drive and 66GB on the E: Drive where the VM's reside.
    My next step will be to apply the updates you suggested.  Do you have any other suggestions in light of this new information?

     

     

     

    Microsoft Windows [Version 5.2.3790]

    (C) Copyright 1985-2003 Microsoft Corp.

     

    C:\Documents and Settings\Administrator>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001 Microsoft Corp.

     

    Writer name: 'MSDEWriter'

       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

       Writer Instance Id: {9b606f7c-95c4-46a6-85ba-6e603adf3fce}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {9d97f622-9890-4142-95cd-2d54c578fab2}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {4fda6004-efde-4f5e-9b76-3c6fda9a68e4}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'Microsoft Exchange Writer'

       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

       Writer Instance Id: {370d9604-63b2-41c2-b31e-030ee5871e99}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'IIS Metabase Writer'

       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

       Writer Instance Id: {d7016165-eda5-44b3-81ec-1dd33cd8dba9}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'Event Log Writer'

       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

       Writer Instance Id: {8e20f230-bb67-4775-b7d8-35c06acbc1cf}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'NTDS'

       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

       Writer Instance Id: {1129ef81-6446-424e-a101-70e0ee57941f}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'Registry Writer'

       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

       Writer Instance Id: {8c7e1393-bc62-4708-bfcb-76a7d79da9ee}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Dhcp Jet Writer'

       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

       Writer Instance Id: {28b7554a-ef22-4e05-a846-8c06a075c0b1}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'WINS Jet Writer'

       Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}

       Writer Instance Id: {caf0ad07-ef98-49be-8ef1-83e4eaa99193}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'COM+ REGDB Writer'

       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

       Writer Instance Id: {c251a444-43c6-4df6-89fd-93ce95c6acde}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'WMI Writer'

       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

       Writer Instance Id: {17c8033d-508c-4092-8f9e-57904ad3a7ab}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'FRS Writer'

       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

       Writer Instance Id: {7de30769-9cde-4b02-9775-37bca81e7b85}

       State: [7] Failed

       Last error: No error


    Writer name: 'TermServLicensing'

       Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}

       Writer Instance Id: {1b1c37f6-b58b-44ff-a139-e529dd33ba6d}

       State: [7] Failed

       Last error: No error

     

     

    C:\Documents and Settings\Administrator>

     

    • Edited by Caleb44 Tuesday, December 14, 2010 8:52 PM bolded failed vss writers
    Monday, December 13, 2010 4:33 PM
  • Additionally, this is our largest VM at around 25GB C-drive VHD and a 75GB E-Drive VHD.
    Monday, December 13, 2010 4:37 PM
  • Hi Caleb_S,

    I dont know how much space is actually required to create a shadow copy but I do think what you have is not enougth. Can you free up more space? Also are you running NTBackup on this server by any chance?

    Also based on the new information you rprovided I found this post (http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/9cf42e8a-2a33-47c5-a797-269330e9ba1a/) that deals with VSS Writers Failing. The problem in this post seemed to be caused by an incorrect active volume wich you had in your case. It may or may not help but it is worth looking into. 

    Tuesday, December 14, 2010 6:20 AM
    Moderator
  • Hey BuchaTech, should I look at freeing up more space inside the VM (if so, which drive) or inside the Hyper-V Host?
    Tuesday, December 14, 2010 8:27 PM
  • Here is the result of running vssadmin list writers after installing the updates and new integration services and rebooting.  Appears that more things are failing including the exchange writer this time.  What do you think?

     

     

    Microsoft Windows [Version 5.2.3790]

    (C) Copyright 1985-2003 Microsoft Corp.

     

    C:\Documents and Settings\Administrator>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001 Microsoft Corp.

     

    Writer name: 'MSDEWriter'

       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

       Writer Instance Id: {043ba04d-c801-433b-90cd-ea05b6807f9b}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {436320bf-9be8-40e5-8404-4bde0adaeca8}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'IIS Metabase Writer'

       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

       Writer Instance Id: {7c1dbf43-5da6-4562-b7a3-4880b593349a}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {a1b1e96d-a600-4aa2-8c5c-a19d5726087b}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'COM+ REGDB Writer'

       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

       Writer Instance Id: {cf183c8e-1347-4681-b742-b279215fe80f}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Registry Writer'

       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

       Writer Instance Id: {30fc3d49-496d-4275-8be9-1cdd3130b8f6}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Event Log Writer'

       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

       Writer Instance Id: {9c0b65df-d811-4bfa-b3fa-977ed96423db}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Microsoft Exchange Writer'

       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

       Writer Instance Id: {5022a5d3-cd6c-498a-bb0c-139b41cf26dd}

       State: [7] Failed

       Last error: Retryable error

     

    Writer name: 'WMI Writer'

       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

       Writer Instance Id: {25a5fc7d-f655-4b50-b09f-71c23eaa6d91}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'NTDS'

       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

       Writer Instance Id: {280c4b4d-3a01-4b0c-b84a-34b693c8e97a}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'WINS Jet Writer'

       Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}

       Writer Instance Id: {bc9bd620-f0c6-4793-8b30-a6b9f4a64f2f}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'FRS Writer'

       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

       Writer Instance Id: {c760c3d0-7ffe-4116-8472-b02c1d11c29b}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'TermServLicensing'

       Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}

       Writer Instance Id: {a07ad8ac-cc88-4443-b547-d9db2626e323}

       State: [7] Failed

       Last error: No error

     

    Writer name: 'Dhcp Jet Writer'

       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

       Writer Instance Id: {494c7d9e-3710-4267-9f6d-962594dd4c97}

       State: [7] Failed

       Last error: No error

     

     

    C:\Documents and Settings\Administrator>

     

    • Edited by Caleb44 Tuesday, December 14, 2010 8:50 PM bolded failed vss writers
    Tuesday, December 14, 2010 8:48 PM
  • More info layed out so that it may be easier to read.  I can still perform exchange backups successfully.  weird.

    Stable Before Updates/Restart:
    1. MSDEWriter
    2. Microsoft Exchange Writer
    3. Event Log Writer
    4. Registry Writer
    5. Dhcp Jet Writer
    6. COM+ REGDB Writer

    Failed Before Updates/Restart:
    1. System Writer
    2. SqlServerWriter
    3. IIS Metabase Writer
    4. NTDS
    5. WINS Jet Writer
    6. WMI Writer
    7. FRS Writer
    8. TermServLicensing


    Stable After Updates/Restart:
    1. MSDEWriter
    2. COM+ REGDB Writer
    3. Registry Writer
    4. Event Log Writer

    Failed After Updates/Restart:
    1. System Writer
    2. IIS Metabase Writer
    3. SqlServerWriter
    4. Microsoft Exchange Writer
    5. WMI Writer
    6. NTDS
    7. WINS Jet Writer
    8. FRS Writer
    9. TermServLicensing
    10. Dhcp Jet Writer


    • Edited by Caleb44 Tuesday, December 14, 2010 9:05 PM underlined changes to vss writers
    Tuesday, December 14, 2010 9:04 PM
  • Tuesday, December 14, 2010 9:56 PM
    Moderator
  • I read over all the posts.  I checked several things that were posted, however, everything seemed to be in order.
    Wednesday, December 15, 2010 1:14 AM
  • Which drive within the VM should be expanded?  The C-Dirve or the E-Drive?
    Wednesday, December 15, 2010 4:23 PM
  • Hi Caleb_S,

     

    The C Drive.

    Wednesday, December 15, 2010 4:25 PM
    Moderator
  • Can I extend a system volume?

    I read the following article that says I can't.  Maybe this means that it has to be done offline?

    http://support.microsoft.com/kb/325590

    Wednesday, December 15, 2010 5:15 PM
  • You most likely need more free space within the virtual machine itself and given the fact that this is a VM KB325590 is not relevant. You simply need to shut down the VM, go into Hyper-V Manager and launch the Edit Virtual Hard Disk Wizard, point it to the VHD file, and finally tell it by how much you'd like to increase the size of the VHD.
    Cheers, Tyler F [MSFT] - This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, December 17, 2010 2:10 PM
    Moderator
  • I haven't had the chance to do this yet.  Additionally, whether it's a VM or not, the volume will still need to be extended within the OS once the VHD will be extended.  Please correct me if I'm wrong.
    Monday, December 20, 2010 4:11 PM
  • Hi Caleb_S,

    You are correct the volume in the VM will still need to be expanded through Windows disk management. From my understanding you also were correct in your previous post that the system volume cannot be extended. Can you clean up some space on that drive? You can try a restore to another VM with a bigger drive using System State. You could also try another imaging tool to take an image of this server and then apply that image to another VM with a bigger hard drive.

    Monday, December 20, 2010 4:47 PM
    Moderator
  • I'm not even sure that expanding this space will resolve the issue.   The c-Drive has dipped down to 2GB a while back and backups still ran fine under that scenario.  That was very low and at that time I cleaned things up and freed up to 7GB.  The back up stopped functioning when the Host OS system volume was changed.  After resolving this I have never been able to get it to backup again.  I'm thinking that maybe this has something to do with a volume on the host OS.  Maybe something got changed their.  I'm not sure.  Any thoughts?
    Monday, December 20, 2010 4:55 PM
  • I should also note, I can do a physical backup of the host from within the VM just fine using DPM.  I have done this in the meantime so I can stay protected while this backup is not working.
    Monday, December 20, 2010 5:02 PM
  • Hi Caleb_S,

    There is a strong chance space is your issue here but that also is why I directed you to this post  http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/9cf42e8a-2a33-47c5-a797-269330e9ba1a/ might help you. They describe a similar issue of the Active Volume being set incorrectly. In one of your previous responses it sounded like you may have had the same issue that could be causing the problems you are having with VSS.

     

    Monday, December 20, 2010 5:12 PM
    Moderator
  • Great Idea until you can resolve your issue! That is one of the nice features of DPM; being able to back up the entire VM or from within the VM itself.

    Monday, December 20, 2010 5:16 PM
    Moderator
  • I just found this article which has some hotfixes listed.  The article is helpful because it describes the proper way to install these hotfixes.  These both relate to DPM and VSS on the host and also include the error message I was receiving.  I'm optimistic that these may help.

    I'll let you know once I've had the opportunity to install them.

     

    http://blogs.technet.com/b/mattmcspirit/archive/2010/03/26/dpm-2010-rc-and-hyper-v-r2-vm-s-on-csv-s-order-of-patches.aspx

     

    Hotfixes:

    http://support.microsoft.com/kb/975921

    http://support.microsoft.com/kb/975354

    Thursday, December 23, 2010 9:47 PM
  • I installed both updates and the backup still failed with the same error.  I'm out of ideas.  Does anyone else have any more?
    Wednesday, December 29, 2010 3:30 AM
  • At this point I would suggest that you open a Microsoft support incident so that someone from our DPM support team can assist and help resolve your issue.
    Cheers, Tyler F [MSFT] - This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, January 7, 2011 2:39 PM
    Moderator
  • Just as a side note.  I never did get this working and I did recently extend the OS volume from 25GB to 40GB.  oh well.
    Thursday, March 28, 2013 4:41 AM