Tuesday, October 20, 2009

SPC 2009: SharePoint 2010 Upgrade Part 1: Fundamentals

Upgrade Part 1 Fundamentals Break-out session notes from SPC 2009.

NOTE:  New content just uploaded to TechNet for Upgrade Scenarios HERE.

Upgrade Scenarios

  • Supported Scenarios:
    • In-Place Upgrade
    • Database Attach Upgrade:
    • Content Database
    • Profile Service Database
    • Project Service Database
    • Singlie Click Install – SQL Migration
    • Windows Internal Database > SQL Express 2008 + File Stream RBS
  • Unsupported
    • Upgrade from earlier than WSS v3 SP2 or MOSS 2007/SP2
    • Direct upgrade from WSS v2/SPS 2003 or earlier
    • Side by Side installation
    • Gradual Upgrade

Upgrade Prep Tools

  • WSS v3/MOSS 2007 SP2
    • Farm Insight
      • Pre-Upgrade Checker
      • stsadm –o EnumAllWebs (Now includes the features that are installed in a Web)
      • SPDiag V2
    • Customizations gathering
      • stsadm –o ExportIPFSAdminObjects
  • SharePoint 2010
    • Farm Insight
      • stsadm –o EnumAllWebs
      • SPDisg 2010 (TBD)
    • Content Database Insight
      • Test-SPContentDatabase

Pre-Upgrade Checker Command

Command: stsadm –o preupgradecheck [-localonly]

  • Details
    • Reports farm and server data
      • Identifies useful farm information
      • Identifies current or potential issues
    • Modes
      • Load server + farm databases (default)
      • Local server only
    • Makes no changes to environment or data (Yes!  This was a huge complaint with going from 2003 to 2007)
    • Introduced in SP2; improved in October 2009 CU
    • Not required like it was for upgrading from 2003 to 2007 but still highly recommended
  • Rules Files (Partial List)
    • Informational
      • Farm Servers, Databases
      • AAM Configuration
      • Lists Site Definitions, Features, Web Parts, Event Receivers
      • Installed Language Packs
      • CAML views/CAML content types
    • Issues
      • Missing Site Definitions, Features, Assemblies
      • Data orphans
      • Modified content databases
  • Command outputs an easy to read HTML-based file

Test-SPContentDatabase Command

  • Content database insight from O14
  • Complements pre-upgrade checker report
  • Reports data from server/database paring
    • Compare against a specific web app
    • Identifies current or potential issues:
      • Data orphans
      • Missing site definitions
      • Missing features
      • Missing assemblies
    • Can show table sizing metrics
  • Scan O12 and O14 content databases
  • Makes no changes to the database(s)

Windows PowerShell Upgrade Cmdlets

Note: B2B – Patching Upgrades,V2V Version to Version Upgrade

  • Upgrade-SPContentDatabase
    • Content database B2B/V2V upgrade
    • Common Scenarios:
      • Initiate/resume content database B2B upgrades
      • Resume failed content database V2V upgrades
    • Upgrade-SPEnterpriseSearchServiceApplication
      • Search Service Application Instance B2B upgrade
    • Upgrade-SPSingleSignOnDatabase
      • O12 data to Secure Store database V2V upgrade

Feature Upgrade Capability

  • Optional Capability
  • Version Ranging for B2B or V2V Upgrades
  • Declarative Feature Upgrade Activities (Final list for RTM, stated that there “may” be more in the future)
    • ApplyElementManifests
    • AddContentTypeField
    • MapFile
  • Custom Code Feature Upgrade
    • CustomUpgradeAction Activity
    • SPFeatureReceiver.FeatureUpgrading
    • Assembly in GAC

Visual Upgrade Capability

  • Stay in O12 UI (default) or move to O14 UI
    • O14 ships O12 Master pages and CSS
    • UI Preview capability (Recommend to perform limited changes will in preview mode)
  • Farm admin or site admin controlled
    • Web level settings and OM
  • Some items not O12 compatible:
    • My site host
    • PWS site collection
    • Report Server web parts

Patch Management Capability

  • Patching state insight
    • Patch management UI
    • Patch reporting PowerShell UI
    • Patch status health rules
  • Backwards compatibility mode (This is awesome!  No need to upgrade the entire farm right after patch install)
    • Binaries can be ahead of the database(s)
    • Defer upgrade for short period of time
    • Not intended for long duration

Downtime Mitigation Process

  • WSS v3/MOSS 2007 SP2
    • Read-only databases
    • Parallel upgrade farms
    • Gradual Upgrade
  • SharePoint 2010
    • Read-only databases
    • Parallel upgrade farms
    • Single farm, multiple upgrade sessions
    • Content database attach with AAM redirection

Upgrade Logging/Status Reporting

  • Upgrade Logging
    • New – One upgrade log per sessions
    • New – Upgrade errors only log
    • New – Fixed upgrade log schema
  • Upgrade Status Reporting
    • Improved – Upgrade status page (This is SO much better.  It provides a lot more information during upgrade compared to the 2007 version.  It will also show all concurrent database upgrades.)
    • New – Upgrade status history
    • New – Command line progress indication

Upgrading a MOSS 2007 Farm

  • Each SSP upgrades into:
    • A Search service app
    • A User profiles service app
    • An excel service app
    • An application registry back-compat service app
    • A new managed metadata service app
  • Web application association are preserved
    • a proxy is created for each service app
  • New databases are created

No comments:

Post a Comment