Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies
Upcoming SlideShare
Loading in...5
×
 

Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies

on

  • 947 views

Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies

Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies

Statistics

Views

Total Views
947
Views on SlideShare
943
Embed Views
4

Actions

Likes
1
Downloads
18
Comments
0

2 Embeds 4

http://www.linkedin.com 3
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • When Microsoft went into the Product development phase for SharePoint 2013, they realised that there were a few key things standing out for people. One of the big ones is that Customers want the upgrades to be safer. Customers also want reduced outages, they complain that the upgrades are too long, I have this big outage and impact my organisation. And then of course Microsoft came up with something a little innovative and they were doing this partially to bring back something that they took away in 2010 which was the gradual upgrade and also to address some of the scale and scheduling aspects.  So first on safer upgrades, in all the previous releases Microsoft allowed you to do an in place upgrade. This was possible in all previous releases until now, it's now gone. They got rid of this mainly from the aspect of safety. A large amount of customers which had issues in previous versions were mainly due to in place upgrades. They would get half way through and then encounter issues, and then perhaps went via the database attach approach. They've given you the ability to do a preview of the site collection. It's been made a little bit more obvious in this release. As for outages one of the things they realised is that if we could reduce how much we have to upgrade when we do a version to version upgrade we can cut away 2 thirds of the upgrade time.  And of course the last part is giving power to the people and giving them control which is the heart of the differed upgrade option.
  • A server farm administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.A server farm administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm.Figure: Create new farm, set old farm to read-onlyRemove orphaned itemsPowerPoint Broadcast sitesWeb analyticsCustomizations you can’t move forward (e.g. incompatible with 2013)Build-out new 2013 farm(s)Install customizations onto new farmEnsure you install customizations for both 14 and 15 mode as appropriate
  • Copy the SharePoint 2010 Products databasesThe second stage in the upgrade process copies the databases to the new environment. You use SQL Server Management Studio for these tasks.With the farm and databases in read-only mode, a server farm administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.The server farm administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.
  • =Performing self service upgrade=Go to site settings and click on site collection upgrade.Click refresh on landing page to show upgrade bar at the top of the page.Slight bug is that it says SharePoint 15!Clicking remind me later will mute the bar for 30 days, this is configurable by the farm admin.Let's actually click on start now and it brings you to site collection upgrade.A couple of controls appears, If you click on evaluation button, it will create a copy your site. Note the URL stating that it's EVAL.  Let's go for the upgrade of the site collection and click on yes you are sure. First thing that is happen is the health check, it will refresh back and will state that the upgrade is in progress. The state that it is in is the queue and the site collection goes into a read only state. =Successful upgrade UI= =Log file= the copy of the log is placed not on the server but in a portion of the site collection. End users aren't supposed to read this, its for support purposes and the users can fire this to the IT pros. *end of demo*
  • =Performing self service upgrade=Go to site settings and click on site collection upgrade.Click refresh on landing page to show upgrade bar at the top of the page.Slight bug is that it says SharePoint 15!Clicking remind me later will mute the bar for 30 days, this is configurable by the farm admin.Let's actually click on start now and it brings you to site collection upgrade.A couple of controls appears, If you click on evaluation button, it will create a copy your site. Note the URL stating that it's EVAL.  Let's go for the upgrade of the site collection and click on yes you are sure. First thing that is happen is the health check, it will refresh back and will state that the upgrade is in progress. The state that it is in is the queue and the site collection goes into a read only state. =Successful upgrade UI= =Log file= the copy of the log is placed not on the server but in a portion of the site collection. End users aren't supposed to read this, its for support purposes and the users can fire this to the IT pros. *end of demo*
  • Requires 3rd party tools or manual migrationRead-only databases  You can use read-only databases to continue to provide read-only access to content during the upgrade process. For this approach, you set the databases to read-only on the original farm while the upgrade is in progress on another farm. This method reduces perceived downtime for users. Also, if you encounter a problem with upgrade, you can restore the read-only farm to read-write and restore access to users while you rework your plans before you try upgrade again.Parallel database upgrades  You can attach and upgrade multiple databases at a time to speed up the upgrade process overall. The maximum number of parallel upgrades depends on your hardware. This results in faster overall upgrade times for your environment. However, you must monitor the progress and your servers to make sure that the performance is acceptable, and for large databases, parallel upgrades can be slower than single upgrades.
  • Since 2001, our infrastructure management software has been fundamental to scaling and growing SharePoint as the backbone of many organizations, supporting SharePoint as a social enterprise collaboration platform.  In 2013, we’re continuing our tradition of extending not only SharePoint’s possibilities by enabling application development, scalable storage, enterprise data protection strategy, geo-distributed collaboration, compliance, records management, and service-oriented data center management – but we’re taking it a step further to enable true enterprise collaboration with confidence. (Click)Microsoft Technologies:Founded and debuted in 2001 with inaugural SharePoint releaseDepth-Managed, Microsoft Certified PartnerProducts Supported:SharePoint -- World's Largest SharePoint-Exclusive Research & Development Team with 1,300 Employees (800+ in R&D)Office 365 Dynamics CRM (near future)(Click)Solutions:Infrastructure ManagementGovernanceComplianceCloudPublic SectorECM/WCMStorage(Insert Your Vertical Specific)etc.(Click)Partners:Depth-Managed Microsoft PartnerNetwork of authorized partners and resellersTechnology Alliance Partners include:Amazon Web Services (AWS)Critical Path TrainingDellIBM NetApp(Click)Support:25 Offices, 13 Countries in 5 Continents & 10,000+ CustomersOffering True 24 x 7 Support - Microsoft Certified TechniciansTechnical account management (TAM) services – premier maintenance package(Click)Services:AvePoint Client Services (ACS)Implementation servicesTraining & Education servicesPartner services(Click)Community:DocAve.com communityGlobal Partner network communityAvePoint innovation center and thought leadership in SharePoint community
  • Identify customizations in your environmentEvaluate the customizationsIs the customization still valuable?Sitedefinitions,customsitetemplates, FAB40, features, workflows, master pages, webpartsSolutionsinstallationusing –CompatibilityLeveloption {14|15}

Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies Presentation Transcript

  • | Lausanne Successful Migration to SharePoint 2013 - Planning Considerations & Migration Strategies Roberto V. Delgado Sr. Technical Solutions Professional @AvePoint
  • Design Goals for SharePoint 2013 Upgrades Farm Upgrade Overview Site Collection Upgrades Upgrade and Migration Strategies General Recommendations 5’ Q&A 10’ 10’ 20’ 5’ 10’ Agenda
  • About me: Roberto V. Delgado Roberto.delgado @avepoint.com
  • Design Goals for 2013 Upgrades Safer upgrades Removal of in-place version to version upgrades (Note: Build to build in-place upgrades still work fine) Adding site collection health checks Adding evaluation sites to allow preview of what upgrade will do Reduced outage duration Separating database upgrade from site collection upgrade (*saves ~2/3 upgrade time) Mitigate more outages with read only time providing air cover for operations Power to the people Let site collection admins control their own destiny (*within farm admin controlled limits) Tell users what’s happening using upgrade email messages and system status bar
  • | Lausanne Farm Upgrade Overview
  • Prepare
  • Detach and Re-attach Databases
  • PowerShell Command
  • Recap Upgrade Stages
  • Demo: Farm Upgrade
  • | Lausanne Site Collection Upgrades
  • Deferred Site Collection Upgrade Eliminate big bang upgrades Upgrade database now, upgrade site collections later Keep existing customizations, updated ones can wait Move forward at a manageable pace Initially let users stay with 2010 experience: • Stay with the familiar • Keep using existing customizations Gradually move users over to 2013 experience: • As training occurs (e.g. incrementally for each team) • As users decide to adopt new experience/features • As new version compatible customizations are available Provide self-service site collection upgrade capability Site collection admins can easily do the upgrade Admins can still do upgrades or prevent users from doing them
  • Site Collection Health Checks Rules can detect and in some cases repair issues Rules can exist for use in 14 and/or 15 modes Same or different rules may apply Can be run without doing upgrade Give advanced notice of potential future issues
  • Evaluation Site Collections Copy of existing site collection Copy not intended for long term use; Evaluation site collection cannot become permanent Version upgraded automatically as default Copy made using snapshot or site collection backup/restore Can only have one evaluation site collection for a given source site collection Self-service creation only for small site collections Maximum size configurable by farm admin controlled web application level settings Large ones need farm admin to do create the evaluation site collection Farm admin can copy any site collection as an evaluation site collection PowerShell command to Request-SPUpgradeEvaluationSite queues creation Evaluation site collections expire Expiration date tracked on each evaluation site collection Expiration date based on creation date and farm admin controlled expiry delay
  • Demo: Site Collection Upgrade
  • Summary of Farm Upgrade 1. Backup everything 2. Upgrade services first Search Administration database Profile, Social, and Sync databases Managed Metadata/Taxonomy database Secure Store database Project Server databases 3. Upgrade content databases Site collection upgrade automatically deferred 4. Upgrade site collections at your leisure
  • Summary of Farm Upgrade 5. Confirm successful upgrade state 6. Enable/disable self-service upgrades as required 7. Re-index existing content
  • | Lausanne Upgrade and Migration Strategies
  • Upgrade and Migration Strategies • Upgrade to next version • Jump to the latest version (i.e from MOSS 2007 or SPS2003) • Migrate to the Cloud
  • Migration with Third Party Tools SharePoint Administrator installs the new version on separate hardware or a separate farm, and migrates content and users using 3rd Party Tool Best For Any size environment, from single server farm to large, distributed farms  Restructuring content  Preservation of any metadata or security  Mappings (Templates, users, field types, content types…)  Pros  Direct migration from 2007 to 2013  Pre-scan to determine content & customizations  Granular migration  Virtually no downtime  Applicable to nonSharePoint repositories  Incremental migrations Cons  Costs associated with purchasing of additional software  Training
  • | Lausanne General Recommendations
  • Best practices • Clean up an environment before an upgrade • Create a plan for current customizations during upgrade • Plan for authentication • Plan for performance during upgrade • Create a communication plan for the upgrade • TEST
  • | Lausanne Q&A