Proper steps for upgrade

[louismccut]

I am currently using Vault Standard version 5.1.2 on a Windows 2003 Server with SQL Server 2008 R2. I have installed a new Windows 2012 R2 server with SQL server 2014 and have purchased the Vault 7.2.1 upgrade and need some advice on the proper way to migrate to the new server and new version of Vault. Several months ago I tried an upgrade to 6.1 which I totally botched and had to do a lot of recovering from backups so I'd like to get this one right.

One thought I had was to install the 5.1.2 on the new server and restore a backup of the database from the old server, and then do the Vault upgrade on the new server. After that is complete, I'll unbind the client, upgrade the client to 7.2.1 and rebind to the new server. Will 5.1.2 work on Windows Server 2012 R2? Do I need to do an intermediate upgrade from 5.1.2 to 6.1 and then to 7.2.1?

[Beth]

You will want to refer to our Upgrading Guide as you are going along: http://support.sourcegear.com/viewtopic ... 13&t=11648&.

Here is what you should do in your situation.

1) Backup the sgvault and sgmaster databases.
2) Upgrade on the current server to Vault 6.1.0.
3) Backup your databases again with a new backup.
4) Restore your last backup to the new server where the SQL Server is.
5) Install Vault 7.1.2.
6) Have the clients install the Vault 7.1.2 client.
7) Rebind using the instructions from this KB article: http://support.sourcegear.com/viewtopic ... 13&t=18956. In particular, the piece you want from that area is http://support.sourcegear.com/viewtopic ... 403#p68403.

[louismccut]

Following your steps worked perfectly. Only problem I had was when I opened a solution in Visual Studio 2010 it went to the old server and gave a "protocol not supported" error. Workaround was easy. I went offline on the solution, unbound everything, and then bound them to the new server and went back online.

Thanks for distilling it all down to the listed steps.

[Beth]

Happy to hear it. Thanks for the update.