Moss Database Server Migration steps

Migration scenario:

Moss Farm has four servers: two front-end, one index server, one database server. The database needs to be migrated to a cluster of databases with centralized storage.

The source database server and the destination database server are in the same ad domain, and the target database server cluster is configured well.

The migration steps are as follows:

(1) Stop all moss services on all Moss servers, including:

Microsoft Single Sign-On Service

Office Document Conversions Launcher Service

Office Document Conversions Load Balancer Service

Office SharePoint Server Search Service

Windows SharePoint Services Administration Service

Windows SharePoint Services Search Service

Windows SharePoint Services Timer Service

Windows SharePoint Services Tracing Service

Windows SharePoint Services VSS Writer Service

Internet Information Services

(2) Backup and restore all databases and move them to the target database server. Includes configuration database, content database, central management database, SSP database.

(3) Confirm that the Moss application pool account has access rights to the target database server.

(4) Run the following command on all MOSS servers (excluding database servers):

CD%CommonProgramFiles%\Microsoft Shared\Web server extensions\12\BIN.

Stsadm-o Renameserver-oldservername <name of the source database server>-newservername <name of the Destinatio N Database server>

newServerName is the virtual access domain name of the database server cluster.

(5) Reboot all servers. If a front-end server is still linked to the old database, rerun the renameserver command and restart the server.

(6) This time the test site, search for content will be reported unable to connect to the search service error, this is because the SSP can not find the index server.

Access the central administration, modify all SSP, and reassign its index server.

(7) Verify that the code in the solution that is already installed in the server farm is consistent with the actual code deployed by the system, because Moss automatically deploys all the solutions once the metabase is adapted.

If the code in your solution is an older version, the next day you will find that all features are returned to a previous version. (NND, still so intelligent, was killed ...)

Reference:

http://technet.microsoft.com/en-us/library/cc512725 (technet.10). aspx