:: infotechGuyz.com ::
> For the IT community by the IT community

• BlackBerry Server (BES)
• Excel Macro/VBA
• Exchange 2007
• Exchange 2010
• Lync 2010
• Scripting/Command-line
• SQL Server 2008
• SQL Server 2012
• Team Foundation Server
• VMware
• Windows 7
• Windows 8
• Windows Server 2008
• Windows Server 2012

Team Foundation Server High Availability

You might want to deploy an application-tier server to an existing environment of Team Foundation Server for one of the reasons below:

• Add redundancy into your Team Foundation Server deployment.
• EnsureTeam Foundation Server runs faster.
• To restore an application-tier server that has failed.
• To migrate an application tier to a diverse server.

 

Redundancy and Scalability

In previous versions of Team Foundation Server, you can run only the data tier on a SQL Server cluster to provide redundancy. This limitation expected that you could improve scalability for only part of your placement of Team Foundation Server: the data tier. Application-tier Only Configuration wizard allows you to enhance the availability and performance of your application level servers. 

To take advantage from many application-tier servers, you must guarantee that your initial installation of Team Foundation Server is:

• Application tier and the config DB are deployed on separate servers.
• Your domain account is used for Team Foundation Server service.
• NLB or hardware LB such as F5 is in place.

NLB is used to create a group of Web servers that look as a single logical Web service. This process is distinct from the Application-tier Only Config wizard.

If you build an NLB cluster, you don’t need to use a SQL cluster for your configdb or any team project. For scalabilityand availability, any SQL cluster that you deploy is autonomous of the NLB cluster.

Application Tier Configuration

1. Start>All Programs>Microsoft Team Foundation Server 2010>Team Foundation Server Configuration Tool.

2. Choose Team Foundation Server, and click “Configure Installed Features”.

3. Choose Application-Tier Only Config, and then click Start Wizard.

4. Read the Welcome screen, and then click Next.

5. In SQL Instance, type the instance of SQL Server then click List Available Databases. 

6. Choose a database, and click Next.

7. Choose the account you want to use. Type the password for the account.

8. clickNTLM to use NTLM authentication or Negotiateto first attempt Kerberos authentication, the more secure option, and if that fails, fall back to NTLM. Click Next.

9. Click Next and Close.