Disaster Recovery Plan for Team Foundation Server 2008

kindlyminnowΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 7 μήνες)

89 εμφανίσεις

Disaster Recovery Plan for Team
Foundation Server 2008

Abstract

The purpose of this document is to outline a disaster recovery strategy for Team Foundation Server
and provide all the information required to implement the same. The purpose of the plan in this
document is to get your TFS back online as soon as possible
assuming
your servers have been
rendered inoperable due to unforeseen circumstances
.


Requirements

Team Foundation Server 2008 (TFS)


Production Application Tier (PAT)


Standby Application Tier (SAT)

SQL Server 2005 SP2


Production Data Tier (PDT)


Backup
Data Tier (BDT)

DNS Entries for:


Application Tier (AT)


Data Tier (DT)

Two or more separate sites connected via WAN

Assumptions

This guide assumes that the standby application tier is already installed as per the
article entitled
“Configuring a Standby Ap
plication Tier” in the
TFS Installation Guide

(
http://go.microsoft.com/fwlink/?LinkId=79226
)
and that your domain is available across multiple
sites.



O
verview

This premise of this plan is that
the two pairs of servers are separated to different sites and
a
bac
kup

of the production databases are present at the same site as the second site. Both sites would be a
member of the same domain and that domain should have domain controllers available if

Site 1
were to go offline.

For example:

Site 1

Production Application Tier

Production Data Tier

Site 2

Standby Application Tier

Backup Data Tier

In case of a disaster, the databases would be restored to the backup data tier and the DNS entry for
the prod
uction data tier would be pointed towards
the hostname or IP address of the backup data
tier server in the same manner that the DNS entry for the application tier would be pointed towards
the Standby Application Tier.

Once the databases are restored, the s
teps to activate the standby application tier would be
followed. Once the clients have cleared their client side cache for TFS and flushed their DNS cache
you should be back up and running.


Configuring Team Foundation Server for Disaster Recovery


This
section will walk you through the steps required to reconfigure Team Foundation Server to be in
a state to facilitate disaster recovery. This guide assume
s

that
you have already configured a
standby application tier. If you have not yet installed Team Fo
undation Server,
create the DNS
entries and install using them rather than the machine names then follow the following guide to
configure the data tier.


Configuring the Aliases for the Data Tiers

1.

Create a DNS entry for your production data tier or request

this be performed by your
domain administrator and have the entry point towards your production servers

2.

Connect to the primary application tier and follow these steps to configure an alias for the
DNS entry

a.

Open SQL Server Configuration Manager on the dat
a tier

b.

Expand “SQL Native Client Configuration” and right click on aliases

c.

Click on “New Alias” and use the following details

Alias Name: virtual DNS entry

Port No: 1433 or the port you are using

Protocol: TCP/IP

Server: Hostname of the machine you are co
nnected to

d.

Click OK

3.

Perform the above

on the backup data tier though include an alias to the production data
tier as well as to the DNS entry.


Configuring the Backups


1.

Use the following guide to backup the reporting services encryption key

http://msdn.microsoft.com/en
-
us/library/ms400729.aspx

2.

Use the following guide to create a scheduled backup plan for your TFS databases

http://msdn.microsoft.com/en
-
us/library/ms253151.aspx


3.

Ensure that the above files are available to the backup data tier in case of emergency

Sharepoint Configuration on the Standby Application Tier

If you have Windows Sharepoint Services installed on
the primary application tier currently follow
these steps to install on the Standby Application Tier for the purposes of failover. If you have a
separate MOSS or WSS server you will need to take steps to ensure these are prepared, the failover
process as
detailed later would be similar however.

1.

Install WSS 3.0 SP1 as per the instructions in the TFS 2008 Installation Guide but do not
configure Sharepoint at this stage as that will be done as a part of the failover process.

2.

TFS Templates will be added once
the server is configured

Performing the Failover


N
ote that you will need to disable “Internet Explorer Enhanced Security” to complete
some of the

next task
s
. You can do this via “Windows Components Wizards” in “Add/Remove Items”

then
uncheck the “Enhanced Security
for Internet Explorer” checkbox and enable it once this process is
completed.



Any command lines should be typed
as

copy and paste will likely cause the commands to fail.

1.

Have your domain administrator change the DNS e
ntries to point towards the backup
servers
:

APPTIER
-
> Standby Application Tier

DATATIER
-
> Backup Data Tier


2.

Restore the TFS databases to the backup data tier using the following guide

