DPM 2012–Event ID 3184 Owner DPM Server

Recently I had an incident on the DPM 2012.  It’s the ActiveOwner issue.

I’m going to share with you how I done it.

The ActiveOwner files are located in "c:\program files\Microsoft Data Protection Manage\dpm\activeowner" on the server hosting the databases (SQL server being backed up). In my case it is one of the SQL server the DPM is protecting.  These ActiveOwner are used to manage ownership of databases, important for ensuring multiple DPM servers aren't attempting to backup/restore resources at the same period of time.

In the Protected Server that is running the SQL, from the Windows Explorer, drill to the location of:
C:\Program Files\Microsoft Data Protection Manager\DPM\ActiveOwner .

Rename all the files that is 0 KB. e.g. rename with the extention of .old

Next launch the Command Prompt in Administrator.

Change the directory to : C:\Program Files\Microsoft Data Protection Manager\DPM\bin in the Protected server (not DPM)

Key in as follow :
SetDPMServer.exe –DPMServerName DPMServerName

Note : Replace the DPMServerName with your DPM Server.  The rest of the syntax stays the same.

Rerun the Synchronization in your DPM Console.  It should resolved.

keywords : DPM, DPM 2012, DPM 2012 R2, Owner DPM Server ID 3184 The file or directory is corrupted and unreadable (0x80070570), DPM could not run backup/recovery job for the data source it is owned by a different DPM Server, Take data source ownership

SCDPM – Protecting SQL 2012 & above.

To protect SQL Server 2012 or SQL Server 2014, the following must be done.

• Login to SQL Server Management Studio

• Add the system account NTAuthority\System to the Sysadmin group on SQL Server
• DPM cannot protect databases that are stored on remote SMB stores
• Availability group replicas are configured as read-only
• When you perform an alternate location recovery for a partially contained database, you must ensure that the target SQL instance has the Contained Databases feature enabled

Hope the above illustration helps

 

 

DPM Reporting – An error has occurred during report processing

I hit an issue on launching the DPM reporting.  The DPM is functioning well except the reporting.  It’s the issue of the SQL Reporting settings.

It stated as :

An error has occurred during report processing. (rsProcessingAborted).
Query execution failed for dataset ‘DataSet2’. (rsErrorExecutingCommand)
Invalid object name ‘vw_DPM_Replica’.

Steps taken to resolve :

• Launch the Reporting Services Configuration Manager in the DPM

• Select the Report Manager URL on the left panel
• Click on the URL on the right panel

• Double-click on the DPMReporterDataSource

• The Connection string is missing.
• Minimize this screen

• Create a file call dbtest.udl on the desktop (it’s a build in Windows)
• Double click on it.

• Once the Data Link Properties launch, Select the server name (using the drop down)
• Use the Windows NT integrated security for the credential
• Select the database (using the drop down)
• Click Test Connection

• Click OK once it’s successful

• Right-click on the dbtest.udl and open with notepad

• Copy the text from “Intergrated ….. “till the end of the line

• Maximize the DPMReporterDataSource
• Paste the copied text into the Connection string.
• Click on Test Connection (may request to key in password again)
• Once successful, click Apply.

Launch the DPM reporting with no issue occurred.

keyword : DPM, SQL, SRSS, Reporting Services, rsErrorExecutingCommand, rsProcessingAborted, dataset, query execution failed, invalid object name

Azure Recovery Services–backup increased to 54TB limit

Earlier last month I shared on how to configure the DPM 2012 R2 with Azure Recovery (Backup Vault). 

Microsoft Azure recovery Services team has officially released the backup per protection group from 1.7TB limit and now to 54TB limit on 12th Aug 2015.

You need to have the Azure Recovery Services Agent 2.0.8715.0 or higher in order for the backup to exceed the limitation of 1.7TB.

The news release is here.

keynote : Azure limit, ASR, Azure Recovery Services, DPM, SCDPM, storage limit.backup limit

SQL Eval has Expired for SCVMM

I had an issue.  Someone installed the SQL as eval copy.  I tried to Start the Database but couldn’t.  It states as expired.

So there’s I’ve to work around.  Firstly I find the location of the Database.  e.g.
C:\Program Files\Microsoft SQL Server\MSSQL10_50.SYSPREPSQL\MSSQL\DATA

Copy both the DB out to a location as backup.

From the services of the VMM check which account is used to start the System Center Virtual Machine Manager. 
In this scenario is pcloud\vmmsvc

 

Then I uninstall the entire SQL and then reboot the VMM server.  Install a fresh new SQL (full license) into the VMM server.

After the installation I copied both the files back into the new SQL path e.g.
C:\Program Files\Microsoft SQL Server\MSSQL_10_50.MSSQLSERVER\MSSQL\DATA

I then launch the Microsoft SQL Server Management Studio.  Expand the Databases. 

Then <right-click>  on the Databases and select Attach …

Click Add …

Select the VirtualManagerDB.mdf from the location that I copied into earlier and click OK twice.

Expand the Security – Logins.  <Right-click> on the Logins, and select New Login ….

Add in the user that was use to start up the VMM Services (information services that was gathered earlier).  In this example is pcloud\vmmsvc.

<Right-click> on the particular user and select Properties.

In the Login Properties select User Mapping.

In the Users mapped to this login select VirtualManagerDB

In the Database role membership for VirtualManagerDB, select db_owner & public then click OK.

Once it’s done, launch the Virtual Machine Manager Console

Then it’s ready to go for administrating through the VMM Console.

Also thank you to both my colleagues, Law WF & Edmund Lim. Hope the steps help. 

keywords : Systems Center Virtual Machine Manager 2012, scvmm, vmm, SQL evaluation, SQL eval, expire SQL, SQL 2012.