Moving just the vault server, but using the same database

jerwin · Post by **jerwin** » Sat Mar 15, 2008 10:15 am

We would like to move our vaut service to a different server but continue using the same SQL Server instance/databases from the new server. Is there a specific way to go about this?

thanks,

JE

Beth · Post by **Beth** » Mon Mar 17, 2008 7:51 am

First, make sure you have a current backup of your database. Then just uninstall where your current Vault server is, but tell it to keep the database, then install it on the other server. During the install, it will ask you where your SQL server is and ask if you want to keep the current database.

jerwin · Post by **jerwin** » Mon Mar 17, 2008 7:55 am

Beth,

Thanks for the prompt response. When you say "make sure you have a current backup", do you mean a backup through the vault admin web interface, or a SQL backup? I ask because I received errors trying to back up through the vault admin web interface over the weekend.

If I do need to backup the database through the vault admin web interface, I'll need to start another thread to troubleshoot the issues I ran into in order to do the backup.

regards,

JE

Beth · Post by **Beth** » Mon Mar 17, 2008 8:40 am

All Vault does is run a SQL backup anyway. Either is fine.

For performing a SQL backup, if you are on a Vault version prior to 4.x, you only need to back up the sgvault database. If you are on 4.x or later, you need to back up the sgvault and sgmaster databases.

We should looking into why your Vault backup gives you errors either way. Feel free to post that error when it's convenient for you.

jerwin · Post by **jerwin** » Mon Mar 17, 2008 2:08 pm

Beth,

Thanks for the clarification. Since this database gets backed up every night, I'll probably just schedule the move to right after the nightly backup. I'll just shut down IIS with vault installed about 15 minutes prior to the backup.

I shouldn't run into any issues if there are files checked out in various repositories before the backup as long as I'm still pointing at the same database after the move, right?

Is the .svgbak file created by the backup utiliity in the vault admin web interface really a sqlbackup file that somehow combines the sgvault.bak and sgmaster.bak files?

regards,

JE

Beth · Post by **Beth** » Mon Mar 17, 2008 5:31 pm

The sgvbak is just a SQL backup, but it will make one for sgvault and sgmaster when the backup is ran from the Vault admin web page.

I would expect checked out files to be fine. Some have users check in their files as a just-in-case measure. Vault will still know what's checked out.