<< Back To All Blogs
Using Data Protection Manager 2007 For Disaster Recovery on SharePoint
Tuesday, April 14th, 2009
I have spent a large amount of time in DPM 2007 lately as we are looking into possibly using this as our backup and recovery solution for SharePoint. There are not that many options out there that do not cost a large amount of money, and we are big fans of Microsoft products.
While setting up the Data Protection Agents on your SharePoint server(s) there are a few gotchas that stuck me and I figured I would share them:
1. Make sure that you have installed the VSS writer hotfix for all MOSS and WSS deployments, for all servers on the farm. This is very important and it won't work without it
2. It is confusing how the documentation explains to use the ConfigureSharepoint tool. Even when you install the DPM console tools it does not install this utility. Copying the utility executable also does not work. I ended up sharing the bin file on my actual DPM server machine, mounted the share as a drive letter, and ran ConfigureSharepoint from that mounted drive letter and everything worked smoothly.
3. Make sure that the domain user you specify when you run ConfigureSharePoint -EnableSharePointProtection is a member of the local SharePoint Farm Administrators group. This is normally named WSS_RESTRICTED_WPG. If you run this tool without the domain user being a member of the Farm Administrators Group it will actually not show anything any longer in the DPM Manager Server. If you ran that Manager before running ConfigureSharepoint it would have been showing a SharePoint backup option (but would have given you an error when you expanded it). This really confused me at first.
4. Ensure that you set Windows SharePoint Services VSS Writer to automatically start with the system. Do the same if you are backing up your SQL database with SQL Server VSS Writer.
Hopefully that will help you all with a few gotchas that stuck me for a few.
DPMin' Tom Out.
Fixing MOSS/WSS SharePoint errors with Alternate Access Mappings
Blocking A Specific Number from Calling Company Extensions in Avaya CM
Resolving ASP.NET Web.Config Inheritance
Restoring Specific Documents from a MOSS 2007 Content Database Backup
Tom said on Thursday, April 16th, 2009 @ 5:57 PM
Thanks for forwarding this onto your doc team. I am very happy to see you guys engaging so heavily in the community, it's a great thing when a company the size of Microsoft still has the time for the little people :).
Jason Buffington said on Thursday, April 16th, 2009 @ 2:28 PM
Nice post - and good finds.
I'm the PM for DPM - and will forward your notes to our doc's team
Add A Comment
Email Address: (not public, used to send notifications on further comments)
Enter the text above, except for the 1st and last character: