How to modify the configuration files after moving the Symantec Compliance Accelerator (tm) or Symantec Discovery Accelerator (tm) databases from a Microsoft SQL Server / Microsoft SQL Server instance to another Microsoft SQL Server / Microsoft SQL Server instance of a different name.

Document ID: 287894
http://support.veritas.com/docs/287894

E-Mail this document to a colleague

Details:

Overview:

When the databases for Symantec Compliance Accelerator (tm) 6.x / 7.x / 2007.x / 8.x or Symantec Discovery Accelerator (tm) 6.x / 7.x / 2007.x / 8.x need to be moved from a Microsoft SQL Server 2000/2005 machine / Microsoft SQL Server instance to another Microsoft SQL Server 2000/2005 machine / Microsoft SQL Server instance of a different name, there are five files on the Accelerator server that need to be modified to replace the name of the original Microsoft SQL Server / Microsoft SQL Server instance with the name of the new Microsoft SQL Server / Microsoft SQL Server instance. These files are located in the installation folder for the Accelerator application (default location is C:\Program Files\KVS\Business Accelerator - Compliance or C:\Program Files\Enterprise Vault Business Accelerator ). The names of the five files are:

AcceleratorManager.exe.config
AcceleratorManagerConsole.exe.config
AcceleratorService.exe.config
ADSynchroniser.exe.config
ImportExport.exe.config

A sixth file must be modified if the Journal Connector is installed on an Enterprise Vault server that is running at least one Journal Task. This file is located on the Enterprise Vault server that has the Journal Connector installed and is located in the Enterprise Vault installation folder (default location is C:\Program Files\Enterprise Vault). This file name is:

JournalTask.exe.config

Solution:

To configure the Accelerator application to start using its databases on the new Microsoft SQL Server / Microsoft SQL Server instance, configure the five files on the Accelerator server prior to starting the Enterprise Vault Accelerator Manager service on that server. To configure the five files, follow these steps:

1. Open Windows Explorer on the server where the Accelerator application is installed.

2. Go to the Compliance Accelerator / Discovery Accelerator installation folder.

3. Open the AcceleratorManager.exe.config file for editing.

4. Find the line with the old Microsoft SQL Server name / Microsoft SQL Server instance name.

For files AcceleratorManager.exe.config, AcceleratorManagerConsole.exe.config, AcceleratorService.exe.config and ADSynchroniser.exe.config, the line is -

<add value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" key="DSNConfiguration" />

For file ImportExport.exe.config, the line is -

<add key="DSNConfiguration" value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" />

where 'SQLServer' is the name of the old Microsoft SQL Server and 'EVConfigurationDatabaseName' is the name of the configuration database for the Accelerator application (default name is EVAccelerator).

NOTE: 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.

5. Replace the old Microsoft SQL Server name / Microsoft SQL Server instance name with the new Microsoft SQL Server name / Microsoft SQL Server instance name.

NOTE: There should only be 1 line containing the Microsoft SQL Server name / Microsoft SQL Server instance in each file.

6. Save and close the file.

7. Repeat Sub-steps 1. through 6. for the AcceleratorManagerConsole.exe.config, AcceleratorService.exe.config, ADSynchroniser.exe.config and ImportExport.exe.config files.

8. Modify the following in the CA or DA Configuration database. Replace the original SQL_NetBios server name with the new SQL_NetBios server name.

Table Name	Column	Value
tblCustomer	Server	New_SQL_NetBiosName

Open SQL Query Analyzer and run the following queries separately against the Configuration database. Replace bold items with the correct server name values:

UPDATE tblCustomer SET Server = 'New_SQL_NetBiosName' WHERE Server = 'Old_SQL_NetBiosName'

If the Journal Connector is installed on an Exchange Server that is running a Journal Task, modify the JournalTask.exe.config file as follows:

1. Open Windows Explorer on each Enterprise Vault server where the Journal Connector is installed.

2. Go to the Enterprise Vault installation folder.

3. Open the JournalTask.exe.config file for editing.

4. Find the two lines with the old Microsoft SQL Server name / Microsoft SQL Server instance name.

The lines are -

<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.

NOTE 2: The following line is used by Compliance Accelerator 5.x and does not need to be modified for Compliance Accelerator 6.x / 7.x / 2007.x / 8.x

<add key='DSN" value="server=EVServer;Integrated Security=true;Initial Catalog=evaccelerator;Connecction Timeout=500" />

5. Replace the old Microsoft SQL server name / Microsoft SQL Server instance name with the new Microsoft SQL server name / Microsoft SQL Server instance name.

NOTE: 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.

6. Save and close the file.

7. Restart all Journal Tasks on the Enterprise Vault server.

Products Applied:
Enterprise Vault Compliance Accelerator 2007 7.5, 2007 7.5 SP1, 2007 7.5 SP2, 2007 7.5 SP3, 2007 7.5 SP4, 2007 7.5 SP5, 2007 7.5 SP6, 6.0, 6.0 SP1, 6.0 SP2, 6.0 SP3, 6.0 SP4, 7.0, 7.0 SP1, 7.0 SP2, 7.0 SP3, 7.0 SP4, 7.0 SP5, 8.0, 8.0 SP1, 8.0 SP2, 8.0 SP3
Enterprise Vault Discovery Accelerator 2007 7.5, 2007 7.5 SP1, 2007 7.5 SP2, 2007 7.5 SP3, 2007 7.5 SP4, 2007 7.5 SP5, 2007 7.5 SP6, 6.0, 6.0 SP1, 6.0 SP2, 6.0 SP3, 7.0, 7.0 SP1, 7.0 SP2, 7.0 SP3, 7.0 SP4, 7.0 SP5, 8.0, 8.0 SP1, 8.0 SP2, 8.0 SP3

Last Updated: November 12 2009 11:20 PM GMT
Expires on: 365 days from publish date

Subscribe to receive critical updates about this document

Subjects:
Enterprise Vault Compliance Accelerator
   Database: Configuration, Setup
   Installation: Config Files
   Service: Configuration
Enterprise Vault Discovery Accelerator
   Database: Configuration, Setup
   Installation: Config Files
   Service: Configuration

Languages:
English (US)

Operating Systems:
Windows 2000

Advanced Server SP4, Datacenter Server SP4, Server SP4

Windows Server 2003

DataCenter, DataCenter SP1, DataCenter SP2, Enterprise SP2, Enterprise Server, Enterprise ServerSP1, R2, Standard Server, Standard Server SP1, Standard Server SP2

Windows Server 2008

DataCenter (x86-32bit), Enterprise (x86-32bit), Standard (x86-32bit)

Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.