Server Migration roadmap?

[swautier]

Hi All,

I'm a one-man band hosting Visual Studio dev (a bit of 2003, but mostly 2005 and 2008) and Sql Server 2005/Vault Server 4.1.3 on the same box.
I just set up a brand new server machine (W2008 Foundation/ Sql Server 2008 R2) and want to move my Vault Server + DB to the new machine.

Here's the move/transition I' d like to do:

- Moving Vault Server to another machine.
- In the same time: Upgrading from Vault 4.1.3 to 5.1
- Moving the DB from Sql Server 2005 Express 32 bits to Sql Server 2008 R2 Express 64-bits
- Switch from Classic client to Enhanced client
- Update bindings in my Visual Studio solutions
- (Oh, I also plan to switch from VSS style to CVS style and wonder about the impact on VS integration but this is another story and I still need to do my homework about that)

I have found a couple of KB articles about some of the steps.
However, I'd be grateful if someone could advice about the best upgrade/migration path and potential pitfalls.

TIA,

[lbauer]

Moving Vault Server to another machine.
- In the same time: Upgrading from Vault 4.1.3 to 5.1
- Moving the DB from Sql Server 2005 Express 32 bits to Sql Server 2008 R2 Express 64-bits
- Switch from Classic client to Enhanced client
- Update bindings in my Visual Studio solutions
- (Oh, I also plan to switch from VSS style to CVS style and wonder about the impact on VS integration but this is another story and I still need to do my homework about that)

Some suggested steps:

First, backup your databases, sgvault and sgmaster. Restore a copy of the databases to the new SQL Server machine. Then install Vault 5.1 on the new server machine. Point it at the database location and the installer will upgrade your databases.

Another option is to upgrade on the machine where you are now, then restore the upgraded databases to the new SQL Server installation. The key point is to always have the databases in place before installing Vault. The installer will create the necessary database user and set permissions in the database and on the server machine.

To rebind you projects, you can open each project in Visual Studio, select File->Source Control->Change source control. Unbind the project. Save all. I'd suggested closing Visual Studio, then the project again. Now the project should not be bound. Under Tools->Options->Source Control->Plugin selection, choose the Enhanced client. Under File->Vault Source control, choose Change Vault Bindings and rebind the project.

Another option would be to try the Rebind projects function in the Vault Admin Web Client. This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Rebind Projects. This removes Classic style bindings and replaces them with Enhanced Client bindings.

Regarding the switch to CVS mode, that should just be a matter of changing your settings in client options. Note that all transactions will be placed in the pending change set and must be committed manually.

[swautier]

Linda,

As always, your answer is outstanding. I followed your procedure and everything worked like a charm.
(Well, except for a small problem vbscript.dll registration problem during installation of the client, but I easily found the answer on the forum).

Thank you very much. Your help is much appreciated.

[lbauer]

Thanks for the update, and thanks for your kind words.

Let me know if we can be of assistance in the future.