Your SlideShare is downloading. ×

Practical Guidance for SharePoint 2010 Upgrade


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.

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
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


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