DPM 2012 R2 (BMR) Replica allways inconsistent

Hello,
I have two Server 2012 servers running DPM 2012 R2. I am trying to do a Bare Metal Recovery backup on one of our protected servers. The protected server is running Server 2008 R2. But since i added the server the replica is allways inconsistent.
Error on the DPM server:
An unexpected error occurred while the job was running. (ID 104 Details: The process cannot access the file because it is being used by another process (0x80070020))
All jobs in Windows Server Backup on the protected server shows as: Succesfull.
No errors in the log files on: C:\Windows\Logs\WindowsServerBackup
DPMRACurr.errlog on the 'protected' server:
createsnapshotsubtask.cpp(971) [000000000228D680] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL Executing PreSnap step ""c:\Program Files\Microsoft Data Protection Manager\DPM\bin\BMRBackup.cmd" \\dpmserver.domain.com\7bbdce9d91934eb9bedbcd71f7665a0d"
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
service.cpp(147) [000000000018F7A0] ACTIVITY CService::ServiceHandlerExInternal
createsnapshotsubtask.cpp(1261) [000000000228D680] NORMAL CreateSnapshotSubTask: this:[000000000228D680], Component: System Protection
vssbaserequestor.cpp(51) [000000000228E640] NORMAL CVssBaseRequestor: constructor [000000000228E640]
vsssnapshotrequestor.cpp(91) [000000000228E640] NORMAL CVssSnapshotRequestor::CVssSnapshotRequestor [000000000228E640]
createsnapshotsubtask.cpp(1302) [000000000228D680] NORMAL CreateSnapshotSubTask: this:[000000000228D680], m_pVssRequestor = [36234816]
vssbaserequestor.cpp(88) [000000000228E640] NORMAL CVssBaseRequestor::Initialize [000000000228E640]
vsssnapshotrequestor.cpp(185) [000000000228E640] NORMAL CVssSnapshotRequestor::InitializeSnapshotCreation [000000000228E640]
miscellaneousutils.cpp(677) WARNING Failed: Hr: = [0x80070002] Could not open HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0
iteratorutils.cpp(648) NORMAL CaseSensitivity NOT enabled on the machine
systemstatewriterhelperplugin.cpp(1206) WARNING Failed: Hr: = [0x80070003] : Encountered Failure: : lVal : hr
vdshelper.cpp(293) [0000000002290D40] NORMAL VdsHelper: VDS Service started
fsmtransition.cpp(111) [00000000008ED4A0] WARNING Failed: Hr: = [0x80070020] HasEventErrorCode: completion: 0xa10c, signature: 0xaabbcc00
vsssnapshotrequestor.cpp(2056) [000000000228E640] NORMAL CVssSnapshotRequestor::DoFailureCleanup [000000000228E640]
vsssnapshotrequestor.cpp(1608) [000000000228E640] NORMAL CVssSnapshotRequestor::ReleaseVolumesForSnapshot [000000000228E640]
aasubtask.cpp(906) [000000000228D680] WARNING <?xml version="1.0"?>
aasubtask.cpp(906) [000000000228D680] WARNING <Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2147024864" Reason="Error" CommandID="RAPreBackup" CommandInstanceID="7f686c79-a38a-4ed9-bf89-f78b72665634" GuidWorkItem="64d01a3c-e977-4f66-a7b8-860d7ce8c792" TETaskInstanceID="ebbbdb3b-f585-4753-8e72-af1d5f44285b"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="998" DetailedCode="-2147024864" DetailedSource="2"/><RAStatus><RAPreBackup xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/StatusMessages.xsd"><BackupTime>130444369564690000</BackupTime><DSStatus><ComponentName>System Protection</ComponentName><LogicalPath>Computer</LogicalPath><BackupStamp></BackupStamp><Metadata></Metadata></DSStatus></RAPreBackup></RAStatus></Status>
runtime.cpp(1376) [000000000087B170] FATAL Subtask failure, sending status response XML=[<?xml version="1.0"?>
runtime.cpp(1376) [000000000087B170] FATAL <Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2147024864" Reason="Error" CommandID="RAPreBackup" CommandInstanceID="7f686c79-a38a-4ed9-bf89-f78b72665634" GuidWorkItem="64d01a3c-e977-4f66-a7b8-860d7ce8c792" TETaskInstanceID="ebbbdb3b-f585-4753-8e72-af1d5f44285b"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="998" DetailedCode="-2147024864" DetailedSource="2"/><RAStatus><RAPreBackup xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/StatusMessages.xsd"><BackupTime>130444369564690000</BackupTime><DSStatus><ComponentName>System Protection</ComponentName><LogicalPath>Computer</LogicalPath><BackupStamp></BackupStamp><Metadata></Metadata></DSStatus></RAPreBackup></RAStatus></Status>
runtime.cpp(1376) [000000000087B170] FATAL ]
systemstatewriterhelperplugin.cpp(373) [00000000022933D0] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : sfDisk.Open((0x80000000L), 0x00000001)
systemstatewriterhelperplugin.cpp(202) [00000000022933D0] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : GetCriticalDisks(ssWindowsBackupSetDir, fCaseSensitive, arrCriticalDisks, arrCriticalDiskSizes)
systemstatewriterhelperplugin.cpp(176) [00000000022933D0] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : GetBMRRecoveryInformation(ssWindowsBackupSetDir, fCaseSensitive, ssOSVersion, isServerOS, ssOSArchitecture, dwBootDiskNumber, arrCriticalDisks, arrCriticalDiskSizes)
systemstatewriterhelperplugin.cpp(557) [00000000022933D0] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : DumpBMRRecoveryInformation()
createsnapshotsubtask.cpp(1508) [000000000228D680] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : pBackupHelper->DoPreSnapshotProcessing()
fsmstate.cpp(167) [000000000228B7A0] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : pTransition->Execute(pEvent)
genericfsm.cpp(225) [0000000000877300] EBBBDB3B-F585-4753-8E72-AF1D5F44285B WARNING Failed: Hr: = [0x80070020] : Encountered Failure: : lVal : m_pCurrentState->SendEvent(pEvent, pNextState)
freesnapshotsubtask.cpp(46) [0000000002295B70] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CFreeSnapshotSubTask: constructor [0000000002295B70]
freesnapshotsubtask.cpp(123) [0000000002295B70] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CFreeSnapshotSubTask::TriggerDone [0000000002295B70]
freesnapshotsubtask.cpp(562) [0000000002295B70] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CFreeSnapshotSubTask: StartBackupComplete [0000000002295B70]
vssbaserequestor.cpp(1068) [000000000228E640] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CVssBaseRequestor::StartGatherWriterStatus [000000000228E640]
vssbaserequestor.cpp(944) [000000000228E640] NORMAL QueryStatus returned 0x4230a, Releasing VssAsync [000000000067A4C0]
freesnapshotsubtask.cpp(675) [0000000002295B70] NORMAL CFreeSnapshotSubTask: ReleaseSnapshot [0000000002295B70]
vssbaserequestor.cpp(1101) [000000000228E640] NORMAL CVssBaseRequestor::CheckWriterStatus [000000000228E640]
vsssnapshotrequestor.cpp(1346) [000000000228E640] NORMAL CVssSnapshotRequestor::ReleaseSnaphot [000000000228E640]
vsssnapshotrequestor.cpp(2022) [000000000228E640] NORMAL CVssSnapshotRequestor::CleanUp [000000000228E640]
vsssnapshotrequestor.cpp(1608) [000000000228E640] NORMAL CVssSnapshotRequestor::ReleaseVolumesForSnapshot [000000000228E640]
freesnapshotsubtask.cpp(181) [0000000002295B70] NORMAL CFreeSnapshotSubTask::GetFinalStatus [0000000002295B70]
freesnapshotsubtask.cpp(63) [0000000002295B70] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CFreeSnapshotSubTask: destructor [0000000002295B70]
vsssnapshotrequestor.cpp(109) [000000000228E640] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CVssSnapshotRequestor::~CVssSnapshotRequestor [000000000228E640]
vsssnapshotrequestor.cpp(2022) [000000000228E640] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CVssSnapshotRequestor::CleanUp [000000000228E640]
vsssnapshotrequestor.cpp(1608) [000000000228E640] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CVssSnapshotRequestor::ReleaseVolumesForSnapshot [000000000228E640]
vssbaserequestor.cpp(69) [000000000228E640] EBBBDB3B-F585-4753-8E72-AF1D5F44285B NORMAL CVssBaseRequestor: destructor [000000000228E640]
workitem.cpp(272) [0000000002288BE0] EBBBDB3B-F585-4753-8E72-AF1D5F44285B ACTIVITY WorkItem stopping
When i run procmon on the 'protected' server during the bmr job:
DPMRA.exe CreateFile \Device\Harddisk0\DR0 SHARING VIOLATION
DPMRA.exe QueryStandardInformationFile C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\DPMRACurr.errlog SUCCESS
DPMRA.exe WriteFile C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\DPMRACurr.errlog SUCCESS
Things i tried:
wbadmin.exe Start Backup –backuptarget:\\justaserver\tempshare –AllCritical
100% complete, no errors.
Removed the protection group (delete data).
Re-installed the DPM agent.
Moved the protected server from dpmserver1 to dpmserver2.
i appreciate any help you can provide.
Kind regards,
BoRo90

