Thursday, May 24, 2012

DPM–Creating DPM Protection group for Protecting Hyper-V Host Server 2008 R2 (Error ID : 31313)


Scenario : Installed DPM 2010 on a Hyper-V 2008 Server R2 SP1. 

The server name of this Hyper-V is

However when trying to create a protection group to protect the Hyper-V VM, it gives the error message (ID : 31313).  The server is already patched with the KB975354 as required by the error message.  Very weird !!  First time happening to me.

So after looking around found something that just works.

I launch the Microsoft SQL Server Management Studio (select the DPMDB database) and then key in the following in the New Query

use dpmdb
Update tbl_am_installedagent
Set ServerAttributes = 31
Where deleted = 0 and serverid in (select Serverid from tbl_am_server where serverName = '')

Just replace the server name in the pink in colour with the correct server name (FQDN).  Execute it

The output as below :


After that I was able to create the protection group to Protect the VMs.  As I mentioned, it’s weird, very weird.  It doesn’t happen to my previous installations before.

Thank you and hope this helps you as it helps me.

Reading resource from here.

Key words : error ID 31313, KB975354 installed, Protecting Hyper-V with DPM 2010

Sunday, May 13, 2012

DPM–Cannot Deploy DPM Agent to Server under same domain

There’s some weird cases going on in one of my deployments.  The server is joined to the same domain as the DPM server, however when wanted to deploy the DPM agent, the assign protected server refused to accept it.

The protected server is a HP Server.

Therefore, did a test in the lab, there was no issue.  However in the production site, there was issue.

The following was carried out :

  • Uninstall the HP Server Tools and Management.
  • Deploy the DPM agent through the trusted way.
  • Install the HP Server Tools and Management

After the steps was carried out, then it works like a charm.  Hope this sharing benefits you.  Thank you.

keywords : DPM 2010, DPM 2012, Cannot backup domain.  Cannot deploy agent as trusted even though is in same domain as DPM server.

Tuesday, May 1, 2012

DPM–Critical Alert–SQL Log Backup job has detected a discontinuity in the SQL log chain for database


Today I’ve a scenario to share with you folks about the SQL Database backup (using DPM 2010 to backup).

The alert that I receive is as follow through the email :


After some investigation, found out that there’s a SQL Native Backup that is scheduled by the application team.  The DPM also uses the SQL backup engine before it’s data is transferred to the DPM.

It’s like 2 people trying to do the same job.  Coming to the extent, it might crash the database if not handled properly in long run.

Resolution :

Since the Application has a Native SQL backup scheduled to a folder e.g. F:\DB_Backup, then the protection group to protect this server was amended according to as below :

  • Removed the SQL Backup in DPM to protect the NOSTROLAB\QTNostro in the Protection Group
  • Add in backup to protect the database backup folder i.e. F:\DB_Backup in the Protection Group 

The above resolve the issue once and for all.

Hope the above helps you to resolve the issue of backing up the database with DPM.

keywords :  DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for database since the last backup. All incremental backup jobs will fail until an express full backup runs. DPM 2010, DPM 2012, DPM 2007,  Critical Alert