Moving Vault from one SQL Server to Another One

[smoosavizadeh]

This is a first for me. The vault server product (3.1.5) is installed on a server (2000) that is about to die, and I need to move it to another server (2003) running SQL Server 2000. The only installation files that I have is for Vault Server 3.1.7, so I went ahead and installed it on the new server, and everything seems to be okay, except I would like to migrate my old repositories from the bad server into the new installation of the Vault server. Any document or link or suggestion is greatly appreciated.

Thanks.

[lbauer]

It's best to restore the database to the new SQL Server first, then install Vaultl, so I'd suggest uninstalling and following the instructions here:

http://support.sourcegear.com/viewtopic.php?t=228

[smoosavizadeh]

lbauer,

I followed the instrux, and I get the following:

OK
Configuring your new Vault Installation
Checking for IIS Version...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing Vault database...Found.
Asking for database's fate...Keep existing.
Upgrading the existing Vault database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Ensuring that sgvaultuser has access to the Vault database... Grant database access to sgvaultuser...OK
Upgrading SourceGear Vault database schema...OK
Upgrading SourceGear Vault stored procedures...Invalid column name 'userid'.
Invalid column name 'labeldate'.
Invalid column name 'userid'.
Invalid column name 'label'.
Invalid column name 'rootpath'.
Invalid column name 'numchanges'.
Invalid column name 'lastchange'.
Invalid column name 'comment'.
Invalid column name 'userid'.
Invalid column name 'labeldate'.
Invalid column name 'userid'.
Invalid column name 'label'.
Invalid column name 'rootpath'.
Invalid column name 'numchanges'.
Invalid column name 'lastchange'.
Invalid column name 'comment'.
Invalid column name 'labeldate'.
Invalid column name 'userid'.
Invalid column name 'label'.
Invalid column name 'rootpath'.
Invalid column name 'numchanges'.
Invalid column name 'lastchange'.
Invalid column name 'comment'.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

[lbauer]

It looks like there's a problem upgrading the database.

I'd suggest uninstalling Vault Server, restoring another backup of your 3.1.5 database, then installing Vault Server 3.1.5. You can download it here:

http://download-us.sourcegear.com/files ... _3_1_5.msi

If that works you could try upgrading to 3.1.9, or just leave the 3.1.5 installation as is until you want to upgrade. We may need to do some diagnostics and run some scripts on the database if you can't install Vault Server or upgrade it.

[honaka]

So I read through the forum and my question is do I need to reinstall Vault if I'm only moving my SQL server? Can I just edit the ConnectString key in the Web.Config?

I have Vault server 4.1.1 installed on a dedicated VM image and connecting to a physical database server. I just want to move Vault database (sgvault/sgmaster) to my second database server (identifically configured). Shouldn't I be able to backup and restore to the 2nd server and update the ConnectString key to point to it? But what I've read all indicates I have to reinstall to point to my DB??? I'm hoping I don't have to reinstall to simply point to a different DB server.

The reason for my question is that my 1st DB server is used by one of my teams and they need to upgrade to SQL2008 (which I checked and I see someone running V4 on it just fine). Since Vault is used by my other teams, I need to minimize the downtime as well as to avoid unforeseen problems after the upgrade which could further impact the downtime. So this past weekend I was able to schedule a short downtime so my operators can perform P2V (Physical to Virtual conversion) on that machine. This allowed us to get the SQL server back online while we could try to perform the upgrade at our own timeline using the VM copy....so we thought. Our current version of VMware only supports 4-way processors and our DB server is 8-way so it kept displaying the 'blue screen of death'. Our next workaround is to move our Vault repositories to our 2nd DB server (identifically configured) that is used by my other teams (which they don't need to upgrade to SQL2008 anytime soon) so Vault will be available to all my developers while we upgrade our 1st DB server.

I'm hoping someone at SourceGear is going to tell me what I want to hear...that is backup and restore to the 2nd DB server and then simply edit the Web.Config to point to it.

Regards

[lbauer]

It isn't enough to just modify the connection string in the web.config file. When you move the SQL Server database to a different machine, the Vault database user does not have a login on the new SQL Server machine. So you need to delete the database user, and re-create it. When you uninstall and reinstall the Vault server, the installation program does this for you.

However, it is possible to do this manually. This KB article has the scripts and steps that you need if you are moving the database, but leaving the Vault server in place.

http://support.sourcegear.com/viewtopic.php?t=924