1 / 33

Zvonimir Mavretić, Chief Technology Officer

Croatia SharePoint User Group SharePoint 2010 Upgrade Zagreb, 13.10.2011. Zvonimir Mavretić, Chief Technology Officer. Upgrade Cycle: Overview. Pre Upgrade. SharePoint 2010 Requirements. SharePoint 2007 SP2 Update ( August CU recommended) 64 bit operating system for application servers

camille-vaughn
Télécharger la présentation

Zvonimir Mavretić, Chief Technology Officer

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. Croatia SharePoint User Group • SharePoint 2010 Upgrade • Zagreb, 13.10.2011. Zvonimir Mavretić, Chief Technology Officer eVision informacijski sustavi

  2. Upgrade Cycle: Overview

  3. PreUpgrade eVision informacijski sustavi

  4. SharePoint 2010 Requirements • SharePoint 2007 SP2 Update (August CU recommended) • 64 bit operating system for application servers • Windows Server 2008 or 2008 R2 • 64 bit SQL Server • SQL 2005 SP3 CU3/2008 SP1 CU2/2008 R2 • For Development environments • 64-bit Vista SP1 and Windows 7 • Virtualization is supported and very common

  5. Learning from PreUpgradeCheck

  6. PreUpgradeCheck Failed Report (snippets)

  7. SharePoint PreUpgradeCheck Report

  8. Test-SPContentDatabase

  9. Upgrade eVision informacijski sustavi

  10. Insight on Upgrade • Binary Upgrade • In Place - New Timeout, Resume on failures • Database Attach - New Parallel, Progress Indicator • Visual Upgrade • Separate process • Delegation by default

  11. In-Place Upgrade • All-at-once upgrade • Must upgrade the whole farm at one time • No SP 2007 and SP2010 in same farm • Schedule downtime • Simplest approach, but *most risky*! • No going back • Resume Upgrade if problems occur • Recommendations • Run Test-SPContentDatabase from SP 2010 farm against databases • Do a full farm backup before you start!

  12. 1. In Place - Binary Approach to Upgrade Caution: Not recommended for most deployments…

  13. Psconfig –cmd upgrade

  14. Psconfig Upgrade Continued

  15. Database Attach Upgrade • Safer, Requires more planning (A good thing) • Upgrade is done on a separate 2010 farm • Done database-by-database • Can be used with 2nd step visual upgrade • Use Test-SPContentDatabase (PowerShellcmdlet) to test database first • To attach • Mount-SPContentDatabase (PowerShell) • STSADM –o Addcontentdb operation • Parallel database upgrades are possible

  16. Read-Only Databases

  17. 2. DB Attach- Binary Approach to Upgrade Recommended for most deployments…

  18. Visual Upgrade • Stay in 2007 (default) or move to 2010 UI • 2010 ships 2007 Master pages and CSS • UI Preview capability • Farm admin or site admin controlled • Web level setting • Some items not 2007 UI compatible • My site host • PWA site collection • Report Server web parts

  19. Attaching Database to SP2010 Farm

  20. Central Admin Upgrade Status

  21. Post Binary Upgraded Site: Preview Visuals

  22. Visual Upgrade Options

  23. Savjeti eVision informacijski sustavi

  24. Operations SchedulingBenchmark upgrade operations schedule Note: • Planned 36 hours outage. • Up to 54 hours emergency outage if rollback is required. • Downtime mitigation processes such as read-only databases can be used to reduce outage time.

  25. Determine cause of failure Status Page & Upgrade Logs: Error log Full upgrade log Customizations Management Commands: Test-SPContentDatabase stsadm -o EnumAllWebs Fix issue(s) Install missing or updated customizations Activate missing services; farm, web app settings Resume upgrade Farm upgrade command Content database specific upgrade command Service specific upgrade commands Common Upgrade Failure Issues & Recovery

  26. UpgradeStrategies eVision informacijski sustavi

  27. Windows PowerShell Upgrade Cmdlets Test-SPContentDatabase • Discover and Document issues 2007/2010 Mount-SPContentDatabase • Initiate Content database B2B/V2V upgrade Upgrade-SPContentDatabase • Resume Content database B2B/V2V upgrade Upgrade-SPEnterpriseSearchServiceApplication • Search Service Application Instance Upgrade-SPSingleSignOnDatabase • O12 SSO data to Secure Store database

  28. Upgrade Testing • Upgrade Issues • Disk Full!!! • Modified databases • Customizations • Authentication providers • Poor dev practices • Recommendations • Test server side customizations & verify in both Visual Upgrade modes • Consider preview environments • Similar hardware, Use real datasets • Don’t ignore warnings

  29. Binary Approaches to Upgrade - Hybrid

  30. SSP to Service App • Each SSP upgrades into: • A Search service app • A User Profiles service app • An Excel service app • An App Registry back-compat service app • New Services can be activated/added

  31. Visual Upgrade Caution • AAM redirection features is complex. Don’t use it if you don’t have to. • No Visual backward compatible UI for My Sites • Database Attach into My Site Host • In place upgrade your My Site Host • Other Services UI may be impacted • Project Web Access site collection • Reporting Server web parts

  32. Q & A eVision informacijski sustavi

More Related