Hi Mike,
FLTMC on DPM server:
Filter Name                     Num Instances    Altitude    Frame
DpmFilter                               0       385300
0
PROCMON23                               0       385200
0
Dedup                                 179       180450
0
SIS                                   179       180400
0
luafv                                   1       135000
0
npsvctrig                               1        46000
FLTMC on Protected server:
Filter Name                     Num Instances    Altitude    Frame
DpmFilter                               0       385300
0
PROCMON23                               0       385200
0
FsDepends                               4       370060
0
MpFilter                                5       328000
0
luafv                                   1       135000
0
Running only a systemstate job works fine! I have already tried that.
Kind regards

Similar Messages

Protection of Exchange 2012 SP1 DAG with DPM 2012R2 not working - Replica is Inconsistent

We are struggling to get DPM 2012 R2 to protect our Exchange 2013 SP1 DAG, and receiving the error "Replica is inconsistent". I have copied the current versions of eseutil.exe and ese.dll to the DPM servers, and the DPM agent is the latest version
on the Exchange boxes.
The sanitised error is:
Affected area: Database123
Occurred since: 10/11/2014 11:39:02
Description: The replica of Exchange Mailbox Database Mailbox Database123 on <servername> 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)
Data consistency verification check failed for LOGS of Exchange Mailbox Database Mailbox Database123 on <servername>. (ID 30146 Details: The extended attributes are inconsistent (0xFF))
More information
Recommended action: Either the database files are corrupt or the proper versions of the Eseutil.exe and Ese.dll files are missing.
If you have recently upgraded your Exchange server, copy them from that server to the DPM server.Contact your Exchange server administrator, and then verify the issue. You can recover the last known good backup to address the corrupted state.
Synchronize with consistency check.
Run a synchronization job with consistency check...
Resolution: To dismiss the alert, click below
Inactivate
Running a synchronization job with consistency check does not work and we end up back to the same error. Circular logging is not enabled.
We are starting an upgrade of Exchange 2007 to 2013 and the DAG has little in it yet, and the Exchange 2007 environment is being backed up by a different product that we are moving away from.
Any suggestions welcome
Mark

