Team Development with Visual Studio Team Foundation Server

One server; 20
to 100 users
Two servers;
100 to 250
users
Applicationtier
and data
tier server
Applicationtier
server
Data-tier
server
Dual processors,
2.2 GHz
Single processor,
2.2 GHz
Dual processors,
2.2 GHz
30 GB 2 GB
20 GB 1 GB
80 GB 2 GB
Two servers;
250 to 2000
users
Applicationtier
server
Data-tier
server
Dual processors,
2.8 GHz
Quadruple
processors, 2.7
GHz
40 GB 4 GB
Direct attach storage, 14,000
– 15,000 RPM RAID 0
spindles
16 GB
Table 16.1 Required hardware for TFS deployment
Backup and Failover Strategy
When considering your backup and failover strategy you need to take into account the impact of
losing a server on your team’s productivity.
Backup
You should plan your backup strategy as part of the deployment of you TFS installation. You
must consider:
• The frequency of your backup.
• The frequency of full and incremental backups.
• The storage requirements for the backup, such as on-site and off-site backup.
You can use the same standard backup practices that you use for any SQL Server 2005 database.
You can use backups to restore TFS in the following three scenarios:
• Data-only recovery.
• Single-server deployment full recovery.
• Dual-server deployment full recovery.
Data-only recovery is used if the data tier becomes corrupted. You can use the backup data and
logs to recover the full database.
Server recovery is used when the servers fail. In this case, you can restore the full database to a
second computer.