Successfully reported this slideshow.

SharePoint Installation and Upgrade: Untangling Your Options


Published on

More info on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

SharePoint Installation and Upgrade: Untangling Your Options

  1. 1. SharePoint Installation and UpgradeUntangling Your OptionsDan HolmeMVP, SharePoint ServerMicrosoft Technologies Analyst & EvangelistIntelliem
  2. 2. Dan Holmedanholme
  3. 3. About This SessionTechnical guidanceHow do I upgrade or migrate?What do I need to know to successfully upgrade?Roadmap to 2013What is SharePoint 2010? What is new at Microsoft? What is SharePoint 2013?When should I upgrade?On-premise or Office 365?Insight, clarity & balanceWhat are enterprises planning and doing?Answer questions
  4. 4. What is upgrade?Version-to-version (V2V)SharePoint 2010 to SharePoint 2013Build-to-build (B2B)Patches, updates, cumulative updates, service packs, etc.
  5. 5. What options are available?In-placeB2B onlyNot available V2VDatabase attachV2VB2BConsider the benefits of using DB attach for B2B
  6. 6. Upgrade: A High Level View Server Farm Administrators 41 2 3 4 5 Upgrade site collections to 2013 mode Site collections remain in 2010 mode 2010 mode available 2010 workflow engine Create SharePoint 2010 customization 2013 Copy databases to models Production farm new farm Upgrade Databases (Full Trust, Sandbox)
  7. 7. Upgrade is “dead”No more in-place upgradeNew Farm + Database AttachBackward compatibility: 2010 & 2013 “modes”2013 includes 2010 root folder (―14 hive‖), features, templates etc.And the 2013 root folder, features, templates, etc.New sites can be created in 2010 or 2013 mode (configurable: SPWebApp/SPSite.SiteCreationMode)Support for 2010 and 2013 approaches2010 workflows and 2013 workflows2010 customization models (full trust & sandbox) and 2013 App modelsOld workloads and customizations continue towork*
  8. 8. Upgrade planningDefinitionCurrent state & future stateWhyWhat must be rebuilt, migrated, or upgradedServers and settingsServices & contentCustomizationsGovernance of upgradeTimeline, roles, responsibilities, policies and procedures, cost/benefit, risk and rewardImpactPerformance, disruption, downtime
  9. 9. Upgrade Learn Validate Prepare Implement Test
  10. 10. Upgrade Learn Validate Prepare Implement Test
  11. 11. Upgrade improvementsFasterDeferred site collection upgradeSaferNo in-place upgradeUpgrade evaluation site collectionsSite collection and health checksManageableCan be delegated to site collection administratorsSite collection upgrade throttlingSystem event notifications systemLogging changesFlexibleFederated services compatibility across versions
  12. 12. Upgrade Learn Validate Prepare Implement Test
  13. 13. ImplementBuild serversDeploy customizationsUpgrade servicesMigrate to claimsUpgrade content databasesUpgrade site collectionsAlong the wayBackup everything firstMinimize downtimeMonitor progress
  14. 14. Build server(s)Scripted deploymentSQLPrerequisitesSharePoint binariesConfigurationCheck out my Deployment Wizard session from the SPC, on video at upgrade the configuration database
  15. 15. Upgrade service applications1. Document settings for service in source farm2. Back up service application database(s) in source farm3. Restore database to target farm4. Create service application app pool5. Create service application Attach or upgrade service database when creating the service application Some service applications require special attention: Project, Search, Secure Store6. Create service application proxy7. Start service instances only After service is created with upgraded databases
  16. 16. Upgrade service applicationsProjectMerge four databases into one before upgradingSecure StoreSet service passphrase to the same value as before upgradeSearchV2V admin database onlyIndex cannot be upgraded, V2VRecommend: Start anew
  17. 17. Upgrade the My Site Host2010 mode or 2013 modeAfter My Site Host is upgraded to 2013 modeSharePoint 2013 social features become availableNew personal sites will be created in 2013 modePersonal site upgradeAs users visit My Site Host, their sites are added to upgrade queueUpgraded by timer jobFailed personal site upgradeIf upgrade of personal site fails, it will be reattempted after a delayCan force upgrade attempt Site collection admin: From personal site UI Farm administrator: PowerShell if farm admin
  18. 18. Authentication considerationsWindows Classic (legacy)SP2013 limited supportWindows ClaimsDefault in SP2013Required for Apps and some other featuresMigrate to claims before upgradeRecommendedAuthentication mode mismatchesDatabase attach detects mismatched authentication modesForms AuthenticationNo changes from SP2010Install and configure provider in SP2013 with same name before attaching database
  19. 19. Migrating to claims authenticationPerform as a separate stepClarify faults to reduce troubleshootingMigrate to claims before upgradeRecommended best practiceUse Test-SPContentDatabase before attachIdentify & remediate authentication problemsPartial migration within content databaseMisconfigured web applicationVerify after upgradeContent securityFunctionalityExternal data sourcesWeb services
  20. 20. Upgrade content databases1. Document settings From source farm2. Configure web app Application pool and managed account Managed paths AAM zones, URLs, IIS bindings3. Install solutions and other customizations Install SP2010 customizations Install SP2013 customizations Make web.config changes4. Ensure service apps are connected to web app5. Attach content database
  21. 21. Deferred Site Collection UpgradeSharePoint 2013 deep backwards compatibilitySharePoint 2010 mode and SharePoint 2013 modeAttach content database2010 mode2010 mode is default. SP2013 mode is an additional step: not automatic on database upgrade.Upgrade availabilityAvailable to farm administratorsAvailable to site collection administrators (configurable: SPSite.AllowUpgrade)System status bar notificationUpgrade evaluation site collectionCopy of site collection to evaluate upgraded functionality
  22. 22. PerformanceEnvironmentSQL server: CPU, memory, disk IOPS, database-to-disk layout (fragmentation), temp DB optimizationsSharePoint server: CPU, memoryNetwork bandwidth & latencySimultaneous upgrades
  23. 23. PerformanceDatabase upgradeRows: Site collections, webs, lists, documents, items, linksDatabase sizeRBSSite collection upgradeRows: Webs, lists, activated upgrading features, documents, items, linksUpgrade throttlingConcurrent upgrades: per web application or per content databaseSite collection content: storage or subweb count (set in web application)If upgrade request is throttled, it is placed in upgrade queue
  24. 24. Disruption and DowntimeDisruptionChange client softwareRetrain usersRefactor or replace customizationsMitigation: Deferred site collection upgradeDowntimeTemporary disruptionNo such thing as ―zero downtime‖: data loss vs. downtime reductionMitigation Add granularity to multi-site content DBs over 100GB: Move site collection to new DB, then upgrade Read-only databases: Content, Services (except Access) Parallel upgrades Upgrade offline, sync, redirect: requires third party tools
  25. 25. Upgrade Learn Validate Prepare Implement Test
  26. 26. Document environmentSettingsPowerShellWinDiff: web server extensions, IIS site (web.config), GAC, 14 & 15 root foldersCustomizationsFull-trust solutions, admin-deployed InfoPath formsMSI, XCopy deploymentsPerformance characteristicsHardwareSQLNetwork
  27. 27. Clean upClean up SP2010 environmentDelete stale contentSite collections and web sitesRemove extraneous document versionsRationalize templates, features & web partsComplete visual upgrades to SP2010
  28. 28. Manage customizationsCategory Examples Likely ImpactVisual Master Pages 2010 mode: function Themes 2013 mode: fail Web Pages Web PartsData Content Types If working: no impact List Types If missing: blocker Web Templates Upgrade required: expensive—iteration Site DefinitionsInternals Web Services Incompatible Windows Services HTTP Handler HTTP Module
  29. 29. Inform UsersActionWhat is needed: requirements, information gathering, content classification & taggingWhen it will happen: events, scheduleExpectationsWhat will happenWhat happens next, if it worksWhat happens next, if it failsInstructionsHow to upgrade site collectionsWhen to upgrade site collectionsHow to validate upgradeSupportHow to communicate with upgrade team
  30. 30. Upgrade Learn Validate Prepare Implement Test
  31. 31. Build test farm(s)Maximize realism of simulationUse similar hardwareUse real data, not samplesDeploy all required customizationsMinimize URL changesMinimize name changes (SQL Alias)Minimize impact on production environmentLive databasesExternal data connectionsSQL server performanceActive Directory profile data
  32. 32. Evaluate techniquesMethods & processesConfirmScriptDowntime mitigationPerformanceSQL Server responsivenessSharePoint responsivenessValidationTroubleshooting
  33. 33. Test & RepairTest-SPContentDatabaseConfiguration gapsOrphaned sites: site collections in content database but not in config database site mapMissing/unregistered customizations: features, site definitions, templates, web partsRow sizing for predicting comparative upgrade speeds: Add –ShowRowCounts switchAuthentication mis-matchRepair-SPContentDatabaseOrphaned websOrphaned listsOrphaned itemsTest-SPSite and Repair-SPSite
  34. 34. Staging MigrationUse a staging farmOfflinePerformance matters only in relation to upgrade, not day-to-day utilizationValidate and remediateIn a non-production environmentParticularly if migrating to the cloudInsufficient access and tools to remediate problems after content is in Office 365
  35. 35. Upgrade Learn Validate Prepare Implement Test
  36. 36. Upgrade Learn Validate Prepare Implement Test
  37. 37. ValidateReview events and logsTroubleshoot failuresRemediate UI/UX issuesRemediate data issues
  38. 38. Logging ChangesUpgrade logs changed to ULS formatTSV format allows improved parsingCan be imported into ExcelIncludes Correlation IDSite collection upgrade logsAvailable to Site Collection adminsUses separate logging level control than rest of upgrade
  39. 39. ValidateReview events and logsUpgrade error logFull upgrade logULSStart at top of log, work downwards (address dependencies)Troubleshoot failuresProcess/assembly loadAuthentication (login, access)Missing servicesMissing files or customizationsContentRemediate UI/UX issuesRemediate data issues
  40. 40. Validation ChecklistExisting sitesHigh-prioritySample of each site definition & featureAll sitesProvisioning of new sitesSite collections and subsitesActivate features, create lists & libraries, create pages, add web partsAs new 2010 modeAs new 2013 modeAs new 2010 mode upgraded to 2013 mode Validate against new 2010 mode
  41. 41. Validation ChecklistAuthenticationVisual customizationsExternal data connectionsOther functionality
  42. 42. Site Collection Health ChecksRule based health checksLooks for common issuesUpgrade-blocking issues Missing SP2013 templatesPost-upgrade issues Un-ghosted filesSite collection level scoped toolUI for Site Collection AdminsPowerShell cmdlet for Farm AdminsRuns automatically before Site Collection V2V upgradePrevents upgrade if blocking issues detectedDoes not run automatically before B2B upgrades
  43. 43. What doesn‟t work?2010 Web Analytics2010 Office Web Applications2013 Office Web Applications used for sites whether in 2010 mode or 2013 modeProject Web Access (PWA) templatesMust upgrade to 2013 modeProject Sites (PWS) supported in both 2010 and 2013 modesSpecific functionalityUser defined functions in Excel ServicesPowerPoint Broadcast sitesExternal BLOB Storage (EBS)
  44. 44. Multi-farm scenarios1. Build SP2013 service and content farms2. Pre-index content3. Upgrade federated services to SP2013 Profile, Search, Social, Metadata, BCS, Secure Store Set SP2010 service databases to read-only at SQL to prevent data loss4. Consume federated SP2013 services in 2010 farm5. Upgrade services and content databases Set SP2010 content databases to read only Validate database upgrades Immediately upgrade databases required to be 2013 mode (e.g. PWA)6. Redirect requests to SP2013 farm7. Upgrade sites
  45. 45. Restructure physical or logicalarchitectureNew features in SharePoint 2010Content type hubDocument information policiesManaged metadataNew features in SharePoint 2013Search: Continuous crawl, Content By SearchCross-site publishing (XSP)Managed navigationLessons learnedInformation management: security, compliance, information lifecycle managementService management: performance, storage, SLAs, content recovery, high availability, disaster recovery
  46. 46. Information assessmentAssess all contentBusiness needs changeInformation management & service management requirements changeArchive, Rebuild, Migrate, Delete (ARMD)Determine migration priority & actionCreate a migration request queue Site source URL Site target URL Action (archive, rebuild, remove, migrate, delete) Priority Roles & responsibilities Information gathering Processes and workflow Migration date
  47. 47. Information (re)architectureInformation architectureContent types, metadata, search, site map, navigationClassification (―tagging‖) processes and toolsPlan for IA migrationMap source IA to target IAPerform IA migrationThird party toolsStaging farmConsider and manage URL changesUtilize IA to facilitate and govern migrationPrioritize and filter sites and content to migrate
  48. 48. Governance, security & complianceUpgrade (improve) or establish governanceHarden securityImprove user and group managementRationalize and re-map security boundaries and controlsCleanse and validate contentIn source farmIn staging farmIn target farm Not recommended (on-premise) Not easy or even possible (Office 365)
  49. 49. Migrate, don‟t upgradeWhyBig bang migrations are complex and riskyDowntime is not tolerableGarbage in – garbage out Bad decisions Database modifications Unsupported site definitionsInformation architecture changes Restructure Metadata Rules-based migration: filter, tag, processMigration of third-party components, e.g. workflowsMigration from 2007 (or other platforms) to SharePoint 2013 or Office 365HowThird-party tools
  50. 50. Upgrade and migration guidanceTreat it as a real projectClean up the source environment firstUpgrade more than just contentImprove and restructure information architectureArchitect governance, security, and compliance into the migration process and end stateUpgrade related infrastructure and services, especially authentication (ADFS)Utilize test and staging farmsParticularly important to test and stage on-premise before migrating to cloudBe granularSplit large content DBs into multiple CDBs with fewer sites prior to upgradeUse migration tools to migrate subsets of content
  51. 51. Evaluate third-party tools: MigrationPrepare Perform migrationPre-scanning Automate Minimize down time:Improve performance, offline, and other optionsRe-architect farm Migrate other components, e.g. workflowsRestructure information architectureAutomatically classify content Support (!!!)Rationalize security management Migration is a one-time or rare activity for youEnforce and audit content & compliance It’s the raison-d’etre for migration tool ISVs Extensive knowledge and experienceAlign with business Services to support your migrationprocessAlign with business process:granularity, metadata-driven rules and filtersGovern: workflows, approvals, controls
  52. 52. Evaluate third-party toolsManagement of cloud, on-prem, and hybridenvironmentsExpose and integrate legacy and non-SharePoint contentMaintain a healthy service for the next changeInformation architecture: content, metadata, tagging, navigationInformation management: security, compliance, information lifecycleService management: performance, storage optimization, recovery, HA, DRCustomization management: application and customization lifecycle managementService portfolio management
  53. 53. Shout OutsRandy Williams Matt McDermottJeremy Thake Eric ShuppsGary Lapointe Paul SwiderChris Givens Shane YoungAndrew Connell Todd KlindtSpence Harbar Wictor WilénJason Himmelstein Asif RehmaniTodd Baginski Rob BogueScot Hillier Agnes Molnar
  54. 54. MAHALO! (thank you!) HUI HO! („til next time!)