Hi,
Has any testing been done with the
option to run Eseutil on the backup not enabled via the DPM GUI when creating protection, and identifying if DPM reports the same error?
Also
with Eseutil enabled I recommend reviewing the below links which, may assist with the issue being faced. The first link aligns with the error reported (ID
30146). The second outlines high level overview for protecting Exchange 2013.
https://social.technet.microsoft.com/Forums/en-us/home?forum=dpmexchbackup&announcementId=0d4fcbc7-199c-4f7a-813a-862437c0aa4e
http://technet.microsoft.com/en-us/library/dn751026.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community
members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

DPM 2012 R2 BMR on Windows 8

There are a couple of posts out there regarding bare metal.
All though BMR seems to working fine on my DPM 2012 R2, when backing up servers, i was wondering if it was possible with workstations.
Seems that it is now allowed to add a workstation (Windows 8) as a server, where one is able to set up System state and BMR, but i keep getting following error:
Affected area: Computer\System Protection
Occurred since: 22-01-2014 12:01:53
Description: The replica of System Protection Computer\System Protection on pcX.mydomain.net 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 failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected computer to store the System State backup. On protected computers running Windows
Server2008, verify that Windows Server Backup (WSB) is installed and that it is not performing any other backup or recovery task. (ID 30214 Details: Internal error code: 0x80990ED0)
More information
Recommended action: You can see the errors reported by WSB in the Eventlog on the protected computer pcX.mydomain.net . For resolution actions and more information on these errors, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.
Synchronize with consistency check.
Run a synchronization job with consistency check...
Resolution: To dismiss the alert, click below
Inactivate
All volume back up completes successfully.
This test so far was done on Legacy boot mode machines. Wonder if same issue is present on UEFI aswell?
Any help is appreciated

