SharePoint 2010 Migrations

Real World Experiences

Pat Terry - ECM DeliveredBackground:

MCTS

Numerous successful deployments of MOSS 07, SharePoint 2010, Project Server, etc.  

Successful upgrades from earlier versions to SharePoint 2010.

Extensive technical and project management experience with large scale implementations of SharePoint and other ECM solutions (i.e. Open Text, interWoven, KnowledgeLake, etc.)

Enterprise Content Management Delivered• Focus includes:

• SharePoint2010• SharePoint as ECM solution (includes

scanning and imaging to SharePoint)• Office 365

• Partnerships with Microsoft and GoScan

Legacy SharePoint EnvironmentMoss 2007

On same Server as Domain ControllerCo-mingled with File Server and other

applicationsWindows 2003 R2

32 bit Sql Server 2005Started out as Small Business Server LAN

Migration/Upgrade GoalsMove MOSS 2007 to its own serverStabilize MOSS 2007 FarmMove SharePoint SQL components from

shared SQL 2005 server on 32 bit 2003 to new SQL 2008 server on 64 bit 2008 R2.

Build 2010 SharePoint FarmMigrate/Upgrade MOSS 2007 farm to

SharePoint 2010

ConsiderationsMigrating to new MOSS 07 WFE server

Insuring new WFE (Web Front End) joined to farm on same build for MOSS including Service Packs, Hotfixes, etc.

Confirm that all SharePoint services are replicated on new WFE

Moving Central Admin to new WFEAlternate Access Mappings and DNS settings

to be adjusted for new WFEShared Services Provider Confirm search settings and user profiles

Considerations (continued) • SharePoint SQL Migration/Upgrade

• SQL Server Name Change and going from 32 bit SQL 05 to 64 Bit SQL 08.

• SharePoint 2010 Farm Build/Prep for Migration

• Migration Questions

Move MOSS 2007 to its own server

Built a new temporary WFE (32 bit) and joined to MOSS farm.

Moved Central Admin and other services to the new box

Created a new SSPUpdated Alternate access mappings and DNS

to reference new WFE.. Removed old server from the Farm.

Migrate SharePoint SQL Requirement – Leave old 32 bit SQL server for other appsCreate a new 64 bit SQL server for SharePoint databases Question: How to address SQL server name change during the

migration process? Solution: Used a 32 bit swing box with the eventual name of the

new 64 bit serverMigrated SP databases to temporary “SQL Swing Server”Detach - Move - Attach affected databasesProvided an alias to SharePoint Farm pointing to “Swing

Server”Stabilize and test farm – left it running in this state for a

week

Tools used for SQL MigrationSwing Server (32 bit W2K3 with SQL 2005)

with new server name.MS SQL Client Config Utility (cliconfg.exe) to

connect to “Swing Server” and set alias to original SQL name to avoid issues with our MOSS 07 farm.

Migrate SQL Server 2005-32 to 2008-64Installed SQL2008 on new box – workgroupDetached and copied databases off “Swing SQL

Server” Took “Swing Server” out of the domainAdded SQL2008 Server to the domain with same

name as “Swing Server”Copied databases to the new serverAttached Databases – upgrade to SQL 2008

occurred during the attach processUpdated Alias, tested and allowed to run for 3-4

days.

Intermediate StatusMoss 2007 Farm successfully moved off DC

and ready for next step SP2010 migration.Updated config: Dedicated MOSS 2007 WFE 1 SQL Server 2008 Windows 2008 R2 with

new name.

Completed evening and weekend. No user disruption and no lost content.

Build 2010 SharePoint FarmNew Virtual Server – Windows 2008 R2

16 Gbytes RAM/C: approx 60 Gbytes/D: approx 100 Gbytes for logs and index files.

Office SharePoint Server 2010Pdf IfilterCreated a new SharePoint 2010 FarmCreated needed service applications, etc.Search, User Profile and Managed Metadata

required

Perform a Database Attach upgrade

Create any needed web applications

Delete the site collection and content database associated with the :80 web application if created by the wizard

Database Attach Upgrade (cont)Preupgrade check on MOSS 07 content: MOSS Service Pack 1 required for

preupgrade check utility Run test-spcontentdatabase on each of your

content databases to anticipate and document challenges

This will generate SharePoint preupgrade report

Roadmap for ID and cleanup migration issues

Note: This process is benign on existing MOSS content dbases.

PreUpgrade Report Sample

Database Attach Upgrade (cont)

Using SharePoint Powershell:Perform database attach upgrade for each

content database and each web applicationRun a full crawlTest and stabilize farmNote: We ran full backups on all the MOSS farm prior to

starting. Additionally, we made copies of content dbases and ran dbase attach upgrade on copies. MOSS farm still running “site collections read only” during upgrade for users

Post Upgrade ItemsSharePoint 2010 Visual Upgrade

Global or Site by Site?

Update Alternate Access Mappings and DNS.

User orientation and working with the ribbon bar.

Implementing a Search Center Page.

Questions and Answers

Contact InformationPat Terrypterry@ecmdelivered.comcell: 913-706-0146http://www.linkedin.com/in/pmterry

Search Center Tip

Search Center Tip