TFS to TFS replication with complete data? - tfs

I have seen that, there are resources available to migrate complete content from TFS to VSTS. However, i have not seen any good thread talks about the possibilities of getting it done between one TFS instance (2017) to another of same instance (again TFS 2017) hosted in different server?

First, you should confirm one thing, do you need to use the original hardware and TFS deployment or not.
You could perform a move when you plan to discontinue use of the original hardware and TFS deployment. You could also perform a clone when you intend to continue using the original TFS instance.
Please take a look at Move or Clone Team Foundation Server from one hardware to another
Note: If you want to do a colne option, you need to reconfigure server IDs and remap databases.

Related

Maintaining Two Different Source Control Servers

We have been hired by a client who would like us to check in code to their Azure Devops Team Foundation Version Control server.
We have our own small team of developers that will work on this project and commit changes to our own TFVC server first. Once all check-ins are approved, we would then like to commit all of our changes to our client's TFVC server. We have been given a single login to their TFS system, so we would like to check in our code into their system using the single login that was provided to us. The client does not need to know the history of all of our own developer's work, we would like them to see our check in as a single author. We don't want to migrate, as this will be a common task for us.
What's the most straightforward way we could do this?
It is not possible to sync code on 2 different TFS server. Since you work in one workspace (command line and GUI) at a time. And a workspace cannot span servers.
The only workaround here is manually copy/past your code directly through windows file system. Finally check in code to your client's TFVC server.
The better solution is to convince your clients to use Git repositories instead of TFVC. There is a lot to win here! And you could migrate your sources with git-tfs with all history.

Sync 2 TFS servers?

We have 2 TFS servers, one is inside the firewall, and the other one is outside the firewall. Because of security reasons, we still need to keep it this way. But the question is: is there a way to Sync these 2 TFS servers, say at every night?
Say we have servers TFS1 and TFS2, right now, we only want to Sync from TFS1 to TFS2, not bidirectional synchronization. If possible, we want to have complete synchronization.
I searched some time, but I could not find a good solution. It seems all recommendations are for old version TFS.
Are there any solutions for the latest TFS? existing products? Or, some information about API that we can use to make a tool for this?
Thanks
There is nothing changed with sync two TFS servers for the latest TFS version. Just as Daniel and many other expert suggested:
TFS generally lives in 1 instance and 1 only. TFS is a production
environment for the development team. It doesn't make sense to have
two TFS systems and have them synchronize to make this separation.
Having your teams work on two different TFS environments at the same
time is a very strange requirement.
Source Link
The best solution in your case, negotiating with your IT team, set up a safe and stable way to allow your top Management users to connect the internal TFS. You could also set up SSL for your TFS server to improve the safety.
It will also save you a lot of time costs for maintaining two servers syncing.
If you insist on syncing two TFS servers take a look at this similar question: Sychronising work between two TFS servers
Another way is using VSTS instead of your external TFS. Microsoft has documentation on this exact scenario which can be found here: Migrate to Visual Studio Team Services : Move from Team Foundation Server (TFS) to Visual Studio Team Services (VSTS) and bring your data along.
This link also contains the download link for the migration tooling which you will want to use
Currently the following versions of TFS are supported for import:
TFS 2017 Update 3
TFS 2018
TFS 2018 Update 1

How can I merge/migrate TFS source code into existing Visual Studio Team System project preserving work items

We have a situation where at a point in our project's life, we needed to split off work item tracking and source control into 2 separate TFS projects, with the work items being in a VS Team Services project, and the source on-prem in TFS 2013.
The reason at the time being, we needed to grant access for our stakeholders to the product backlog, without them being on the corporate network where TFS is hosted. At the time there was concerns about security of the source code, hence the whole project was not lifted and shifted, just the backlog.
Now we're realizing some of the security concerns were not warranted, and we are missing out on the integration of ALM provided by a single project having both responsibilities, and would like to merge our source control out into the cloud-based VSTS project.
The problem is, the migration tools are overwriting the Work Items in VSTS. Is there some way we could merge, preserving that data, or any alternative to merge these two things together somehow?
I think you're looking at the Team Foundation Server Integration Tools here if you want to migrate source code history. Bear in mind that it's not going to be perfect (data time stamps will not be the same etc.).
If you can get away with it then just stick the latest code in VSTS and consider the on-prem server your archive should you need to go back. That doesn't tend to be too popular so you'll be wrestling with the integration tools. It's not the most friendly thing to use but mostly it will get the job done.
When you configure your session, you will want to choose Team Foundation Server\VersionControl.xml for your configuration. Then select a One-way-migration between your on-prem and VSTS.
You'll need to install VS 2012 or at least the Team Explorer.
Edit Coincidentally I had to do this myself so I blogged about the process here

Having two TFS Servers

I'd like to know if there is some way to make a checkin on a TFS server associated to a Work Item that's on another.
Currently some of our developers use a TFS that's hosted offshore containing the source code and we need to install another TFS locally to use Work Items as a project management tool and for the rest of our developers.
Beeing able to associate the two (work items + checkins) would be nice but I presume it's not possible.
Thanks
Apparently it's not possible: http://social.msdn.microsoft.com/Forums/en-US/tfsgeneral/thread/d3ddf813-dc13-48a2-808e-7887ddc4d9b1

TFS 2010 source control backup/restore

Is there a way to backup just the source control component of a team project and restore it into a different TFS server? We setup a TFS 2010 server for RND, but decided to use it's source control manager for a development project. We did this so the developers can learn how to work with it before we use it on a much bigger project. Now, we need to blow away the server since it is a VM for RND. We're going to setup a new TFS server for production. I don't want to lose the source code history.
Yes, you can use the TFS Integration Tools to migrate source with history for one or more Team Projects to another server. It is very easy to use.
TFS Integration Tools Download
I hope this helps
Mike
Use the features built into the product. In Dev10, collections were added so artifacts (including source) would be portable between TFS servers - leverage that. Pilot projects were a key scenario for portable artifacts and a justification for collections.
Dettach the collection from the VM TFS instance. It's available from the collection node of the admin console.
Backup the database from the database you dettached.
Deploy the new real server (non-VM).
Restore that collection database to the sql server used for the production instance.
Using the administration console collections node, attach the collection to the newly deployed TFS server.
Now you have the source available from the prototype period and you have a new production collection available for the new production instance.
BTW, in Dev 11 (you can get build conference CTP or beta soon) TFS upgrades the collection on attach so if you deploy a Dev11 TFS server, you can attach that prototype collection and pull it forward.

Resources