The document outlines the upgrade process to SharePoint 2010, detailing prerequisites, methods, and techniques for minimizing downtime during the upgrade cycle. It emphasizes the importance of testing and validating customizations and provides insights into the upgrade strategies, including in-place upgrades and database attachments. Recommendations are given for scheduling and managing the upgrade to ensure a smooth transition while addressing common issues and mitigation processes.

2. (OFS302) Upgrading to SharePoint 2010Joel OlesonSharePoint ArchitectQuest Softwarehttp://sharepointjoel.comMuhanad OmarSharePoint ConsultantDevosis

3. Who is SharePoint Joel? 9+ Year SharePoint Veteran5 Years in MS IT & Online2 Years in SharePoint Product TeamProduct Architect for Deployment AdvisorSr. SharePoint ArchitectSharePoint Product Architect & Strategy @ Quest

4. Meet Mo!

5. Upgrade Cycle: Overview

6. 64 bit only

7. Operating System

8. SQL server

9. Missing dependencies

10. UI changes

11. Lack of space

12. Forms Authentication Providers

13. In-Place

14. Database Attach

15. Content

16. Profile

17. Project

18. WID to SQL Migration

19. Read-only content databases

20. Parallel upgrades:

21. Multiple temporary farms

22. Parallel database attach

23. AAM redirectionUpgrade Cycle: LearnPrerequisitesCommon issuesUpgrade methodsDowntime mitigation

24. Upgrade Cycle: Prepare

25. Upgrade Cycle: Test

26. Upgrade Cycle: Implement

27. Upgrade Cycle: Validate

28. Learning from PreUpgradeCheck

29. SharePoint PreUpgradeCheck Report

30. PreUpgradeCheck Failed Report (snippets)

31. Upgrade OverviewDrill Down on Binary Upgrade MethodsWindows PowerShell Upgrade CmdletsApproaches to UpgradeDev - Feature UpgradeVisual UpgradePatch ManagementDowntime Mitigation Processes:Parallel Upgrade PipelinesContent DB Upgrade with AAM RedirectionImprovedUpgrade Status ReportingUpgrade LoggingRead-only DB SupportSimplified Upgrade MethodsRemovedGradual UpgradeSide By Side Installation

32. 64 bit SQL Server 2008Why Upgrade?Engine optimizationsFILESTREAM support for Remote Blob Storage (RBS)Why Enterprise?Backup compression (faster and smaller)High Availability Mirroring enhancements with built in support in SharePoint 2010!Transparent database encryption

33. Insight on UpgradeBinary UpgradeIn Place - New Timeout, Resume on failuresDatabase Attach - New Parallel, Progress IndicatorVisual UpgradeSeparate processDelegation by default

34. Test-SPContentDatabase

35. Attaching Database to SP2010 Farm

36. Binary Upgraded Site: Preview Visuals – Sneak Peak Screenshot

38. DB Attach with SharePoint 2010 Powershelldemo

39. Drill Down on Upgrade Methods

40. 2010 MS Upgrade PhilosophyYou need to understand what MS was thinkingDetect issues earlyProvide O12 tools to adminsReport critical issues at start of upgradeKeep the administrator informedNo data lossKeep content and settingsMinimize downtimeDowntime mitigation processesContinue when at all possibleAbility to resumeUpgrade should not be catch 22

41. In-Place UpgradeAll-at-once upgradeMust upgrade the whole farm at one timeNo SP 2007 and SP2010 in same farmSchedule downtimeSimplest approach, but *most risky*!No going backResume Upgrade if problems occurRecommendationsRun Test-SPContentDatabase from SP 2010 farm against databasesDo a full farm backup before you start!

42. Database Attach UpgradeSafer, Requires more planning (A good thing)Upgrade is done on a separate 2010 farmDone database-by-database Can be used as 2 step gradual visual upgradeUse Test-SPContentDatabase (PowerShellcmdlet) to test database firstTo attachUpgrade-SPContentDatabase (PowerShell)Addcontentdb operation (STSADM)Parallel database upgrades are possible

43. Visual UpgradeStay in 2007 (default) or move to 2010 UI2010 ships 2007 Master pages and CSSUI Preview capabilityFarm admin or site admin controlledWeb level settingSome items not 2007 UI compatibleMy site hostPWA site collectionReport Server web parts

