Friday, September 14, 2012 3:13 PM
We are planning to create a new TFS Test environment on different set of hardware but using the existing TFS databases from an existing test environment. The new environment will be exactly same as the existing one but on a different server and a different domain. We will be backing up the data from existing environment and then restoring to new.
We have multi-tier deployment, AT, DT, Reporting,Build and WSS 3.0 all on different server.
We went through so many documents available on MSDN and other forums but couldn't get the proper guidance. We are looking for some expert guidance who has actually done similar kind of exercise.
Here are our doubts.
1) What are the sequence of steps we need to follow, basically how do we tell TFS to use existing Databases?
Restore the database first to the new DT and then later run the TFS configuration? But the Advanced config wizzard says either to create new databases or use existing empty database?
Run the TFS Configuration first, which will create the empty database on DT and then overwrite all of these databases while restoring the databases?
2) Could you please arrange the following in proper sequence considering our case?
Run the TFS configuration.
Restore the existing TFS Databases from backup.
Configure the Reports.
Configure the SharePoint (WSS 3.0).
Install the TFS Extension for SharePoint.
Configure the Build Server.
Run the TfsConfig commands to replace the old configuration stored in database.
Other steps we are missing?
Friday, September 14, 2012 3:44 PM
There are two kinds of move for TFS
1. Environment Based
3. Restore Based
In simple words if you are changing your hardware it is Restore Based move and if you are changing domain it is environment based move. If I understand your scenario correctly, you are trying to change both.
I am not sure about the availability of documentation anywhere which helps you to accomplish both the things at one go. Even if you try a single move out of these above types, if gives you sufficient issues. If you try to accomplish both at one go it will be quite complex scenario.
If I have to take a decision in this scenario:
1. I will move my existing TFS setup to new domain by using the steps for environment based move.
2. Once everything is functional in new domain, I will apply restore based move steps to take the TFS to new set of servers by applying steps for restore based move
So in summary you have to first perform all steps for environment based move and then all steps for restore based move. All the steps are well documented for both of these move types at http://msdn.microsoft.com/en-us/library/ms404860(v=vs.80).aspx
How to move server from one domain to other:
How to move server from one hardware to other:
- Edited by Abhijeet Mohite Friday, September 14, 2012 3:45 PM
Friday, September 14, 2012 4:09 PM
We are not moving the TFS environment, we need both environment working, it's kind of copying the data from current environment and creating a new environment.
Monday, September 17, 2012 7:01 AM
- Can you just mention what all data you want to move?
- Does the destination domain to which you are setting up your new environment has the user accounts which are there in your source domain?
Monday, September 17, 2012 2:47 PM
Thanks for helping us on this.
Here are the answers to your question.
We need to setup a complete new environment (multi-tier), so we will need to restore all database right? like TFS_Config, Collection, Reports, SharePoint databses etc.
some of the users are there which are in both domain, but we are not much conerned about users in destination domain, as the new environment will be just used by admin users (few members) who already are users to destination environment.
Tuesday, September 18, 2012 8:58 AM
I got your point and that's the reason I was saying about the two methods of movement.
If you see your response above then you can understand that there is nothing more left in TFS other than these DBs. So if you are setting up a new environment using these DBs then its a complex process specially when you want to set up in another domain. Because there are number of references which are there in configuration which point out to your domain information.
Let me have little more research on this as frankly I have not done this before. Specially across domains.
- Marked As Answer by Cathy KongMicrosoft Contingent Staff, Moderator Monday, September 24, 2012 2:06 AM