Import/Export Tool - Issues

[pogaz]

In order to test the import/export tool, I created a new, empty directory and put a single, small 1KB text file and, in order to create some history, made an extremely small text change and committed the file. That being said, I now have some questions on the Import/Export tool:

1. When exporting this new directory, why does it "process" commits/transactions that are outside the directory?
2. Why does it take so very long to export out this directory (it never finished - after an hour or more, I canceled the export).
3. I've read that if Obliterate was used it will casue a problem with exporting (which, sorry for saying, seems extremely odd that the export tool can't handle obliterated items); as the "admin" of Vault at my company, I have never used Obliterate, but have no idea if the person before me had used it. Can Vault be checked to see if Obliterate was used?
4. If Obliterate was used at some time in the past and, thus, has resulted in making the Export/Import tool unusable, what are my options for exporting out directories (my goal is to get a large repository down to a more comfortable size)?

Oh - I attempted this "export" on the Vault server and did use "localhost" (as I've read to try). I really hope that our options are not just going to be "use Get to get the files out of the repository" and, thus, lose history.

Paul

[lbauer]

1. When exporting this new directory, why does it "process" commits/transactions that are outside the directory?

It depends on the history of the repository. Perhaps the parent of the folder you are exporting once was a branched or was moved. The Export\Import tool recreates all of the history, not just what you see in the tree at the moment.

2. Why does it take so very long to export out this directory (it never finished - after an hour or more, I canceled the export).

I'd have to review your logs to determine why the Export failed. The export log is in the Vault GUI Client directory along with the Vault Folder Export\Import tool.

We'd like to see a copy of the Vault Server log during the export. It's called sgvault.log and is in %windir%\temp\sgvault on the server machine. Send the logs zipped up to support at sourcegear.com attn: Linda. Include a link to this forum post.

I've read that if Obliterate was used it will cause a problem with exporting (which, sorry for saying, seems extremely odd that the export tool can't handle obliterated items); as the "admin" of Vault at my company, I have never used Obliterate, but have no idea if the person before me had used it. Can Vault be checked to see if Obliterate was used?

You could do a "Show history" from root and filter on the Obliterate action in the Actions tab of History Explorer. Also, we have a SQL Query we can provide that looks for the obliterate transaction in the repository.

4. If Obliterate was used at some time in the past and, thus, has resulted in making the Export/Import tool unusable, what are my options for exporting out directories

You could do a GET Latest and then ADD to a new repository, and keep the hold repository for history, until you don't need it anymore.

[Beth]

We are also discussing this issue in this thread: http://support.sourcegear.com/viewtopic ... 359#p62359.

[pogaz]

Linda and Beth, thank you for your replies--

Linda, thanks for the info - it has helped me to understand a bit more. As Beth mentioned, there is another thread where we are discussing this (see her post for the link). As far as sending the log you mention, I will send upon the next try of an export, if it fails and if it is needed.

Thanks.

[lbauer]

Ok, we'll wait to hear from you.