Mark Harmsworth Architecture Nate Bruneau Engineering Scott Kleven Program Management Microsoft Corporation SESSION CODE OSP321 Session Objectives and Takeaways Session Objectives ID: 435889
Download Presentation The PPT/PDF document "Microsoft IT: How MSIT Upgraded Microsof..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Microsoft IT: How MSIT Upgraded Microsoft to SharePoint 2010
Mark Harmsworth – ArchitectureNate Bruneau – EngineeringScott Kleven – Program ManagementMicrosoft Corporation
SESSION CODE: OSP321Slide2
Session Objectives and Takeaways
Session Objective(s): Learn how Microsoft IT upgraded to SharePoint 2010Learn SharePoint 2010 upgrade Best PracticesHow to prepare for upgrade
Learn from our real-world MSIT
experienceSlide3
SharePoint at Microsoft
Scott KlevenSlide4
The Microsoft Ecosystem
170,000 full time employees and vendorsGlobally distributed workforceGlobally distributed IT datacentersFour classes of users
Office Dweller (40% Full Time employees)
Campus Nomad (40% Full Time employees)
Remote Users (20% of Full Time employees)
Business Partners (approx. 100,000)Slide5
41,381
Top-Level Sites
73,273
Webs
3.26
Terabytes
137,290 Top-Level Sites
298,348 Webs
17.06 Terabytes
48,379
Top-Level Sites
112,301
Webs
6.63
Terabytes
As of 3/8/2010
Global DistributionSlide6
Total Content
6
227,050 Top-Level Sites
483,922 Webs
27 Terabytes ContentSlide7
MSIT Specific Upgrade Challenges
Running pre-release code used for beta testingEvaluation scripts unusableDeprecated Templates and Web Part
Number of portals/services
Extremely aggressive timeline
Gradual Upgrade removed
Upgrade = maintenance window
DB Attach only allowed method
Flatten/Rebuilds required for all upgradesSlide8
Preparing for Upgrade
Scott KlevenSlide9
Pre-requisites for upgrade
Upgrade must be from a post-WSS v3 SP2
New Farm:
SQL Server (x64)
2005 Service
Pack 3 + Cumulative Update
2
2008 Service Pack 1 + KB970315
Windows Server (x64)
2008
SP2 Standard
2008
R2 StandardSlide10
Preparing for Upgrade
Evaluation of new features and servicesPartnership with Product GroupRelease CriteriaPortal prioritization
Service Rollout
Supported upgrade methods
Milestone definitions
Dogfood FarmSlide11
Preparing for Upgrade
Project planCommunication PlanWhat do we have?Shape of DB’sCustomizations, Features, LPK’s, Web Parts
Dry Run
“Dogfood Champions”
How will we do it in Production?
Upgrade is a Science
“A winning effort begins with preparation.” - Joe Gibbs Slide12
Upgrade Performance
Database Shape Centric
# Site Collections
# Webs
# Lists
# Document Versions
Document Versions Size
# Documents
# Links
Overall DB Size
Hardware Centric
SQL Disk I/O per second
SQL Database to disk layout
SQL Temp DB optimizations
SQL CPU & Memory
WFE CPU & Memory
Network Bandwidth & latency
Note:
Each new build’s upgrade could be impacted by newly
added upgrade actions or database content changesSlide13
Database Shape
DATABASENAME
SPACEUSED
MB
SITES
WEBS
LISTS
LINKS
red_sharepoint_00
330981.57
1981
5545
64536
3450111
red_sharepoint_01
119068.69729
194724271
749983
red_sharepoint_02
175708.69
736
2207
26455
1868105
red_sharepoint_03
122513.63
734
2015
25495
1178877
red_sharepoint_04
204301.57
731
2388
28085
1335996
red_sharepoint_05
176060.5
727
2445
30029
1726491
red_sharepoint_06
133066.81
738
1993
23618
1057653
red_sharepoint_07
150448.94
896
2353
28905
882741
red_sharepoint_08
164010.81
739
2044
25498
1214226
red_sharepoint_09
140853.94
733
2288
26928
3049061Slide14
MSIT Upgrade – Dry Runs
Established PPE instances for each platformBackup/restore production content (all)Mimic actual production upgrade scenariosAutomate build out
Script upgrade
Parallel upgrade
Audit
Capture db upgrade times
Resolve all identified errors, do againSlide15
Production Upgrade Preparation
Automate Build OutScript the upgradeSite identification and remediation
Pre-upgrade prep
Backups
DNS / AAM
Roll back plans
Customer communicationSlide16
Architecture for SharePoint 2010
Mark HarmsworthSlide17
Designing for SharePoint 2010
Assuming a typical farm in 2007;
2 Web servers
1 Application
1 SQL server (cluster/mirror
)
In 2010 consider adding 1 additional Web and 1 additional application
server
For higher load farms, add an additional SQL for Usage AnalysisSlide18
Designing for SharePoint 2010 (cont)
Feature / Role
2007
2010
IIS
Web Servers
2 Web Servers
2-3 Web Servers
Application Servers
1 Application Servers
2 Application Servers
Index / Crawl Target
Crawled through web servers1 Dedicated crawl web targetExcel ServiceRan on application/web server
No change from 2007WACN/AAdditional app servers or run on Excel app serverAccess and Visio Services
N/AShares WAC app serverUsage
AnalysisN/ARecommend dedicated SQL for medium to large farmsSlide19
SharePoint 2010 Upgrade Physical TopologySlide20
SharePoint 2010 Final Physical TopologySlide21
Considerations for your topology design
Decide up frontWhich services you might run in the futureDesign for scale out over scale up
There is no substitute for spindles
Memory is cheap
Network VLANs
Measure your disk i/o before upgrade
Estimate your future usage data collection carefully
Don’t under estimate the crawler loadsSlide22
Visual Snapshot Upgrade Tool
Nate BruneauDemoSlide23
Upgrading SharePoint 2007 to 2010
MSIT choseRead-only databases
Parallel
content database upgrades
Content
database attach with AAM redirection (2010
)
Gave our users
Access to the 2007 content
Fall back to 2007 if not completed on time
Maximum chance of completing in the maintenance windowSlide24
Read-only Content Databases
Approach :Set source content databases to Read-only
Backup/Restore copies of content databases
Attach database copies to new farm
Read-only
locking:
Content remains static
SQL controls read-only lock status
Upgrade
copy of database on different farmSlide25
Read-only Content DatabasesSlide26
Parallel Upgrade Process
Manually initiated processSeparate upgrade sessions2007 let us run separate single farm upgrades
Parallel
farms still an option too
Max
parallel upgrades determined by
hardware
We ran 27 simultaneous upgrades across 5 SQL serversSlide27
Parallel Upgrade Process – Single Farms
Farm 1
Farm 2
Farm 3Slide28
Parallel Upgrade Process – Parallel FarmSlide29
Parallel Database Upgrade
Nate BruneauDemoSlide30
AAM Redirection Process
Use with Content DB Attach upgradeGranularity at content databaseSingle Site Collections require their own databasestsadm -o
mergecontentdbs
(Improved in April 2009 CU)
Downtime mitigation process but its expensive
Complex to set up
Introduces URL changes and additional URLs
URLs will proliferate through organization
Not all clients will handle URL changes well
Client side scriptingSlide31
Database Attach with AAM Redirect
SQL Instance
WFE
v3 Farm
WFE
v4 Farm
http://WSS
http://WSSold
http://WSS
SQL
v3
Config
v4
Config
SQL
v3
Content
v4
Content
Move DB
?
302
WSS v3
Web App
WSS v4
Web AppSlide32
AAM Mapping Tool
Nate BruneauDemoSlide33
Post Upgrade
Monday Morning….Slide34
MSIT Upgrade
SharePoint Server 2010 kicked off at 6PM73 db’s, 8TB contentDB Attach kicked off with 16 parallel threadsHigh Point – 27 threads
No net new services deployed at upgrade
By 6PM Sunday, single db remained. Decision to continue upgrade till completion. Last db completed by noon on MondaySlide35
Post Upgrade
Post UpgradeWar room established week after upgrade24/7 support establishedPartnered with Product Group for troubleshooting
Customer summary end of first
week
Key Upgrade Issues:
SUPERUSER
Throttling: Performance, Lists, Data View Lookups
CustomizationsSlide36
Summary and Key Takeaways
Learn from our real-world MSIT and Field experience
Key Takeaways:
Thoroughly familiarize yourself with upgrade documentation & resources
Start
testing upgrade
now
Plan
for upgrade strategy by considering new improvements to upgrade
systemSlide37
Track Resources
Link to Nate’s IT SharePoint Blog : (Content/Resources from the
TechEd
Demos, PowerShell Tips, IT SharePoint Automation)
http://blogs.technet.com/b/nathbr/Slide38
Track Resources
For More Information – http://sharepoint.microsoft.com SharePoint Developer Center – http://msdn.microsoft.com/sharepoint
SharePoint Tech Center –
http://technet.microsoft.com/sharepoint
Official SharePoint Team Blog –
http://blogs.msdn.com/sharepoint
Required Slide
Track PMs
will supply the content for this slide, which will be inserted during the final scrub. Slide39
Related Content
Breakout Sessions – See Conference Guide for full list of OSP Track SessionsInteractive Sessions – OSP Track has 10
Interactive Sessions – OSP01-INT – OSP10-INT
Hands-on Labs – OSP01-HOL – OSP20-HOL
Product Demo Stations – Yellow Section, OSP
Office 2010, SharePoint 2010, Project Server 2010, Visio 2010
have kiosks and demos
Required Slide
Speakers,
please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session.Slide40
Resources
Required Slide
www.microsoft.com/teched
Sessions On-Demand & Community
Microsoft Certification & Training Resources
Resources for IT Professionals
Resources for Developers
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn
LearningSlide41
Complete an evaluation on
CommNet
and
enter to win!
Required SlideSlide42
Sign up for Tech·Ed 2011 and save $500
starting June 8 – June 31sthttp://northamerica.msteched.com/registration
You can also register at the
North America 2011 kiosk located at registration
Join us in Atlanta next year
Slide43
© 2010 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.Slide44