my personal blog about systemcenter

All posts in SQL

Data Protection Manager 2012 R2 UR4 Support SQL 2014

Categories: Data Protection Manager, DPM, SQL
Comments Off on Data Protection Manager 2012 R2 UR4 Support SQL 2014

With the release of update rollup 4 for Data Protection Manager 2012 R2 , it is now supported to protect a remote SQL server running SQL 2014 (about time)

http://blogs.technet.com/b/dpm/archive/2014/10/29/protect-sql-server-2014-using-dpm-2012-r2.aspx

There are still some features that isnt supported to test and verify , v.next will support/require SQL 2014 as DPM database target but in 2012 R2 UR4 its protected data only

Install is pretty straight forware as usual

Push the agent , will require a reboot due to updated filter driver

clip_image002

After server have been reboottet verify that SYSTEM have sysadmin rights on the SQL server you want to protect

image

Create new protection group

image

Select Servers

image

browse the SQL instance , and select auto to ensure that all databases will be added

image

Name the protection protectoin group , in the demo setup there is no tape libarary so short term only

image

And a hourly backup

image

Sucess ! Smiley

image

and a few minutes later we now have a valid backup , ready for first restore test

Had a question today about the ability to recover the SQL master database if the SQL server wasnt operational.

To set the scene for the converation we did the following

Image

Installed the Data Protection Manager on the SQL 2012 server , created a brand new fresh and shiny protection group , added the SQL instance

Image

Created short term recovery this was after all just a test

Image

And a backup every hour kept for the last 5 days

 

Image

And as always with Data Protection Manager Sucess is an option :)

Image

And a few minutes later we now have a full backup of the SQL server

Image

And lets try to add the human factor

Image

Twice

Image

And after that we have a non functional SQL Server

 

Image

And as we can see the reason if lack of master databases

 

Image

DPM to the rescue , enter recovery select the master database

Image

Option One , Recover to original instance (otherwise restore to folder and copy the files manually)

 

Image

And leave database operational as we are not recovering from additional logs

 

Image

Verify server/files

Image

And 35 seconds later the database is recovered without incident

 

Image

Recovery is complete , SQL instance is restarted and we can fire the blogger that deleted the master database

With System Center 2012 SP1 the support to use SQL Server 2012 as a database for Data Protection Manager was added

The use the SQL Server 2012 to colocate DPM databases there are a few things that needs to be configured

 

 

image

image

SQL Reporting Services Need to be installed

 

image

SQL needs to run under a service account (not its against recommendations to use the same account on for each role but for testing it works great)

image

Just to be safe I always set the collation to “CPI_CI_AS” but honestly not sure if it’s a requirement

image

Adding the account that host SQL and the admin account I will install DPM with

image

And just default install of reporting services.

image

On the SQL server run the DPM Remote SQL Prep Installer

image

This only takes a few seconds after VC redist install

 

image

On the DPM server start the installer and select use existing instance and enter administrative permissions for the remote SQL server

image

and when the installer states that we need the requirement we can proceed

image

Location for database is greyed out as the DB is on the remote sql instance

image

And we need credentials for the reporting user

 

image

And the installer skips SQL Server install and jumps directly to tools and workstations

image

and a little bit later we are good to go

image

and we can see that the installer added the rights needed to the SQL instance

 

image

and DPM is ready for action.

 

Microsoft have released a update for data protection manager 2012 SP1 that support backup to Azure

The updates features is support for SQL based workloads and 120 days retention , the 120 days is a BIG feature enhancement

http://support.microsoft.com/kb/2779569

Description of an update rollup package that adds features to Windows Azure Online Backup in System Center 2012 SP1 DPM and in Windows Server 2012

This article describes an update rollup package that adds the following features to the Windows Azure Online Backup for Microsoft System Center 2012 Service Pack 1 (SP1) Data Protection Manager (DPM) and for a computer that is running Windows Server 2012:
This update improves the performance of Windows Azure Online Backup.
Windows Azure Online Backup support for a SQL Server data source in System Center 2012 SP1 DPM is available.
The retention range of Windows Azure Online Backup for System Center 2012 SP1 DPM is increased to support 120 recovery points

 

http://www.windowsazure.com/en-us/home/features/online-backup/ there is a 300gb trial available install guide here http://flemmingriis.com/?p=1103 the “old” installer needs to be installed before installing the upgrade

image

Verify that no jobs are running against Azure before starting the upgrade

image

And 16 seconds later we are ready to rock

 

 

image

And with the updated integrations we can now add SQL based workload
image

And select the Cloud option , as always we need to backup to disk before cloud so short term is a requirement

image

And another cool feature we can select what database we want protected with Azure

image

And 120 days very very cool Smiley , we still need long term for tape in most environments , but then there is room for new features later on.

 

.image

And we can create a recovery point manually to the cloud instead of having to wait until the schedule kicks in

image

and a short while later our data is moved to the cloud

My normal weekend procedure these days goes with baby sitting Virtual to Virtual converting from VMware to Hyper-V using Virtual Machine Manager 2012

I had a few servers that failed and for instead of trouble shooting I did a retry as the source servers was in dire need of being put down so I thought the error was due to that , but again after x hours the covert job through VMM failed again.

 

image

The Convert job starts without issues

image

But fails on disk 2

image 

Error 2909 , from the Virtual to Virtual Conversion , claiming that the file already exists , looking the target before job start shows no vhd files in the directory.

 

image

Looking at the source side I can see that there is a vmdk for the system drive that completes without error

image

And the data drive that fails.

The Error 2909 was due to the drives both being called test.vmdk as vmware don’t enforces different vmdk names if the files are located on different data stores.

So after changing the vmdk file name on the source I can convert the virtual machine from VMWARE to Hyper-V