We are using TFS2013 on windows server 2008R2 with sql server 2012. Now we want to move this to TFS2015... with connection to sql server 2014 (WINDOWS SERVER 2012..diff machine)...any pointers in right direction?
I recently upgraded our SQL server using this using this post as a guide. It's spot on but missing one step, at the very end before you start TFS back up you need to start IIS.
I would recommend first doing the upgrade for TFS then migrate the databases.
Based on the information here and here you should be fine restoring your backups from 2012 to 2014. Just verified that we did exactly that, moved from 2012 to 2014.
Related
I've found this article about moving collections between TFS and DevOps:
https://learn.microsoft.com/en-us/azure/devops/server/admin/move-project-collection?view=azure-devops
TFS 2012 isn't listed beneath the article heading, so I'm assuming it's not possible to move a 2012 collection to Azure DevOps. Can anyone confirm or otherwise?
I guess I could just try it, but I would need to do so out of hours to avoid the disruption of detaching the collection from the live TFS 2012 server. Now I can reattach it once it has been backed-up right?!
It isn't supported, as you can find in the Azure DevOps Services Migration Guide and the Migration tool, the current oldest version supported is Tfs2018 Update 3. So you will need to upgrade to that version first.
Do note that this will also mean that you need to upgrade the SQL server database your are using to MSSQL 2016.
I am using TFS 2015 U3.
I am working on Migration of TFS from 2015 U3 to TFS 2018 RC2.
We have a TFS 2015 current set up as follows:
Single App Tier- includes vNextBuild agents (Windows Server 2012 R2)
Single Data Tier - SQL server 2016 is used
If i want to configure code search server in the same application tier, is there any issue? what would be the process to do that?
Search can be used on any size physical server or virtual machine that
runs TFS 2017 or above. It can be configured on the same server as
TFS, or on a separate server dedicated to Search. When configuring
Search on the same server as TFS, you must take into account the
existing CPU utlization factor due to TFS itself. In most cases you
should consider configuring Search on a separate server.
Please go through the article below, and follow the steps there to configure Search feature:
https://learn.microsoft.com/en-us/vsts/search/code/administration
By the way, TFS 2018 RTM is available, you can upgrade to RTM version instead of RC2. Also, TFS 2018 requires SQL Server 2016 (minimum SP1), make sure your SQL Server meets this requirement.
Does anybody know if it's possible to move a TFS repository from SQL 2012 Express to SQL 2008R2?
Background:
At some point someone in our shop installed TFS to test it. This was done on a SQL 2012 Express.
Over time this installation has become our de facto source control system and contains history for 25+ different solutions.
Now our Sys Admin would really like to get rid of this 2012 Express edition. Which means we have to move it to our 2008R2 SQL production server.
No, as far as I know this is not officialy supported. SQL Server is backward compatible meaning you can go from 2008 to 2012. The other way around however is not supported.
By far the easiest solution would be to move to a regular SQL Server 2012 install. When you have a license for TFS, you also get a license for SQL Server Standard that you can use.
If that's not possible, you should contact Microsoft support. They have a script that you can use to migrate the data from one database to another. This can be done to run a downgrade but it's only supported if Microsoft helps you with it.
I have two TFS servers. One is a legacy TFS2010 server that contains an old collection of our projects. Last year, we spun up a new TFS2012 server. However, we never migrated our source code from the old server (we treated it as a fresh install and created new projects).
We are now looking at retiring the 2010 server completely and I want to migrate the legacy 2010 collection (actually all I care about is the source control and history) to the new server as a separate collection, but I can't figure out how. I've followed the instructions on MSDN (http://msdn.microsoft.com/en-us/library/vstudio/dd936138.aspx) but when I get to the step for attaching the collection on the new server, TFS complains that "no attachable databases were found" on the sql server.
I've also tried running the "tfsconfig Collection /attach" command on the target TFS server (even though numerous posts I read say it was deprecated in 2012). It tells me it can't connect to the target database server (even though my production collection is attached to it on that box).
Does anyone know if a collection migration from 2010 to 2012 is even possible or if I'm just spinning my wheels? There's no official documentation from Microsoft that I can find that says such a migration is even possible (even though there's nothing I can find that refutes it either)
Server Specs:
Old SQL Server: Enterprise 64 Bit 2008 SP3 (10.0.5500)
New SQL Server: Enterprise 64 Bit 2008R2 SP2 (10.50.4000)
Old TFS Server: 10.0.40219.1 (SP1 KB2182621)
New TFS Server: 11.0.60315.1 (TFS2012 Update 2)
You can migrate a single collection. The steps I know working are:
detach the collection from the 2010 instance using TFS Admin console
backup the database (or detach from SQL)
restore the database new SQL instance (or copy the files and attach them from SQL) -- check does not clash with existing database names
attach the collection from the 2012 TFS Admin Console
The last step will kick off the upgrade process: the collection will not be available until the process is complete. It could takes minutes or hours depending on the size, and make sure you have enough space for SQL transaction logs.
Take a look at Team Foundation Server Integration Tools (March 2012 Release): http://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-9ead-fa115b27fefe
The TFS Integration Tools is a project developed by the Team
Foundation Server (TFS) product group and the Visual Studio ALM
Rangers to integrate Team Foundation Server with third party systems
for migration and synchronization of data.
There is a migration guide for TFS 2010 to TFS 2012 located here: https://upgradetfs2010totfs2012.codeplex.com/
it may be faster in some cases depending on the size of the projects that need to be moved (and the number) to start by importing the latest code into the existing version of 2012 since you are concerned only with moving the source code. You do loose the history however.
Do a in-place migration, described in Team Foundation Server Upgrade Guide, from Microsoft ALM Rangers (http://vsarupgradeguide.codeplex.com/), and next migrate the collection to the new server. From 2010 to 2012 it's a very simple migration.
Don't forget backup the databases before doing a in-place migration.
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