MOSS 2007: Migration Steps from Beta 2 / Beta 2TR to Final Release
Finally, MOSS 2007 had been released and available in MSDN last month. Its about 6 month after beta 2 / beta 2 tr, more or less couple projects using beta version. So now what? Since no upgrades option from beta to final release, then we must migrate it - hoping that we don’t need to rebuilt it all over again. Fortunatelly, if you do the migration carefully - all sites will be up so quick.
The migration process basically is simmilar with fresh installation process. However, in migration we must backup all custom builds, settings and database so we can restore it later.
1. Install .NET 3.0 final release
MOSS 2007 uses .NET 3.0 final release. Before you can install it, any .NET 3.0 beta component must be uninstalled in correct order. I suggest to use uninstall tool from Microsoft. When you run the tools, it will search and uninstall any beta component, including SQL browser component. Stop all MSSQL services to prevent from data disruption. Finally, install .NET 3.0 release and check if the SQL server is running properly.
At this stage, the server will run beta on .NET 3.0 release. Make sure that all sites operates correctly.
2. Copy Any Custom Builds and Settings
Since virtual servers creation are managed by MOSS, then uninstalling the server also deletes the virtual servers and their contents. In this stage, any custom builds and setting must be copied out from virtual server folder. For example, I copied files from bin, custom, and web.config, to tmp folder. You must do this to any site collection that you might have.
_3. Identify All Databases for current site
_MOSS 2007 has several type of database,
- Configuration database, to keep global server settings
- Admin content database, this is basically is a content database but only one for every server
- Content database, this is where all site contents are saved at least one for every web application
- Search database, uses by sharepoint search service
- Shared services databases, uses by shared services provider
We need to keep all Content and Shared services databases - and discard other database type. For example, in the following database system, I keep WSS_Content_* (content database) and SharedServices1_* (shared services database).
4. Uninstall MOSS 2007 Beta
Now we are ready to uninstall MOSS 2007 Beta version (beta 2 or beta 2 tr). Before uninstalling, you can choose to disconnect the server from configuration database - especially when there are two or more servers in server farm. You can skip to disconnect and directly go to uninstallation button from windows add remove programs.
_5. Install MOSS 2007 Release
_Run setup.exe from MOSS 2007 distribution media and follow the wizards - make sure that you choose server farm installation.
At the end of installation process, Sharepoint Products and Technologies Configuration Wizard window will open. Choose create a new server configuration database, and follow the wizards.
It will creates configuration database and admin site - open the admin site for final configuration.
_6. Re-establish All Site Collections
_If you are familiar with the beta, then you can start to enable services the server from operations tabs. Then go to Application Management tab to create new web application.
Open your note from step 3, and start to re-create all site collection using their respectives database. The key procedure to re-establish your site collection is that you must specify the same content database. I specify WSS_Content_1282 for my site collection in http://localhost:1282 , etc.
_7. Re-establish Shared Services Provider
_Using Shared Services database (from step 3) - we can restore the SSP into the new system. Goto Manage this Farm’s Shared Services and click “Restore SSP”.
It will open Restore SSP Page, enter the same SSP database information on the filling form and completes the all other form fill.
_8. Restore Custom Builds and Settings
_If you have custom builds then this is the time to restore it. Copy all files from backup location to the respective location in virtual directory folder. If you changes/add entry in old web.config, then don’t forget to make the same changes/additional entry in new ones on virtual directory folder.
And - done, all sites are now running using final release.