How to fix “Replica is inconsistent” in DPM during backing up SQL 2012 DBs?

After creating protection group ,includes SQL 2012 DBs, DPM showed me “Replica is Consistent” for all databases.

ImageMy first question was “Does DPM 2012 fully support SQL Server 2012?”. I checked release notes and noticed:

Do the following to protect the Microsoft SQL Server 2012 database:

Connect to the SQL Server 2012 instance through the Management Studio, and then select and expand Security. Select and expand Logins, right-click NT AUTHORITY\SYSTEM, and then click Properties. Click Serverroles, click sysadmin, and then click OK.

1) Open SQL Management Studio and grant NT AUTHORITY\SYSTEM with sysadmin rights. 

Image

2. On DPM Server delete existing protection group and create new one. Next, re-run creating replica on necessary DBs. It works! 🙂

Image

Deploying DPM Agent 2012 to Untrusted or Workgroup Computers

My DPM server name is DPMSRV , x64

My target server which I want to protect is TERMSRV

1. On target server open cmd.exe with administrator permissions

2. Type net use Z: \\DPMSRV\c$

3. Change directory to Z:\Program Files\Microsoft DPM\DPM\Agents\RA\4.0.1908.0\amd64 and execute DPMAgentInstaller_amd64.exedpm-client-1

4. Great! You installed main files of DPM agent on target server. Now we have to say to agent what DPM server we want to use. For this, turn back to your system drive and change directory where  installed DPM agent ( for me, cd c:\Program Files\Microsoft Data Protection Manager\DPM\bin\ ). Then run SetDpmServer.exe -dpmservername dpmsrv -isNonDomainServer -userName dpmsrv1 for adding firewall exceptions and user account to communicate with your DPM server.

-userName creates an NT user account with the specified username for this server to communicate with DPM server. You don’t have to create one manually!!

dpm-client-2

5. Update installed agent to the latest version

6. Open your DPM Management Console and attach DPM agent. During wizard steps use account and password from step 4

dpm-client-3 dpm-client-4dpm-client-5
dpm-client-6

7. Now you are ready to create protection group using an attached agent

dpm-client-7