Mainly TFS Admins or any DBA with overlapping TFS Admin roles looking for a cheaper way to backup and restore TFS
TFS (Team Foundation Server) utilizes multiple databases to store data for source control, work item tracking, server configuration and reporting. In order for TFS to perform correctly, these databases must be kept in a synchronized state. This creates challenges for traditional disaster prevention strategies in regards to database backups. Since a backup of the collection database could be occurring while modifications are being made to the configuration database and vice versa. The time offset of the two backups could be significant either by design due to the backup plan or because the collection database is large
To address the need to ensure, at a minimum, that the collection and configuration databases are kept synchronized, transaction log marks are employed. That way, if disaster strikes the databases can be restored to the same consistent point.
The first alternative is to use the TFS scheduled backup utility that as of TFS 2012 Update 2, is included in the base product. Previously, it was part of the TFS Power Tools. The built-in utility makes the process of creating backups of all the TFS related databases easy. The restore process is also straightforward when the tool is used to complete the backups. However, in this Document I will be discussing Backing up and Restoring TFS using Idera
Why I Want to Present This Session:
Because I rock!!