Monday, September 15, 2008

Fix Error 3114 & Error 30216

Errors:

Recovery point creation jobs for Storage group Storage_Group_04 on Server1 have been failing. The number of failed recovery point creation jobs = 1. (ID 3114)

DPM has detected a discontinuity in the log chain for Storage group Storage_Group_04 on Server1 since the last synchronization. (ID 30216 Details: Unspecified error (0x80004005))

Fix:

Although DPM prompts you to Create a recovery point... it will not perform a Full Backup as needed to recover from this error.  Click the Protection tab, navigate to the Storage Group you are protecting, right click, and choose create recovery point.  Then choose to create an express full backup.  You can now inactivate this alert, as the Full backup will resolve the issue.

5 comments:

Ken said...

When I try this fix I get another error back saying that the state is inconsistent so it will not let me create a recovery point. Any ideas why this is happening?

Thanks!

Ken

Dan B. said...

When the replica is showing inconsistent, there are two different types of Consistency Checks:

1: Consistency Check
2: Consistency Check with Synchronization

They are COMPLETELY different. The first is a normal Consistency Check - run from right clicking the Protection Group, and choosing Run Consistency Check.

The second is Consistency Check with Synchronization. This can ONLY be done from the monitoring tab. Select the alert for the inconsistent storage group. In the details section, you will see the link to run ac Synchronization with a Consistency Check.

I know this sounds stupid, but I actually spoke with one of the developers that wrote DPM 2007, and he confirmed that they are indeed two types of Consistency Checks.

So, to answer your question, you need to run the second one - the Synchronization with Consistency Check.

Hope this helps!

Brian said...

i've done everything suggested here and still get the error
"DPM has detected a discontinuity in the log chain for Storage group First Storage Group on morgan03.MI2K3.local since the last synchronization. (ID 30216 Details: Unspecified error (0x80004005))"

Any other ideas?
Thanks for your site.

Abigirl234 said...

Hiya

Has anyone come up with a resolution for this as i am experiencing the same issue as brian?

Thanks

Everyday Nerd said...

I'm assuming that you are protecting a CCR? If so, re-seed your CCR for the storage group that is failing.

Welcome!

I use Microsoft System Center Data Protection Manager 2007 on a daily basis, and although it is a great product, it takes a lot to master. I have created this blog to share my experiences with DPM with other System Administrators out there. All of my experience with DPM is in the role of protecting Microsoft Exchange 2007, and SQL server (the DPM database itself).

There have been many issues that I've run across, and not been able to find answers for on the Internet, so I'm going to "pay it forward" to the IT community!

Hope you find this blog informative!