TFS Migration to a new server

Has anyone been successful in migrating a TFS server to a new machine with a new name We are currently still using the RC, but I was surprised at some of the problems I had during a migration. Specifically Sharepoint, I don't know if its been improved with the RTM, but the restore procedures I saw were just wrong. The 1st trial I did had Sharepoint completely messed up. I finally fixed it, but it took my own understanding of Sharepoint, not the backup\restore procedures provided on msdn. Has anyone else had these issues


Answer this question

TFS Migration to a new server

  • mrbelk

    I'm sorry about the delay in getting back to you, job change sort of had me preoccupied.

    Short answer, no you can fix it but its not all that nice.

    Long answer, uninstall TFS, delete the databases (make sure you have backups!), and reinstall, this time not restoring the config database. I had to do this when I first discovered the problem and although a pain, wasn't bad if you did it right then (once again, I am sorry for the delay). If you kept on going while Sharepoint didn't work this would still work, as long as you used the most up to date backups instead of the originals.



  • robinjam

    How can one try to migrate the existing TFS Server on one domain to a new server on another domain. Is it possible to do this, if so where could I find this documentation or help files, chm files anything related to migration from one domain to another. I have looked through some of the chm files and most of them require that I be on the same domain.

  • StephanieR

    For those reviewing this thread now, it appears the the MSDN documentation for this has changed to reflect the things we have been discussing here, so a lot of this now covered in the official documentation.

  • Test1234525

  • MSP.Saami

    We are experiencing the same issues, but we already went thru the process and restored all the databases, including the config one. So if this is the case any idea what our best course of action is In your recommendation, step 1 is to not restore the config databases, so are we screwed
  • Tom_M_Wisconsin

    The admininistration guide has a topic for just this activity, and I believe it has been updated since RTM.

    Have you seen the How-to on server migration (and if so, can you check out the latest version and see if the Sharepoint-related sections are better than the one you were using)

    The guide is available here: http://www.microsoft.com/downloads/details.aspx familyid=2AED0ECC-1552-49F1-ABE7-4905155E210A&displaylang=en (Note that you probably need to save the guide CHM file, then unblock it, before you'll be able to view it correctly).

    The section you want is "How to: Restore Team Foundation Server Data to a Different Server" - I got to via TF Admin Walkthroughs -> Backing up and Restoring a Team Foundation Server (there's a link to the howto in backup & restore #4.

    Let me know if this doesn't help (or is "old news" to you) and we'll dig in farther.



  • Tzal

    hi guys,

    well i experienced moving the server to new one.. at first i had a problem but its just a version problem in my SQL (coz i havent installed the SP1). but i manage to finish it and now all is smooth and clean :)

    just follow this (Step by step):

    http://msdn2.microsoft.com/en-us/library/ms404869.aspx



  • SavasCilve

    I followed those instructions the 1st time I went through and Sharepoint came out trashed. I might have missed a step, but after talking with a few more people that know more about Sharepoint than I do I don't think so. The problem is with restoring the config database, it has all sorts of references to the original server and when you try to do anything and it can't access that original database server it blows up. I fixed it like this, which I think is along the lines of what the instructions were going through:

    1. When restoring databases skip the STS_Config_TFS and STS_Content_TFS databases
    2. Go into Sharepoint Administration, manage the content databases and remove the STS_Content_TFS database that was installed by default
    3. Restore only the STS_Content_TFS database
    4. Add in the STS_Content_TFS database through Sharepoint Administration

    FYI, I am going to run this again in a test environment just to make certain, but I'm pretty certain this is correct.



  • grellsworth

    I am having this same problem. Can you let me know how it turned out in the test environment
  • y2k4life

    I have never tried this, so take this as it is.

    It should be possible, following pretty closely with the Migrating TFS to a New Hardware instructions. The only problem outside of this will be with the ID's that are used to run TFS when it was originally setup and the existing users since they will no longer be accessible after the migration. You can change the ID's used with TFS by using the TFSAdminUtil command line tool. The users you will have to resolve manually.



  • Fantonis

    I rn through one more time and I'm fairly certain that I was correct. I've talked with some people who know Sharepoint a lot better than me and they confirmed what I thought, that you shouldn't restore the config database on a new server name but add in the content database through sharepoint the way I described earlier. The config database has a lot of references to the machine and content databases on it and restoring the config database will have those references as well.

  • giddy

    I haven't tried this yet, but it may be what you are looking for: http://msdn2.microsoft.com/en-us/library/ms404869.aspx
  • TFS Migration to a new server