Monday, 25 March 2013

SharePoint 2013 Migration

  • 1. SharePoint Conference
  • 2. Unleashing SharePoint Potential01 Key Business Reason to Migrate02 Migration Approaches03 Migration Cycle04 Migration Problems05 Single Shot Migration07 External Tools08 References
  • 3. 3: Key Business Drivers to Upgrade1.Storage Infrastructure improvements2.Increase End User Productivity3.Strong and Effective Enterprise Search4.Improved BI for Decision Makers5.Web Content Management6.Governance Automation7.Easy moving from SharePoint 2013 to Office 365
  • 4. 3: Migration Approaches SharePoint 2013 SharePoint 2010 MOSS 2007• No direct migration approaches to migrate MOSS 2007 to SharePoint 2013• divided it into two phase approach• first phase the MOSS 2007 code & content will be migrated to SharePoint 2010 second phase the migrated SharePoint 2010 code & content will again be migrated to SharePoint 2013.
  • 5. 3: Available Upgrade Approaches In-place Database attach1. An in-place upgrade takes place on the same A database attach upgrade enables us to move to new hardware as your previous version installation. When hardware or a new farm. During a database attach upgrade, we you run an in-place upgrade, the process upgrades detach (backup) all the content databases from an existing farm the complete installation in a fixed order. This entire and then attach the databases to a new server farm installation. migration can be executed offline in a single and When you attach the databases to the new server farm, the combined process. upgrade process runs and upgrades the data in place.2. Environment will be down for an undefined amount Does not require your source environment be down during of time. upgrade.3. As this process creates a lot of SQL transactions and This process doesn’t create any large amount of system or SQL other system logs on the system disk, it creates a disk logs on disks. overhead on multiple drives. Also this upgrade process isn’t recommended for large content database i.e. more than 50 GB.4. The upgrade proceeds continuously. You cannot Can be done one content db at a time instead of upgrading all pause the upgrade process in between. the content db in a single transaction.5. No rollback As source environment will be untouched no need of rollback.6. Less control over upgrade process, can’t predicate More flexible than in-place, exact time can be determine for most activities time involved in overall process. each activities involved in overall process.
  • 6. 3: Migration Cycle 1.Plan 5.Validate 2.Prepare 4.Implement 3.Test
  • 7. 3: Migration CyclePlan Prepare Test Implement Validate Document Build test farms Build/upgrade TroubleshootingDetermine strategy environment farms Manage Use real data Deploy Upgrade eventCreate a plan for customizations customizations failurescurrent customization Plan upgrade Evaluate Minimize UI/UX issuesPlan for site collection strategy techniques downtime Make items Find issues early Monitor progress Data issuesPlan for performance upgradableCreate acommunication planClean up anenvironment
  • 8. 3: Plan Checklist Content Databases Service Applications Farm/Web Application Farm Settings List down all the customizations Plan Upgrade Performance
  • 9. 3: Plan – Best PracticesEnsure that the environment is fully functioning before you begin toupgrade.Perform a trial upgrade on a test farm first.Plan for capacity.Back up your databases.Optimize your environment before upgrade..
  • 10. 3: Prepare – Moss 2007 to SharePoint 2010 Create the SharePoint 2010 farm • Installs SharePoint 2010 to a new farm Web Application Creation & Code Deployment • Creates a new web application Or database database • Installs all server-side code customizationsIn-place attach attach Upgrade MOSS 2007 databases • Sets the MOSS 2007 Site Collection to read-only so that users can continue toOOTB Migration Approach Recommended access the old site while upgrade is in progress on the new farm /Available in 2013 • Back up the content databases from the SQL Server instance on the MOSS 2007 Web Application • Restores a copy of the databases to the SQL Server instance on the SharePoint 2010 Web Application • Attaches the content databases to the new farm and upgrades the content databases for this web application
  • 11. 3: Testing – Best PracticesKnow what is in your environment. Do a full survey first.Make your test environment as similar as possible to your real environment.Use real data.Run multiple tests.Do not ignore errors or warnings.Test the upgraded environment, not just the upgrade process.
  • 12. 3: Implement – SharePoint 2013 Upgrade Process
  • 13. 3: Implement – SharePoint 2013 Upgrade Process Create the SharePoint 2013 farm • GATHER INFORMATION AND CLEAN UP 2010 • Installs SharePoint 2013 to a new farm FARM • PREPARE 2013 FARMPREPARE Web Application Creation & Code Deployment • Creates a new web application • Installs all server-side code • COPY DATABASE customizations • UPGRADE SERVICE APPLICATION DATABASES Copy & Upgrade SharePoint 2010 • CREATE WEB APPLICATIONS AND APPLY databases UPGRADE CUSTOMIZATIONSDATABASES • UPGRADE CONTENT DATABASES • Sets the SharePoint 2010 Site Collection to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm • RUN SITE COLLECTION HEALTH CHECKS • Back up the content databases from the • RUN SITE COLLECTION HEALTH CHECKS SQL Server instance on the SharePoint • CREATE AN UPGRADE EVALUATION SITE 2010 Web ApplicationUPGRADE COLLECTION • Restores a copy of the databases to the • UPGRADE A SITE COLLECTION SITES SQL Server instance on the SharePoint 2013 Web Application • Attaches the content databases to the new farm and upgrades the content databases for this web application
  • 14. 3: Validate Review Logs• Upgrade Logs• Application Event Logs Validate Migrated Environment• Review and Validate Web Applications• Review and Validate Services• Validate External Data Sources• InfoPath • BCS Connections (External Content Types and External Lists) • Excel Services connections • External targets for Enterprise Search• Authentication Providers• Customization defects and fixes
  • 15. 3: Site Collection Health Check• The health checks are run automatically in repair mode when you start to upgrade a site collection.• Health checks examine a site collection and list potential upgrade issues, such as missing or unsupported elements Rule name Description This rule checks for any files that were customized Customized Files in the site collection or sub sites Missing Galleries This rule checks for all default galleries This rule checks to make sure that the template the Missing Site Templates site is based on is available and reports if any elements are missing. This rule checks to make sure that the language Unsupported Language Pack References packs that are used by the site collection exist and are referenced correctly by the site collection. This rule checks to make sure that the multi-user interface elements that are used by the site Unsupported MUI References collection exist and are referenced correctly by the site collection.
  • 16. 3: References
  • 17. 3: Migration Problems1. SP technology 2013 workflows are built on Windows Workflow Foundation 4(WWF4). However, SharePoint 2010 workflows continue to Windows WorkflowFoundation 3 (WWF3). The workflow migration is not suggested:- There is one more framework available with SP 2013 called as WAW. But AFAIK you can still create SP2010 type workflows using SPD2013.2.Error during upgrade is missing server-side files, templates, features, or otherserver-side customizations— either files that were installed with SharePoint2010 Products or customized files:- When you prepared for upgrade, you should have created an inventory of theserver-side customizations. Check this inventory to make sure that all the files thatare needed for your customizations are installed in your new environment.3.More than 5,000 site collections in a database, consider breaking them outinto multiple databases.To avoid errors during upgrade or broken sites after upgrade, we recommend thatyou move some site collections into separate databases. If you have multiplecontent databases, you can also speed up an upgrade process by upgradingmultiple databases in parallel
  • 18. 4. Some sites and site templates are not available in SharePoint 2013 .Sitesbased on these templates will not work in SharePoint 2013. Remove these typesof sites before you upgrade:-You can use the Get-SP Site Windows PowerShell command togetherwith the following options to find these sites:Get-SPSite|Where-Object{$_.RootWeb.Template- eq"PowerPointBroadcast#0“}5. If you haven’t installed SharePoint 2010 SP1, after you upgrade to SPServer 2013, your out-of-the-box workflow tasks (such as Approval, CollectFeedback) will go into locked status:-Users should install SharePoint 2010 SP1 before upgrade to SharePointServer 2013.6. We could create a list item under folder in custom list using Create ListItem action in SharePoint 2010 but in SharePoint 2013 Create List Itemaction doesn’t support creating items in the folder due to platform limitation:- Try calling SharePoint 2010 workflow using Start a list/site workflow action in the SharePoint 2013 workflow.
  • 19. 7.A mismatch in authentication methods can cause problems when you upgrade:-Claims-based authentication is the default authentication method for webapplications in SharePoint 2013. If the web application was using classic mode, youcan either update it to claims before you upgrade the database, or create the webapplication in classic mode and then migrate it to claims.8.You cannot upgrade a database that is set to read-only.Make sure that you set the databases to read-write before you attach and upgradethe databases.9.You must manually create all trusted data connections for Excel Services afterupgrade.10.How to upgrade environments that include services farms to SP2013.Some services in SharePoint 2010 Products can be shared across multiple farms . Aservices farm hosts services such as Business Data Connectivity service, Search, andUser Profiles that other farms consume. When you upgrade to SharePoint 2013, youfirst upgrade the services farm, and then upgrade the farms that consume thoseservices.
  • 20. Metalogix Content Manager 6.0 Features:1. Direct Upgrade to SharePoint 20132. Migrate File Shares and more 1. Content Matrix 6.0 connects and moves terabytes of content from file shares, blogs, wikis, Exchange Public Folders, PST files, eRoom and websites. 2. Content Matrix 6.0 moves the content, files, associated metadata and other relevant attributes such as permissions or information structure into SharePoint. Empower Content Owners
  • 21. Key Benefits:1. Upgrade with Confidence2. Move to the Cloud: Office 365 and Office 365 Dedicated3. Keep SharePoint Organized4. migration speeds of up to and beyond 125GB per hour5. Move Structure, Workflows and Permissions6. Analyze your existing contentSupported Source Systems1. SharePoint Server 2013 & 20102. SharePoint Foundation 2013 & 20103. Office 3654. Office SharePoint Server 2007 & WSS 3.05. SharePoint Portal Server 2003 & WSS 2.06. File Shares7. Exchange Public Folders & PST files8. Google Blogger, Word press, Movable Type, Telligent9. Blogs using Metaweblog standard or RSS10. Atlassian Confluence, Media Wiki11. HTTP or HTTPS accessible websites

No comments:

Post a Comment