Hyper-V System state backup fails - DPM 2010 RRS feed

  • Question

  • Hi all,

    I asked the following question in the DPM forum, but no answer. Maybe this is the right place to ask this question.

    We have two hyper-v hosts in a failover cluster, both w2k8r2 sp1.
    We use DPM 2010 to create system state backup on both servers.
    Everything worked fine, but two days ago we Live Migrated all vm's to host1 and turned the
    host2 off to do a memory upgrade. So far so good.

    After we Live Migrated all vm's to host2 and turned off host1 to do the memory upgrade here too.
    Today I realized that on host1 the system state backup fails with the following error
    message(there are no other error messages):
    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          2012.05.17. 13:16:12
    Event ID:      521
    Task Category: None
    Level:         Error
    User:          SYSTEM
    Computer:      HOST01.production.local
    The backup operation that started at '?2012?-?05?-?17T11:14:47.562000000Z' has failed

    because the Volume Shadow Copy Service operation to create a shadow copy of the volumes

    being backed up failed with following error code '2155348129'. Please review the event

    details for a solution, and then rerun the backup operation once the issue is resolved.
    Event Xml:
    <Event xmlns="">
        <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}"

        <TimeCreated SystemTime="2012-05-17T11:16:12.551149900Z" />
        <Correlation />
        <Execution ProcessID="3448" ThreadID="5344" />
        <Security UserID="S-1-5-18" />
        <Data Name="BackupTime">2012-05-17T11:14:47.562000000Z</Data>
        <Data Name="ErrorCode">2155348129</Data>
        <Data Name="ErrorMessage">%%2155348129</Data>

    We can backup the host2 fine, but on host1 the backup fails.
    What I noticed is I cannot find WindowsImageBackup folder on host1, if I look at host2,

    there is a WindowsImageBackup folder on D:\ (data) drive.

    What i tried:
    - checked the free space, there are enough on every volume

    - remove windows backup feature from host1, rebooted and installed it back.

    - i checked the PSDataSourceConfig.xml and I saw that there is a row "<FilesToProtect>Y:\WindowsImageBackup</FilesToProtect>", i modified this to "<FilesToProtect>D:\WindowsImageBackup</FilesToProtect>" (I don't know why it was Y: but I cannot see WindowsImageBackup folder there)

    - I created a registry key under wbservice (SystemState) and created a DWORD AllowSSBToAnyVolume, and set it to 1. (on host2 this key already existed, but on host1 it wasn't there). After I rebooted a server.

    - ran vssadmin list providers, and every provider say "No Error".

    - rebooted DPM

    - stopped the system state protection of host1 and added back again with modifying the protection group

    - tried to do consistency check a lot of times, but no luck.

    So I don't know how to solve this now.
    One more thing, if I try to backup the hyper-v initial store, it is able to back that up.

    I also read about that if it's an OEM Os that I have to check if C:\ is the active partition. I saw that the active partition is the RECOVERY partition, but on host 2 that's the active partition too and that works.

    So please if you have any suggestions, please tell me.

    best regards,

    Tuesday, May 29, 2012 9:44 AM


  • Hi!

    Please note that I'm not an DPM specialist.

    I found an article mentioning the error code 2155348129 here:

    You can try to delete eventually existing shadows that might not have been properly cleansed and might interfere with the VSS writer, using DISKSHADOW from an elevated prompt rather than vssadmin. In the DISKSHADOW CLI type DELETE SHADOWS ALL to remove existing shadows.

    Also make sure that the DPM system state folder is empty, delete any files created locally from earlier backup attempts. Check the properties of the protected group containing the system state in the DPM administration console, and make sure that enough space has been specified to be used locally on the protected server for preparing DPM backups by WSB.

    These are the additional steps I can provide for your continued troubleshooting. If you're not able to resolve the error you can try posting in the Data Protection Manager - Hyper-V and CSV Clusters forum if you haven't already, as there are lots of qualified DPM specialists posting there:

    Saturday, June 2, 2012 12:54 PM