Hi,
SystemState protection is not supported on desktop operating systems but as you found out DPM does not hide the system protection option when you protect a desktop operating system as a server.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 CU 4 - issue w/ system state backup completing on non domain servers with T2embed.dll

I am really new to DPM and just took over a system that has servers being backed up that are not part of the domain. The volumes backup fine and system state will not complete. In looking at the protection group server the WindowsImageBackup folder is created
and the backup starts however it will fail and DPM server will say Replica is inconsistent. Back on the protected server in the backup event log, it fails w/ error code 2155347997. In the backup error log file in C:\windows\logs\windowsserverbackup.
It says "Error in backup of C:\windows\system32\t2embed.dll during read. Error [0x80070005] Access is denied.
We have about 4 other servers that are not domain joined and they are getting similar errors w/ t2embed.dll in that system32 directory or in the WinSXS folder. All servers are 2008 SP2 or 2008 R2 SP1.
Thank you in advance for you help

Hi,
DPM has no control over errors that Windows server backup receives, but check permissions and Remove the DENY permission for EVERYONE on the below files:
C:\Windows\system32\t2embed.dll
C:\Windows\winsxs\amd64_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7601.17514_none_13e628b635935244\t2embed.dll
C:\Windows\winsxs\x86_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7601.17514_none_b7c78d327d35e10e\t2embed.dll
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 Consistency Check (Replica Inconsistent) Error for Failover Cluster

I have a SCDPM 2012 R2 instance running against a Windows Server 2012 R2 Failover Cluster on the network.
However, any new/migrated Roles/Virtual machines that I add under an existing protection group always gives me an error saying that the replica is inconsistent.
I've verified the following :
1. All windows updates are applied on the cluster hosts & the DPM server.
2. The VSS and DPMRA services are running on the hosts & DPM server.
3. The Windows Server Backup feature has been installed on all the machines as well.
4. The short term storage disks attached to the DPM server are LUNs and there is enough free space on those.
What else am I missing that could be causing the Replica to be inconsistent - considering that these are new VMs on the hosts themselves - is there a way to force a fresh replica to be created?

Do not remove any of the providers they come with the system. There is just something wrong with that VM, your trying to backup, as it could take the initial replica creation.
Check all of the following
1) Make sure you have enough C drive space on the guest - need space to create a snapshot
2) Check the vssadmin list wirters for any errors
If none of the above, rerun the consistency check when no other backup is running. Check the Application log on the host for any vss failures
Ensure you have all the DPM hotfixes - I am compiling a list since i've been thru many DPM issues.
Great product when you get it going but like any product there are bumps in the road :)
ANNCEX

DPM 2012 R2 - Replica is inconsistent (ID 104 Details: The parameter is incorrect (0x80070057))

Since implementing DPM 2012 R2, we have been having issues with several replicas in different protection groups. We are running version 4.2.1254.0. We have been unable to backup, as we are receiving the following error when running a consistency check:
An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))
Any idea how to get this fixed?

104
An unexpected error occurred while the job was running.
This error can appear if you are trying to protect a SQL Server database that has files on a remote share. This is not supported by DPM.
Please check below DPM error codes list for reference.
http://social.technet.microsoft.com/wiki/contents/articles/24613.system-center-data-protection-manager-error-codes.aspx

DPM 2012 R2 UR4 and BMR backup from physical 2008 R2 (DC, DNS, DHCP,WSUS, WDS)

Hi,
I'm completely lost.
We updated from DPM2010 (2008 R2) to DPM 2012 R2 RU4 (2012 R2).
Clean install. Same hardware. Everything went quite smoothly.
Our new (and also old did the same thing) DMP protects some Hyper-V guest on our 2008 R2 Hyper-V cluster, one Exchange (2010) DB's and SQL 2008 R2 DB's and one physical server - 2008 R2 (DC, DNS, DHCP,WSUS, WDS ~160GB of data).
Currently we are using some Buffalo Terastation's III (TS-RIXL) iSCSI SAN storage to hold our DPM protected data.
Configured as RAID 5.
Our new DPM server is connected to those iSCSI devices using built in MS iSCSI initiator via secondary NIC on this server using dedicated iSCSI subnet.
Everything seems to be fine unitil System State and BMR (I'v checked both) runs.
Basically my iSCSI NIC shows Write about ~170Mbit/s and Read about 520Mbit/s when backing up virtual machines, Exchange or SQL.
When it comes to System State and BMR backup the trouhgput is MUCH slower (about 65Mbit/s) and I can not figure out why. I understand that the BMR backup initiates direct writing to the DPM created and shared replica volume on my iSCSI NAS (my wording
might be not correct but basically I understand how this works). But I don't understand why the speed is so much slower. I'v tried everything, googeled around, changed NIC drivers, firmware etc. No luck.
If I just copy some big ISO file from/to server to DPM or vice versa the speed is arount 100MB/s (as reported by windows itself). So it seems to able to utilize full network speed. But why this backup is so slow? I'm excpecting to see speed about ~170Mbit/s
because it corresponds my iSCSI Write speed as seen when backing up hyper-v guests and DB's..
What I'm doing wrong?
Any help is appreciated :)
rgds Sven

