Upgrading Microsoft Office SharePoint Server 2007 to SharePoint Server 2010<br />Ivan Sanders<br />SharePoint ArchitectDim...
Who Am I?<br />Ivan Sanders<br />Blog: www.dimension-si.com/blog<br />Twitter: @isanders<br />Facebook http://facebook.com...
Upgrade Scenarios and Methods<br />Supported Scenarios<br />In-Place Upgrade<br />Database Attach Upgrade:<br />Content Da...
In-Place<br />Next, next, finished ;)<br />Advancements<br />Restartable!<br />Common blocking time outs removed<br />
In-Place Upgrade<br />All sites are unavailable during upgrade <br />Site visitors continue to use the same URLs after upg...
Inplace Upgrade<br />DEMO<br />
In-Place Pros/Cons<br />Pros<br />Cons<br />Farm wide settings are preserved and upgraded<br />Customizations are availabl...
Database Attach Steps<br />Stsadm –o preupgradecheck on your 2007 farm<br />Backup 2007 Content DB<br />Restore to SharePo...
DB Attach Pros/Cons<br />Pros<br />Cons<br />Upgrade multiple content databases at the same time <br />Combine multiple fa...
Database Attach<br />DEMO<br />
Hybrid Approach<br />Detach DBs<br />Upgrade to 2010 in-place<br />DB Attach content DBs<br />
Hybrid Pros/Cons<br />Pros<br />Cons<br />Farm wide settings preserved<br />Customizations alreadyin place<br />Multiple c...
Hybrid Approach<br />DEMO<br />
Downtime Mitigation Processes<br />Read-only databases (v3 SP2, v4)<br />Parallel content database upgrades<br />Parallel ...
Move DB<br />Database Attach with AAM RedirectUser interaction model<br />SQL<br />SQL<br />?<br />302<br /><br />http://...
What is “Visual Upgrade”<br />A feature that separates data upgradefrom UI upgrade<br />Data and code upgrade happens all ...
Why “Visual Upgrade”?<br />IT<br />Focus on the data<br />Schedule flexibility<br />Developers<br />Clear expectations<br ...
Visual Upgrade<br />DEMO<br />
Core Upgrade Overview Improvement<br />Upgrade improvement areas<br />Predictability/reliability<br />Diagnostic ability/l...
Core Upgrade Improvements<br />Logging<br />Upgrade logs per session(saved in same place)<br />Error log per session ( -er...
Upgrade points to consider<br />V3 must be Service Pack 2 or later<br />You cannot upgrade a Trial SKU<br />FBA web applic...
Q & A<br />
Upcoming SlideShare
Loading in...5
×

SoCalCodeCamp Upgrade Microsoft Office SharePoint Server 2007 to SharePoint Server 2010

951

Published on

Upgrade your Server farm SharePoint 2007 to a new version, or migrate content to a new SharePoint 2010 environment. This presentation helps you plan and perform the upgrade.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
951
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "SoCalCodeCamp Upgrade Microsoft Office SharePoint Server 2007 to SharePoint Server 2010"

  1. 1. Upgrading Microsoft Office SharePoint Server 2007 to SharePoint Server 2010<br />Ivan Sanders<br />SharePoint ArchitectDimension Solutions inc.<br />ivan@dimension-si.com<br />
  2. 2. Who Am I?<br />Ivan Sanders<br />Blog: www.dimension-si.com/blog<br />Twitter: @isanders<br />Facebook http://facebook.com/iasanders<br />LinkedIn http://linkedin.com/in/iasanders<br />MSDN Forums<br />
  3. 3.
  4. 4. Upgrade Scenarios and Methods<br />Supported Scenarios<br />In-Place Upgrade<br />Database Attach Upgrade:<br />Content Database<br />Profile Service Database<br />Project Service Database<br />Single Click Install - SQL Migration<br />Windows Internal Database (WID) -> SQL Express 2008 + File Stream RBS<br />Unsupported Scenarios<br />Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2<br />Direct upgrade from WSS v2/SPS 2003 or earlier<br />Side by side installation<br />Gradual upgrade<br />
  5. 5. In-Place<br />Next, next, finished ;)<br />Advancements<br />Restartable!<br />Common blocking time outs removed<br />
  6. 6. In-Place Upgrade<br />All sites are unavailable during upgrade <br />Site visitors continue to use the same URLs after upgrade<br />Does require v3 to be 64 bit<br />Whitepaper on moving from 32 bit to 64 bit SharePoint <br />http://technet.microsoft.com/en-us/library/dd622865.aspx<br />Previous version must be manually removed when upgrade is complete<br />
  7. 7. Inplace Upgrade<br />DEMO<br />
  8. 8. In-Place Pros/Cons<br />Pros<br />Cons<br />Farm wide settings are preserved and upgraded<br />Customizations are available in the environment after the upgrade if they are v4 compatible<br />Servers and farms areoffline while the upgradeis in progress<br />The upgrade proceeds continuously<br />Existing v3 farm must support (64 bit and performance<br />
  9. 9. Database Attach Steps<br />Stsadm –o preupgradecheck on your 2007 farm<br />Backup 2007 Content DB<br />Restore to SharePoint 2010 SQL Server, using SQL Tools<br />Test-SPContentDatabase –name wss_content_2007 –webapplication http://Team2010WebApp <br />Mount-SPContentDatabase –name wss_content_2007 –webapplication http://Team2010WebApp<br />
  10. 10. DB Attach Pros/Cons<br />Pros<br />Cons<br />Upgrade multiple content databases at the same time <br />Combine multiple farmsinto one farm<br />Customizations must be transferred manually<br />The server and farm settings are not upgraded<br />Customizations must be transferred manually<br />Missing customizations<br />
  11. 11. Database Attach<br />DEMO<br />
  12. 12. Hybrid Approach<br />Detach DBs<br />Upgrade to 2010 in-place<br />DB Attach content DBs<br />
  13. 13. Hybrid Pros/Cons<br />Pros<br />Cons<br />Farm wide settings preserved<br />Customizations alreadyin place<br />Multiple content databasesat the same time<br />Non-upgraded sites(in read-only mode) whileyou upgrade the content<br />Labor intensive<br />Direct access to the database servers<br />x86 is a lot of work<br />Existing hardwaremay need replacing<br />
  14. 14. Hybrid Approach<br />DEMO<br />
  15. 15. Downtime Mitigation Processes<br />Read-only databases (v3 SP2, v4)<br />Parallel content database upgrades<br />Parallel upgrade farms (v4)<br />Single farm, multiple upgrade sessions (v4)<br />Content database attach with AAM redirection (v4)<br />http://technet.microsoft.com/en-us/library/ee720448(office.14).aspx<br />
  16. 16. Move DB<br />Database Attach with AAM RedirectUser interaction model<br />SQL<br />SQL<br />?<br />302<br /><br />http://WSS<br />http://WSSold<br />http://WSS<br /> WFE<br /> WFE<br />v3 Farm<br /> v4 Farm<br />WSS v4<br />Web App<br />WSS v3<br />Web App<br /> SQL Instance<br />v4<br />Config<br />v3<br />Content<br />v4<br />Content<br />v3<br />Config<br />
  17. 17. What is “Visual Upgrade”<br />A feature that separates data upgradefrom UI upgrade<br />Data and code upgrade happens all at once<br />Site UI has two modes: this version andprevious version<br />Pages and components make the decisionat runtime, and it’s safe by default<br />
  18. 18. Why “Visual Upgrade”?<br />IT<br />Focus on the data<br />Schedule flexibility<br />Developers<br />Clear expectations<br />More control over legacy code and controls<br />Users<br />Puts the user impact into users’ hands<br />Accommodates big shifts (ribbon)<br />
  19. 19. Visual Upgrade<br />DEMO<br />
  20. 20. Core Upgrade Overview Improvement<br />Upgrade improvement areas<br />Predictability/reliability<br />Diagnostic ability/logging<br />End-user experience<br />Admin experience<br />Logging<br />Upgrade logs per session(saved in same place)<br />Error log per session ( -error.log)<br />Separate log for just errors <br />Shows callstacks<br />Upgrade logs always have same columns of data making reporting easier to automate.<br />
  21. 21. Core Upgrade Improvements<br />Logging<br />Upgrade logs per session(saved in same place)<br />Error log per session ( -error.log)<br />Separate log for just errors <br />Shows callstacks<br />Upgrade logs always have same columns of data making reporting easier to automate.<br />Admin experience<br />Visual feedback<br />Better warning<br />Quota handling and locked site collections<br />Upgrade status page<br />
  22. 22. Upgrade points to consider<br />V3 must be Service Pack 2 or later<br />You cannot upgrade a Trial SKU<br />FBA web applications now use Claims in v4<br />Stsadm command shipped with SP2, updated with Oct 09 CU<br />–o preupgradecheck<br />Do Spring cleaning before you upgrade<br />Stale sites<br />Excessive document Versions<br />Reorganize Site Collections into databases as necessary<br />Plan to revisit branding<br />http://technet.microsoft.com/en-us/sharepoint/ff420396.aspx<br />
  23. 23. Q & A<br />
  24. 24. Reference<br />
  25. 25. Track Resources<br />For More Information – http://sharepoint.microsoft.com <br />SharePoint Developer Center – http://msdn.microsoft.com/sharepoint<br />SharePoint Tech Center – http://technet.microsoft.com/sharepoint<br />Official SharePoint Team Blog – http://blogs.msdn.com/sharepoint<br />
  26. 26. Thank you<br />
  27. 27. SharePoint Solution Accelerators andSystem Center<br />PLAN<br />SharePoint <br />Asset Inventory Tool<br />Microsoft<br />System Center <br />Capacity Planner<br />SharePoint <br />Capacity Planner<br />Microsoft<br />System Center <br />Virtual Machine Manager<br />Microsoft<br />System Center <br />Configuration Manager<br />Microsoft<br />System Center<br />Microsoft<br />System Center <br />Configuration Manager<br />OPERATE<br />DELIVER<br />Microsoft<br />System Center <br />Operations Manager<br />Microsoft<br />System Center <br />Virtual Machine Manager<br />SharePoint <br />Configurator<br />SharePoint <br />Monitoring Toolkit<br />
  28. 28. Who can you trust??<br />The blogs I trust through all of the noise.<br />Maurice Prather<br />Andrew Connell<br />Spence Harber<br />Jim Duncan<br />Heather Solomon<br />Todd Klindt<br />Todd Baginski<br />Todd Bleeker<br />Jan Tielens<br />Patrick Tisseghem<br />WictorWilen<br />RasoolRayani<br />Lars Fastrup<br />CarstenKeutmann<br />
  1. A particular slide catching your eye?

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

×