Version mismatch protection for Vault v3 and beyond

Roman · Post by **Roman** » Sat Nov 20, 2004 12:49 pm

Maybe you have this feature on your list, but if not maybe it is not too late to add it.

We started using Vault starting v2.05. When 2.06 was released, I told everyone to update their client version to 2.06, but a couple of people did not do it on their systems. Fortunately there were no interoperability problems that affected us, BUT IT WOULD BE GREAT IF A VERSION OF THE CLIENT DIFFERS FROM THAT OF SERVER, A CLIENT WOULD NOT CONNECT TO THE DATABASE, and instead pop up a message explaining that there is a mismatch in versions, and a client should be either upgraded (or potentially downgraded, if administrator had a reason to stick with the older version).

I think adding this feature will help the customers, and will protect Source Gear from complains because of the customer data corruption caused by version mismatch.

Post by **jclausius** » Sat Nov 20, 2004 9:35 pm

Roman:

Vault already does this

We've strived very hard to ensure interoperability between the same major version of Vault clients / servers. For example, a Vault 2.0.1 client can work with a Vault 2.0.6 server, without causing any corruption. The only thing "dot releases" bring are bug fixes. So, not upgrading between these incremental releases would NOT cause any type of corruption.

However, if you would try to connect a Vault 1.2.1 client to a Vault 2.0.6 server, the connection would be refused.

The same will be with Vault 3.0. Only Vault 3.0 clients will be able to connect to a Vault 3.0 server. Once the server has been upgraded, all clients will need to be upgraded to Vault 3.0

GregM · Post by **GregM** » Sat Nov 20, 2004 10:46 pm

Will Vault 3.0 clients be able to talk to Vault 2.x servers? That way we can upgrade all the clients first, and then upgrade the server.

ericsink · Post by **ericsink** » Sun Nov 21, 2004 11:34 am

GregM wrote:Will Vault 3.0 clients be able to talk to Vault 2.x servers? That way we can upgrade all the clients first, and then upgrade the server.

Sorry, no.

Everything will have to be upgraded simultaneously.

Post by **jeremy_sg** » Mon Nov 22, 2004 10:36 am

Another thing to note with this is that after version 3.0, the error message stating that the server and client are incompatible versions will include a link to dowload the appropriate version from the server. In the next release after 3.0, the upgrade process will look like this:

Upgrade server from 3.0 to 4.0. Every user who still has a 3.0 client installed on their system will get the error message saying that the versions are incompatible, with a link to download the 4.0 client from the Vault web server. After upgrading, they will be able to connect to the 4.0 server.