Sharepoint 2010 protection in DPM 2010: Part 3
Hey All,
This is part 3 of our Sharepoint protection in DPM 2010 serie and also the last part.
You can find the other two parts here:
http://scug.be/blogs/scdpm/archive/2010/03/11/sharepoint-2010-protection-in-dpm-2010-part-1.aspx
http://scug.be/blogs/scdpm/archive/2010/03/12/sharepoint-2010-protection-in-dpm-2010-part-2.aspx
Item-level recovery
So what is Item-level recovery? Item-level recovery means that you can recover a single document, list, page or whatever. While it was already possible in Sharepoint 2007 and DPM 2007, you needed a sharepoint recovery farm to do this. And the recovery farm had to be at the exact level as the production farm. If you hadn’t had this farm, then you could only recover a complete farm or site collection.
With Sharepoint 2010 and DPM 2010, you can do item-level recovery without the need of a recovery farm.
Every 24 hours, DPM will create a catalogue of the Sharepoint environment in order to allow the item-level recovery. In case you need to do an item-level recovery before the 24 hour (such as demo-purposes :-)) you can run the following powershell commands to force this task
$pg = Get-ProtectionGroup <dpmservername>
$ds = Get-Datasource $pg[index1] (index1 points to the protection where
SharePoint is protected, to see all protection groups try $pg)
Start-CreateCatalog $ds[index2] (index2 points to the SharePoint datasource,
to see all datasources try $ds)
Example
In my demo environment, I have a sharepoint farm running which is the view you will get after a basic installation with one site configured
As you can see in the screenshot, I have modified the home page a bit. Now I’m going to modify it again
Of course, now I realize I made a mistake, don’t have a clue what it used to be before and I call IT to restore :-)
So IT will start from the DPM UI
As you can see, In the recovery pane, I can see the sharepoint farm and some items under there. I need to recover a page, so I need to be in the WSS Content
After some drilling down, I reached the page that need to be recovered. I select this page, also select the time from which I want to recover and start a recovery.
So here are my options.
- Recover to original site
- Recover to alternate site
- Export selected items into a network folder (not possible in this case)
- to tape
In our case, I’m going to recover to the original site
Now I get the option to do a recovery without or with a recovery farm. Since the purpose of today was to demonstrate it without the recovery farm…
Now you need to make some decisions. The first you need to decide is the SQL instance that you want to use to recover temporarily the content database where the item is located. You can use the same SQL instance as where the production farm is located, but this will give some additional load so if that is not an option, choose another SQL instance if possible.
The second choice you need to make is a location where the database can be temporarily copied to. This can be any volume or share that you want, but you need to have enough space free to copy the entire database to that location.
Next screen, you will need to give again a file location for the temporary location of the item that you want to recover. This has to be on a front-end web server so that the item can be inserted from there into the sharepoint farm.
Again some options in the next screen. the security that you want to apply, bandwidth throttling if necessary, SAN recovery if that is supported and a notification if you have configured email notification
Finally you will receive the summary.
And here the recovery is busy. You can close this window and follow the progress in the jobs pane.
And here you can see that the recovery is successful.
Now when I switch back to the sharepoint farm, you can see that my original page is restored
That’s it
Cheers,
Mike