I wanted to take a minute and talk about a really cool new feature of SharePoint 2010 relating to backups – Granular Restores. While doing some test migrations from MOSS 2007 to SharePoint 2010, we needed to choose the best method to selectively move data from an old site to a new site.
In SharePoint 2010, you have the ability to restore content (down to the list level) from an unattached SQL database. How cool is that! Here’s the new Backup and Restore options in Central Admin:
Performing a granular restore has 2 main steps:
Let’s look at a couple situations on how this might work.
You’re already running SharePoint 2010, and you’re recovering data from a backup. You have restored an existing 2010 database in SQL to another name and is online, but it is not attached to a SharePoint web application. How do I get my data?
Pick the site collection, site and/or list you want to restore. Specify a filename (local or UNC) with .cmp, if you want all of security information, and what versions of the content you want, and click Export. It looks like this:
Import-spweb -identity http://intranet.contoso.com/projects -path c:\backups\sharedocuments.cmp
That’s it! Now, what if you wanted to move data from one site to another that was online but on different networks? Well then you could skip down to step 3 and run your export, then powershell to restore the data. What if the data came from WSS 3.0 or MOSS 2007 as part of an upgrade? Well there are a couple more steps for that.
You are upgrading to SharePoint 2010, but as part of a phased migration. The content in your existing site is very disorganized, and you want to stand up pieces as you go. This prevents you from performing an in-upgrade upgrade (I wouldn’t recommend anyway), or a db-attached method for the whole site collection. You’re doing a more hybrid approach. We will perform the same steps as above, however we need to get the content database upgraded to 2010 format. How do we do that? First we’ll assume you’ve already built a new SharePoint 2010 farm on new shiny hardware, created your service applications, and a web application.
NOTE: This is not a blog on upgrades. Be sure to meet prereqs for upgrades, like installing SP2 and running stsadm preupgradecheck. You need to be sure you have no upgrade blocking missing features.
Mount-SPContentDatabase -name wss_content_2007 -webapplication http://sp2010webapp
This mounts the database and attaches it to the web application http://sp2010webapp. While it runs, it will show you a progress in percent complete that it is upgrading. If the upgrade fails at this time, you can run the Upgrade-SPContentDatabase PS command to retry.
You have a couple options here. You can browse to the site and see what it looks like, and copy data out that way. Or, you can detach it from the web application (Dismount-SPContentDatabase in PS) and run the restore from unattached content database, then export it and restore it. Up to you.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.