We are receiving multiple errors when trying to protect our Primary DPM 2012 server with a Secondary Server. These errors happen at random times during the day. Most of the errors seem to deal with SQL protection.

We have 104 Members being protected on the Primary DPM 2012 Server by the Secondary DPM 2012 Server. The two servers are currently in the same server room, but I want to move the secondary server to a remote location for DR.

The errors seem to clear themselves, but I'm concerned if we put the secondary server at a remote location there may be more issues because of bandwidth.

Creation of recovery points for SQLServer\Database1 on DPMServer1 have failed. The last recovery point creation failed for the following reason: (ID: 3114) Synchronization for replica of SQLServer\Database1 (SQLServer) on DPMServer1 failed because the replica is not in a valid state or is in an inactive state. (ID: 30300)

Creation of recovery points for H:\ on DPMServer1 have failed. The last recovery point creation failed for the following reason: (ID: 3114) No recovery point was created, either because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID: 208)

Creation of recovery points for SQLServer\Database2 on DPMServer1 have failed. The last recovery point creation failed for the following reason: (ID: 3114) DPM encountered a retryable VSS error. (ID: 30112)

Creation of recovery points for SQLServer\Database3 on DPMServer1 have failed. The last recovery point creation failed for the following reason: (ID: 3114) DPM encountered a retryable VSS error. (ID: 30112)

• Edited by netlander Wednesday, June 06, 2012 12:31 PM
• Changed type Yegor StartsevMVP, Moderator Wednesday, March 27, 2013 11:21 AM inactivity

Hi,

Can please tell me what is Backup time for both Primary DPM and Secondary DPM?

Primary varies for each protection group, but the SQL group is the group that gives us the most trouble.

Primary: 60 min synch and express full at 1 am  Recovery points at 8 am and 6pm

Secondary: 6 hour synch and express full at 8pm Recovery points at 8am and 6pm

We are getting at least 20 errors each day for all protection groups.

• Edited by netlander Wednesday, June 20, 2012 5:26 PM

Sorry for late reply

Change recovery point time on secondary make 9 am and 7pm if it is possible. Cause primary hard drive get block at create recovery point time and it has conflict occur. 

Please let me inform 

Check event log please send me that error will under hyper-v

I am not backing up Hyper-V resources.

• Edited by netlander Monday, July 02, 2012 1:40 PM

Did you ever figure out this issue on your secondary?  I've been having this since deploying my secondary, and am getting tired of it because it requires daily manual intervention to get everything synchronized.  My system is DPM 2012 SP1 with UR 3.  Never had this problem on DPM 2010 or 2007.  I opened a support case with MS on this and they were of no help.  They just abandoned the case after not being able to figure out what was going on with THEIR product.  Although the case was never closed, I've not heard anything in months.  My errors are all ID 208 errors indicating no changes to the primary have been made, when I know with absolute certainty that this is not possible.

Check dpm service under which server it is running primary or Secondary?

Click on Start->Run-> component Services

Look for DPMService right click on it click on property and please send screen Capture.

Are you talking about DCOM config?

Have you found a resolution to this issue?

I have this error daily, on nearly every item that is replicated from the primary server.  I can manually force a resync and that works fine, but I don't want to do that every day. 

(ID: 3114) No recovery point was created, either because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID: 208)

Thanks for your time!

No have not.  Doing the same manual operations you are.

However, unfortunately, I've just found out today that my primary DPM server has silently stopped creating file system recovery points about a 2 months ago.  Everything seems to be working but no recovery points exist.  All the disk volumes from multiple systems have stopped.  I have to figure that out immediately.  This has been going on longer than 2 months, however.

• Edited by simdoc Wednesday, September 11, 2013 11:23 PM