my personal blog about systemcenter

Archive for November, 2011

 

One of the great features of Data Protection Manager is the ability for DPM Admins to delegate part of the restore process to SQL Database Administrators without having to give them the keys to the castle (aka DPM server)

This ensures that we DBA’s can restores databases with having to wait for the DPM administrator having time to help , personally this feature have helped me convince most DBA that its not a problem that DPM handles the backup as they can do restore when needed.

image

In the Data Protection Manager Console start “Self Service Recovery”

image

Create Role , security is role based in Data Protection Manager 2012

image

I created a SQLDBA and a user group containing the user, and added that the role to the role , if other people needs rights to restore later on we can just add them to the group

image

We then need to add the instance name, and database name if needed , empty field means all databases can be restored, but from a security point of view we can delegate rights to restore a single database  , a browse button would have been nice for both group and server/database

image

Default recovery target is source server but we are not allowed to override source database

image

Or we can select a remote server , this will enable a DBA to move a database from protection to test if needed withouth DPM admin interaction and without having to find space for .bak files.

image

We then need to install the DPM Self Service Recovery Tool located on the DPM install media

image

image

image

When starting the Data Protection Manager Self Service Recovery Tool for the first time we need to connect to the DPM server

image

We can the in the drop down select the server we want to restore from and what database

image

And what recovery point to we to restore from

image

In this case restore to other servers was disabled so we can only recovery to a network drive

image

DPM can only recover from less express full backup so a recovery is needed after last express full backup you still need to call the DPM admin

image

Enter a destination of the restored files

image

And we are ready to recover the database

image

image

And on the DPM console we can see that the recovery job have completed

image

And on our restore target we can see the database files restored

 

repost from scug.dk

One of the many new features in DPM2012 is the ability to use Generic Data Source Support where application owners can provide VSS support so Data Protection Manager can make a backup of the application, Microsoft have provided a writer for VMM 2012 that protect the database, hopefully more complex applications can be backed up this way in the future imagine having a writer for BizTalk that will protect all needed items , or Oracle / Domino and other 3rd party applications.

For a license point of view i don’t know if it require a enterprise ML or a standard one so protection VMM wouldn’t require a Enterprise ML for SQL , but time will tell on that one.

 

 

image

Microsoft have provided a new VSS writer for Virtual Machine Manager 2012 that Data Protection Manager can use

 

 

image

 

So on our protection group we can select the VMM Express Writer

image

Setup the protection group

 

image

And as we are used to with DPM Success !

image

On the Virtual Machine Manager we can see that the VSS writer now calls SQL and create a backup of the configuration database

image

And before we break anything we verify that the backup is Complete and OK.

 

image

Lets detach

image

and then delete the database in the file system

image

And verify that the Virtual Machine Manager is “broken”

 

image

Go into recovery select latest recovery point for the VMM Backup

image

And we can see that we want to recover the VirtualManagerDB

image

And as we have broken the running install we will replace/overwrite with recovery to original instance

image

And we can see the list of items for the recovery

image

and 20 seconds later we have Success

image

And in the eventlog we can see that the database have been restored

image

And SQL agrees

image

Then we close and open the Virtual Machine Manager interface again.

image

Success ! no overcast clouds are still here , nice detail that VMM recovers without service restart or anything.

 

This will be a series of blog posts mostly serving as a reminder for myself on how and why the demo setup was build.

The purpose of the setup is to have a static enviroment that is high performing and always will be able to demo system center products , and to have a playground for testing new version and having a place to experiment outside of production enviroments.

image

The demo setup currently contains 4 servers dedicated to HyperV and one for ESX/XEN providing legacy support for Virtual Machine Manager integration testing.

Storage is currently a single point of failure one server is running Microsoft ISCSI 3.2 (pending 3.3) hosting 15*300gb and 6*146gb , with a quad port 1gb for iscsi support so each HyperV have a dedicated nic for storage access , again currently due to lack of hardware a single point of failure.

There is also one server dedicated for Data Protection Manager , that have internal drives to provide protection , this mainly provide backup of the demo setup and wont be used for experimenting there will be created virtual Data Protection Manager Servers for that.

Networking is one layer 3 switch

On HV01 and HV02 there are a domain controller running outside of the cluster to ensure that the cluster can get up and running again after a power failure or a shutdown

On HV01 there are also a jump host installed installed locally so if i somehow manage to kill the Threat Managment Gateway i wont be locked out and would have to drive to the datacenter to be able to continue working (not that i ever needed that Smiley, der blinker…right )

image

Microsoft ISCSI Server hosting Qourum Lun and 6 data luns , the “larger” of the drives is each a 3disk raid 5 , and the last drive is 6 smaller drives in a raid5 , this was mainly done to ensure that one VM couldnt take all IO on one LUN but the offset is cost in drives

Only “complaint” about ISCSI Server is the lack of hardware vss support for test Data Protection Manager with HyperV but then again you cant get everything with a free product.

So first few steps  , getting firmware updated to Virtual Machine Manager is able to control the hardware , installing base OS , installing Domain Controller , Setting up Clustering and Virtual Machine Manager , then the baseline is in place for the real “work” to begin.