Vault VSS migration, without history

[cellardoor]

Hello All,

I m trying to migrate our VSS into Vault, vault is set up in a 64 bit windows server 2003.

I d like to do a clean VSS migration and run vault in 64 bit mode.

I like to know that is there anyway I can keep the 'shared files' and dont import history data? Then run vault in a 64 bit mode?

Thanks a lot.

Dave

[Beth]

If you are performing a hand-off, that isn't supported with 64-bit: Hand-off Sources: http://download.sourcegear.com/misc/vau ... urces.html. Even if you switch IIS to 32-bit mode, you wouldn't be able to go back to 64-bit mode because Visual SourceSafe is 32-bit only.

If you are performing a full import, then you can choose certain folders to not import, but not individual files. You could perform the imports, and then delete the shared items and remake the shares, or use our debug import tool for any shares that don't import properly.

[cellardoor]

Hello, Thanks for the reply.

In my configuration, 64 bit windows server 2003, 32 bit vault server, VSS handoff migration. There seems a bug, when I open the web interface, expand the VSS migrated source files tree, click on a single file, then click on Detail, the vault server hangs and a memory leak occurs. The detail feature works fine with the client, but takes a really long time to load the details.

In my case, there are thousands shared files in our VSS database, almost impossible to re make the shared files manually, can you tell me a bit more about the "debug import tool" ?

Thanks

Dave

[Beth]

Hand-off is not supported on 64-bit IIS. Additional information can be found here: http://download.sourcegear.com/misc/vau ... urces.html.

When you click Details on the version that was handed off, you are asking for all the details of the transaction. The transaction is that entire hand-off. You will find that any versions after that hand-off will work fine with Details, but an entire hand-off is going to take a long time to pull up in details. The web-client is likely to time outthough. There is a details area in the client as well, and in the next version of Vault, you will be able to see the details of your hand-off transaction in the client.

Import is completely different than hand-off. I couldn't tell by your initial post which you were using. Importing is far more involved and takes some preparation. You would want to start with our KB articles on importing if you want to learn more about it:
Tips for a Successful VSS Import: http://support.sourcegear.com/viewtopic.php?t=7
Options for a VSS Import: http://support.sourcegear.com/viewtopic.php?t=6949
Importing a solution or project that uses IDE Integration: http://support.sourcegear.com/viewtopic.php?t=3953
Finding the full VSS Import Tool for Vault 5.0: http://support.sourcegear.com/viewtopic ... 13&t=12240

[cellardoor]

Hello Beth,

Thanks a lot for the reply, it really helps.

My plan is to migrate VSS files with recent file versions and keep the shared files. In this link you mentioned "Options for a VSS Import: viewtopic.php?t=6949", a "special version of the VSS Import Tool.*" can be used to import the shared files.

can you tell more about this "special version of the VSS Import Tool.* please? It seems not included in the VSS import installation.

Also, I like to know that where can I get the "The VSS Archive utility " mentioned in the same post.

Thanks a lot.

Dave

[Beth]

The VSS archive utility installs with the VSS database. Look inside your VSS admin tool.

For the debug import tool, send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread.