How to modify the configuration files after moving the Compliance Accelerator or Discovery Accelerator databases to different SQL server
How to modify the configuration files after moving the Compliance Accelerator or Discovery Accelerator databases from a Microsoft SQL Server / Microsoft SQL Server instance to another Microsoft SQL Server / Microsoft SQL Server instance of a different name or a different TCP Port.
- A configuration database. CA and DA require their own configuration database. CA cannot use a DA configuration database and DA cannot use a CA configuration database.
- At least one customer database. Both CA and DA can have multiple customer databases, but at least one is required for the environment.
- DA can also have a special customer database knows as a Custodian Manager database.
The names of the five files for CA are:
- JournalTask.exe.config (for Microsoft Exchange journal archiving)
- EVLotusDominoJournalTask.exe.config (for Lotus Domino journal archiving)
- Discovery Accelerator EV event log errors 34 and 429 after SQL database migration
- Journaling Stops when using the Journal Connector and how to properly configure the Journal Connector.
- How to move Discovery Accelerator and Analytics databases
- How to move Compliance Accelerator (CA) or Discovery Accelerator (DA) databases.
- Enterprise Vault Compatibility List
- Method 1 is to uninstall and re-install CA / DA.
- Method 2 is to manually edit the appropriate files on the EV / CA / DA servers.
Starting with CA and DA 12.0.0, SQL Always-On is supported. A CA or DA 11.0.x installation must first be upgraded to version 12.0.0 or greater before the Accelerator databases can be moved to a SQL Always-On installation and configured for Always-On support. The basic steps to configure a database for Always-On are to (a) backup the database, (b) add the database to the AlwaysOn High Availability | Availability Groups | Availability Databases in the SQL Server Management Studio, than (c) edit the relevant Accelerator database connections; this should be performed by the onsite SQL team. Once the upgrade is complete and the databases have been configured for Always-On support, follow the steps below and wherever a database connection is mentioned, replace the appropriate SQL server name or IP address with the Always-On listener name or IP address.
Method 1: Uninstall and re-install CA / DA
- Log onto the CA / DA server as the Vault Service Account (VSA).
- Stop the Enterprise Vault Accelerator Manager Service (EVAMS) on the CA / DA server.
- On the SQL Server hosting the CA / DA databases, backup the CA / DA configuration and all customer databases (including the Custodian Manager customer database if it exists in DA) using an account that has sufficient permissions to backup those databases (the VSA should have sufficient permissions).
- Move to or restore the databases on the new SQL Server or SQL Instance. Note that this step can be skipped if just changing the TCP Port number used by SQL Server.
- On the CA / DA server, open the AcceleratorManager.exe.config file using a text editor (ex., Notepad) and note the name of the CA / DA configuration database (ex., EVConfiguration) before closing the editor.
- Uninstall CA / DA.
- When the uninstall has completed, check for the installation folder presence on the server and either rename or delete it if it still exists.
- Also, check the registry for the presence of the CA or DA registry keys in the HKEY_LOCAL_MACHINE\Software\Wow6432Node\KVS key and either rename or delete it and all of its sub-keys.
- Restart the server to clear it's memory of any left over information of the CA / DA installation.
- When the server restart completes, log in as the VSA.
- Install CA / DA.
- After the CA / DA installation of the binary files completes, access the EVBAAdmin site using Internet Explorer.
- The EVBAAdmin site will first display the page to create a new or use an existing configuration database. Choose the option to use the existing configuration database by
- Entering the name of the new SQL Server / SQL Instance / SQL Server TCP Port (ex., for SQL Server named EVSQL using an instance named CADBs and TCP Port number 14554, the SQL server name field entry would be EVSQL\CADBs,1455)
- Enter the name of the configuration database noted in Step 5.
- Click on the Use Existing Database: check box to place a check mark in it.
- Click the OK button
- When prompted, restart EVAMS.
- After EVAMS has completed its restart, click the OK button in the EVBAAdmin page to open the EVBAAdmin site.
- For each customer listed in the left panel:
- Right click on the customer name.
- Select the Properties option to access the customer properties page.
- In the customer properties page that will appear:
- Change the name of the SQL Server \ instance to be the new SQL Server \ instance \ Port name / number.
- Click the OK button to save the change.
- When all customers have had their SQL Server information changed, close the web browser.
- Restart EVAMS again.
- Log onto the EV server as the Vault Service Account (VSA).
- Stop all Journal Archiving tasks on all EV Journaling Archiving servers.
- Uninstall the CA Journaling Connector.
- Re-install the CA Journaling Connector. When prompted, enter the name \ instance : TCP Port number where the CA configuration database is hosted and enter the CA configuration database name.
- After the CA Journaling Connector re-installation has finished successfully, start the EV Journal Archiving task(s).
Method 2: Manually edit the appropriate files on the EV / CA / DA servers
To configure the Accelerator application to start using its databases on the new Microsoft SQL Server / Microsoft SQL Server instance, edit the files noted above on the Accelerator server prior to starting the Enterprise Vault Accelerator Manager service (EVAMS) on that server using the following steps:
value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" />
<add key="DSNConfiguration" value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" />
UPDATE tblCustomer SET Server = 'New_SQL_NetBiosName
' WHERE Server = 'Old_ SQL_NetBiosName
If the Journal Connector is installed on an Enterprise Vault Server that is running a Journal Task, modify the JournalTask.exe.config or EVLotusDominoJournalTask.exe.config file as follows:
<add key="DSNConfiguration" value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=500" />
<add key="DirectoryDSN" value="packet size=4096;integrated security=SSPI;data source=SQLServer;persist security info=False;initial catalog=EnterpriseVaultDirectory" />
NOTE 1: If Microsoft SQL Server instances are used, the Microsoft SQL Server instance will be identified in each line as "SQLServer\InstanceName', where 'InstanceName' is the name of the Microsoft SQL Server instance. Also, if a specific port has already been configured for the Microsoft SQL Server access, that port number will be noted with a comma followed by the port number after the SQL Server or SQL Server instance name (i.e., 'SQLServer,1600' or 'SQLServer\SQLInstance,1600').
NOTE 2: The following line is used by Compliance Accelerator 5.x and does not need to be modified for Compliance Accelerator 6 or greater
<add key='DSN" value="server=EVServer;Integrated Security=true;Initial Catalog=evaccelerator;Connection Timeout=500" />
NOTE 3: There should only be 2 lines containing the Microsoft SQL server name or Microsoft SQL Server instance name in the file which need to be modified.
If the databases have been moved to a newer version of SQL Server, the database compatibility level should be changed to match the SQL Server version. For example. if the databases have been moved from a SQL Server 2000 machine to a SQL Server 2005 machine, the compatibility level should be changed from "SQL Server 2000 (80)" to "SQL Server 2005 (90)". Likewise, if the databases have been moved to a SQL Server 2008 machine, the compatibility level should be changed to "SQL Server 2008 (100)". The compatibility level can be found and changed in the Properties of the database, on the Options page.
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):