my personal blog about systemcenter

Archive for September, 2011

repost from scug.dk

This post will cover the disaster recovery of Data Protection Manager Server , there are a few ground rules that needs to be followed.

NEVER ever loose your tapes (duh)

ALWAYS keep a backup of the configuration database

ALWAYS keep a domain controller alive , and keep a backup of a domain controller with Windows Backup so it can be restored if everything else is gone.

clip_image001

If we loose our data protection manager server due to hardware issues flood earthquake or fonzie attack we need always to keep our data on tape a copy on a different Data Protection Manager with the DPM to DPM backup feature.

In this scenario we will kill the Data Protection Manager server and recover data from tape only, i use the excellent filesteamer from http://www.cristalink.com awesome for testing and for long term recovery to disk.

clip_image002

DPM uninstalled and all data deleted, remember if you need to rebuild the operating system you need to call the server the same as before the rebuild.

clip_image003

We then need to start the installation of Data Protection Manager

clip_image004

This setup used the local sql database so for testing we will create a new sql instance for the Data Protection Manager Server

clip_image005

And we will use the default file paths for install

clip_image006

After install we don’t have any recovery points as all our data is located on tape and we have lost our configuration database

clip_image007

Go to Management and Libraries

clip_image008

Select Rescan for Data Protection Manager to scan for tape devices

clip_image009

Yes please.

clip_image010

When the tape library is connected after rescan we can see the tapes but not what’s on them

clip_image011

We then need to perform a detailed inventory

clip_image012

After the detailed inventory the tapes now shows as imported with label the tapes was created with

clip_image013

If you know what tape the data protection manager configuration database is on in the newest version run the “Recatalog imported media”

clip_image014

Yes please , this will take time

clip_image015

But very fast on a test setup with a virtual tape library

clip_image016

We can then see the Data Protection Manger server and recovery points for the configuration database

clip_image017

Data Protection Manager cant restores its own database directly so it needs to be restored to a network location

clip_image018

And we can only restore locally as we have no agents connected to the Data Protection Manager server (but we need to db. locally)

clip_image019

Here we will just restore the Data Protection Manager configuration database

clip_image020

And Data Protection Managers trade mark “Successful” as usual clip_image021

clip_image022

There are different ways to connect the database i prefer just to stop all Data Protection Manager services

clip_image023

Detach the database from our clean install

clip_image024

Copy the database files from the restore to C:restore (example)

clip_image025

Attach the database files

clip_image026

And reboot the data protection manager server

clip_image027

After reboot we can now see that Data Protection Manager knows the tapes

clip_image028

And the agents is connected again and we can restore from multiple sources.

There is some housekeeping that needs to be run after this but this will get you up and running and start restoring data

repost from : scug.dk

Data Protection Manager 2010 can protect Hyper-V guests with backup from either the guests or from the Hyper-V Cluster.

 

image

We have a protection group for this server in the cluster so we don’t have to worry about what hosts the guest is running on DPM will protect the the guest no matter what cluster node its running on.

image

In our recovery mode we can see the protected guests we able to restore

 

image

We are able to recover the whole machine or drill down one level and recovery a vhd to a network folder

 

image

If we drill down further than the vhd file we are able to recovery single items , however this requires that the DPM host is able to run Hyper-V

 

image

So we will make a quick jump to role services and installer Hyper-V so when planning for a new backup setup keep in mind that the hardware will need to run Hyper-V but then again if it’s a new setup its very hard not to buy a server that will run Hyper-V

image

No network bindings are required to keep the ability to restore single files.

image

and its time to reboot.

image

and we should be ready for our single file restore from Hyper-V guests

image

and with Hyper-V role installed we can drill down to a single file

image

and we are ready to restore the file

 

image

Single files can only be recovered to a network share when backed up though the Hyper-V integration , hopefully in the future we will be able to restore to source directly.

 

 

image

We can however restore over the network to our original source , but a “restore to original path” option would be nice

 

image

and we ready to restore

image

and after a short wait the job is complete and we should be able to see data on our source

image

and we got our data back.

