my personal blog about systemcenter

Archive for October, 2011


repost from

One highly requested feature is the ability to backup and restore SharePoint server , Microsoft have improved their SharePoint support in Data Protection Manager 2012 and added support for single item level recovery without having to restore the whole content database this will give a faster recovery.

The procedure for creating the backup haven’t changed from DPM2010 and i can highly recommend Mike Resseler’s 3 step blog post with setting up the 2010 part

Current limitations as pr beta 2 (subject to change)

· Item-level recovery for items in Filestream databases will not be optimized.

· Tape recovery will not be optimized.

· DPM does not support item-level recovery for SharePoint sites using Variations. For more information about Variations, see Variations overview. beta2 and documentation download


On the SharePoint server after DPM Agent Installation , run ConfigureSharepoint.exe –EnableSharepointProtection , this will prompt you for a account that is SharePoint Administrator


Create a protection group and add the SharePoint install (here everything is located on one server) and let the first backup complete


DPM = Success clip_image004


DPM will index the SharePoint content once a day , so there can be some delay in restore selection showing all content this can be forced with

get-ProtectionGroup dpm10.demo.local |get-datasource |where-object {$_.type –like “*SharePoint*”} | start-createcatalog , this will index the backup


If we then delete the document


then we can go into DPM and restore the item


When we select recovery



Since the original farm is running we will Recover without the using recovery farm


The new party trick is that DPM2012 will mount the content database from the replica on the Data Protection Manager server, this will save a significant amount of data transfer , but require that the replica being recovered from is located on disk (not sure if that will change as we go closer to RTM)



And we have our document back.




We can then on the SharePoint Server see that DPM have attached a database to the local instance and then run the export / import commands on SharePoint to recovery the data, if we are fast enough we can see the database being mounted over the network to the DPM server.

repost from :


Had a backup error with DPM 2010 against Exchange 2010 SP1 (issue was there before sp1 also) where no matter what we did Replica ended up inconsistent

Database backup completed but as soon as log backup started DPM stopped and the replica turned inconsistent

the mailbox server posted Event 914 Information Store (5352) The surrogate backup by Server has stopped with error 0xFFFFFFFF.

DPM Error Log

214C    17B4    10/05    11:52:05.133    03    clusterutil.cpp(2144)    [000000000486E540]    6A4EF04B-3B3A-452E-880A-AD3D2DF27FBA    WARNING    Failed: Hr: = [0x8007001f] Either the volume ?Volume{5a396542-a6be-11df-8ce6-18a9055b001a} is offline or the volume is not a clustered disk.
214C    17B4    10/05    11:52:05.133    31    vssfilereadhelper.cpp(883)        6A4EF04B-3B3A-452E-880A-AD3D2DF27FBA    NORMAL    ssLocalVolumeGuid = [?Volume{5a396542-a6be-11df-8ce6-18a9055b001a}], ssClusterVolGuid=[?Volume{5a396542-a6be-11df-8ce6-18a9055b001a}]
214C    17B4    10/05    11:52:05.133    18    readeriterator.cpp(108)    [00000000065CB240]    6A4EF04B-3B3A-452E-880A-AD3D2DF27FBA    NORMAL    CFileReaderIterator:AddIncludeFiles(filepath:L:Log XXX A-E, filespec:E02.chk, snapshotpath:?GLOBALROOTDeviceHarddiskVolumeShadowCopy9Log XXX A-E) called


Notice the path on the Log Files for Exchange

[PS] C:Windowssystem32>get-mailboxdatabase -Identity “xxx a-e” | fl LogFolderPath,edbfilepath

LogFolderPath : L:Log xxx A-E
EdbFilePath   : L:Databasexxx A-E xxx A-E.edb


The mailbox database in question was created with a space before the file location , that works with Exchange (amazingly enough”) but it breaks backup

So create new mailbox database without space and move content was our solution to that issue.


repost from :


One of the great features in Data Protection Manager is the ability to protect virtual machines without having to install agents, this will though Hyper-V and VSS create a backup of the virtual machine.

This is one of the many “smaller” features that completes the systemcenter suite of products , Hyper V and Virtual Machine Manager enables flexible automates virtualization and Data Protection Manager enables best of class backup of Windows Guests in the same Hyper-V Cluster.

Just one more reason to evaluate Hyper-V , Virtual Machine Manager and Data Protection Manager


First we need to make sure that we have the DPM agent on all our Hyper-V Hosts so we can protect resources in a cluster (the same feature set is now available in DPM 2012 for stand alone hyper-v hosts.


Create a Protection Group and browse though the cluster to the resource you want to protect.


Setup protection goals and transfer the data for the first backup


and lets transfer some data to the guest


And head back into the Data Protection Manager and Create Recovery Point


and Create Recovery Point for Short Term Protection


and or backup is running


and we can see that a backup will transfer the data moved into the guest instead of a full copy of the guest (this is new on stand alone hosts)


And we can see our VHD file for the guest in our recovery options and we are able to drill and and restore individual items if needed