Migrate from VSS 6.0d on Windows Server 2003R2 to Vault Standard on Windows Server 2016, 64 bit

[enicolson]

I am wanting to move from, and decommission, a windows server 2003 R2 machine with VSS 6.0d (build 9848) and SourceOffSite 4.2.

I want to move to Windows server 2016, 64 bit, running Vault 10 Standard.

I understand I can create new repos with Get, import the VSS repo, or use Handoff.

The developers want to keep the history, so either import or handoff should be used.

In my reading it sounds like handoff requires VSS to be running on a 32 bit machine, is that correct?

I need to decommission the Windows server 2003 machine, so to use handoff it sounds like I should move the VSS database to a new 32bit server first. Is that correct?

Really I would prefer to import, however I understand for import I need to use VSS 6.0c. Is it possible to use the data files created with VSS 6.0d with VSS 6.0c, or do I first need to move to a later version of VSS like the 2005 version?

A lot of questions here. Just looking for a direction to head in next.

[Tonya]

Hello,

Yes, you are correct. Since VSS is a 32-bit only application, Vault's VSS connectivity features are only available when the 32-bit Vault Server is installed. You may have to configure IIS 7 to allow 32-bit applications.

Yes, you should move your VSS database before performing the Handoff feature.

On the machine with the VSS database, you should be running the English language version of SourceSafe 6.0c, plus the following hotfix that is available from Microsoft. VSS 6.0d is not supported and I don't believe you can transition backwards to 6.0c. I would suggest upgrading to VSS 2005.

I have copied below a link a knowledge base article we have available in regards to Tips for performing a Handoff:

viewtopic.php?f=13&t=11526

Along with a link to our migration guide:

http://sourcegear.com/vault/documentati ... yGuide.pdf

Please let us know if you have any additional questions.

Thanks,

Tonya

[enicolson]

Ok looks like I need VSS 2005. I found posts saying that VSS 2005 can run on Windows10 64 bit with WOW and the VSS 2005 update.

I think the following install procedure will work:
Install windows feature .NET framework 3.5 (including .NET 2.0 and 3.0)
Be sure that WOW is enabled if a 64 bit OS
Install VSS 2005
Install VSS 2005 update: vs80-kb943847-x86-intl.exe

References:
https://support.microsoft.com/en-ph/hel ... 005-update
https://answers.microsoft.com/en-us/win ... fb9a3c1f9a
https://social.msdn.microsoft.com/Forum ... ioncontrol

Question: For either Import or handoff, is it ok to have VSS and Vault on the same server? I think I saw a note saying they should be different machine.

[Tonya]

Hello again,

We actually recommend that the VSS software and database be on the same machine as the Vault server.

Thanks,

Tonya

[enicolson]

Ok, I followed my procedure with the install of VSS 2005 on Windows server 2016 and there were no problems. I have brought the smallest VSS database over and analyze found no problems.

Next I have to decide between Import or handoff. I will need to do some more reading.

[Tonya]

Thank you for the update. The VSS to Vault Migration Guide may help you decide on which import to use:

http://sourcegear.com/vault/documentati ... yGuide.pdf

Tonya