Hyper-V and Data Protection Manager is a very powerful combination fast safe backup with VSS and easy restore of whole machines and even single items.

 

repost from : scug.dk

There is one thing that cant be said to many times about Data Protection Manager (regardless of version) ALWAYS backup the configuration database and when you have created one backup create another one.

DPMBackup.exe this can be schedules with windows task scheduler to create backup and then move of the Data Protection Manager server so if there is a hardware failure you will be able to recovery the database fast and start restoring data.

DPMBackup –db –targetlocation C:DPM will create a backup of the local database instance and place the bak file in C:DPM

clip_image001

clip_image002

The DPMBackup calls SQL and creates a regular SQL to file backup.

clip_image003

Or you can on the locally Data Protection Server select the databases and place then in a regular protection group , you need to ensure that to goes to tape on a regular basis.

clip_image004

If possible i prefer to add one additional Data Protection Manager and use that to protect other Data Protection Managers Configuration Databases , so push a agent to the Data Protection Server

clip_image005

And add the SQL database

clip_image006

and set a retention range that fits your environment , short retention should be fine this is only to help if the database gets corrupt or the Data Protection Server vanishes into thin air.

 

repost from : scug.dk

One of the new features in Data Protection Manager 2012 Beta 2 is the Central Console based on Operations Manager 2007/2012 , this have enhanced the feature set from the old management pack to include direct links to the Data Protection Manager servers though the DPM Remote Administration and filters and common tasks for day to day operation of Data Protection Manager.

This blog post will cover the basics of the installation and features , if time permits a update will follow with the Service Level integration where we can only get alerts if backup fails over a period of time, so a reboot that will cause a job to fail wont raise a error if the following jobs complete without errors , this will reduce the signal/noise level and help report back to the business side of view.

This is in my opinion a very strong feature giving total overview of your Microsoft environment and is a must install if you have the Operation Manager license.

 

 

 

image

Installation is as with all of Data Protection Manager very fast and easy , so on the Operations Manager server start the installer and select DPM Central Console

 

image

Install Central Console Server and Client Side Components

 

image

Let the installer do it magic for a short while.

image

And then import the management packs on the Operations Manager , note that the Management Packs is located in Microsoft DPM not Microsoft Data Protection Manager

image

Import the management pack

image

Success

image

And we can see the Data Protection Manager 2012 views and folders being created

 

 

image

The management pack for Data Protection Manager have a discovery targeted at windows servers that runs every 12 hours looking for new seed servers (that have Data Protection Manager Server installed)

 

image

Once a day at 12am the detailed discovery runs the Data Protection Server versions and then twice a day all other discovery runs pr default.

So if a new server is being added to the Data Protection Manager server it will take some time before they show up in the Operations Manager Console , all discoveries can be overridden if you want faster discovery

 

 

image

If a error occurs (here a database have been forced offline) we can see the monitor causing the alert and troubleshooting tips , if we select troubleshoot to get additional information

image

And then the new Data Protection Manager console opens with a filtered view so we only get the information we need

 

image

If operations want to start a backup job then can select the datasource and “Create Recovery Point”

 

imageimage

There is currently only disks on the test setup so we only have the options to create short term , and after creation we can open the console and look at the job

 

image

And again the Operations Manager Console opens the Data Protection Manager Remote Console and sets the correct filter so we only get the information we need

 

repost from : scug.dk

One of the new features in Data Protection Manager 2012 is the improvements in administration , this is the basic part install the Remote Administration and “point” to one Data Protection Manager Server at a time , handy for smaller environments where you don’t want to logon to the Data Protection Manager server or switches between multiple for administrator , again this is a very straight forward setup but i try to show a feature at a time even if its very simple clip_image001

clip_image002

Install DPM Remote Administrator

clip_image003

45 seconds later we are ready to use the console

clip_image004

And we can connect to the server we prefer , note that SQL needs to be open in the inbound firewall on the Data Protection Manager server you are connecting to

clip_image005

And there is full access to the Data Protection Manager interface

clip_image006

And you can also push agents from the new Remote Administration feature.