Migration steps of the moss Database Server

Migration scenario:

 

The moss field has four servers: two front-ends, one Index Server and one Database Server. You need to migrate the database to a database cluster that uses centralized storage.

The source database server and target database server are in the same ad domain, and the target database server cluster has been configured.

 

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) Restore all databases by backup and move them to the target database server, including the configuration database, content database, management center database, and SSp database.

 

(3) confirm the moss ApplicationProgramThe pool account has the permission to access 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 destination Database Server>

 

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

 

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

 

(6) At this time, when the site is tested and the content is searched, an error will be reported that the server cannot be connected to the search service. This is because the SSP cannot find the Index Server.

Access the management center, modify all SSPS, and re-specify their index servers.

 

(7) Confirm thatCodeThe code is consistent with the actual deployment code of the system, because after the database is adapted, moss automatically deploys all solutions.

If the code in the solution is of the old version, all functions will be returned to the previous version the next day. (nnd, still so intelligent, it is killed ...)

 

Refer:

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