44. UI UpgradeMigrating to SharePoint 2010:All content will migrate overNo changes required to site content or brandingSharePoint 2007 / 3.0 style UI is retainedExisting master pages & page layouts are usedManually migrate to SharePoint 2010 UI Ribbon, Improved Site Settings, AJAXVisual Upgrade

45. Upgrade Pipeline FlowUpgrade internals step by stepPSConfigStage 1: Boot StrapConfiguration DatabaseAdmin Content DatabasePre-Joined FarmJoin FarmStage 2: Central AdminWeb TemplatesSPIISSite ObjectsFeatures UpgradeAdmin Web ServiceAdmin Web ApplicationLocal FarmAdmin Content DatabasesSPSitesPSConfig/TimerSharedResourceProvider12 ObjectsPartner Service ApplicationsService Application ObjectsPartner DatabasesStage 3: User DataLocal FarmWeb TemplatesSPIISSite ObjectsFeatures UpgradeWeb ApplicationSPSitesContent Databases

46. Tactical Insights

47. Customizations TestingWill it work after upgrade?Custom JavaScriptCustom ServicesCustom FeaturesCustomSearch Provider or Security TrimmerModified OOB FeaturesOM/Contract CompatibilityStructural CompatibilityUser Interface and (x)HTML CompatibilityCustom Web PartsModified DatabasesCustom Site DefinitionsCustom CSSCustom Authentication ProvidersModified OOB Site Definitions

48. Upgrade TestingWhat are you looking for in a test?Upgrade IssuesDisk Full!!!Modified databasesCustomizationsAuthentication providersPoor dev practicesRecommendationsTest server side customizations & verify in both Visual Upgrade modesConsider preview environmentsSimilar hardware, Use real datasetsDon’t ignore warnings

49. Operations SchedulingBenchmark upgrade operations scheduleNote:Planned 36 hours outage.Up to 54 hours emergency outage if rollback is required.Downtime mitigation processes such as read-only databases can be used to reduce outage time.

50. Upgrade PerformanceWhy prediction is difficultDatabase Shape CentricHardware Centric# Site Collections# Webs# Lists# Document VersionsDocument Versions Size# Documents# LinksOverall DB SizeSQL Disk I/O per secondSQL Database to disk layoutSQL Temp DB optimizationsSQL CPU & MemoryWFE CPU & MemoryNetwork Bandwidth & latency

51. Common Upgrade Failure Issues & RecoveryDetermine cause of failureStatus Page & Upgrade Logs:Error logFull upgrade logCustomizations Management Commands:Test-SPContentDatabasestsadm -o EnumAllWebsFix issue(s)Install missing or updated customizationsActivate missing services; farm, web app settingsResume upgradeFarm upgrade commandContent database specific upgrade commandService specific upgrade commands

52. Upgrade InternalsMinutia and NuancesV2V upgrade DBs set to simple recoveryDB growth during upgrade:Versions and indexes; SQL logsShrink DBs after upgrade; not automaticSQL timeouts:Removed command timeouts (query time)Retained connection timeoutsSetupPath fallback logicObject locking during upgrade:Maintained in config DBAutomatic removal of stale locks (2 minutes)

53. Upgrade Strategies

54. Read-Only Content DatabasesReducing perceived downtimeNot just for upgrade or patchingManually initiated processRead-only locking:Content remains staticSQL controls read-only lock statusSharePoint promotes SQL lock to site lockUI Trimming enforced by site lockUpgrade copy of database on different farm

55. Single Click Install - SQL MigrationHidden complexity in simple environmentsWindows Internal Database not supportedDB could be >4GBSQL Express 2008 (Single Click, Manual Install)DB >4GB not supportedMigration Process Occurs Before UpgradeCopy of WID Content DBs restored to WIDDBs scrubbed of BLOB dataDBs moved to SQL Express DBs modified to support RBSBLOBs copied into RBSAll Content DB migration with in-place upgradeIndividual Content DB migration command

56. Windows PowerShell Upgrade CmdletsTest-SPContentDatabaseDiscover and Document issues 2007/2010Mount-SPContentDatabaseInitiate Content database B2B/V2V upgradeUpgrade-SPContentDatabaseResume Content database B2B/V2V upgradeUpgrade-SPEnterpriseSearchServiceApplicationSearch Service Application InstanceUpgrade-SPSingleSignOnDatabaseO12 SSO data to Secure Store database