I did a pre-production upgrade of TFS 2015 to TFS 2018 on another Windows server. It worked fine. During my TFS 2018 tests developers submitted new code to TFS 2015. Now, I would like to restore the latest TFS 2015 DB on TFS 2018 again and switch all dev's workplaces to TFS 2018.
Do I need to repeat whole TFS 2018 installation process to upgrade TFS 2015 to TFS 2018 or there is another way of doing this?
If I need to repeat TFS2018 installation, do I need to uninstall TFS 2018 before that?
Thanks
No, you do not need to uninstall: simply remove the Application Tier configuration. You can do it easily from the Administration Console (screenshot is for removing the Proxy feature, simply what you need).
Pre-production upgrade is just a dry run of your upgrade in a production environment.
Usually we use this to test your upgrade. This process test upgrades the databases. You can use this to simultaneously test your TFS 2018 on another hardware while continue to use your existing older TFS up.
Once you are ready for upgrade, restore the databases again and just use the Production Upgrade scenario during the server configuration wizard.
Not sure if you would like to restore the latest TFS 2015 DB on TFS 2018 on production environment or pre-production environment.
If you want to restore the newly changes on TFS2015 to pre-production TFS 2018 environment. It's not a common situation, usually we will abandon the pre-production environment. If you insist on this, you may have to re-upgrade to TFS2018 with pre-production style again. You could also try to back up the database on TFS2015 and restore it in TFS2018 pre-production environment. And you may have to change server IDs which ensures that this deployment will not interfere with the production environment.
Otherwise, suggest you directly move the changes in the production environment later, a tutorial for In-place upgrade to TFS2017(similar to TFS2018 without sharepoint) for your reference.
Related
I was working with Team Foundation Server 2015 where I had some releases configured for some environments (env1, env2, ...).
I installed TFS 2018 in a different machine. I migrated the code and I have completed the creation of a build definition.
I'd like to configure a release, using the old TFS 2015 environments. Can I install a TFS 2018 Agent, in the environments where I had installed the TFS 2015 agents?
In this way both of the agents would work without issues? The TFS 2015 Agent would work with TFS 2015 and the TFS 2018 Agent would work with TFS 2018 (both in the same machine).
I want to do this because my team is still working with TFS 2015, but as I am still setting up and testing TFS 2018 build/releases, I'd like TFS 2015 to work flawless (whithout any issue) while I am setting up and using TFS 2018 (with TFS 2018 Agents).
Different versions of agents can easily work on the same machine. As long as you keep the rule of thumb of 1 cpu core for the system and 1 cpu core per agent.
I have had multiple versions of agents running before on the same build machine without any issue. The only problem would be to try and connect an agent with 1.* versions to TFS 2018, since that wouldn't work, but since that is not what you are asking for, I would say that you are good to go :-)
We are trying to upgrade our TFS 2013 Update 5 to TFS 2018 Update 2. I have checked this thread to make sure we meet the prerequisites.
From the list, it looks like we met the prerequisites, but when i run the TFS2018 installer it gives me an error saying there is no direct upgrade path from 2013 to 2018. Im not sure why we are getting this error when i looked at the Microsoft site, there is a direct upgrade from TFS2013 update 5 to TFS2018. What am i missing?
Here are our specs on our TFS 2013:
SQL: SQL Server 2016 SP2
OS: Windows Server 2012 R2
TFS: TFS 2013 Update5
P.S. we moved the databases to a SQL server 2016 from a 2014 SQL just to comply with the prerequisites.
Ahh yes, the added error message makes sense. What the TFS installer is telling you is that it can't perform the upgrade while TFS 2013 is installed and running on that server.
You first have to uninstall the Application Tier and Build Services on the machine. This doesn't impact your databases in any way.
Then you can install TFS 2018.2 or 3 directly into that server, point it to the existing SQL databases and it will ask you whether you want to upgrade those.
You'll need to verify a few server settings, plus decide whether you want to enable SSH and Search on this machine.
After the integrity check the installer will install the TFS Application tier and start the database upgrade process.
Only of you're on TFS 2005 or 20008 do you need to perform this step multiple times. first with the 2010 installer before you can take it to 2018. This is what's meant by 'not possible to do a direct upgrade' in some parts of the docs and which confused me at first.
I am performing a migration upgrade from TFS 2015 to TFS 2018. I have performed the pre-production upgrade and everything went successful. I now wish to perform the production upgrade with a new set of DB backups but I do not see the option for the production upgrade in the Team Foundation Server Administration Console. How to do tell TFS to move from pre-production to production upgrade?
You need to unconfigure the app tier.
Ref: https://blogs.msdn.microsoft.com/tfssetup/2017/09/25/unconfigure-team-foundation-server/
Basically we have existing TFS 2013 running in PROD, can we just install TFS 2018 in a new machine and restore the DB?
Please guide me with the upgrade from 2013 to 2018
I'm afraid your SQL Server version doesn't meet TFS 2018's requirement. As TFS 2018 only supports SQL Server 2017 and SQL Server 2016 (minimum SP1).
You need to go through article Upgrade your deployment to the latest version of TFS before doing upgrade. And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system requirements for TFS 2018. Upgrade SQL Server is
necessary for your scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and consistent set of database backups in case something
goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install the new version of TFS to get new binaries, and then run
through the upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from, you may need to configure each team project to gain access
to some of the new features made available.
Here is a useful blog for your reference:
https://blogs.msdn.microsoft.com/rob/2016/12/22/upgrading-from-tfs-2013-to-tfs-2017/
Even if the detach/attach upgrade is possible, it is not recommended to go that way and you could find more details here and here why is that. You could still go that route but at least you would be aware of the possible issues.
For the safest way to go here, would be to make an actual upgrade of your systems from TFS 2013 to TFS 2018. However, due to the TFS requirements, you would have to make something like that approach to make it possible:
From TFS 2013 upgrade to either TFS 2015 or TFS 2017. Based on your current SQL Server that you are using, if that is SQL Server 2012 you would have to go first to TFS 2015, upgrade your SQL Server to be SQL Server 2016 (minimum SP1), and afterwards proceed with the second upgrade to TFS 2018.
I want to move the whole team project data(source files and work items…) from TFS 2008 to TFS 2015. Can anybody tell me the detailed step by step process, as I have never done migration within TFS versions?
You would need to do a upgrade for your TFS. Direct upgrade to TFS 2015 is supported only from TFS 2010 and newer. If your TFS deployment is on an older version than that, you will need to upgrade to TFS 2015 in multiple hops. For your scenario, you are on TFS 2008 you could upgrade to TFS 2010 or TFS 2012 first and then to TFS 2015.
The general process for upgrading an existing deployment of Team Foundation Server is to:
Prepare your environment. New system requirements may require you to upgrade hardware or software.
Expect the best, prepare for the worst. The single most important step you can take here is to ensure you have a complete and consistent set of database backups.
Do the upgrade!
Configure new features. Depending on what version you upgraded from, you may need to configure each team project to gain access to some of the new features made available.
Walk through an upgrade from TFS 2005 to TFS 2015.