none
Replica is inconsistent with Hyper-V VM backup in DPM2010 RRS feed

  • Question

  • Hi,  

    Backing up every virtual machine using clild partition backup on a Windows server 2008 R2 Hyper-V cluster failed with error “Replica is inconsistent”.

    When I perform a consistency check the same error appears again.

    The product is DPM 2010 with cumulative update KB2250444 installed on Windows Server 2008 R2

    The Hyper-V VM’s are Windows server 2008 R2

    Details of this error are:

    Affected area:   \Backup Using Child Partition Snapshot\AD02

    Description:        The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\AD02 on AD02.vcl01.domain.com is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

    Failure occurred while adding one or more of the volumes involved in backup operation to snapshot set. Please check the event log on AD02.vcl01.domain.com to troubleshoot the issue. (ID 30290 Details: Internal error code: 0x80990A00)

                    More information

    Recommended action:  Check recent records from the VolSnap source in the Application Event Log to find out why the problem occurred.

                    Synchronize with consistency check.

                    Run a synchronization job with consistency check...

     

    On every Hyper-V host in the cluster the windows server Backup and command line tools are installed.

    The data size of a specific machine (AD02) is 11.21 GB

    The Replica volume 16.58 GB

    The Recovery point Volume is 9.31 GB

    No VSS or backup errors are shown on the Hyper-v hosts or in the VM AD02

    Bare metal backup of fysical machine is successful.

    I like to know what's causing these inconsistent backup's?

    • Moved by MarcReynolds Tuesday, January 18, 2011 1:11 PM (From:Data Protection Manager)
    Tuesday, January 18, 2011 11:32 AM

Answers

  • I added more space to the snapshot volume and now it's working. summary: Configure hardware VSS provider Make sure there is enough space for Snapshots on the snapshot volume.
    Monday, January 24, 2011 4:06 PM

All replies

  • Hello,

    Are you using a Hardware VSS writer?  This error I have seen when there is a login failure for the Hardware VSS writer to the SAN box.

    Just my 2 cents,

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Tuesday, January 18, 2011 1:29 PM
    Moderator
  • Ok,

    Could you do the following:

    - Run VSSADMIN LIST WRITERS on the guest server (AD02) and on the host that holds the VM and/or the CSV

    - Check the eventlog on the guest (AD02) to see where the error is

    Post the output what you have found here

    Thanks

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Tuesday, January 18, 2011 3:04 PM
    Moderator
  • These are the writers on the AD02 (guest):

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {1d89855b-7157-4c60-a8b2-88ac09cb6014}
       State: [1] Stable
       Last error: No error

    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {8a1a4b62-d43b-4047-be73-067a82f957e3}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {e2548f85-997c-45b6-9e9f-acc9a4138d24}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {c6ab5e03-52e9-4d96-afb8-e1cd0a682fb7}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {6a6e1a09-a577-4480-b342-86cf92bdcfab}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {c4da5c11-cb54-4335-b703-9ab9cb991d9b}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {145cd0da-d9c6-48a3-9c53-11533e6df996}
       State: [1] Stable
       Last error: No error

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {b20d453d-3a0c-46ab-96f9-911870bb43c9}
       State: [1] Stable
       Last error: No error

    These are the writers on the Hyper-v server that host the AD02:

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {9a630ae5-8373-4c0b-9de5-72bcc82f729d}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {6f0101f3-0f57-462f-94de-92fdc4dc76ca}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {b7097bc9-c529-469b-aa68-3909e6b57f7b}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {6c4448d1-fbab-477e-a9e9-e626e350b56a}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {9174c8fe-6894-4705-9e66-5bd85cd0e004}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {b9f5bd9b-fb26-4d86-8ca7-da5841c1e1d8}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {5f7712ba-6cb5-4b81-a15b-b5c01146533e}
       State: [1] Stable
       Last error: No error

    Writer name: 'Cluster Database'
       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
       Writer Instance Id: {e08213f4-51b1-41ed-be06-ecae00cc8cfa}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {d5002cfe-4bb7-4070-94c7-b44534c2c817}
       State: [1] Stable
       Last error: No error

    I checked the application log on Hyper-V host and guest but the only related event to VSS is informational: The VSS service is shutting down due to idle timeout.

    In the system log: The Microsoft Software Shadow Copy Provider service entered the running state.

    Tuesday, January 18, 2011 4:04 PM
  • Hello Mike,

     I use a Dell hardware VSS writer.

    I wonder if the problem is caused by the fact that the DPM server has no ISCSI connection to the Equalogic San with the VSS snapshot volume and therefore cannot access the snapshot volume.

    It's difficult to find good guidelines how to configure DPM with Hyper-V cluster farm connected to a SAN.

    Monday, January 24, 2011 11:44 AM
  • I configured the Dell VSS writer with an username and password and now have a different error:

    Affected area: \Backup Using Child Partition Snapshot\AD02
    Occurred since: 1/24/2011 4:13:09 PM
    Description: The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\AD02 on SCVMM AD02 Resources.vcl01.domain.com is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

    The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The shadow copy provider had an error. Check the System and Application event logs for more information.
     (0x80042306))
     

    On the Hyper-V host i get this error:

    Snapshot creation failed with error 0x80004005 (Volume hpvboot: Not enough snapshot reserve to create this snapshot) for target \\.\PHYSICALDRIVE5 (0-8a0906-b11e83606-525b19224ef4d271).

    Monday, January 24, 2011 3:22 PM
  • I added more space to the snapshot volume and now it's working. summary: Configure hardware VSS provider Make sure there is enough space for Snapshots on the snapshot volume.
    Monday, January 24, 2011 4:06 PM