Restore Sharepoint From Databases new server instance


  • Please, I hope somebody have done this before.

    I have a Commerce Server installation inside of SharePoint and a site that we are maintaining.

    We are currently moving hosting companies and that requires us to install new SharePoint and Commerce Server instances.

    The problem with this is that all the data that is encrypted in one server would be useless in the new server.  We tried to copy all the databases and change the webconfigs and keys to match the ones in the old server.  

    We kind of figured that it would not be that simple but it was worth giving it a shot.    

    Has anybody done this before? Or have some recommendations of how to move databases and data from one installation to a new one? 

    Notice it is not just a new SQL server is a new sharepoint installation with new sql server. 

    We use: 

    Sharepoint 2010 server

    Commerce Server 2009

    Sql Server 2008 R2

    Tuesday, April 10, 2012 4:16 PM


All replies

  • Hi Dan,

    I don't have any experience with Commerce Server so I can't comment on that... however, I understand you are trying to take an existing SharePoint Server environment and move the content to a new SharePoint farm, in a separate active directory. In short, you are going from one SharePoint Server(s), different SQL Server and different Active Directory Domain.

    At the end of the day, this won't be seamless... but all you really care about is the data, in the databases... I'd suggest you approach it this way (note these are your high level steps):

    1. Create a new SharePoint Farm in your new domain with you new SQL Server - build it properly, to best practice. There are lots of resources out there to help you with this - you could wizard this install but that is really only a good idea if you are demo'ing thr product. Otherwise, do it right. Todd Klindt provides some recent and good content here -
    2. Create your new web applications (likely matching the URL's you had previously I suspect) with dummy databases - make sure SharePoint works at these new URL's (with DNS setup right, etc.), temporary site collection, etc..  I.e. validate SharePoint is healthy before going further. Note, if you can find out if the previous web application used Claims instead of Classic Authentication, this would be useful to find out.  If you aren't sure, create new web applications as classic and worst case you can convert the web app to claims, not the other way around
    3. Once SharePoint it tickety-boo, detach the dummy database you had attached to the SharePoint Web Application (see: removing a database from a web application)
    4. Restore the database provided by the hosting provider (I'm assuming the database backup is healthy of course) to SQL. Ensure your SharePoint Admin Account and Farm account have full access to the database (Security, Logins, select the user and give them DBO)
    5. Attach the database to your web application - do the following from the SharePoint command shell - stsadm -o addcontentdb -url http://yourwebappurl - databasename NameOfTheRestoredSQLDatabase

    ... note, at this point, if it was the same domain, etc. life would probably just carry on. But in your case, your account/security descriptors are going to have no meaning with the restored content database, so you have a few more steps...

    1. You need to manage/be able to open this site collection(s). So, go into SharePoint Central Administration and under manage applications, choose Change Site Collection Administrators. Find your site collection and assign new site collection admins (it will have the old site collection admins there but they'll be red/squiggly underlined as SharePoint has no idea who they are anymore)...
    2. Once you can connect and view that your content is cool at your web application, as the site collection admin, you now just have the exercise of remapping all the user accounts to new accounts (if you have the same usernames in the new domain as the old, you can look up details for how to 'migrate user accounts' - otherwise you are looking at just doing a new reassignment of user accounts (and you can delete the old accounts from the site collection)

    That's it in a nutshell.  It will be a long night though ;)

    Hope that helps,


    Sean Wallbridge, SharePoint MVP | Victoria, BC | On The Web: | Blog:

    Wednesday, April 11, 2012 3:48 AM
  • I don't have experience with commerce server either, but one big improvement in SharePoint 2010 is you do not have to restore the configuration database because you can restore the farm configuration directly:
    Thursday, April 12, 2012 2:16 AM