Hi Sven,
Sometimes BMR is slower than backing up virtual machines (VHDs). If there is a free local disk, please test to do a backup locally to see the speed. From your description a common backup works much faster so let's see if it is the backup speed which causes
the issue or not.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

DPM 2012 R2 failing on backup of BMR and System State

We are running DPM 2012 R2 on Windows Server 2012 and I am trying to protect another Windows 2012 Server with a Bare Metal Recovery and system state but it fails on initial synchronization. I get the following error in DPM:
DPM failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected computer to store the System State backup. On protected computers running Windows Server2008, verify that Windows Server
Backup (WSB) is installed and that it is not performing any other backup or recovery task. (ID 30214 Details: Internal error code: 0x80990ED0)
This is a new server and there is 65.7 GB of 99.9 GB free on the C drive. 131 of 136 GB free on the F drive. The P drive only has 100 MB free of 36.3 GB but that is where the pagefile is located, nothing else is on the P drive.
Would that be a problem or is that irrelevant?
The replica volume is 30 GB and the recovery point volume is 6.06 GB. I tried increasing the replica volume all the way up to 200 GB and the recovery point volume to 30 GB but that didn't matter.
Why is this not working?

Hi,
Try this and troubleshoot any errors along the way.
1) Set up a network share on a remote machine
\\server\bmrshare
2) From an administrative command prompt on the Protected Server you want the BMR backup for, type:
wbadmin.exe start backup -allcritical -backuptarget:\\server\bmrshare
This should show you the list of volumes included in the BMR backup and ask "Do you want to start the backup operation?. - Type
Y to continue..
3) Once completed, see how large the BMR backup is on the remote server, then resize the DPM replica accordingly to accommodate the size of the manual BMR backup.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 SP1: Unable to connect to the DPM DB, because the DB is inconsistent state.

We are getting the following error when we try to recover from a specific server ( Recovery Tab | Domain | File Server )
Unable to connect to the DPM Database because the database is in an inconsistent state. (ID943)
=> There are no double entries for the specific server in the database. Verified by the following query:
select servername, domainname from dbo.tbl_AM_Server order by servername
=> DBCC Check DPMDB results in no errors.
=> Yesterday we used the following script to remove a ghost tape from our reports. The tape belongs to the PG where the File Server is member of.
http://social.technet.microsoft.com/Forums/en-US/a654c323-7b48-4ab5-8812-850115d9e430/dpm-2012-ghost-tapes-in-weekly-report?forum=dpmtapebackuprecovery
Is there a relation between our error and the removal of the ghost tape? Any idea how to fix this?

Hi,
I have not heard of that script causing any problems in the past, so may or may not be related. What are the details of the msdpm service crash found in the msdpmcurr.errlog after the error ?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2, Scale-out and secondary replicas

Hi all,
TechNet says scale-out protection for VMs and DPM chaining isn't supported - is this still the case for 2012 R2?
Our scenario: We have numerous clusters with a ~dozen Hyper-V (2012/2012R2) nodes each, and lots of running VMs. We need to use DPM scale-out to have multiple DPM servers protect the
clusters, but also need off-site replicas for the data sources.
Cheers

Hi,
There is no change in DPM 2012 R2 with respect to secondary protection for scale out Hyper-v. Consider backing up to Azure for offsite solution.
Backing Up DPM using Windows Azure Backup
http://technet.microsoft.com/en-us/library/jj728752.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 Roll Up 2: Agent Terminating or Checksum mismatch during backups