http://msdn.microsoft.com/en
-
us/library/ms252458.aspx

Do not restore WSS_Config or WSS_AdminContent, only WSS_Content

and as the services are
stopped skip to the restoration procedures


3.

Open a command prompt and run the following command on the SAT and BDT

ipconfig /flushdns

This will ensure the new IP addresses are used rather than the cached entries


4.

Run the Sharepoint Configuration Wizard on the SAT

a.

Select “New Farm”

b.

Database server: Data Tier Virtual name

Database Name: WSS_Config

Username: WSS or TFS
Service Account (same as Primary App Tier)

Password: for the above account

c.

Enter the port used by the Admin site on the Primary App Tier (17012 by default)

Leave NTLM selected


5.

Once configuration completes the Central Admin Site should be displayed

and we
can attach
the content database to Sharepoint to
give access to the Team Portals and project document
libraries

a.

Click on the “Application Management” tab then “Create or extend Web
Application”

b.

Select “
Create a new
web application” then use the following s
ettings:

“Use an existing IIS Web Site” and “Default Web Site”

Select NTLM

Leave the URL for the local hostname present

Select the “Team Foundation Server” application pool

Click OK

c.

Click on “Application Management” then “Content Databases”

d.

There should be

one database listed. Click on it, scroll down and check “Remove
Content Database” then OK.

e.

Open a command prompt to the following path:

C:
\
Program Files
\
Common Files
\
Microsoft Shared
\
web service extensions
\
12
\
bin”

f.

Run the following command:


stsadm.exe

o addcontentdb

url
http://
STANDBY
APPTIER
:80

databaseserver
DATATIERDNS

databasename WSS_Content”

g.

Click on the “Operations” tab then “Alternate Access Mappings”

h.

Click on “Add Internal URLs” then use the following settings:

Alternate Access Mapping Collec
tion: Central Admin”

URL:
http://APPTIERDNS:17012

(or whichever port admin uses)

Save

i.

Click on “Add Internal URLs” then use the following settings:

Alternate Access Mapping Collection: Central Admin”

URL:
http://APPTIERDNS:17012

(or whichever port admin uses)

Save

j.

Click on “Add Internal URLs” then use the following settings

then click “Save”
:

Alternate Access Mapping Collection: “Default Web Site”

URL:
http://APPTIERDNS:
80


k.

I
nstall the “Sharepoint
Extensions

for Team Foundation Server” on the Standby
Application Tier


6.

Open “Report Server Configuration Manager” on the Standby Application Tier

to configure
Reporting Services for use with your
restored
databases


a.

Connect to the
machine hosting Reporting Services

using the Report Services
Configuration Manager

b.

In “Report Server Virtual Directory” and “Report Manager Virtual Directory” check
“Apply Default Settings” then “Apply”

c.

In “Windows Service Identity” select “Network Service
” or enter the same
credentials SSRS was running as prior to DR then click Apply

d.

In “Web Service Identity” select “ReportServer” as the application pool for both
Server and Manager then click Apply

e.

In “Database Setup” enter the virtual DNS name for the dat
a tier then “Connect”,
select the “Report
Server” and “Credentials Type” of “Service Credentials” then
“Apply”

f.

In “Encryption Ke
y
s” select restore, locate the backup file you created earlier then
enter the password


7.

Connect to the backup data tier using S
QL Server Management Studio
, we will now add
rights to a number of stored procedures to the RS Exec Role to enable team project creation

a.

Expand the Master database, Security, Roles and Database Roles then right click on
RSExecRole

b.

Click on Securables and a
dd the
following “Extended Stored Procedures” and grant
all three “Execute” permissions:

xp_sqlagent_enum_jobs

xp_sqlagent_is_starting

xp_sqlagent_notify


8.

Open a command prompt and navigate to

the following path
:

C:
\
Program Files
\
Microsoft Visual Studio Te
am Foundation Server 2008
\
Tools”

and run the following command:


tfsadminutil activateat
apptierdns




Client Configuration

To complete the failover each client machine must clear their metadata and DNS cache, this will
ensure that Team Explorer is using t
he correct server information. Depending on the rights of the
user, an administrator may be required to perform some

1.

Close Visual Studio and delete the “Cache” folder from the following path:

Application Data
\
Microsoft
\
Team Foundation
\
2.0
\

2.

“ipconfig /flus
hdns” on the client machine

3.

Open Visual Studio

Failover Complete


After completing the steps above your instance of Team Foundation Server should be fully
operational once more.