Practical Guidance for Your SharePoint 2010 Upgrade: It’s Not Just Going from Point A to Point B<br />Joel Oleson<br />Sr....
SharePoint 2007 vs. 2010: Should I stay or Should I go?!!<br />
Upgrade Cycle: Overview<br />
Prerequisites<br />Common issues<br /><ul><li>64 bit only
Operating System
SQL server
Missing dependencies
UI changes
Lack of space
Forms Authentication Providers</li></ul>Upgrade methods<br />Downtime mitigation<br /><ul><li>In-Place
Database Attach
Content
Profile
Project
WID to SQL Migration
Read-only content databases
Parallel upgrades:
Multiple temporary farms
Parallel database attach
AAM redirection</li></ul>Upgrade Cycle: Learn<br />
Upgrade Cycle: Test<br />
Upgrade Cycle: Implement<br />
Upgrade Overview<br />Drill Down on Binary Upgrade Methods<br />Windows PowerShell Upgrade Cmdlets<br />Approaches to Upgr...
Upgrade Cycle: Validate<br />
Drill down<br />
Learning from PreUpgradeCheck<br />
SharePoint PreUpgradeCheck Report<br />
Test-SPContentDatabase<br />
Attaching Database to SP2010 Farm<br />
Insight on Upgrade<br />Binary Upgrade<br />In Place (New No Timeout, Continue on failures)<br />Database Attach (New para...
Binary Upgraded Site: Preview Visuals – Sneak Peak Screenshot<br />
In-Place Upgrade<br />All-at-once upgrade<br />Must upgrade the whole farm at one time<br />Cannot intermingle SP 2007 and...
Database Attach Upgrade<br />Safer, Requires more planning (A good thing)<br />Upgrade is done on a separate 2010 farm<br ...
Visual Upgrade<br />Stay in 2007 (default) or move to 2010 UI<br />2010 ships 2007 Master pages and CSS<br />UI Preview ca...
Unsupported Upgrade Methods<br />Unsupported Scenarios<br />Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2 (Requires S...
Insights<br />
2010 Upgrade PhilosophyWhat were we thinking<br />Detect issues early<br />Provide O12 tools to admins<br />Report critica...
Upgrade PerformanceWhy prediction is difficult<br />Database Shape Centric<br /># Site Collections<br /># Webs<br /># List...
Common Upgrade Failure Issues & Recovery<br />Determine cause of failure<br />Status Page & Upgrade Logs:<br />Program Fil...
Upgrade TestingWhat are you looking for in a test?<br />Upgrade Issues<br />Long, Wide lists<br />Modified databases<br />...
Upgrade InternalsDetails<br />V2V upgrade DBs set to simple recovery<br />DB growth during upgrade:<br />Versions and inde...
Upgrade Strategies<br />
Read-Only Content DatabasesReducing perceived downtime<br />Not just for upgrade or patching<br />Manually initiated proce...
Windows PowerShell Upgrade Cmdlets<br />Test-SPContentDatabase<br />Discover and Document issues 2007/2010<br />Upgrade-SP...
1. In Place - Binary Approach to Upgrade<br />Caution: Not recommended for most deployments…<br />
2. DB Attach- Binary Approach to Upgrade <br />Recommended for most deployments…<br />
Binary Approaches to Upgrade - Hybrid<br />
Upcoming SlideShare
Loading in...5
×

Practical Guidance for SharePoint 2010 Upgrade

12,209

Published on

SharePoint 2010 upgrade can be a daunting task. This session attempts to simplify while drilling into techniques and approaches and tactics to better execute upgrade and its methods.

Published in: Technology, Business
1 Comment
9 Likes
Statistics
Notes
No Downloads
Views
Total Views
12,209
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
948
Comments
1
Likes
9
Embeds 0
No embeds

No notes for slide

Transcript of "Practical Guidance for SharePoint 2010 Upgrade"

  1. 1. Practical Guidance for Your SharePoint 2010 Upgrade: It’s Not Just Going from Point A to Point B<br />Joel Oleson<br />Sr. Product Architect<br />Quest Software<br />http://www.sharepointjoel.com<br />Contributions: Sean Livingston<br />
  2. 2. SharePoint 2007 vs. 2010: Should I stay or Should I go?!!<br />
  3. 3. Upgrade Cycle: Overview<br />
  4. 4. Prerequisites<br />Common issues<br /><ul><li>64 bit only
  5. 5. Operating System
  6. 6. SQL server
  7. 7. Missing dependencies
  8. 8. UI changes
  9. 9. Lack of space
  10. 10. Forms Authentication Providers</li></ul>Upgrade methods<br />Downtime mitigation<br /><ul><li>In-Place
  11. 11. Database Attach
  12. 12. Content
  13. 13. Profile
  14. 14. Project
  15. 15. WID to SQL Migration
  16. 16. Read-only content databases
  17. 17. Parallel upgrades:
  18. 18. Multiple temporary farms
  19. 19. Parallel database attach
  20. 20. AAM redirection</li></ul>Upgrade Cycle: Learn<br />
  21. 21. Upgrade Cycle: Test<br />
  22. 22. Upgrade Cycle: Implement<br />
  23. 23. Upgrade Overview<br />Drill Down on Binary Upgrade Methods<br />Windows PowerShell Upgrade Cmdlets<br />Approaches to Upgrade<br />Dev - Feature Upgrade<br />Visual Upgrade<br />Patch Management<br />Downtime Mitigation Processes:<br />Parallel Upgrade Pipelines<br />Content DB Upgrade with AAM Redirection<br />Improved<br />Upgrade Status Reporting<br />Upgrade Logging<br />Read-only DB Support<br />Simplified Upgrade Methods<br />Removed<br />Gradual Upgrade<br />Side By Side Installation<br />
  24. 24. Upgrade Cycle: Validate<br />
  25. 25. Drill down<br />
  26. 26. Learning from PreUpgradeCheck<br />
  27. 27. SharePoint PreUpgradeCheck Report<br />
  28. 28. Test-SPContentDatabase<br />
  29. 29. Attaching Database to SP2010 Farm<br />
  30. 30. Insight on Upgrade<br />Binary Upgrade<br />In Place (New No Timeout, Continue on failures)<br />Database Attach (New parallel Db upgrade, progress in CA & better logs)<br />Visual Upgrade<br />Not required until next version<br />Separate process<br />You decide when & how!<br />Often delegated<br />
  31. 31. Binary Upgraded Site: Preview Visuals – Sneak Peak Screenshot<br />
  32. 32.
  33. 33. In-Place Upgrade<br />All-at-once upgrade<br />Must upgrade the whole farm at one time<br />Cannot intermingle SP 2007 and SP2010 in same farm<br />Schedule downtime<br />Simplest approach, but *most risky*!<br />No going back<br />Resume Upgrade if problems occur<br />Recommendations<br />Run Test-SPContentDatabase from SP 2010 farm against databases<br />Do a full farm backup before you start!<br />
  34. 34. Database Attach Upgrade<br />Safer, Requires more planning (A good thing)<br />Upgrade is done on a separate 2010 farm<br />Done database-by-database <br />Can be used as 2 step gradual visual upgrade<br />Use Test-SPContentDatabase (PowerShellcmdlet) to test database first<br />To attach<br />Upgrade-SPContentDatabase (PowerShell)<br />Addcontentdb operation (STSADM)<br />Parallel database upgrades are possible<br />
  35. 35. Visual Upgrade<br />Stay in 2007 (default) or move to 2010 UI<br />2010 ships 2007 Master pages and CSS<br />UI Preview capability<br />Farm admin or site admin controlled<br />Web level setting<br />Some items not 2007 UI compatible<br />My site host<br />PWA site collection<br />Report Server web parts<br />
  36. 36. Unsupported Upgrade Methods<br />Unsupported Scenarios<br />Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2 (Requires SP2, but Oct CU or later is preferred)<br />Direct upgrade from WSS v2/SPS 2003 or earlier<br />Side by side installation<br />Gradual upgrade<br />Third party tools like Quest Software Migration Manager will have support for Upgrade from 2003<br />
  37. 37. Insights<br />
  38. 38. 2010 Upgrade PhilosophyWhat were we thinking<br />Detect issues early<br />Provide O12 tools to admins<br />Report critical issues at start of upgrade<br />Keep the administrator informed<br />No data loss<br />Keep content and settings<br />Minimize downtime<br />Downtime mitigation processes<br />Continue when possible<br />Be reentrant<br />Upgrade should not be catch 22<br />
  39. 39. Upgrade PerformanceWhy prediction is difficult<br />Database Shape Centric<br /># Site Collections<br /># Webs<br /># Lists<br /># Document Versions<br />Document Versions Size<br /># Documents<br /># Links<br />Overall DB Size<br />Hardware Centric<br />SQL Disk I/O per second<br />SQL Database to disk layout<br />SQL Temp DB optimizations<br />SQL CPU & Memory<br />WFE CPU & Memory<br />Network Bandwidth & latency<br />
  40. 40. Common Upgrade Failure Issues & Recovery<br />Determine cause of failure<br />Status Page & Upgrade Logs:<br />Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12Logs<br />Error log<br />Full upgrade log<br />Customizations Management Commands:<br />Test-SPContentDatabase<br />stsadm -o EnumAllWebs<br />Fix issue(s)<br />Install missing or updated customizations<br />Activate missing services; farm, web app settings<br />Resume upgrade<br />Farm upgrade command<br />Content database specific upgrade command<br />Service specific upgrade commands<br />
  41. 41. Upgrade TestingWhat are you looking for in a test?<br />Upgrade Issues<br />Long, Wide lists<br />Modified databases<br />Customizations<br />Authentication providers<br />Recommendations<br />Test server side customizations<br />Verify in both Upgrade modes including visual<br />Consider read only preview<br />Similar hardware<br />Use real datasets<br />Don’t ignore warnings<br />
  42. 42. Upgrade InternalsDetails<br />V2V upgrade DBs set to simple recovery<br />DB growth during upgrade:<br />Versions and indexes; SQL logs<br />Shrink DBs after upgrade; not automatic<br />SQL timeouts:<br />Removed command timeouts (query time)<br />Retained connection timeouts<br />SetupPath fallback logic<br />Object locking during upgrade:<br />Maintained in config DB<br />Automatic removal of stale locks (2 minutes)<br />
  43. 43. Upgrade Strategies<br />
  44. 44. Read-Only Content DatabasesReducing perceived downtime<br />Not just for upgrade or patching<br />Manually initiated process<br />Read-only locking:<br />Content remains static<br />SQL controls read-only lock status<br />SharePoint promotes SQL lock to site lock<br />UI Trimming enforced by site lock<br />Upgrade copy of database on different farm<br />
  45. 45. Windows PowerShell Upgrade Cmdlets<br />Test-SPContentDatabase<br />Discover and Document issues 2007/2010<br />Upgrade-SPContentDatabase<br />Common Scenarios:<br />Initiate/resume content database B2B upgrades<br />Resume failed content database V2V upgrades<br />Upgrade-SPEnterpriseSearchServiceApplication<br />Search Service Application Instance<br />Upgrade-SPSingleSignOnDatabase<br />O12 SSO data to Secure Store database<br />
  46. 46. 1. In Place - Binary Approach to Upgrade<br />Caution: Not recommended for most deployments…<br />
  47. 47. 2. DB Attach- Binary Approach to Upgrade <br />Recommended for most deployments…<br />
  48. 48. Binary Approaches to Upgrade - Hybrid<br />
  49. 49. Downtime Mitigation Processes<br />Read-only databases<br />Parallel upgrade farms<br />Single farm, multiple upgrade sessions<br />Content database attach with AAM redirection<br />
  50. 50. SSP to Service App<br />Each SSP upgrades into:<br />A Search service app<br />A User Profiles service app<br />An Excel service app<br />An App Registry back-compat service app<br />New Services can be activated/added<br />
  51. 51. Visual Upgrade Capability<br />Stay in O12 UI (default) or move to O14 UI<br />O14 ships O12 Master pages and CSS<br />UI Preview capability<br />Farm admin or site admin controlled<br />Web level setting and OM<br />Some items not O12 UI compatible:<br />My site host<br />PWA site collection<br />Report Server web parts<br />
  52. 52. Visual Upgrade Caution<br />No Visual backward compatible UI for My Sites<br />Database Attach into My Site Host<br />In place upgrade your My Site Host<br />Other Services UI may be impacted<br />Project Web Access site collection<br />Reporting Server web parts<br />
  53. 53. Depreciation<br />Performance Point – Included in SharePoint 2010 Enterprise <br />My Site Host Redesign – No visual upgrade for my sites <br />Side by Side Installation - Gradual Upgrade <br />SSP Admin UI – Any work you did on either the SSP Admin Site Collection or the Central Admin site has changed.  <br />Admin task list and other CA lists <br />Document Discussions is deprecated.  Not very common.<br />Deprecated Templates<br />SSP Admin Site<br />Great Plains (STSPKPL (Plus Pack)<br />References: Deprecation of Features in SharePoint 2010<br />
  54. 54. What about Custom Site Definitions?<br />Most custom site definitions from v3 should continue to work unmodified while in v3 UI mode of Visual Upgrade. However depending on what is in that site definition, a person may still want to do more featurization or other definition refactoring, which is where the upgrade definition file comes in handy. As always, test the existing definition against an upgraded server in both UI modes<br />- Sean Livingston, Upgrade PM<br />
  55. 55. Dev - Feature Upgrade Capability<br />Optional Capability<br />Declarative Feature Upgrade Activities:<br />ApplyElementManifests<br />AddContentTypeField<br />MapFile<br />Custom Code Feature Upgrade<br />CustomUpgradeAction Activity<br />SPFeatureReceiver.FeatureUpgrading<br />Assembly in GAC<br />
  56. 56. Upgrade PlanningHow to manage a complex process – PMs Matter A LOT!<br />Customer Communications<br />Farm/Customizations Surveys<br />Upgrade/Customizations Testing<br />Environment Cleanup<br />Hardware Build-out<br />Customizations Deployment<br />Backups Before Upgrade<br />Operations Scheduling<br />Rollback/Restore Plan<br />Post-Upgrade Activities<br />Ongoing Support Calls<br />
  57. 57. What can I do today to prepare?<br />Test!!!<br />Work towards 64-bit server environments<br />Upgrade to Service Pack 2 (SP2)<br />Review and identify your customisations<br />Cleanup as much as possible<br />Verify custom solutions work and deploy in 2010<br />Optimise your large lists<br />Optimise your content databases<br />Run PreUpgradeCheck that’s part of SP2<br />
  58. 58. Announcing FREE!<br />Quest Reports For SharePoint<br />
  59. 59. http://www.quest.com/reportsforsharepoint<br />
  60. 60. Quest Solutions for SharePoint <br />Site Administrator for SharePoint <br />Understand, manage and secure your SharePoint environment<br />Quest SQL Server Solutions <br />Maximize SQL Server performance while simplifying tasks and providing visibility and control<br />Quest Web Parts <br />Enable rapid development <br />of SharePoint applications<br />Recovery Manager for SharePoint<br />Granular SharePoint recovery for enterprise-level needs<br />Migration Manager for SharePoint <br />SharePoint to SharePoint migration<br />File Migrator for SharePoint <br />File shares to SharePoint migration<br />Public Folder Migrator for SharePoint<br />Exchange Public Folders to SharePoint migration<br />Notes Migrator for SharePoint<br />Notes application content to SharePoint migration<br />
  61. 61. Technology Responsibilities<br />Toughest Challenges<br />User Provisioning/de-provisioning<br />Delegation of Admin Rights<br />Compliance Reporting<br />Disaster Recovery<br />Technology Used / Deployed<br /><ul><li> 99% MS Server OS
  62. 62. 90% Management Frameworks
  63. 63. 55% - MOM
  64. 64. 27% - HP OpenView
  65. 65. 21% - IBM Tivoli
  66. 66. 87% Exchange
  67. 67. 74% SharePoint</li></ul>Source: DEC 2008 Attendee Survey Whitepaper<br />45<br />
  68. 68. Thank You!<br />
  69. 69. Q&A<br />
  70. 70. Additional Resources<br />Slides:Preparing for Upgrade to SharePoint 2010 Today<br />Article:Preparing for SharePoint 2010 Upgrade Today <br />Upgrade Resources: http://www.SharePointJoel.com!<br />SharePoint 2010 Upgrade Resource Centers<br />Upgrade and migration resource center for SharePoint Foundation 2010 - TechNet <br />Upgrade and migration resource center for SharePoint Server 2010 – TechNet <br />SharePoint 2010 Upgrade Resource Center – MSDN  <br />SharePointUpgrade.com - Community driven wiki based SharePoint 2010 Upgrade resources<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×