Hi There,
I have dual DPM server deployment. Primary DPM server backs up to disk in my production site and then I have a Secondary DPM server creating replicas to Disk and Tape in my DR site. Both DPM servers are running DPM 2012 R2. I recently installed DPM 2012
R2 Roll Up 2 (Was running Roll up 1 for weeks without issue), careful not to install the bugged version of the update. Everything was running normally and then suddenly about 4 days later some of my resources started failing and became inconsistent on my Secondary
DPM server.
Either:
1. My DPMRA service on my Secondary DPM server terminates with the following Application Log error
Faulting application name: DPMRA.exe, version: 4.2.1235.0, time stamp: 0x536a4419
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0x80004005
Fault offset: 0x0000000000047b8c
Faulting process id: 0x1f18
Faulting application start time: 0x01cf8a0713e8c930
Faulting application path: C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\DPMRA.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 19d99bee-f5fd-11e3-93fe-782bcb479b76
Faulting package full name:
Faulting package-relative application ID:
OR
2. DPM has detected a checksum mismatch during data transfer over the network (ID: 30087)
I have already removed and deleted from disk the failing resources on the Secondary DPM server and then re-added them to the protection groups, but again either the agent terminates or fails with checksum during replica creation or consistency check. Note
that the Primary DPM server is happy and all the resources are green and backing up successfully numerous times a day.
I suspect that the update 4 days before the issues started might have created this issue. Has anyone had these issues or know of potential ways to fix it?
Your help would be greatly appreciated as I really don't want to rebuild the Secondary DPM server.
Thanks
Jacques

Hi,
Here is an update. I have managed to get a workaround.
If I enforce IPSec with ESP between my primary and secondary DPM server then the agent stops terminating or reporting checksum errors.
Still waiting on someone from the DPM team to give a suggestion here as it seems to be a bug that started after I installed Roll Up 2 for DPM 2012 R2
Thanks
Jacques

DPMRA crashing after update to DPM 2012 R2 UR2

Hi,
we have a problem on our DPM2012 R2 server.
The DPM servers OS is Windows Server 2012.
After applying Update Rollup 2, the DPMRA service on the DPM server started crashing when trying to create a new recovery point or trying to synchronize:
Faulting application name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Faulting module name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Exception code: 0xc0000005
Fault offset: 0x000000000023442c
Faulting process id: 0x630
Faulting application start time: 0x01cf606a8d5b3262
Faulting application path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Faulting module path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Report Id: ed0d579b-cc5d-11e3-9436-00155d0f6501
Faulting package full name:
Faulting package-relative application ID:
When DPMRA crashes, the DPM jobs fail:
The replica of CDC-RND-SQL01\Tfs_RnD_Configuration on CDC-RND-SQL01.dev.local is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
DPM failed to communicate with the protection agent on WP-DPM02.alpha.local because the agent is not responding. (ID: 43)
Creation of recovery points for WPCLUSTERSQL\WSS_Content_WP-SP-INTRA_TEMP on SQL Server (MSSQLSERVER).WPSQLCluster.alpha.local have failed. The last recovery point creation failed for the following reason: (ID: 3114)
DPM failed to communicate with the protection agent on WP-DPM02.alpha.local because the agent is not responding. (ID: 43)
Creation of recovery points for WPCLUSTERSQL\CDC-INTRA-SPS01_WSS_Content_80_Changes01 on SQL Server (MSSQLSERVER).WPSQLCluster.alpha.local have failed. The last recovery point creation failed for the following reason: (ID: 3114)
The protection agent on WP-DPM02.alpha.local was temporarily unable to respond because it was in an unexpected state. (ID: 60)
Already tried disabling UAC, firewall is disabled, checked network connectivity, reinstalled agents on the protected servers.
Does anyone have encountered this? How did you solve it?
Here are a few DPMRA logs:
DPMRA_log_01.log
DPMRA_log_02.log

