As part of a server move, we'll be transferring our TFS and its SQL back-end. Can someone tell me if this is possible, and if so, what order we should be doing the migration vs upgrade? Would it be best to do the upgrade in-place before moving hardware/domain? Are there any particular pitfalls I should be wary of?
Details:
Moving TFS2010 to TFS2018 (potentially via 2013.5)
Moving SQL Server 2008 R2 to 2017
All moves will be done to new hardware on a new domain
Build and work item compatibility is not a concern, as we use TFS only for version control
Direct upgrade to Team Foundation Server 2018 Update 2 is supported from TFS 2012 and newer. If your TFS deployment is on TFS 2010 or earlier, you will need to perform some interim steps before upgrading to TFS 2018 Update 2. Please see the chart below for more information.
Can someone tell me if this is possible, and if so, what order we should be doing the migration vs upgrade?
Yes. You can upgrade from TFS 2010 to TFS 2018. But you have to upgrade to TFS 2012 and newer, then upgrade to TFS 2018. You could refer to the link below:
https://learn.microsoft.com/en-us/vsts/tfs-server/upgrade/tfs-2005-to-2015?view=tfs-2015&viewFallbackFrom=tfs-2018
And, changing the hardware is a restoration-based move, and you should never combine the two move types. First complete the hardware move, and then change the environment: https://learn.microsoft.com/en-us/vsts/tfs-server/admin/move-across-domains?view=tfs-2015v
Would it be best to do the upgrade in-place before moving hardware/domain?
You could do in place upgrade, or move to new hardware. If you're upgrading in place, consider doing a dry run of your upgrade in a pre-production environment, and make sure the system environment is meet.
Are there any particular pitfalls I should be wary of?
Before upgrade, you can read this article first, and be sure you have full backup of your database.
Related
I'm planning to upgrade TFS from 2013 to 2015. In case something goes wrong during the upgrade installation, I'll rollback and revert every thing to its original state (TFS 2013). I'm performing the upgrade on the same server, which means that if the upgrade is successful, TFS 2015 will override 2013.
Is there an article to follow in case of rollback? Preferably an official article from Microsoft.
Just as jessehouwing's answer above, you can follow the restore procedure, but if your setup includes Sharepoint, Report Server and one or more build servers you may need to revert those too, that would be a very tedious and complex job.
Another way is that you can make a system image to back up you environment first,then restore it in case something goes wrong during the upgrade installation. Please see Back up and restore your PC for details,or use any other backup tools.
You're basically looking at the Restore procedure outlined here:
https://www.visualstudio.com/en-us/docs/setup-admin/tfs/admin/backup/restore-data-same-location
But before you restore you need to uninstall TFS 2015 and reinstall TFS 2013 and its latest update packs.
If your setup includes SharePoint, Report Server and one or more build servers you may need to revert those too. As far as I know there is no definitive rollback documentation. The recommendation is to do a trial upgrade on a second environment, resolve any issues you may find and then perform the final upgrade.
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
HELP!!
I'm learning on the fly here with no training whatsoever! I'm a system administrator who is responsible for supporting the developers. They use Visual Studio, TFS, Plastic SCM and TeamCity amongst other tools.
My task was to get TFS 2015 and SQL Server 2014 installed on a new VM. This I have done but my biggest task now is setting up TFS which seems complicated.
For your information, The developers use TFS 2012 as a Kanban board.
Can anyone point me in the right direction to documentation that simply explains how to copy a project from one collection to another? I'm reluctant to move the project to the new version of TFS without testing the current project.
Thanks in advance.
You cannot copy a single project, there is the TFS integration platform, but it sucks and doesn't officially support TFS 2015
I would say your best bet is to follow the following steps.
In TFS 2012, detach the collection using the TFS Admin Console.
Backup the collection database in SQL server
Copy the backup to the new SQL server
Restore the Database
In the TFS Admin Console in TFS 2015, attach the collection
Wait for TFS to update the Database Schema.
You should now have the full team project collection available in the new server.
Can I confirm that if I already have a functioning TFS 2015 server and I want to upgrade an existing TFS 2010 server - I need to backup any existing collection DBs, reinstall TFS with upgrade of new instance and then restore/attach existing collection DBs?
In other words, there doesn't seem to be support for adding extra collection DB's from an older version? (e.g. like a SharePoint Content DB attach).
TFS upgrade guide is here: http://vsarupgradeguide.codeplex.com/releases and suggests a reinstall for Migration Path upgrade.
The process is described at When upgrading from TFS 2008 or TFS 2010.
Shortly, there is no direct path from 2010 to 2015, so you need to upgrade your collection to 2012 or 2013 (I recommend the latter).
In your case I would:
Backup, backup and make sure backup can be restored
Prepare a new TFS 2013 instance in a VM -- you may share the SQL instance if you are careful
Detach from TFS the 2010 collection you want to move
Copy the detached collection database to the SQL instance supporting TFS 2013 (you can use a full backup copy-only)
Attach the collection database on TFS 2013, the upgrade process starts asynchronously
Adjust the Process Templates etc. as described in the article
Detach the collection, now upgraded to 2013
Copy the detached collection database to the SQL instance supporting TFS 2015
Attach the collection database on TFS 2015, the upgrade process starts asynchronously
Adjust the Process Templates etc. as described in the article
I my experience the TFS detach and attach operations are generally safe, but may fail (e.g. 2012u2 attach was buggy); that is why I recommend backup with tested restore procedure.
Update:
In addition to Rangers' guidance, you may find useful SSW Rules to Better TFS 2015 Migration.
What you do is simply detach the collection though the TFS admin console, then backup & restore, then attach it to TFS 2015. The attach process will then do the upgrade on that collection. See this
I have been searching the web for a clean solution on how to migrate our 2010 tfs collections to our new tfs 2012 server, but no luck. May someone please assist with the steps or a good blog I could look at to achieve this process. The reason we want to do a MIGRATION and not an upgrade is because we got new hardware and would first like to trial TFS 2012 before we upgrade our live environment. Therefore we would like to import all our collection including the work items and build process templates.
Here is a decent blog post: http://mohamedradwan.wordpress.com/2013/01/05/upgrade-tfs-2010-to-tfs-2012-with-migration-to-a-new-hardware-series/
The basic steps you want to follow are:
Backup all of your 2010 databases.
Restore those databases on the SQL Server on your new hardware.
On your new hardware, install TFS 2012
When it comes time to configure. Select the upgrade option.
It will asks where your databases are. Select the SQL Server that you used in #2.
Press Go.
Note, if you want to test 2012 with the same clients you are using for 2010 then you'll need to "clone" the system otherwise your clients will get confused. To do that, see http://msdn.microsoft.com/en-us/library/vstudio/ee349259.aspx
You can move a collection at a time using the detach option in 2010 and attach it back to 2012 using the attach option there.
See http://msdn.microsoft.com/en-us/library/dd936138(v=vs.100).aspx