• Blog
  • Info Support
  • Career
  • Training
  • International Group
  • Info Support
  • Blog
  • Career
  • Training
  • International Group
  • Search
logo InfoSupport
  • Latest blogs
  • Popular blogs
  • Experts
      • Alles
      • Bloggers
      • Speakers
  • Meet us
  • About us
    • nl
    • en
    • .NET
    • Advanced Analytics
    • Agile
    • Akka
    • Alexa
    • Algorithms
    • Api's
    • Architectuur
    • Artificial Intelligence
    • ATDD
    • Augmented Reality
    • AWS
    • Azure
    • Big Data
    • Blockchain
    • Business Intelligence
    • Cloud
    • Code Combat
    • Cognitive Services
    • Communicatie
    • Containers
    • Continuous Delivery
    • CQRS
    • Cyber Security
    • Dapr
    • Data
    • Data & Analystics
    • Data Science
    • Data Warehousing
    • Databricks
    • DevOps
    • Digital Days
    • Docker
    • eHealth
    • Enterprise Architecture
    • Hacking
    • Infrastructure & Hosting
    • Innovatie
    • Integration
    • Internet of Things
    • Java
    • Machine Learning
    • Microservices
    • Microsoft
    • Microsoft Bot Framework
    • Microsoft Data Platform
    • Mobile Development
    • Mutation Testing
    • Open source
    • Pepper
    • Power BI
    • Privacy & Ethiek
    • Python
    • Quality Assistance & Test
    • Quality Assurance & Test
    • Requirements Management
    • Scala
    • Scratch
    • Security
    • SharePoint
    • Software Architecture
    • Software development
    • Software Factory
    • SQL Server
    • SSL
    • Start-up
    • Startup thinking
    • Stryker
    • Test Quality
    • Testing
    • TLS
    • TypeScript
    • Various
    • Web Development
    • Web-scale IT
    • Xamarin
    • Alles
    • Bloggers
    • Speakers
Home » Cloning a Team Foundation Server
  • Cloning a Team Foundation Server

    • By Martijn Beenes
    • .NET 14 years ago
    • .NET 0 comments
    • .NET .NET
    Cloning a Team Foundation Server

    This weekend we upgraded our production servers running Team Foundation Server (the “Whidbey” release) to the Beta 2 of the Team Foundation Server “Orcas” release.
    First, I have to say, the upgrade experience compared to the beta 1 is much, much better. Just run the installer, fill out some account information and wait a while until the upgrade is done.

    We encountered no problems during the upgrade, but unfortunately after the upgrade things took a bad turn. The first server we upgraded crashed. The operating system was completely deleted from the hard drive. In turned out that we ran into a nasty bug on TFS “Orcas” that is very hard to run into. My colleague Marcel de Vries wrote a blog post about it. You can read it here.

     

    So with the server gone, we had to install our server from scratch.

    To prevent these kind of production problems and because of the need to store our customer code separately from our own codebase, we had already decided to split our big Team Foundation Server in two. To accomplish this, we created a clone of our main Team Foundation server and upgraded the cloned server to the “Orcas” Beta 2 bits. As the server had crashed, we needed to run this process again.

     

    There is a nice guide available from Microsoft to clone a (Whidbey) Team Foundation Server. You can read it here.

    There is one imported thing to note when using this guide. This guide is meanly meant to re-install your server after it crashed or for whatever other reason. But it assumes that after (or even during) the cloning process the “source” server is no longer available.

    In our case we wanted the “source” server to be up and running next to the newly cloned server. To accomplish this you need to give one of the Team Foundation servers a new instance id. This can be accomplished with the following commands:

     

     “%TFSInstallDir%ToolsInstanceInfo.exe" stamp /setup /install /rollback /d TFSWorkItemTracking,TFSBuild,TFSVersionControl,TFSIntegration /s <<your new data tier>> 

    "% TFSInstallDir %ToolsInstanceInfo.exe" stamp /d TFSWorkItemTracking,TFSBuild,TFSVersionControl,TFSIntegration /s <<your new data tier>>

    The first command is the clear the instance id, the second to stamp a new instance id. After executing these commands you have a newly cloned server side-by-side with the original server.

    The cloning process can take up quite some time. It took us about 4 hours to clone the server. This might take less or more time depending on the size of the Team System databases. We have a TfsVersionControl database of over 6 gigabytes and it took about 25 minutes to create a backup of this database and another 25 minutes to restore it.

    Because of the server crashes (It crashed twice before we understood what was causing the problem) we cloned our production server three times in the last few days. Since the backup and restore actions for the Team System databases took us so much time, we created a T-SQL script to restore the databases and move them to a new location. You can download the script here. (Note that the location and names of the backup files will be different on your machine.)

     

    Our servers our now al up and running with the Team System “Orcas” Beta 2 bits, thanks to the guys of Microsoft that helped is fix the data that was causing the server crash.

     

    Hope this helps.

    Share this

