ofc304 moss upgrade and migration
DESCRIPTION
From TechED 2007 (New Zealand)TRANSCRIPT
OFC304
Microsoft Windows SharePoint Services and
Microsoft SharePoint Portal Server 2003 Upgrade and Migration
(Level 300)
Chandima Kulathilake (Microsoft MVP - Microsoft Office SharePoint Server)http://www.chandima.net/Blog/
Solutions ConsultantProvoke Solutionshttp://www.provoke.co.nz
Upgrade Preparation PRESCAN and Disk Considerations
Upgrade Methods and OptionsIn-Place, Gradual and Content DB Migration
Post-Upgrade ConsiderationsCustomizations, Content
Partner Upgrade Tools
Summary
Q & A
Session Objectives and Agenda
Upgrade/Migration Path
Content ManagementServer 2002 Microsoft Office
SharePoint Server 2007
Windows SharePointServices 3.0
SharePoint PortalServer 2003
Windows SharePointServices 2.0
Preparing for Upgrade
Scope and plan your upgrade Review Hardware End of Life, plan for upgrade capacity disk space, memory, processorTest your upgrade and estimate your upgrade duration
Review customizations Keep or decommission customizations
CleanupRemove orphans, increase close quotas, remove locks
Service offeringRedesign, training, communication plan
Prerequisites
Do a backup (SQL or STSADM) Make sure you know how to recover from backup
Get all SharePoint servers to Service Pack 2Use SPSiteManager from SharePoint Utility Suite v2.5 with the -analyze option to find anywhere you violate the capacity guidelines
http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724
Run prescan.exe early and repeat as necessary
PRESCAN IS YOUR FRIEND!
Running Prescan.exe
SharePoint Server: prescan.exe /c preupgradescanconfig.xml /allWindows SharePoint Services: prescan.exe /allPrescan Log and Summary created in \%temp%\
What Will Prescan find?
Sites based on site templates: Site Template Upgrade Kithttp://www.microsoft.com/downloads/details.aspx?FamilyID=a70bd8f8-a0f0-4d00-9010-8e40b7c98f68&displaylang=en
Sites based on custom site definitionsUn-ghosted pagesOrphaned objectsCustom Web PartsSites that need language packs
Prescan
Example of good Prescan results07/19/2006 17:17:01 Scan finished without failure07/19/2006 17:17:01 Number of sites skipped (already scanned): 007/19/2006 17:17:01 Number of sites scanned: 107/19/2006 17:17:01 Number of broken sites: 007/19/2006 17:17:01 Number of webs scanned: 1307/19/2006 17:17:01 Number of broken webs: 007/19/2006 17:17:01 Number of webs using custom template: 007/19/2006 17:17:01 Number of pages scanned: 007/19/2006 17:17:01 Number of unghosted pages: 63
Issues Found with Prescan?
Site/List not scanned error at the end of the logSolution: Post-SP2 Hotfix
UpdateListSchemaInAllWebs() Method not foundSolution: Install SP2
Virtual server is not in a ready stateSolution: Run it against v2 Virtual server
Great resource for errors and resolutionshttp://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx
Core Upgrade Methods
In-Place Upgrade
Gradual Upgrade: Side by Side Upgrade
Content DB Migration: Upgrade Into Separate Farm
In Place Upgrade
ProsSimple and fast upgradeBest for smaller or non-production environments
ConsEnvironment offline during upgradeRiskier in large environmentsUpgrade fails if it encounters errors; -fix then rerun
Not recommended for most deploymentsEven for customers whose production environment is perfect for this scenario, I still recommend gradual method. Why? Lack of flexibility and recoverability
Database Mapping
V2 Config DB
V2 Content DBs
V2 Search and User Profiles DBs
V3 Config DB
V3 Content DBs
SSP DBSearch DB
Gradual Upgrade
ProsOld and new SharePoint versions run in parallelAllows upgrade with minimal downtime
Only the site collection you are upgrading is unavailable
Can roll back upgrades per site collection
ConsRedirector could cause user confusion
Uses URL redirects which aren’t compatible with Microsoft Office and most other applications
Additional impact from two SharePoint versionsRequires lots of extra SQL storage space
SQL Instance
WSS Farm
WSS 2003Web App
Gradual Upgrade Process
Temp ConfigConfig Content Content
WSS 2007Web App
http://WSSoldhttp://WSS http://
WSS
Gradual Upgrade URL Redirection
Current URL: http://portal.company.comDuring upgrade, define temporary URL
http://portal.company.com:8080 or http://temp-portal.company.com
All v2 content moved to temporary URLv3 automatically redirects requests to temp URL using 302 redirectsAs each site collection is upgraded v3 content is placed at current URLv2 content still available at temp URL
Gradual Upgrade
On existing hardware, install SP2, .NET Framework 3.0, then run PrescanPrepare URL Redirect DomainInstall Binaries and Choose Gradual Upgrade optionRun Configuration Wizard to setup a new farm
Install Language Packs
Deploy Upgrade Definition, Site Definition and Feature FilesDeploy Custom Web Part Packages and any other custom code (only if in Bin directory)
Upgrade steps
Gradual Upgrade
Review log files and resolve any issuesRepeat setup and upgrade on each server in the farmStart content upgrade thru UI or stsadmReview your upgraded content
If customized sites, reset pages to 2007 site definition versionsFix issues and reapply customizations using SharePoint DesignerIf upgrade result is undesirable, revert to 2003 site
Upgrade steps
Gradual Upgrade
When upgrade result is undesirable, “revert” deletes 2007and resets redirect to 2003Confirm 2003 site still exists before reverting to itRevert to 2003 via UI or command line
UI: Select Sites for Upgrade > Revert SiteCommand line: stsadm –o upgrade –revert
Once complete, re-upgrade originalUse SharePoint Designer to merge changes from “fixed”and re-upgraded versions
Revert to 2003
Gradual Upgrade
Business/Customer approvalRemoves gradual upgrade redirectorYou can remove SharePoint 2003 afterwardsYou can still upgrade using database attach method
Finalize Upgrade
Gradual Upgrade
Works best for staging environmentEnvironments with heavy customizationsRecommended for large databases and site collectionsUpgrade a subset of site collections only Environments requiring minimal migration window
DEMO – Gradual Upgrade!
Scenarios
Content DB Attach Upgrade
ProsFast upgrade methodBest option if you have 1000s of site collections
ConsYou must redeploy custom configuration
Install Web Parts
Define inclusion rules
Setup search and related components
Note: This does still require Prescan. Required for scalable hosting mode/account creation mode, and host header mode deployments
2003 Farm 2007 Farm
2003Content
2007Content
2007Config
2003Config
– SQL CPU– SQL Disk I/O
SQL Server
Content DB Migration
2003Content
Content DB Migration Steps
Create new 2007 farm on clean hardwareInstall prerequisitesConfigure farm-level settingsCreate a new Web application for each 2007 virtual server
Manually re-apply configuration settingsEnsure all inclusions re-created in 2007 (required)Deploy Upgrade Definition, Site Definition and Feature FilesDeploy custom Web Parts to GAC or BIN
Content DB Migration Steps
Run Prescan on farm or Web application and correct any issuesBack up 2003 content database using SQLRestore backup to copy in 2007 farmAdd content DB to Web application via command line
Ensure root site included in first database
stsadm –o addcontentdb
Upgrade triggers automatically, runs until it completes
For large databases, command line preferable
Review log files for any issues
Repeat for all additional content and search/user profile databasesstsadm –o restoressp
Continued
Content DB Migration
Moving to new hardware or a new architecture Customers who need to maximize upgrade throughputRequired for Scalable Hosting Mode or Active Directory Account Creation ModeRecommended for large farms
Scenarios
In-Place Gradual DB Attach
Pros
Simple
Uses existing hardware
Provides granularity
Provides revert back option
Reduces user impact
Uses existing hardware
Upgrade to new farm
Existing, 2003, farm not affected
Cons
Entire farm offline during upgrade
No revert back option
Failure will stop upgrade
Hardware-intensive, memory and storage
URL Redirects during upgrade
Performance impact on 2003 farm
WSS Scalable Hosting mode not supported
Complex, many manual steps
Requires new farm an up to double storage
Scenarios Dev/Test platforms
Medium, large farms
Customized environments
Large databases and site collections
New hardware and topology
WSS Scalable Hosting modes
Large databases
Methods in a Nutshell
Need more methods?
Content Migration UpgradeMulti Threaded Database AttachVirtual In Place UpgradeMigrate Then Upgrade
http://blogs.msdn.com/joelo/archive/2007/05/22/3-methods-to-upgrade-let-me-give-you-4-more.aspx
SQL Instance
.
Database Attach on SteroidsMultithreaded DB Attach
.
2007 Farm2007 Farm
2007 Farm2007 Farm
2007 Farm2003 Farm
Virtual Upgrade• Build V2 Virtual Server
(Pre migration)• Build V3 Virtual Server• Take STSADM backups
from V2 server• Restore to V2 Pre
migration and clean up• Run PRESCAN!• Backup DB• Run STSADM –o
attachcontentdb into V3 Pre Migration or V3 UAT
• Take STSADM backups• Restore to new V3 PRD
server
Customization Common Choice Recommendation
Site Template Revert to Site Definition Use Site Template Upgrade Toolkit
Custom Web PartWorks most of the time (Gradual)
Test it out on a sample server with .NET 2.0 (DB Attach)
Event HandlerWorks most of the time (Gradual)
Rewrite and Redeploy as a Feature
Un-ghosted Page Revert to site definitionReview options: Retain customizations or revert
Themes and Stylesheets Reapply ThemeCreate Masterpage or stylesheet to apply standardization
Custom Site DefinitionCreate v3 Site DefinitionCreate Upgrade Mapping and Prescan Mapping
Migrate sites to out of box site Definition, upgrade then apply features with Solution Deployment
Code or pages in /_Layouts Ignore and re-evaluate (gradual)Analyze and create solution deployments for requirements
Inclusions/Exclusions Ignore with GradualRecreate Inclusions (DB attach)Exclusions are assumed
Add-ons Workflow, Web Parts, Server Controls
Determine per solutionContact vendor
Determine per solutionContact vendor
Customization Considerations
Changes to SharePoint Search
UnchangedCustom content sourcesCrawl rules
Upgraded but should be checked for conflicts
Custom crawl file types
ChangedScopes are lost, must recreate
Only 1 index now, default in SharePoint Server
Docicon.xml modifications must be redone
Thesaurus/noise file modifications must be redone
Search schedule lost, must recreate
If using gradual upgrade both v2 and v3 index will be running Disable v2 indexer ASAP to reduce strain on hardware
Other SharePoint Server-specific Issues
Portal alerts are lost during upgrade (site alerts are retained)Link listing: upgraded to a special links list called listingsContent listing: upgraded to news article pageBuckets (“c12”) are moved to real URLIf conflict, number appended starting with zero
http://portal/c12/finance becomes http://portal/finance (retains structure)
Areas are upgraded to publishing sitesAfter upgrade you can only create publishing sites as subsite can be changed http://msmvps.com/blogs/shane/archive/2007/02/08/moss-after-an-upgrade-you-can-only-create-publishing-sub-sites.aspx
Common Issues
Local administrator on server no longer has full access to SharePoint
Can be re-granted http://msmvps.com/blogs/shane/archive/2007/01/21/become-administrator-of-the-entire-web-application.aspx
New blocked file typesASMX, REM, RESX, SOAP, ASHX
E-mail enabled document libraries don’t work Look at new feature “Incoming e-mail”
More Common Issues
Office Web Components not available in 2007Discussion lists are changed
Multithreaded discussion upgraded to single thread
Site Directory now creates sites (sub-sites)
FrontPage Customizations
Important consideration: keep customizations or move to 2007
Custom pages kept by default during upgradeBe aware: customized pages do not match rest of site
“Reset to Site Definition” Returns page to layout in site definition Option exists to reset all pages during Gradual upgrade Available in site settings or within SharePoint Designer
SQL Instance
Upgrade Effects on Ghosting
Config Content
2003 Farm2007 Farm
60\Template60\TEMPLATE\1033\
STS\default.aspx
12\TEMPLATE\SiteTemplates\STS\
default.aspx
12\Template
Custom Web Parts
Most will work post-upgradeTest in Windows SharePoint Services 2003 SP2 with ASP.NET 2.0 Must re-build custom parts if you used ASP.NET 1.1 “obfuscation” tools Must re-deploy Web Parts if
Moving to a new server farm (Content DB Migration)Web Part in the \bin (Gradual Upgrade)
Deploying Web Partsstsadm –o addwppack
Troubleshooting Tips
Prescan logs%temp%Prescan.logPrescan Report and Summary
Log files Upgrade and Server logsLogs are in\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs
Watch the Event Viewer
Partners Helping You Upgrade
CorasWorks MigratorRe-ghost multiple sites at onceMigrate customizations and Web Parts to sites post upgradeHelps you add layouts, master pages, Web Parts en masse
EchoHelps you quickly roll out customizations and settings and permissions across your farm with no site collection boundaries
2007 version coming soon
AvePoint DocAveUsed to connect to 2003 and move content to 2007 without dependencies on customizations. Quickly and easily move your lists and libraries into a clean slate (out-of-box site definitions)
Takeaways
Prepare, plan and test your customizations!Become familiar with Prescan and upgradeConsider customization policies in the new platform, using features over site definitions
ReferencesMy Blog: http://www.chandima.net/Blog/
Will make all resource links and slides available on blog!
Migration and Upgrade Information for SharePoint Developers
http://msdn2.microsoft.com/en-us/office/aa905505.aspx
Migration and Upgrade Information for SharePoint Server (IT Pros)
http://technet.microsoft.com/en-us/sharepointserver/bb421259.aspx
Upgrade Documentation
http://technet2.microsoft.com/Office/en-us/library/396c85d9-4b86-484e-9cc5-f6c4d725c5781033.mspx?mfr=true
Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide
http://www.microsoft.com/technet/solutionaccelerators/collaboration/default.mspx
Upgrade in WSS SDK
http://msdn2.microsoft.com/en-us/library/ms460185.aspx
Fix your Orphans HotFixesrepair content databases in Windows SharePoint Services http://support.microsoft.com/kb/918744
Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in
SharePoint Portal Server 2003 http://support.microsoft.com/kb/918742/
References
Supportability2003 Best Practices to ensure upgradeability http://msdn2.microsoft.com/en-us/library/ms916859.aspx
KB Article on Site Definition Supportability in 2003 http://support.microsoft.com/Default.aspx?id=898631
Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows SharePoint Services and in SharePoint Portal Server 2003 http://support.microsoft.com/kb/898631/en-us
Community ToolsSharePoint Configuration Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=918f8c18-89dc-4b47-82ca-34b393ea70e1&DisplayLang=en
SharePoint Utility http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724
SPReport http://workspaces.gotdotnet.com/spreports
Managing SharePoint Products and Technologies Performance at Microsoft http://www.microsoft.com/technet/itshowcase/content/spsperfnote.mspx#ETKAE
Microsoft SQL Server Report Pack for Microsoft Office SharePoint Portal Server 2003 http://www.microsoft.com/downloads/details.aspx?FamilyID=49159368-544b-4b09-8eed-4844b4e33d3d&DisplayLang=en
BlogsResources and Recommendations for Upgrading Site Definitions and Site Templates http://blogs.msdn.com/joelo/archive/2007/01/03/resources-and-recommendations-for-upgrading-site-definitions-and-site-templates.aspx
Upgrade Content IT Pros may not have seen http://blogs.msdn.com/joelo/archive/2006/12/06/upgrade-content-it-pros-may-not-have-seen.aspx
Other Upgrade Topics from Joel’s Blog http://blogs.msdn.com/joelo/archive/tags/Upgrade/default.aspx
Orphaned Objects
Windows SharePoint Services Content DB orphans
Post-SP2 Hotfix, KB 918743 and KB 918744stsadm -o databaserepair -url http://WSSSite -databasename DatabaseNamestsadm -o databaserepair -url http://WSSSite -databasename DatabaseName –deletecorruption
SharePoint Server Config DB orphansPost SP2 Hotfix, KB 918742spsadm –o repairorphans http://PortalSite
Windows SharePoint Services Config DB orphansRemove and then reattach the content databases on the virtual server
Effect of Upgrades: Low Customization Site (Original)
Effect of Upgrades:Low Customization Site (Upgraded)
Effect of Upgrades:Low Customization Site (Re-Ghosted)
Effect of Upgrades:High Customization Site (Original)
Effect of Upgrades:High Customization Site (Upgraded)
Effect of Upgrades:High Customization Site (Re-Ghosted)
Effect of Upgrades:Themed Site (Original)
Effect of Upgrades:Themed Site (Upgraded)
Q&APlease fill the evaluation form!
Thank You
Resources
Technical Communities, Webcasts, Blogs, Chats & User Groupshttp://www.microsoft.com/communities/default.mspx
Microsoft Developer Network (MSDN) & TechNet http://microsoft.com/msdn http://microsoft.com/technet
Trial Software and Virtual Labshttp://www.microsoft.com/technet/downloads/trials/default.mspx
Microsoft Learning and Certificationhttp://www.microsoft.com/learning/default.mspx
New Zealand Technical Communities, Webcasts, Blogs, Chats & User Groupshttp://www.mscommunities.net.nz
The Microsoft Office SharePoint Conference 2008
March 3rd – 6th 2008 at the Washington State Convention and Trade Center, Seattle, USA
Sign up for more information and registration notification at http://www.mssharepointconference.com
Announcing!
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.