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.
Related
We have TFS 2013 SP 4 (our existing version) and TFS 2017 (which is under testing for we are upgrading the TFS version).
My question is : Is it possible to work and test on both the TFS at the same time with the same workspace?
Business users are able to configure the new TFS 2017 and work there. However, when they are switching back to TFS 2013 (since we have not gone live with TFS 2017), it throws an 'Identity does not exist error'.
Has anyone tried it?
Is it even possible to test this way? Or shall we have one TFS version at a time for one workspace even for testing?
Thank you.
Anant
When upgraded TFS 2013 to TFS 2017(using TFS 2013 backup) on a new Server, the two servers have the same TFS GUID, which will confuse your Visual Studio clients.
You should avoid having two TFS up & running with the same set of GUIDs. And this is usually avoided by shutting down the old TFS server after the upgrade has finished and has been tested & verified.
We need to migrate projects in TFS from one server to another. On source server we have TFS 2010 with several VS.NET projects in the DefaultCollection. On the destination server, we have TFS 2013 with an empty DefaultCollection but 2 other collections in use by other developers. Each instance of TFS has its own SQL Server.
The problem we face is how to take the DefaultCollection from the TFS 2010 server and place it on the TFS 2013 Server?
I'm aware of several articles about migration but have not found one that exactly fits our situation. I appreciate any ideas anyone may have.
This is a very straightforward scenario.
Something along these lines should work:
Detach DefaultCollection from TFS 2010 using the admin console.
Take a backup of your TFS 2010 DefaultCollection database
Migrate the database to your TFS 2013 database server
Attach the TFS 2010 DefaultCollection database in TFS 2013 via the admin console. As part of the attaching process, you should be able to rename it.
The team project collection database will be upgraded to TFS 2013 and made available to users. At that point, you can go back and clean up unneeded project collections and rename things if you'd like.
Always take backups before you attempt any sort of migration or upgrade. I always recommend performing the upgrade against a test environment first.
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/
We have a collection in TFS 2012 which contains more than one project.
We are considering to migrate to TFS 2013.
The TFS servers are already up and running.
Is it possible to migrate the data of a specific project in the collection from one TFS server (2012) to the other (2013) or we must migrate the whole collection?
The best way to do it would be to split up the team project in team project collection and then upgrading only the new team project collection. See below for splitting up team project from project collection
http://msdn.microsoft.com/en-us/library/dd936158.aspx
Also, the Tfs To Tfs migration guide will be useful.
http://tfstotfsmigration.codeplex.com/releases/view/37382
There are a lot of questions about upgrading here, but I have another, very specific one, that I don't see asked.
When installing TFS 2010, on the first run, you get a wizard, which lets you choose a database (which you presumably backed up, and restored onto the new instance) to use, and it allows you to upgrade that instance in-place.
If I'm performing a dry-run, during the course of which I do not want to disable access to the OLD tfs, is it possible for me to do this upgrade a second time without reinstalling TFS?
IE: can I create a new team project collection and point it to a tfs 2008 database and have it upgrade that?
I dont think it is possible to point to a TFS 2008 database from TFS 2010.
We have migrated our TFS 2005/2008 too.
We installed a fresh new TFS 2010 and migrated the old projects into the new TFS 2010.
All files of the projects in TFS2005/2008 are set to read only, workitem history and changesets are migrated into the new TFS2010.
We decide to switch the process template too so we created another team project with the Scrum Template.
Afterwards the source and all needed files are copied to the new Scrum team project.
Now if I let me show the history of a item under source control, it shows the history till the beginning of each item (points to the "old"/first migrated team project in TFS 2010).
I did it an upgrade test on a dummy machine and when i get to the real thing I had to uninstall and remove all leftover db's (tfs_configuration) you can see migrate data from TFS 2008 to an already working TFS 2012