Move to another farm (Windows SharePoint Services 3.0)
Updated: April 2, 2009
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2009-02-17
The following procedures will help you move a Windows SharePoint Services 3.0 deployment to another farm. Use these procedures to move a farm to the same configuration on identical computers in a different location. If you want to migrate a farm to a new configuration or equipment type, see Deploy a new server farm, then migrate content databases. For more information about the differences between moving, migrating, and upgrading a farm, and about which set of procedures apply most directly to your situation, see Move and migrate servers and server farms (Windows SharePoint Services 3.0).
Moving a farm typically involves the following steps:
Set up the new server farm
Move the databases to the new server farm
Shut down the old server farm
Be sure to document any customizations that have been made to the front-end Web servers so that you can configure the new servers the same way. Such customizations may include the following:
The %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12 directory.
Any customizations that are made to the Web.config file.
Default quota templates.
Blocked file types.
Administrator-deployed form templates.
Database names and locations.
Web application names and databases. Be sure to document the content database names that are associated with each Web application.
Deploy the new Windows SharePoint Services 3.0 farm by using the Deploy in a simple server farm (Windows SharePoint Services) procedure.
Move the databases by using the Move all databases to a different database server procedure.
After you have tested the new server farm to ensure it is operational and there is no loss of data, remove the servers from the old farm by using the Remove a server from the server farm (Windows SharePoint Services) procedure.