Upgrade Vault 5.1.1 to Vault 7.1

[kha]

6) Since the server changed, if users are using Vault integrated with Visual Studio or SSMS, then you will need to rebind to the new server. See instructions here: http://support.sourcegear.com/viewtopic ... 13&t=18956.

I will use the same server name, will users need to rebind as well?

[Beth]

If users used the server name for binding their projects and the new server has the same server name, then no rebinding is needed. You can check what users are setting for bindings by opening either a .sln or project file (.csproj, .vbproj, etc.) and looking for a url that looks like http://<your Server name or IP>/vaultservice.

[kha]

Thanks, Beth. Since my earlier question is on the 1st page, you might have missed it.

Hi Beth,

I tested the upgrade on a new web server. I am ok with that and want to use it as production, however it's pointing to a test db. The production db is still with version 5.1, can i just run the web application install again and point it to production db then it can upgrade the production database to 7.2?

Or it won't work and I have to uninstall the current web application 7.2 on my new web server, start the whole upgrade process again and point to production database this time?

Thanks!

[Beth]

If you are installing on a machine that has the Vault server installed on it, then you need to uninstall Vault first. Then you can install again and point to the new server.

Also, I see a past question I'm not sure I answered. It is recommended that one upgrade in steps. By that I mean you would install Vault 6.1.0 and then Vault 7.2.1, and if you're going to Vault 8, you would install Vault 8.0.1 last.

[kha]

Thanks, Beth!