Tell me please. I can configure two TFS servers and replicate them. Thank you
Blockquote
No, you can not do that. TFS does not support replication. I remember only one system with replication: IBM Rational ClearQuest https://www.ibm.com/support/knowledgecenter/en/SSSH5A_8.0.1/com.ibm.rational.clearquest.ms_admin.doc/topics/c_admin_db_replicas.htm
You can try to Move a team project collection from one TFS to another.
Detach the collection from TFS 1
Back up the collection database
Move the collection database to TFS2
Attach the collection
Configure the moved team project collection
Configure projects
Related
We have a TFS 2013 on-premises server that we just migrated over from VSO for a customer. They originally had 2 VSO accounts. Each account had a collection of projects. They have now been attached to the TFS thereby creating 2 collections that we can see & browse successfully. They'd like to merge all of the projects into one collection while maintaining all history info, etc... Is this possible? We are NOT trying to merge projects...ONLY the collections.
The process for merging Collections is exactly the same as the process for merging Team Projects. You would pick one collection to keep and create a new Team Project for each of the Team Project that you want to migrate from the other collection. You would then use the TFS Integration Platform to push the data across...
I know this is not what you want to hear but it is the only possible way to achieve this.
I have a project that is in the default collection on my TFS server. Is it possible to move the project from this collection to a new one that I created? Thank you
The project exists within the Collection Database, you can't just pickup and move a Team Project out of a database.
There is a TFS Integration Platform that can copy Team Projects between services.
Generally it's best to plan this sort of stuff upfront as to avoid issues like this down the line. I have heard rumours Microsoft are working on improving this, but I don't think anything will be available for a while.
We've lost our TFS and domain servers. TFS was configured to use domain accounts. We could resotre only the TFS Project Collection databases and thanks to the "TFSConfig repair" command, we finally attached them to a new TFS instance.
But all of the default security groups for repaired projects are lost (except the administrators). For example we don't have "Contributors" group anymore.
Now we want to restore these standard groups. Maybe it's possible to fix it by applying the default TFS "project proccess templates" on all existing projects and collections again.
Is there any way to address it?
As you lost the Domain server you have to follow the Move User and Service Accounts chapter of the "Move Team Foundation Server from One Environment to Another" procedure.
By the way, there's no such feature as reapplying a process template on an existing Team Project.
Have you tried to recreate at least one group that you lost? Only to know if that is working (maybe TFS will return an error because the group still exists in the database but it's not shown for whatever reason) ?
One last thing: check the TFS Scheduler Windows Service is running on the TFS Server and look for errors in the Windows Event Log.
I am having short place in the disk where my TFS server is installed and i want to move some projet collections to a different disk on network where there is more place, can i proceed this moving without reinstalling again TFS and detach the collection and attach it again ?
TFS installation is server specific. On that server you will have your collection db named: Tfs_XXX along with that you have your warehouse, sharepoint, reporting and configuration tables.
I think what you are asking is "Can I have X team project on server X and Y team project on server Y but still only have one installation of TFS to manage them both" or "Can I have X Collection on server X and Y collection on server Y but still only have one installation of TFS to manage them both"
The answer to both questions is no. Server has collections - Collections have Team Projects.
You will need to have a separate installation if you want to move your Collection or Team Project to another server.
What our team does is run TFS in a Virtual Image so that we can dynamically expand the drive as needed. You may want to consider a similar solution assuming you have the hardware to do it. Alternatively, you can ofcourse expand your drive or setup tasks to Shrink your db.
Yes I achieved this by moving certain Project Collection SQL databases to a different SQL Server Instance while leaving the config database on the original server.
Basically you need to configure a second SQL Server Instance to allow TFS databases on it, then move the database to that server, then reconfigure the project collection to point to the second SQL Server instance.
See exactly how to do it in this blog post: http://healthedev.blogspot.com/2011/12/move-tfs-2010-project-collection.html
is there a (simple) way to move a single TeamProject from one server to another? Including source code, work items, documents, project site...
We don't want to move our server from one machine to another. Just a single project from server A to server B.
You have two options
You can use the TFS to TFS migration tool: Click Here. This doesn't include the WSS project site.
Or you can backup your TFS db and restore on a new TFS instance, then use the TFSDeleteProject.exe tool to remove the projects you don't want.
The latter option is the easiest, but will not merge the backed up projects with any existing projects on the target instance. Existing projects will be lost. WSS sites can also be moved in this manner as well. See How to: Back Up a Team Foundation Server
The TFS to TFS migration tool is obsolete. The features you are looking for is part of TFS Integration Platform.
Goto http://tfsintegration.codeplex.com/ for more info.
In TFS 2010 you can detach the Project Collection database using the TFS Admin Console and then re-attach it to another TFS Server.
http://msdn.microsoft.com/en-us/library/dd936138.aspx
If you want an entire Project Collection to be moved from one TFS server to another:
1) Detach the collection via Admin Console.
2) Backup the Tfs_SomethingCollection database using SSMS, then restore it to the other database server.
3) On the second TFS Admin Console, attach the project collection. It will show up as an available collection to attach just because it has been restored in the second sql server instance.
I did not migrate the Tfs_Configuration database. In my case I was not utilizing reporting services, build services, or sharepoint.
I hadn't installed the second TFS server and was wondering, what options to choose when installing, and if you should install it after or before restoring the migrated DB(it doesn't really matter): Install TFS on the second machine. If TFS and its database instance will be on seperate servers, then choose Advanced configuration and specify the name of the DB server instance. When you have an opportunity to create a DefaultCollection, then opt to skip that step. The install will create a new Tfs_Configuration DB on the new server. Then follow the above steps to migrate the collection DB to the new DB server instance and attach it.
Programmers will need to add the new server to Team Explorer, and hit Change Source Control... twice in a row for each solution. Make sure the local path mappings are correct, and then Bind each solution/project.