Installing Vault on one server, SQL Server on another

[cknox]

We're looking to move our Vault install to a new server, and one of the issues is that we don't want the Vault software on the same server as the SQL Server. Is this a supported configuration where it connects to a SQL instance on another server?

Also, the server we're looking to install it on, already has IIS configured to WSUS. Will this cause issues? Or not because it uses a VaultService virtual directory?

Thanks,

[lbauer]

Yes, having Vault server on one machine and SQL Server on a different machine is a supported configuration.

I don't have enough experience with Windows Server Update Services to know how it might affect the Vault server. In what ways you think it might conflict? Certainly if it is using a lot of system resources it could affect your Vault performance.

To move the Vault server, uninstall it from the current location, leaving the databases in place when prompted. Then reinstall Vault Server on the new machine. Be sure to backup your databases before you start any move.

Since the Vault server and SQL Server are not on the same machine, you will need to choose SQL Server authentication for the Vault connection to SQL Server during the installation process, or if you want to use Windows authentication for SQL Server, use a domain account for the IIS process model during the installation. The installer will use this domain account to create the SQL Server login and database owner role for the Vault databases.

[cknox]

Linda,

Thank you for that reply. I was just noticing that when I was installing a test vault (well I install the vault, then backup and restore the DB from production). We're still trying to upgrade to 5.x from 4.1.4, and with the need to move the server this seems to be the perfect opportunity.

[lbauer]

Let me know if you have additional questions during the move.