Hi,
For those experiencing the below DPMRA crash after installing DPM 2012 Sp1 UR6 or DPM 2012 R2 UR2
DPMRA.exe, version: 4.1.3441.0 = DPM 2012 Sp1 UR6
DPMRA.exe, version: 4.2.1226.0 = DPM 2012 R2 UR2
Faulting application name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Faulting module name: DPMRA.exe, version: 4.2.1226.0, time stamp: 0x5346902f
Exception code: 0xc0000005
Fault offset: 0x000000000023442c
Faulting process id: 0x630
Faulting application start time: 0x01cf606a8d5b3262
Faulting application path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Faulting module path: C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe
Report Id: ed0d579b-cc5d-11e3-9436-00155d0f6501
Faulting package full name:
Faulting package-relative application ID:
You can run the below Windows Powershell script on the DPM Server to clean up the *DPMRA.CRASHDETECT files. This should eliminate the dpmra crashes until a new fix is released to address the original problem.
1) Stop MSDPM and DPMRA Services.
2) Copy / Paste the below script into notepad and save as deletecrashfiles.ps1
3) Open Windows PowerShell using administrative privilege.
4) Run the deletecrashfiles.ps1
5) Restart the DPM services.
#get DPM install path
$dpmsetup = "HKLM:\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup"
$dpminstallregkey = get-itemproperty $dpmsetup
$installpath = $dpminstallregkey.installpath
$path = $installpath + "\Volumes\Replica"
cd $path
function GetFolders($path)
$folders = Get-ChildItem "."
foreach ($folder in $folders)
if (Test-path $folder.Name -pathtype Container)
#write-host $folder.name
GetCrashitems(".\"+$folder.Name)
else
#write-host $folder.Name
function GetCrashItems($path)
$crashfile = "dpmra.crashdetect"
$folders = Get-ChildItem $path
foreach ($folder in $folders)
#write-host $folder
if (Test-path $folder.fullname -pathtype Container)
write-host 'getting items from ' +($folder.fullname)
$items = Get-ChildItem $folder.fullname
foreach($item in $items)
if ($item.name -match $crashfile)
write-host 'Deleting *dpmra.crashdetect file: '$item.fullname
$item.delete()
GetFolders $path
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

A few SQL related protection group Questions - DPM 2012 R2

Hi - Here is my environment: DPM 2012 R2 backing up SQL 2012 DBs. Some of the DBs are simple recovery model, some are full recovery model in the same protection group.
1) Regarding the fact that DPM only looks to the recovery model when the DB is first added to the protection group, if I ever changed the recovery model in the future, would stepping through the "Modify Protection Group" wizard without changing
anything be the solution for DPM not changing its methodology on the backing up or not backing up the log files? Or would I have to remove the affected databases from the protection group and add them back in?
2) I have disk protection configured for 30 Days, sync every 15 minutes, and application recovery points once per day. Online protection is configured for 90 Days. Does this mean my disk consumption on the DPM side for full model databases will be the full
size of the databases, plus the amount of changes observed over 30 days? OR does it mean it will keep 30 full copies of the DB? I am fairly sure the former.
3) If I do decide to reduce the retention range on the disk side of this protection group to say 14 days, are there any specific issues with changing that after the PG has been working for some time?
4) My former backup solution had an option to run consistency checks after every SQL job. Is that still considered best practice? Would the "Run a daily consistency check" be a better choice than the "Only run if a replica becomes inconsistent"
option that I currently have in place? Would there be any ramifications to enabling this now after this PG has been in place for some time?
Thanks very much!

Hi
Q1) Regarding the fact that DPM only looks to the recovery model when the DB is first added to the protection group, if I ever changed the recovery model in the future, would stepping through the "Modify Protection Group" wizard without changing
anything be the solution for DPM not changing its methodology on the backing up or not backing up the log files? Or would I have to remove the affected databases from the protection group and add them back in?
A1)
Changing the Recovery Model of a Database
To change the recovery model of a protected database to the simple recovery model
Stop protection of the database, selecting the retain replica option.
Change the recovery model on the SQL Server database.
Add the database to a protection group.
Q2) I have disk protection configured for 30 Days, sync every 15 minutes, and application recovery points once per day. Online protection is configured for 90 Days. Does this mean my disk consumption on the DPM side for full model databases will be the full
size of the databases, plus the amount of changes observed over 30 days? OR does it mean it will keep 30 full copies of the DB? I am fairly sure the former.
A2) Your disk consumption on the DPM will be for size of model databases plus the amount of changes observed over 30 days.
Q3) If I do decide to reduce the retention range on the disk side of this protection group to say 14 days, are there any specific issues with changing that after the PG has been working for some time?
A4) Not really, but to gain back the potential extra space allocated for the original 30 day retention - you can try shrinking the recovery point volume once the retention range is reduced and the older recovery points are pruned. I would wait until
after midnight to be sure the old RP's are deleted, then try to shrink.
Q4) My former backup solution had an option to run consistency checks after every SQL job. Is that still considered best practice? Would the "Run a daily consistency check" be a better choice than the "Only run if a replica becomes inconsistent"
option that I currently have in place? Would there be any ramifications to enabling this now after this PG has been in place for some time?
A4) A consistency check will only run if DPM detects the replica is inconsistent. Even if you have the option selected to run nightly, if the replica is already consistent a consistency check will be skipped.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 (ID 104 Details: Internal error code: 0x809909FF)

