Question

I've been testing a VSS to TFS migration for my job. The test server that we have tfs installed on has the drives partitioned. The system stays on C drive and we don't touch that drive. We have the E drive for our applications.

I wrote the configuration file so the migration would run and it runs fine. But for some reason it's migrating the data to the C drive. The C drive only has enough space so the system will run fine. Here is what my config file looks like:

<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
 <Source name="VSS">
      <VSSDatabase name="E:\TFS\projectfolder\project"></VSSDatabase>

 </Source>
 <ProjectMap>
      <Project source="$/" Destination="$/Test-Location"></Project>
 </ProjectMap>
</ConverterSpecificSetting>
<Settings>
<TeamFoundationServer name="servername" port="port" protocol="http" collection="tfs/DefaultCollection" />
 <Output file="Migration.xml" />
</Settings>
</SourceControlConverter>

Why is VSSconverter migrating my files to the C drive? I've researched this for a week or more and cannot find anything that is helping me out. Do I need to specify the E:\ in the destination? Could this be caused by how the TFS server was configured? Any help would be appreciated.

Was it helpful?

Solution

I'm not sure which data you are talking about. TFS stores all data in the SQL database unlike VSS that stores the source on the file system. Do you store your TFS database file on C: drive on that box by any chance?

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top