Back up all the databases for Team Foundation.

For more information, see How to: Back Up a Team Foundation Server.

Note:
You must also back up any custom site definitions, custom site templates, or custom Web parts for SharePoint Products and Technologies that you want to keep. For more information, see these pages on the Microsoft Web site: Backup and Restore Options for Windows SharePoint Services 2.0 or Recommendations for data protection and recovery for Windows SharePoint Services 3.0.

If SharePoint Products and Technologies is installed on the application tier and you want to move the databases for SharePoint Products and Technologies to the new data tier, make sure that you back up the administrative database for SharePoint Products and Technologies. (SharePoint_AdminContent_ID) along with the content and configuration databases.

Back up the encryption key for Reporting Services. Make sure that you store it in a secure location on a different computer from the server that is running Team Foundation Server and that the new application-tier server can access the key. You must also store the password with which the key is encrypted.

For more information, see How to: Back Up the Reporting Services Encryption Key.

Install SQL Server in the new environment, and make sure that it is operational.

For detailed instructions, open the installation guide for Team Foundation, and find the topics about how to install SQL Server in a dual-server deployment. You must install the same version of SQL Server that you used in the original deployment. You can find this guide on the Microsoft Web site.

On the application-tier server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

At the command prompt, type the following command:

TfsDB.exe install /server:"NewSQLServerName" /property:"TFS_SERVICE_ACCOUNT=TFSServiceAccount;TFS_REPORTING_ACCOUNT=TFSReportingServiceAccount;LCID=LCIDNumber;VSTF_AS_INSTANCE=AnalysisServicesServerName;VSTF_AS_DATABASE=TeamFoundationDataWarehouseName;VSTF_AS_ACCOUNT="

• NewSQLServerName is the name of the server where you just installed SQL Server and where you intend to restore the data. If you used a named instance, you must include not only the server name but also the instance name.

• TFSServiceAccount is the service account for Team Foundation Server in Domain\Account or Computer\Account format. If you are using a system account, you must specify that account using the System\Account format. For example, if you want to use Network Service, you would specify it as NT Authority\Network Service.

• TFSReportingServiceAccount is the data sources account for Reporting Services in Domain\Account or Computer\Account format.

• LCIDNumber is the language collation ID number for your language edition of SQL Server. For example, the LCID for English is 1033.

• AnalysisServicesServerName is the name of the server on which SQL Server Analysis Services is installed. By default, this is the same server as NewSQLServerName.

• TeamFoundationDataWarehouseName is the name of the original data warehouse for Team Foundation. By default, this value is TfsWarehouse.

On the server that is running Reporting Services, retrieve and save a list of the installation IDs for Reporting Services.

1. Open the Command Prompt window, and change directories to the following directory:

   %ProgramFiles%\Microsoft SQL Server\90\Tools\binn\

2. Run RSKeyMgmt -l.

3. Note the installation IDs, and print a list or save it in a safe location.

Log on to the appropriate server, open Computer Manager, and stop the services and application pools in following table in the order specified:

Important Note:

To move user accounts and service accounts in a restoration-based move, the new deployment of Team Foundation Server must be in a stopped state. If you restart Team Foundation Server after you restore data but before you move user accounts and service accounts, you could cause users that are targeted for migration to be marked as deleted in the TFSIntegration database. This problem occurs when the group security service cannot find the user’s system identification (SID) during synchronization with Active Directory.

For more information about how to start and stop services and application pools, see How to: Stop and Start Services, Application Pools, and Web Sites.

On the new data-tier server, click Start, point to All Programs, point to Microsoft SQL Server, and then click SQL Server Management Studio.

Note:
For more information about how to restore databases, see "Implementing Restore Scenarios for SQL Server Databases" on the Microsoft Web site.

In the Server type list, click Database Engine.

In the Server name list, click or type the appropriate server.

In the Authentication list, click the appropriate scheme.

In User name, type the user name of a valid account.

In Password, type the password of the account if SQL Server requires it, and then click Connect.

Expand the Databases node to show the list of databases that make up the data tier for Team Foundation.

Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.

Important Note:
In most deployments, neither the SQL Server databases nor the SharePoint Products and Technologies databases will appear in the list of databases under the Databases node. To restore any databases that do not appear in the list, you must right-click the Databases node, click Restore Databases, and specify any databases that are not in the list.

The Restore Database dialog box opens.

Under Source for restore, click From Device, and then click the ellipsis button (…).

In the Specify Backup dialog box, specify the location of the backup file, and then click OK.

The first backup that you apply must be a full backup, followed by the transaction log backups, in the order in which they were created.

