Friday, June 5, 2015

SharePoint 2007: How to Migrate to SharePoint 2010

Print this posting
Introduction

This posting consolidates my notes with respect to migrating a SharePoint 2007 farm to SharePoint 2010 using the database attach method.  It focuses only on content migration, not service application migration. The SharePoint 2010 web application is configured to use standard NTLM authentication and non-encrypted (HTTP).  This posting installs SharePoint 2010 onto Windows Server 2012; you'll need the May 1, 2014, SharePoint 2010 SP2 slipstream media for this. It also employs SQL Server 2012.

Procedure
  1. Verify/create SharePoint 2010 service accounts.
  2. Build SharePoint Server 2010 farm (destination farm) on Windows Server 2012.
  3. On destination farm, create new web application NTLM and site collection.
  4. On source farm, execute STSADM.exe –o preupgradecheck and resolve any issues that are found.
  5. On source farm, set content databases to read-only.
  6. On source farm, perform content backup.
  7. On source farm, copy SharePoint Server 2007 farm content database backup to 2010 farm.
  8. Restore 2007 database to 2010 farm database server.
  9. In SSMS, map SharePoint Setup User Admin account as DBO of restored 2007 content database.
  10. Verify database read-only property is false.
  11. Remove 2010 web application content database.  You will need to rename the content database files (data and log) if the database you are migrating has the same file names.
  12. Mount 2007 content database to 2010 web application.
  13. Optional: initiate Visual Upgrade on all sites in site collection.
References
  1. SharePoint 2010 SP2 and Windows Server 2012 R2
  2. SharePoint 2010: How to install onto Windows Server 2012
  3. Upgrade from Office SharePoint Server 2007 or Windows SharePoint Services 3.0 to SharePoint Server 2013 or SharePoint Foundation 2013
  4. Migrate from classic-mode to claims-based authentication in SharePoint 2013
  5. SharePoint 2010 Claims: Migrating Windows users to Claims users on existing sharepoint site
  6. Migrate from MOSS 2007 to SharePoint 2010 - Step by Step
  7. Perform a database attach upgrade to SharePoint Server 2010
  8. Checklist for database attach upgrade (SharePoint Server 2010)
  9. Upgrade Worksheet for SharePoint 2010 Products
  10. SharePoint 2013: Service Account Configurations and Permissions
  11. Error lors de l’installation des Office Web Apps 2010 sur Windows 7
  12. SharePoint 2010: Install on Windows Server 8 Beta
  13. SharePoint 2010 on Windows Server 2012!
  14. Installing SharePoint 2010 and SQL Server 2012 on Windows Server 2012 Release Preview
  15. Upgrade and migration: Stsadm operations (Windows SharePoint Services)
Notes
  • Where is stsadm.exe?: The stsadm command can be found here (default): C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN.
  • 2010 SP2 Slipstream ISO file name: Need to use sw_dvd5_sharepoint_server_2010w_sp2.2_64bit_english_mlf_x19-65035.iso to perform this installation.  This version is available through your Microsoft Volume Licensing or MSDN subscription.
  • If the (source) databases you are migrating have the same file names as the ones already in the 2010 farm (destination), detaching the destination databases is not enough in this case.  You must also rename the destination database files.  Otherwise, you will encounter errors like the following during the restore database process:
    TITLE: Microsoft SQL Server Management Studio
    ------------------------------
    Restore of database '[content database name]' failed.
    (Microsoft.SqlServer.Management.RelationalEngineTasks)
    ------------------------------
    ADDITIONAL INFORMATION:
    System.Data.SqlClient.SqlError: File "[source content database file]" cannot 
    be restored over the existing "C:\Program Files\Microsoft SQL 
    Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\[destination content database file].mdf". 
    Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing 
    files, or WITH MOVE to identify an alternate location. 
    (Microsoft.SqlServer.SmoExtended)
    

No comments: