Hi guys, I'm working on the usual DPM errors this week (replica is inconsistent). I got one server, which is a hyper-v server, which hosts about 20 VM's. In DPM I get this error:
The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\vm child on vm host.domain.local 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)
On the child VM, which is running 2008r2, I get these errors:
Log Name: Application
Source: VSS
Date: 8/21/2013 1:52:07 PM
Event ID: 12344
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: child vm.domain.local
Description:
Volume Shadow Copy Error: An error 0x00000000c000014d was encountered while Registry Writer was preparing the registry for a shadow copy. Check the Application and System event logs for any related errors.
Operation:
OnFreeze event
Freeze Event
Context:
Execution Context: Registry Writer
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {61189d5b-362b-40e3-ba48-319c74d36b29}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12344</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-21T11:52:07.000000000Z" />
<EventRecordID>1435837</EventRecordID>
<Channel>Application</Channel>
<Computer>child vm.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>0x00000000c000014d</Data>
<Data>
Operation:
OnFreeze event
Freeze Event
Context:
Execution Context: Registry Writer
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {61189d5b-362b-40e3-ba48-319c74d36b29}</Data>
<Binary>2D20436F64653A20575254524547524330303030303337392D2043616C6C3A20575254524547524330303030303335342D205049443A202030303030353130302D205449443A202030303030343136342D20434D443A2020433A5C77696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
Log Name: Application
Source: VSS
Date: 8/21/2013 1:52:07 PM
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: child vm.domain.local
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
Freeze Event
Context:
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {61189d5b-362b-40e3-ba48-319c74d36b29}
Command Line: C:\windows\system32\vssvc.exe
Process ID: 5100
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8229</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-21T11:52:07.000000000Z" />
<EventRecordID>1435838</EventRecordID>
<Channel>Application</Channel>
<Computer>child vm.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
</Data>
<Data>
Operation:
Freeze Event
Context:
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {61189d5b-362b-40e3-ba48-319c74d36b29}
Command Line: C:\windows\system32\vssvc.exe
Process ID: 5100</Data>
<Binary>2D20436F64653A20575254575254494330303030353239392D2043616C6C3A20575254575254494330303030333034322D205049443A202030303030353130302D205449443A202030303030343136342D20434D443A2020433A5C77696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
Also, on the child VM, when I list the vss writers, the Registry Writer is often in a failed state. I checked the integration services version on the child VM which is up to date, restarted the child VM, but it did not solve the problem. I cannot get any useful results regarding these two EventID's, can anyone point me to the right direction to solve this?