Welcome to MSDN Blogs Sign in | Join | Help

Real-Time Visibility Through Technology

"Never innovate to compete, innovate to change the rules of the game" - David O. Adeife

News

About me

My Photo

Sr. Product Manager,BizTalk RFID



Disclaimer

These postings are provided "AS IS" with no warranties and confer no rights.
Using SQL Mirroring with TFS

Failover is a big concern for everyone using Team Foundation Server. What happens if the server hosting Data Tier of Team Foundation Server crashes? How can we get the whole system back up and running in least amount of time? There are various solutions to this problem. Traditionally we have recommended using Clustering for maximum availability. Clustering is a great solution, as it provides automatic failover that is transparent to end users. Another option is to use backup and restore mechanism of SQL Server. In this case users can take combination of Full and incremental backup of the Data Tier and if there is a failover of primary server you can easily recover the TFS Data Tier using the backed up data. This could be a very time consuming process.

Clustering provides automatic failover; Backup/restore provides long lead time recovering of server. SQL Mirroring can be used as a solution in between both of these options. SQL Mirroring provides warm standby but TFS does not support automatic failover with mirroring. Few manual steps need to be executed when the primary server fails with mirroring in TFS. We are working on a White paper to provide detailed steps on using SQL Mirroring for failover scenarios in TFS. We should have it ready within few weeks for everyone to use. Till then following are the high level steps required to use mirroring.

The process of configuring a VSTF deployment for mirroring can be defined in following steps

  1. Backup databases from the main Data Tier Server(Principal server)
  2. Restore backed up databases on mirror server.
  3. Setup Mirroring for each database between Principal and Mirrored servers
  4. Perform manual Failover to enable Mirrored Server as principal server.
    1. Manual failover when primary server is available can be performed using Management studio
    2. Manual failover when primary server is unavailable(Forced service Failover) can be performed using ALTER DATABASE command in TSQL Statements
  5. Map Application Tier to talk to new Data Tier(Mirror Server)

 

More detailed Mirroring steps should be up on MSDN in next few weeks. I will keep all of you updated when that happens.

Posted: Monday, October 30, 2006 10:37 AM by sudhirh

Comments

Jason Barile - Microsoft in Raleigh, NC said:

One of our Program Managers, Sudhir Hasbe , has posted a draft of a whitepaper detailing how to use SQL

# November 6, 2006 9:01 AM

bharry's WebLog said:

We continue to evolve and improve upon the TFS reliability and disaster recovery story. Fundamentally

# November 24, 2006 9:40 AM

Sudhir Hasbe said:

Some of you may have read by previous post on Mirroring with TFS at http://blogs.msdn.com/sudhir/archive/2006/10/30/using-sql-mirroring-with-tfs.aspx

# September 19, 2007 4:42 PM

Microsoft Japan Forum Operators Blog said:

こんにちは! フォーラム オペレーターの服部清次です。 ^o^ ついに、アメリカではオバマ新大統領が誕生しましたね。 僕は、昨日の夜、テレビでオバマ新大統領の就任演説を見ようと頑張って起きていたのですが、直前に落ちてしまいました。。。

# January 20, 2009 8:27 PM
Anonymous comments are disabled
Page view tracker