Moving vault service

[brian.chance]

We are moving our vault service from w2k3 r2+IIS6 to w2k8 r2+IIS7 (version 5.1.1.19215). I have read this topic about moving the database: http://support.sourcegear.com/viewtopic.php?t=924.

The document recommends uninstalling the current service then installing the new service. Is it necessary to uninstall the current, or can I just stop the service? I would like a viable, easy rollback plan.

If I do not need to uninstall, can I go ahead and install the new server, configure it, then shut off the old one? Giving us very little to no downtime.

Any help would be appreciated.

Brian

[Beth]

Are you currently on Vault 5.1.1, or will there be an upgrade as well during this?

[brian.chance]

We are currently on 5.1.1.19215 and do not plan any upgrades during the change.

[Beth]

I'm assuming the database will be moving as well. If the database is not moving, then the original install will lose its connection to the database when the second instance is installed.

You don't have to uninstall the old one, but you do have to perform an install of the new one on the new server and not just copy over files. Here is a summary of the steps you would take:
1) Backup sgvault and sgmaster databases. If you are on Vault Pro, you would backup sgdragnet as well.
2) Restore the database backups to the new SQL Server.
3) Install the new Vault server instance. During the install, you will point it to the new SQL Server. It will see its databases there and pick them up.

[brian.chance]

We are not moving our database. So if I just install the new server, the old server loses it connection. If things go bad, do I reinstall the old server?

[Beth]

If things go bad, you can just install the old one again, but it will require an uninstall first.

You "could" try just reconnecting the old one manually using the KB article on moving the SQL Server: http://support.sourcegear.com/viewtopic.php?t=924, but I haven't tried it that way.

[brian.chance]

Sounds like the safe play is to uninstall the first, then install the second.

Does everyone need to check their files first?
How do visual studio projects and solutions react to the change?

Thanks for all you help.

[Beth]

Users don't have to check in their files, but the bindings in VS will change. Since the bindings will change, it's sometimes easier on users if they check in their changes. Then after the new server is up, users can perform a fresh Open from Vault or Open From Source Control (depending on which client they are using). If the layout isn't very binding friendly, then one could instead manually rebind through the Change Bindings (or Change Source Control) option that is under the VS File menu.

Which client is used inside of Visual Studio?

[brian.chance]

We use the enhanced client

[Beth]

Our KB articles on the Enhanced Client may help:
Visual Studio Enhanced Client FAQ
Welcome to the Vault/Fortress Visual Studio Enhanced Client

If your layout looks like the following, then you can just perform an Open From Vault to set up the new bindings. The .sln file is at the top of the hierarchy and project folders are at the same level. The layout on your client machine would match what is in Vault.
$
|---Project Folder
...............|---Solution file.sln
...............|---subfolder
...........................|---Project file.proj (.csproj, .vbproj)
...........................|---project files
...........................|---subfolder
......................................|---more project files
...............|---subfolder2
...........................|---Project file.proj (.csproj, .vbproj)
...........................|---project files
...........................|---subfolder
......................................|---more project files


Other layouts may require you to manually rebind:
1) Go to File - Source Control - Change Source Control or Vault Source Control - Change Vault Bindings depending on which client you are using.
2) Select all lines in the window that opens and click Unbind.
3) Click OK and Save All.
4) Go to File - Vault Source Control - Change Vault Bindings or Vault Source Control - Change Vault Bindings.
5) Select one line and click Bind.
6) When the binding window opens, select the folder that element resides in and click OK.
7) Check that the status for that line is Valid.
8_) Repeat on each line. When all are Valid, click OK.
9) Check in the changes to the .sln and project files.
10) All other users who work on that project need to an Open From Vault or to rebind like you did.