Restore an Application-Tier Server
The databases for Team Foundation store all data for your deployment of Visual Studio Team Foundation Server. Even if you back up the application-tier server, you will not back up any data for Team Foundation Server. However, if the hardware of an application-tier server fails, you can install another application-tier server and configure it to use the databases for your deployment. That server will then replace the offline server as the application-tier server for the deployment. If your application-tier server hosted SharePoint Products, you must also restore that software on the new hardware. For more information, see Backup and Recovery (SharePoint Server 2010), Protecting and restoring a farm (Office SharePoint Server 2007), or Protecting and restoring a farm (Windows SharePoint Services 3.0).
After you restore an application tier to new hardware, make sure that all users, groups, and service accounts for your deployment are configured with the permissions that they require to perform necessary tasks. For example, administrators for Team Foundation must be members of the local Administrators group on the application-tier server so that they can open the administration console. For more information, see Add Users to Team Projects, Set Administrator Permissions for Team Project Collections, Set Administrator Permissions for Team Foundation Server, and Service Accounts and Dependencies in Team Foundation Server.
You can also add more than one application-tier server to a deployment of Team Foundation Server, but you must configure clients to connect to that server as a separate application tier. You cannot configure automatic load balancing between application-tier servers. For actual load balancing and transparency to clients, you must first install and configure a hardware or software device for network load balancing (NLB).
To install and configure a server as the application-tier server
Stop the application pools and services that Team Foundation Server uses.
For more information, see TFSServiceControl Command.
If you are using Network Service as the service account for Team Foundation (TFSService), on the application-tier server, open a Command Prompt window, and change directories to Drive:%Program Files%\ Microsoft Team Foundation Server 2010\Tools. At the command prompt, type the following command:
TfsConfig Accounts /add /account:"NT Authority\Network Service" /SQLInstance:ServerName /DatabaseName:DatabaseName
For more information, see Accounts Command.
Install Team Foundation Server on the new server, and start the Application-Tier Only wizard.
For more information and step-by-step procedures, see Checklist: Adding an Application Tier, or download the most recent version of the installation guide for Team Foundation, and follow the instructions for how to use the Application-Tier Only wizard: Installation Guide for Team Foundation.
If you are using Visual Studio Lab Management, install the System Center Virtual Machine Manager (SCVMM) Administrator Console on the application tier, and configure it to connect to the server that is running SCVMM.
For more information, see Configuring Lab Management for the First Time.
If the computer name has changed, open the administration console for Team Foundation.
In the navigation bar, click Application Tier, and then click Change URLs.
The Change URLs window opens.
In Notification URL, type the URL for the new application-tier server, and then click OK.
The name of the old application-tier server will still appear in the list of application-tier servers in the administration console for Team Foundation. If you select the Filter out machines that have not connected in more than 3 days check box, the old server will disappear from the list within three days.