1 / 25

ON PREM - SHAREPOINT 2013 MIGRATION

ON PREM - SHAREPOINT 2013 MIGRATION . Deepak Srinivasan Manager Consultant Sogeti USA LLC. Introductions. SharePoint 2013 Key investments. Common Migration/Upgrade Options. Option 2 and 3 will require new farm . Option 4 will require a Microsoft O365 service. . Types of Migration.

khanh
Download Presentation

ON PREM - SHAREPOINT 2013 MIGRATION

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ON PREM - SHAREPOINT 2013 MIGRATION Deepak Srinivasan Manager Consultant Sogeti USA LLC

  2. Introductions

  3. SharePoint 2013 Key investments

  4. Common Migration/Upgrade Options • Option 2 and 3 will require new farm. Option 4 will require a Microsoft O365 service.

  5. Types of Migration • Database Attach Service Applications, Content Databases • 3rd Party Tools • Migrate Manually (with C# code/powershell or copy/paste) • Note: Custom solutions need to installed separately to make sure the requisite features are available in the new farm. This is separate from attaching and mounting databases or using a tool/script to migrate.

  6. Define High Level Migration Strategy

  7. What do you need? (DB ATTACH) • Staging machines for • SharePoint 2013 • SharePoint 2010 • Prod, QA and Dev machines for • SharePoint 2013 Note: A staging machine is a throw away machine that will only be used during the course of the migration • SP 2007 Version – at least 12.0.0.6608 • SP 2010 Version – at least 14.0.6112.5000

  8. Overview of Migration process

  9. Upgrade Testing Cycle Test Environment

  10. Service Upgrade Processes • Common pattern used for most cases: • Restore copy of old version service database(s) to SQL • Can be done using command line or SQL Management Studio • Create the service application using the new service application cmdlet applicable for that service type • Pass in the old database(s) as parameter(s) to the cmdlet • Create the service application proxy using the new service application cmdlet applicable for that service type • Start the applicable service(s) instance

  11. Content Database Upgrade Process • Backup content databases • Restore to 2013 • Mount to web app • Migrate Users

  12. 0-90 Day Plan 0-30 days: • Migration preparation • Setup Staging Environments for WSS 2.0, WSS 3.0, SP 2010 and SP 2013 • Communicate to WSS 2.0 owners based on iterations • WSS 2.0 Production migration • WSS 3.0 and SP 2010 test migration iterations • UAT • Migration Fix and Mitigations • Prepare for SP 2013 Production environment setup 30-60 days: • Setup SP 2013 Production environment • Final Migration iteration • UAT 60-90 days: • Production migration • Support • Training and Knowledge Transfer • Establish SharePoint Governance

  13. Things to consider.. • Migration necessities (tool license, storage capacity, testing new farm install etc) • Release/down time • Communications • Authentication methods (of All Web Applications) • AAMs • Managed Paths • Resource Throttling (thresholds for large lists, lookups etc) • SSL • Office Web Access setup and configuration • Resource availability • Training

  14. Things to consider… • Before attaching content databases, configure web apps • Ensure web applications are setup correctly • Using correct managed account for application pool • Correct managed paths exist • Same AAM zones and URLs are configured • Solutions and other customizations are installed • Setup Portal User Accounts with the claims format. • Ensure service instances are connected to web application • Some content database upgrades attempt to use service instances • Service unavailability should not block upgrade • Service issues during upgrade may require additional work afterwards • To finish the specific service interaction missed during upgrade • Check log to look for issues

  15. Things to consider… • Content Database upgrade throttle settings • SPContentDatabase.ConcurrentSiteUpgradeSessionLimit • Maximum number of concurrent site collection upgrades that can occur against the content database at once. If exceeded the upgrade is queued. • Web Application upgrade throttle settings • Found within SPWebApplication.SiteUpgradeThrottleSettings • AppPoolConcurrentUpgradeSessionLimit • Maximum number of concurrent site collection upgrades that can occur within the web application process. If exceeded the upgrade is queued. • UsageStorageLimit • Maximum size a site collection can be for upgrade to occur within the web application process. If exceeded the upgrade is queued and occurs in timer job. • SubwebCountLimit • Maximum number of subwebs a site collection can have for upgrade to occur within the web application process. If exceeded the upgrade is queued and occurs in timer job.

  16. Install 2010 customizations Extract wsp files from current farm and install in new farm Use XCopy when not solution based Install SP2013 customizations Recommend using solutions only In some cases, 2010 customization may be used Make Web.config changes Trusted code entries Authentication providers Things to consider… • Installing Customizations Categories: • Custom authentication providers • Existing custom 2010 site definitions into 14 Site Templates directory • New SP2013 site definitions when available, 2010 if not • New upgrade definition files into 15 Upgrade Config directory • Existing custom 2010 Features into 14 Features directory • New custom SP2013 Features into 15 Features directory • Existing custom 2010 Controls into 14 CustomControls directory • New custom SP2013 Controls into 15 CustomControls directory • Existing custom 2010 Themes, JS, CSS and images into 14 directories • New custom SP2013 Themes, JS, CSS and images into 15 directories • Existing/new custom resource files into 15 directory • Existing/replacement custom Web services into 15 directories • Existing/new custom Web part or other assemblies into GAC • New custom assembly redirects into 15 directory

  17. Tips and Tricks (virtualization) Use virtualization effectively • Example, for staging machines • SharePoint 2013 • Space Needed - Add the space of your database folders, if you are migrating from different farms • Memory Needed – At least 24 GB, if you are using a single machine. • SharePoint 2010 • Space Needed - Add the space of your database folders, if you are migrating from different farms • Memory Needed – At least 16 GB, if you are using a single machine Note: A single VM staging machine is advantageous for staging machines, so you can go back to a clean state after a migration iteration. Using thin provisioning allows you to expand the space if needed.

  18. Tips and Tricks (Load Balancer) • Use your Load Balancer • Auto Redirect links to new URL • Use a test mapping group to test out the QA mappings before you cut over to production 2013

  19. Tips and Tricks (Database) • Use DB Partial Restore • Truncate transaction logs in source • Allow space for expansion when database is restored • Set Content DBs to Read only to prevent source farm from being modified

  20. Tips and Tricks (Automate) • Script everything • Web Config Modifications • Solutions installation • DB Backup • DB Restore • DB Mount • Web Application User Migration (MigrateUsers) • Fix alert links • Fix top navigation links • Fix quick launch links

  21. Tips and Tricks (Communication) • Communicate Early and Often to the right audience • Project Team • Infrastructure and Storage • Networking • Decision Makers (Approvals) • Site Owners

  22. Watch out for • Custom Web parts with dependencies (web.config, urletc) • Content Editor Web parts • Web part connections • Broken Web parts in source • Alerts (in a farm with a different URL) • Duplicate sites between two farms • Fab 40 sites • ‘#’ in quick launch (WSS 3.0) • Javascript/Jquery code that references the HTML DOM • Custom CSS • Large Lists and List View Thresholds

  23. Upgrade Related PowerShell Commands • Content Database • Mount-SPContentDatabase • Test-SPContentDatabase • Upgrade-SPContentDatabase • Site • Test-SPSite • Repair-SPSite • Upgrade-SPSite • Request-SPUpgradeEvaluationSiteCollection • Farm • Upgrade-SPFarm • e Management • Get-SPSiteUpgradeSession • Remove-SPSiteUpgradeSession • Services • New-SPBusinessDataCatalogServiceApplication • Restore-SPEnterpriseSearchServiceApplication Upgrade-SPEnterpriseSearchServiceApplication • Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings • New-SPMetadataServiceApplication • New-SPPerformancePointServiceApplication • New-SPProfileServiceApplication • New-SPProjectServiceApplication • New-New-SPSecureStoreApplication • New-SPSubscriptionSettingsServiceApplication

  24. Migration Scripts

More Related