Martijn Beenes

View profile

Related IT training

Go to training website

Related Consultancy solutions

Go to infosupport.com

Related blogs

  • Innovative patterns in software quality management

    Innovative patterns in software quality management Tom van den Berg - 1 month ago

  • Developing a Service Fabric service using another host

    Developing a Service Fabric service using another host Tim van de Lockand - 5 months ago

  • Adding a package to your private WinGet.RestSource feed…

    Adding a package to your private WinGet.RestSource feed… Léon Bouquiet - 10 months ago

Related downloads

  • Beslisboom voor een rechtmatig ‘kopietje productie’

  • Klantreferentie: Remmicom zet wetgeving om in intellige…

  • Klantreferentie RDW: Samenwerken voor veilig en vertrou…

  • Klantreferentie BeFrank: Strategische IT voor een innov…

  • Wie durft te experimenteren met data in de zorg?

Related videos

  • mijnverzekeringenopeenrij.nl

    mijnverzekeringenopeenrij.nl

  • Winnaar | Innovation Projects 2017

    Winnaar | Innovation Projects 2017

  • Explore | Info Support & HAN & Poliskluis

    Explore | Info Support & HAN & Poliskluis

  • LifeApps bij HagaZiekenhuis

    LifeApps bij HagaZiekenhuis

  • Info Support | Bedrijfsfilm

    Info Support | Bedrijfsfilm

Nieuwsbrief

* verplichte velden

Contact

  • Head office NL
  • Kruisboog 42
  • 3905 TG Veenendaal
  • T +31 318 552020
  • Call
  • Mail
  • Directions
  • Head office BE
  • Generaal De Wittelaan 17
  • bus 30 2800 Mechelen
  • T +32 15 286370
  • Call
  • Mail
  • Directions

Follow us

  • Twitter
  • Facebook
  • Linkedin
  • Youtube

Newsletter

Sign in

Extra

  • Media Library
  • Disclaimer
  • Algemene voorwaarden
  • ISHBS Webmail
  • Extranet
Beheer cookie toestemming
Deze website maakt gebruik van Functionele en Analytische cookies voor website optimalisatie en statistieken.
Functioneel
Altijd actief
De technische opslag of toegang is strikt noodzakelijk voor het legitieme doel het gebruik mogelijk te maken van een specifieke dienst waarom de abonnee of gebruiker uitdrukkelijk heeft gevraagd, of met als enig doel de uitvoering van de transmissie van een communicatie over een elektronisch communicatienetwerk.
Voorkeuren
De technische opslag of toegang is noodzakelijk voor het legitieme doel voorkeuren op te slaan die niet door de abonnee of gebruiker zijn aangevraagd.
Statistieken
De technische opslag of toegang die uitsluitend voor statistische doeleinden wordt gebruikt. De technische opslag of toegang die uitsluitend wordt gebruikt voor anonieme statistische doeleinden. Zonder dagvaarding, vrijwillige naleving door uw Internet Service Provider, of aanvullende gegevens van een derde partij, kan informatie die alleen voor dit doel wordt opgeslagen of opgehaald gewoonlijk niet worden gebruikt om je te identificeren.
Marketing
De technische opslag of toegang is nodig om gebruikersprofielen op te stellen voor het verzenden van reclame, of om de gebruiker op een website of over verschillende websites te volgen voor soortgelijke marketingdoeleinden.
Beheer opties Beheer diensten Beheer leveranciers Lees meer over deze doeleinden
Voorkeuren
{title} {title} {title}