Under Select the backup sets to restore, specify the backup sets to restore.

In the Select a page pane, click Options, and then select the Overwrite the existing database check box.

In the Restore the database files as list, verify that the paths match your current database paths.

This step is important if you are restoring the database to a different drive.

Under Recovery state, click the appropriate state.

Perform one of the following steps:

• If you are not applying additional transaction logs, click Leave the database ready to use.

• If you are applying additional transaction logs, click Leave the database non-operational.

Click OK to close the Restore Database dialog box and restore the database.

If you are applying additional transaction logs, follow this procedure for each set of log backups in the order in which they were created. Start with the one made after the full backup.

For more information, see "Applying Transaction Log Backups" on the Microsoft Web site.

Log on to the server that hosts SharePoint Products and Technologies, open a Command Prompt window, and change to the following directory:

%PROGRAMFILES%\microsoft shared\web server extensions\12\bin.

Type the following command:

stsadm –o renameserver –oldservername OriginalDataTierServerName -newserver NewDataTierServerName

For more information about how to restore SharePoint Products and Technologies, see "White paper: Backing up, restoring, high availability, and disaster recovery for Office SharePoint Server farms" on the Microsoft Web site.

On the server that is running Reporting Services, click Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click Reporting Services Configuration.

In the Report Server Installation Instance Selection dialog box, make sure that the computer name is the name of the new application-tier server. Make sure that the instance name is MSSQLSERVER, and then click Connect.

Note:
If you used a named instance, you must specify the instance name and not the default instance of MSSQLSERVER.

In the Explorer pane, click Server Status.

The Report Server Status pane opens.

In Instance Properties, click Start.

In the Explorer pane, click Database Setup.

The Database Connection pane opens.

In Server Name, type the name of the new data-tier server, and then click Connect.

In the SQL Server Connection Dialog dialog box, click OK.

The Database Connection pane opens.

Click Apply.

In the Explorer pane, click Windows Service Identity.

The Windows Service Identity page opens.

In the Built-in Service Account list, click Local Service.

The Apply button becomes available. Do not click it.

In the Built-in Service Account list, click Network Service, and then click Apply.

In the SQL Server Connection Dialog dialog box, click OK.

Close the Reporting Services Configuration tool.

Open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft SQL Server\90\Tools\binn.

Type the following command to list installation IDs of Reporting Services:

RSKeyMgmt -l

In the list, find the installation ID that corresponds to the old data-tier server.

Type the following command to remove that installation ID, where DTInstanceID corresponds to the old data-tier server:

RSKeyMgmt –r DTInstanceID

Note:
Do not remove the installation ID that corresponds to the new data-tier server.

On the server that is running Reporting Services, click Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click Reporting Services Configuration.

In the Explorer pane, click Encryption Key.

On the Encryption Key page, click Restore.

The Encryption Key Information page opens.

In Password, type the password for the encryption key file.

In Key File, type or click the location of the backup encryption key (.snk file), and then click OK.

Log on to the appropriate server, open Computer Manager, and start the application pools and programs in the following table:

Open the Command Prompt window, change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools, and type the following command:

TfsAdminUtil RenameDT newDataTierServerName

Important Note:

For this command to succeed, the application pools and programs in the previous step must be running. This requirement is new in Visual Studio Team System 2008 Team Foundation Server. Also, this command requires the connection string in the services web.config file to refer to the original server for your deployment. If the connection string refers to the new data-tier server, the command will fail. You must restore the name of the original server for the command to run correctly.

On the application-tier server, open the %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControl directory.

Delete the contents of the Data subdirectory, but do not delete the Data subdirectory itself.

For more information, see How to: Delete the Version Control Cache on the Application-tier Server.

Repeat this procedure on any server in your deployment that is running Team Foundation Server Proxy.

On the server that is running Reporting Services, open Computer Manager, and start the following components if they are not already started:

• ReportServer or ReportServer$InstanceName (application pool)

• SQL Server Reporting Services (TFSINSTANCE)

On the new application-tier server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

At the command line, type the following command:

TfsAdminUtil ChangeAccount OldDomainOrComputerName\OldTFSServiceAccount NewDomainOrComputerName\NewTFSServiceAccount NewPassword

Note:
Ignore any warning that says that the service account does not exist or asserts that the account is not a member of the data warehouse role.

At the command line, type the following command:

TfsAdminUtil ChangeAccount/ra OldDomainOrComputerName\OldTFSReportingServiceAccount NewDomainOrComputerName\NewTFSReportingServiceAccount NewPassword

Note:
Ignore any warning that says that the service account is not a member of the data warehouse role or that prompts you to add the account to the service accounts group.