Moving DA databases
We want to move our Discovery Accelerator databases from one SQL server (SQLOLD\Vault) to a new SQL server (SQLNEW\Vault). We don't use Compliance Accelerator at all, just DA. I'm trying to work out a plan for moving them, and am a little confused about the difference between the steps outlined in this article:
https://www.veritas.com/support/en_US/article.TECH51129
OR, just logging in to http://daserver/EVBAAdmin as the vault service account and changing the pointers/DSN's there. Am I confusing two separate configurations? We are JUST moving the DA databases right now, and leaving the actual enterprise vault databases in place where they are.
The part that has me confused is that right off the bat, the "AcceleratorManager.exe.config" has a DSN line that references a db that doesn't exist ("Initial Catalog='EVConfiguration'). We do not have that db in our SQLOLD\Vault instance, so is this file really where the config is coming from for DA?
Under the EVBAAdmin site, there are two DB's configured, one called "CustodianManager" and another that was configured with a custom name related to our organization (call it "Company_Name" for a generic description) and both have DSN's listed that point to them in the correct location on the existing SQL server (SQLOLD\Vault).
To just move the DA databases, can I simply stop EVAMS services, detach and move the DB's, log in to http://daserver/EVBAAdmin as vault service account and update the DSN's/pointers, and restart EVAMS services?
[EDIT]: OK, my bad. We DO have the EVConfiguration database on our SQLOLD\Vault server. Is this db a part of Enterprise Vault, or is it a part of DA? If we are not moving the EV databases yet, can I leave the .config files alone and simply change the database DSN's in http://daserver/EVBAAdmin after moving "CustodianManager" and "Company_Name" customer databases? Or do I need to also move EVConfiguration, and modify the five .config files in the program installation dir?
In answer to your additional question:
As I mentioned, the Configuration DB is a part of DA, and you'll likely want to move that to the new SQL server, particularly if you're retiring it. DA can't work without that database.
I have my own method of moving DA databases which I find to be much simpler. It's basically this:
- Shut down DA services and copy the databases to the new server
- Uninstall and reinstall DA
- Point the browser to the EVBAAdmin page to perform initial configuration. This is the point where it either configures a new config database or attaches to an old one. Enter the new SQL Server name and Config database name and check the 'Existing Database' check box.
- After you restart services, you should see your custodian and customer databases on the page.
- Edit each of the databases (custodian and customer) and change the SQL server name.
You should be good to go after that.