Tuesday, June 10, 2008

High Level DB Upgrade Steps[SPS 2003 to MOSS 2007 Migration]

  1. Prepare your environment (SPS 2003 production)
    1. Download PreScan tool
    2. Identify customization to your SPS2003.
      1. Custom Site Definitions
      2. Custom/Third Party Web Parts
      3. Custom/Third party tools installed
    3. Identify solution to migration above customizations (More on this in my next blog "Handling Customizations in your MOSS Upgrade")
  2. Prepare for Upgrade
    1. Run Pre Scan on SPS2003 box

    %PROGRAMFILES% \Common Files\Microsoft Shared\web server extensions\12\BIN\prescan.exe /c preupgradescanconfig.xml /all

    1. Review Pre Scan results
    2. Set SPS2003 to Readonly
      1. Central Administration>Virtual Server List>Manage site collection quotas and locks>Configure site quotas and locks >select the 'Adding content prevented' radio button.
  3. On MOSS Environment
    1. Create Web App
    2. Specify dummy DB
  4. Upgrading
    1. On SQL Restore the content database for Upgrade
    2. Perform the DB Upgrade by adding the content database

stsadm o addcontentdb url http://%3cservername%3e/
databasename <contentdbname>

3. Perform MySite Upgrade

    1. Create the new mysite host with the command:

stsadm -o createweb -url http://%3cwebapp%3e/%3cdesiredpath%3e -sitetemplate SPSMSITEHOST -title "MySite Host"

  1. Through MOSS Central Administration, under Application Management, create a new web application. This will be the web application for the SSP.
  2. Perform a restore of the SSP site to capture and upgrade the profile/audience information with the following command:

stsadm -o restoressp -title <SSP Title> -url http://%3cwebappcreatedin2b%3e/ -ssplogin <serviceaccount> -mysiteurl http://%3cwebapp%3e/desiredpath -indexserver <servername> -indexlocation "<filepath" -sspdatabaseserver <dbserver> -sspdatabasename <restored profil db> -ssppassword "<password>" searchdatabaseserver<searchdb> -searchdatabasename <searchdb>-ssl no

DB Upgrade Lessons Learned [SPS 2003 to MOSS 2007 Migration]

  • To start with migration, first build SPS Dev Env and Match the source SPS2003 Service pack/Hot Fix
  • To perform PreScan for migration, SPS 2003 SP2 is must.
  • On SPS2003, you cannot restore more than one copy of the same portal. Each portal has an unique ID that is stored in the Config_DB.
  • When restoring portal, if restore fails, look at the end of the log for most recent restore error. Restore process maintains single log file for successive restores.
  • After STSADM databaserepair you need to remove and re-attach the content database so that the Config DB sheds off the deleted sites. More than one person has experienced the Remove content DB action from the central admin interface doesn't really remove the content db. May be since the databases are huge. In this case simply perform the Delete portal with retain databases and add/restore clean new portal.