none
DPM 2010 - 1 Hyper-V VM is protected, the other 2 not RRS feed

  • Question

  • On a Hyper-V host, 1 of the VM's is protected, but the other 2 not. They give replica inconsistent.

    When I do a consistency check, after a couple of seconds, it gives me:

    Affected area: \Backup Using Child Partition Snapshot\Bucksrv32 - 2003 - ISA 2006
    Occurred since: 29-6-2010 15:25:08
    Description: The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\Bucksrv32 - 2003 - ISA 2006 on bucksrv00.bciglobal.nl 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.

    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
     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
    Recommended action: Check the Application Event Log on bucksrv00.bciglobal.nl for the cause of the failure. Fix the cause and retry the operation.
    For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.
     Synchronize with consistency check.
     Run a synchronization job with consistency check...
    Resolution: To dismiss the alert, click below
     Inactivate alert

    The VM is frontend for Exchange 2003, running Windows Server 2003.

    Application Log nor System Log on the Hyper-V host nor on the DPM Server show any errors that could be related.

    Anyone a clue?

    • Moved by Parag Agrawal Tuesday, August 17, 2010 10:20 AM Hyper - V related issue (From:Data Protection Manager)
    Tuesday, June 29, 2010 1:31 PM

Answers

  • [shot in the dark mode]

    did you install the integration tools?

    [\shot in the dark mode]

    Tuesday, June 29, 2010 3:44 PM
  • A good test would be to take a systemstate backup inside the guest o.s to see if that works - this will check most writers - if that fails, troubleshoot the vss issue inside the VM.

     

    If you can live with "saved state backups" until you figure out why VSS is failing, you can uncheck the Integration
    Services "Backup (volume snapshot)"  component for that guest and DPM will perform saved state backups.  You can put that VM in a seperate PG and choose to back it up off hours so it doesn't effect production.

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, June 29, 2010 4:43 PM
    Moderator

All replies

  • Hey Robert,

    Check out following hotfixes if they apply:

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

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

    http://support.microsoft.com/?kbid=981948

    If they don't, give us the output of vssadmin list writers on both the host and the guest

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Tuesday, June 29, 2010 1:59 PM
    Moderator
  • Hi Mike,

    Hotfixes were not applicable.

    On the guest, there apparently are no vss writers. Guest is Windows Server 2003 X86, with all regular updates. vssadmin list writers does not show anything other than the info about the program.

    On the host, output is this:

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {94b3a83a-489c-4d14-89a8-9588d8d1eaee}
       State: [8] Failed
       Last error: Retryable error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {62f42cfa-60fb-4a76-acf4-09497263d984}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {f5632077-0de7-4305-8c9f-f8d0f49b2c4d}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {8356bea6-ce04-4587-8ae0-232fc8b80e32}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {7c7cea0d-180a-4887-a6c1-155fb9c092d0}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {56591acf-0134-4306-8eb5-2923addce9b1}
       State: [1] Stable
       Last error: No error

    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {028ead75-776e-4d3c-b0e5-97dcd73b68eb}
       State: [1] Stable
       Last error: No error

    Writer name: 'WINS Jet Writer'
       Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
       Writer Instance Id: {59303649-7532-48e1-aacd-eba2b0ff1c95}
       State: [1] Stable
       Last error: No error

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {2ce9fef0-7606-4767-9308-3daa9fbd468f}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {65a9b335-85e6-4413-8ca4-11ed75e8c751}
       State: [1] Stable
       Last error: No error

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {ee2b1061-63bd-4c4c-beee-5350fcb8b753}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {b93d27e6-0d94-48d5-b0d9-d5d972e2213e}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {d835ee9e-88ea-4fb7-8a0a-c7a7fe4f4a04}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {8c91865f-7dd2-40c0-b2bb-663fd06332f0}
       State: [1] Stable
       Last error: No error

    Tuesday, June 29, 2010 2:26 PM
  • hi Robert,

    any vss errors in the evetlog on the VM?

    groeten,

    Alex

    Tuesday, June 29, 2010 2:27 PM
  • Hi,

     

    You will need to look inside the guest for any VSS errors in the application event log.  For the server running ISA 2006 - manually stop ISA services then see if you can take a backup.  We have seen ISA service cause problems with online backups.


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, June 29, 2010 2:35 PM
    Moderator
  • ISA is not on the box anymore.

    Guest application log came up with this:

    Volume Shadow Copy Service error: internal inconsistency. Event 12032, Source VSS.

    Tuesday, June 29, 2010 2:56 PM
  • [shot in the dark mode]

    did you install the integration tools?

    [\shot in the dark mode]

    Tuesday, June 29, 2010 3:44 PM
  • A good test would be to take a systemstate backup inside the guest o.s to see if that works - this will check most writers - if that fails, troubleshoot the vss issue inside the VM.

     

    If you can live with "saved state backups" until you figure out why VSS is failing, you can uncheck the Integration
    Services "Backup (volume snapshot)"  component for that guest and DPM will perform saved state backups.  You can put that VM in a seperate PG and choose to back it up off hours so it doesn't effect production.

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, June 29, 2010 4:43 PM
    Moderator
  • You're good at shooting in the dark. Integration tools were outdated. It's now synchronising.

    Can we use you next friday in the Dutch national team ? :-)

    Edit: and number 2 is backupping just fine as well!

    Thank you.

    Tuesday, June 29, 2010 6:38 PM
  • You're good at shooting in the dark. Integration tools were outdated. It's now synchronising.

    Can we use you next friday in the Dutch national team ? :-)

    Edit: and number 2 is backupping just fine as well!

    Thank you.


    good to hear, best not to use me if we want to advance to the next round :)
    Wednesday, June 30, 2010 7:22 AM
  • Hi Alex,

    I'm having the same problem with DPM 2010 backing up HyperV.  Can you tell me what you mean by "Intergration tools"?

    thanks

    Friday, August 13, 2010 3:10 PM
  • Those are the integration components you install on a Windows machine to have it running properly under Hyper-V. You startup the Hyper-V manager, connect to a VM, then on the action menu, click 'Insert Integration Services Disk'.

    Kind regards,

    Robert Bleumer

    Monday, August 23, 2010 5:21 PM