index > Team Foundation Server - Administration > Restore TFS to a different server

Restore TFS to a different server

The Back Up-Restore process was made according to the following articles:

BackUp

1) http://blogs.msdn.com/vstsue/articles/511396.aspx

Restore

2) http://msdn2.microsoft.com/en-us/library/ms252516.aspx

A backup-copy of TFS on the <Serv_1> had been made and then restored on the <Serv_2>. When TFS had started it gave the sequence of the following errors in Application Event Log:

Event Type: Error
Event Source: TFS Services
Event Category: None
Event ID: 3021
Date: 26.05.2006
Time: 16:29:14
User: N/A
Computer: Serv_2
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 26.05.2006 13:29:14
Machine: Serv_2
Application Domain: /LM/W3SVC/3/Root/services-1-127931237470667557
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 1804
Thread Id: 3836
Account name: Domain\tfsidentity

Detailed Message: TF53007: The application tier name Serv_1 recorded in the database does not match the local machine name Serv_2. Please contact your Team Foundation Server administrator.

*****************************

Event Type: Error
Event Source: Tfs
Event Category: None
Event ID: 3059
Date: 26.05.2006
Time: 16:29:21
User: N/A
Computer: Serv_2
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 26.05.2006 13:29:21
Machine: Serv_2
Application Domain: TFSServerScheduler.exe
Assembly: Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: TFSServerScheduler
Process Id: 2236
Thread Id: 3760
Account name: Domain\tfsidentity

Detailed Message: TF50801: The TFSServerScheduler service did not initialize. The Team Foundation Registration Service returned the following error: The request failed with HTTP status 503: TF53007: The application tier name Serv_1 recorded in the database does not match the local machine name Serv_2. Please contact your Team Foundation Server administrator.

*****************************

Event Type: Error
Event Source: TFS Services
Event Category: None
Event ID: 3055
Date: 26.05.2006
Time: 16:29:22
User: N/A
Computer: Serv_2
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 26.05.2006 13:29:22
Machine: Serv_2
Application Domain: /LM/W3SVC/3/Root/services-1-127931237470667557
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 1804
Thread Id: 3308
Account name: Domain\tfsidentity

Detailed Message: TF50621: GSS: Failed to retrieve identity from source : [S-1-5-21-1582758608-1126111627-1400566485-1267]
Exception Message: Thread was being aborted. (type ThreadAbortException)

Exception Stack Trace: at System.DirectoryServices.ActiveDirectory.NativeComInterfaces.Pathname..ctor()
at System.DirectoryServices.ActiveDirectory.DirectoryEntryManager..ctor(DirectoryContext context)
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at Microsoft.TeamFoundation.Server.IdentityStoreAccessor.GetDomainDirectoryEntry(String domain)
at Microsoft.TeamFoundation.Server.IdentityStoreAccessor.ReadIdentityFromAD(String domain, String username)
at Microsoft.TeamFoundation.Server.IdentityStoreAccessor.ReadIdentityFromSource(String sid)

*****************************

Event Type: Error
Event Source: TFS Services
Event Category: None
Event ID: 3058
Date: 26.05.2006
Time: 16:29:22
User: N/A
Computer: Serv_2
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 26.05.2006 13:29:22
Machine: Serv_2
Application Domain: /LM/W3SVC/3/Root/services-1-127931237470667557
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 1804
Thread Id: 3308
Account name: Domain\tfsidentity

Detailed Message: TF50642: A problem occurred updating the Identity grp-TFS-Team Foundation Administrators (with SID S-1-5-21-1582758608-1126111627-1400566485-1267). Changes to this Identity and any of its members have not been propagated into the Team Foundation Server database. The Team Foundation Server will retry the update at the next scheduled synchronization.
Exception Message: TF50604: There was an error getting identity information from Active Directory. (type ActiveDirectoryAccessException)

Exception Stack Trace: at Microsoft.TeamFoundation.Server.IdentityStoreAccessor.ReadIdentityFromSource(String sid)
at Microsoft.TeamFoundation.Server.IdentityCache.ReadIdentityFromSourceWrapper(String sid, Dictionary`2 membersList, Dictionary`2 syncList)

Inner Exception Details:

Exception Message: Thread was being aborted. (type ThreadAbortException)

*****************************

Event Type: Error
Event Source: TFS Services
Event Category: None
Event ID: 3018
Date: 26.05.2006
Time: 16:29:22
User: N/A
Computer: Serv_2
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 26.05.2006 13:29:22
Machine: Serv_2
Application Domain: /LM/W3SVC/3/Root/services-1-127931237470667557
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 1804
Thread Id: 3308
Account name: Domain\tfsidentity

Detailed Message: Update identity cache
Exception Message: Thread was being aborted. (type ThreadAbortException)

Exception Stack Trace: at Microsoft.TeamFoundation.Server.IdentityCache.SyncIdentity(Identity idToSync, Boolean syncChildren, Dictionary`2 syncedGroups, DateTime sourceTimeStamp, Int32& sequenceId)
at Microsoft.TeamFoundation.Server.IdentityCache.SyncWithWindows(Identity idToSync)
at Microsoft.TeamFoundation.Server.BackgroundCacheManager.SyncGroup(Object group)

======================================================================

It has to be mentioned that I've discovered a lot of entrances of <Serv_1> in Report Service, Share Point and TFS databases. So may be the article (2) is not completely correct. I tried to correct tables manually but with the same result.

Are there any ideas or suggestionst regarding to this problem?

Dmitry N. Oleshko

It sounds like the step involving tfsadminutil either wasn't run, or hit some sort of error.

Can you confirm you ran the steps in the restore guide under "Configure the Application Tier to Use the New Data Tier"? If so, did you by any chance save the output from the tfsadminutil command? That may help us figure out why it's still not working...

Chris Rathjen

CRathjen-MSFT

In addition to what Chris said, the error you got of "TF53007: The application tier name Serv_1 recorded in the database does not match the local machine name Serv_2" means that the pointer we store in the database is still pointing at the old server. This means that you either didn't run the "tfsadminutil activateat" step, or it failed, or it ran against the wrong database.

if you haven't run it, run it and see if that takes care of the issue
if you ran it and it had failed, post a reply here to let us know how it failed
if you ran it and it seemed to work, check the ConnectionString property in %ProgramFiles%\Microsoft Team Foundation 2005\Web Services\Services\web.config to make sure it's pointing at the right data tier name.

Team Foundation Server - http://blogs.msdn.com/jmanning/

James Manning MSFT

Thank you for paying your attention to my question, but

There is an important addition to the description of my problem.

I tried to restore NOT ONLY a data-tier but also an application-tier to a new server.

So, the procedure described in (2) is not applicable for my case.

Now I'm in search for instructions on how to restore both Application and Data tiers on a new server. Of course if it is possible.

I will appreciate any suggestions in this direction.

Dmitry N. Oleshko

Hi Dmitri,

I restored both application and data tier. On new servers, I installed ?�pure??application and data tier with same name as old TF servers (of course, old TF servers was down), I made backup TF databases (in advance) and by the procedure ??ow to: Restore Team Foundation Server Data??I attached these databases to new data tier.

Regards

Software configuration manager

janko

Hi Dmitri,

the procedure I described above is not correct. The problems occur later and I didn't notice them at this time.

You have to follow next blogs:

http://blogs.msdn.com/vstsue/articles/558116.aspx

Thanks

Janko

Software configuration manager

janko

this one is much better..