We are running DPM 2012 R2 on Windows Server 2012 R2
We have a Protection Group:Servers (9 members) where 5 servers always give the same error message, when we try to run a synchronization job with consistency check. With other 4 server everything is fine. (All 9 servers: Windows Server 2012 R2)
All servers have "Windows Server Backup" feature installed
Error message:
The replica of Microsoft Hyper-V \Online\S022 Reports on S022 Reports.SynCrust.********.eu 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)
Any help would be appreciated

Just wanted to add some further details to this thread...
As suggested in
this article, Windows Server Backup has been installed on all 3 cluster nodes. I have also tried disabling/enabling the WinRE agent, as it suggests, with no effect.
The Virtual Machine I am trying to back up is running Windows Server 2008 R2 with the latest updates, and has integration services version 6.3.9600 installed.
Additional searching led me to
this article, which states "DPM works seamlessly with Hyper-V VSS writer to ensure that consistent versions of virtual machines are captured and protected without affecting virtual machine access." It doesn't clarify if this is the method used
when backing up VMs stored in a CSV, however. Regardless, the Hyper-V VSS writer is not listed when issuing
vssadmin list providers
I went through the steps outlined in
this article to install the writer, but even after following said steps, the writer still does not appear as registered on the Windows Server 2012 R2 cluster node via the above command.
I should also mention that
this prereqs article mentions that the Hyper-V role should be installed on the DPM server. The hardware I'm using has an old AMD Sempron 3400+ CPU, so I'm unable to install this role on the DPM. The article states "DPM protects Hyper-V virtual
machines even without the role, but you cannot perform item-level recovery (ILR) unless the role is installed.", so it's doubtful that lack of the role would cause this issue; MindaugasKa, is the Hyper-V role installed on your DPM?
Despite the effort of upgrading my storage server to Windows Storage Server Standard 2012 R2, my cluster nodes to Windows Server 2012 R2 Datacenter, and my DPM to 2012 R2, the
nightmare continues...

DPM 2012 R2 Crashes after upgrade - Tape Backup

Hello guys,
I have recently upgraded from DPM 2012 SP1 to DPM 2012 R2 Rollup 3 on Windows 2012 R2 (in-place upgrade)
The basic procedure was to backup the DB, uninstall DPM, install DPM 2012 R2, restore the DB. re-sync all the inconsistent replicas and upgrade server agents. When it comes to the offsite tape backup for whatever reason every time the tape backup
commences it fails instantly with the below error and reports "Backup to Tape Failed"
"Event Log shows MSDPM Error ID 945"
It appears to be failing due to a missing stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'. The stored procedure does not exist on other DPM servers. I'm guessing this is something hanging around in the DB from prior to the upgrade but I can't
seem to track it down. Does anyone have any ideas upon how to resolve the issue?
The description for Event ID 945 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Unable to connect to the DPM database because of a general database failure. Make sure that SQL Server is running and that it is configured correctly.
Problem Details:
<FatalServiceError><__System><ID>19</ID><Seq>84123</Seq><TimeCreated>25/10/2014 23:01:01</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>SqlException</ExceptionType><ExceptionMessage>Could
not find stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'.</ExceptionMessage><ExceptionDetails>System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.prc_SMTE_ComputeDailyTrend'.
   at Microsoft.Internal.EnterpriseStorage.Dls.SummaryManager.SummaryManagerMachine.OnStart(ErrorInfo& eInfo)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.SimpleStateMachine.Start(Message msg)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Engine.ChangeState(Message msg)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.TaskInstance.Process(Object dummy)
   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.FsmThreadFunction.Function(Object taskThreadContextObj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
ClientConnectionId:fbd15cf8-5b7b-4438-befe-a3a54426d371</ExceptionDetails></FatalServiceError>

For this issue, you can refer below link
http://blogs.technet.com/b/dpm/archive/2012/01/30/fix-the-dpm-console-crashes-and-logs-event-id-945-when-making-any-changes.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

DPM 2012 R2 (BMR) Replica allways inconsistent

Similar Messages

Maybe you are looking for