Merging Vault Databases/Data

[Scottie]

Our Company is currently looking at taking on a new developer and taking on one of his major applications.
He has been using a Fortress Single User licence for Source Code Control and as far as I’m aware he hasn’t been using any of the other features of Fortress.
We have a Vault Server with a 8 full user licences and a couple of repositories.
Ideally we would like to be able to take the data from his Source Control and import/merge it into our Vault system under a new repository, and of course purchase a new licence for him.
Is there any way that this can be done easily?
Failing that I’m assuming our only other option is to add his files to our server as a new project and abandon all his old check-in comments and history. We’re certainly open to other options if there are any.
Extra Info:
We are running version 4.1.3.18336 of Vault Server
I believe the single user Fortress version is the current version.
I believe we still have valid Gold Support even though it doesn’t exist anymore.

[lbauer]

You should be able to import his data, including history.

Both Vault and Fortress have a folder export/import tool. It is located in the Fortress or Vault GUI client directory and is called VaultFolderExportImport.exe. Documentation is in the ExportImport.chm in the same directory.

When you export his project folder from his Fortress repository, the Export\Import tool creates a file called export.vfe.

Copy this file to your system, and use the VaultFolderExportImport.exe from your Vault Client installation to import the export.vfe file into your Vault repository.

Let me know if you have additional questions.

NOTE: if the user has previously obliterated files or folders from his project, export\import may not work, since chunks of history have been removed.

[Scottie]

ahhh, its simple when you know how.
Thanks for the response Linda.

[lbauer]

its simple when you know how

And a total mystery when you don't.

Now you know.

[darkvader]

This is my scenario:

Do to the massive time the VSS import tool takes to import into Vault (15 days for 25GB VSS DB), I end up creating a repository 1 just for the import and a repository 2 with the same folders and files structure as the VSS DB being imported into repository 1, to continue development while the import tool finished.

Now what I will like to do is to use the Vault export tool to export the Repository 2 and import into Repository 1 in a way that basically history and changes from repository 2 get appended to folders and files on repository 1 seamless like I had been developing on Repository 1 all the time.

Is this possible?

Is hard to explain, I hope you understand what I'm trying to do.

Thanks in advance for any help.

[lbauer]

It's not possible to merge history this way.

However, you could:

1) Just keep two different repositories, one for the VSS imported items so you can view and get from older history, and continue development in the newer repository

2) Check out projects from the VSS import repository and in the working folders, replace the files with the latest version from the new repository. You'll lose the last few weeks of history, but the rest will be in one place.

[darkvader]

We already consider the suggested alternative, but since it won't append the history of development during the import we had not decide yet to do it. Will see what happen, but at least you answer the question and now we know that what we were hoping to do is not an option.

Thanks for the reply anyway.

[lbauer]

Let us know if you have further questions.

[darkvader]

This question may not belong to this topic but since we already have a conversation going I will ask you here.

We started the import process and the import got to a point now where it don't seem to be moving foward at all. THe progress bar had been on the same spot for about 8 hrs and the Estimated Time Remaining counter had not change either.

The INformation on the screen said that is Verifying Label: XXXX and Correcting label differences for label [XXX].

IS this normal?

I had attached a screenshot.

[darkvader]

Well finally the estimated time remaining move after almost a day. At least I know that the program is not hang, but I wonder what this part of the import is doing that is so slooooooooooow.

Before this part, the import was moving a lot faster.

Here is the latest screenshot.

[lbauer]

The INformation on the screen said that is Verifying Label: XXXX and Correcting label differences for label [XXX].

Importing Labels can take a very long time.