How to move Compliance Accelerator (CA) or Discovery Accelerator (DA) to a new server

Description

This Article describes the steps to move Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) to a new server.

It is very important to use the same existing CA or DA Configuration database after moving CA or DA to a new server. The Configuration database maintains key settings used to fine tune the operations of CA or DA Searches, Exports, etc. for each Customer. After the changes below have been made, the Customer database(s) will automatically be available.

It is also critical to install the same versions of CA/DA and EV on the new CA/DA server as are present on the original CA/DA server. Installing a newer version of the EV binaries or EV API can cause issues with the Enterprise Vault Accelerator Manager Service start-up and with accessing the EVBAAdmin administration website in the steps below. In such cases, Event ID 40966 may be logged in the EV Event Logs on the Accelerator server referencing one or more assembly errors, such as the following:

Could not load file or assembly 'KVS.EnterpriseVault.Interop.DirectoryConnection, Version=11.0.1.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Diagnostic:
Type: System.IO.FileLoadException

If installing an Update Release version, such as 14.1.1, the base version must first be installed before the Update Release version is installed.  Failure to install the point release, such as 14.1.0, can cause an Event ID 372 error referencing one of more missing DLL files such as the following:

Error When Starting the Accelerator Service. System.IO.FileNotFoundException: Could not load file or assembly 'KVS.Accelerator.Sampling, Version=12.5.0.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c' or one of its dependencies. The system cannot find the file specified.
File name: 'KVS.Accelerator.Sampling, Version=12.5.0.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c'
   at KVS.Accelerator.Server.CommonStarter.StartApplicationThreads(CustomerType custType)
   at KVS.Accelerator.Server.CommonStarter.Start()
   at KVS.Accelerator.Server.AcceleratorServiceProcessor.MainThread()

Here are the steps.

1. Install prerequisite software on the new server as described in the Installing and Configuring Guide (See Related Articles below).

Notes:

1.1. Be sure the following Roles and Features are installed on the server:

- Go to Server Manager.
- Click on Add roles and features.
-- Before you begin: Next.
-- Installation Type: Select installation type: Role-based or feature-based installation | Next.
-- Server Selection: Select a server from the server pool | Select the Accelerator Server | Next.
-- Server Roles: Roles | Web Server (IIS) | Add features that are required for Web Server (IIS) | Select Include management tools (if applicable) | Add Features | Next.
-- Features: Select all .NET Framework options | Select Include management tools (if applicable) for any pop-up panes.
--- Expand .NET Framework 3.X Features | Select all features.
--- Expand .NET Framework 4.X Features | Select all features.
--- Select IIS Hostable Web Core.
--- Next.
-- Web Server Role (IIS): Next.
-- Web Server Role (IIS) | Role Services: 
--- Common HTTP Features: Default Document, Directory Browsing, HTTP Errors, Static Content, HTTP Redirection.
--- Health and Diagnostics: HTTP Logging, Logging Tools, Request Monitor, Tracing.
--- Performance: Static Content Compression.
--- Security: Request Filtering, Basic Authentication, IP and Domain Restrictions, URL Authorization, Windows Authentication.
--- Application Development: .NET Extensibility 3.X, .NET Extensibility 4.X, ASP, ASP.NET 3.X, ASP.NET 4.X, CGI, ISAPI Extensions, ISAPI Filters.
--- Management Tools | IIS Management Console.
--- Management Tools | IIS 6 Management Compatibility | Select all.
--- Management Tools | IIS Management Scripts and Tools.
--- Management Tools | Management Service.
--- Next.
- Finish.

1.2. Ensure the following folders have the NTFS permission of Full Control set for the Authenticated Users group, adding that group with that permission if not already present:

- C:\Windows\Temp\
- C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\
- C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
- C:\Windows\Microsoft.NET\Framework64\v4.0.31319\Temporary ASP.NET Files\

1.3. Note: For CA 14.0 and higher:
- Verify the IP and Domain Restrictions role is installed under Web Server (IIS) | Web Server | Security.
- Verify the .NET Core Hosting Bundle 2.2.8 is installed. This can be downloaded here: https://download.visualstudio.microsoft.com/download/pr/ba001109-03c6-45ef-832c-c4dbfdb36e00/e3413f9e47e13f1e4b1b9cf2998bc613/dotnet-hosting-2.2.8-win.exe
- For CA 14.2 and higher, verify the .NET Core Hosting Bundle 5.0.4 is installed. This can be downloaded here: https://download.visualstudio.microsoft.com/download/pr/2281cc70-3851-4dec-b418-4f5be60d8f2e/0163e524e63c2bb07d9da642ca1468d5/dotnet-hosting-5.0.4-win.exe
- For CA 14.3 and higher, verify the .NET Core Hosting Bundle 6.0.1 is installed. This can be downloaded here: https://download.visualstudio.microsoft.com/download/pr/b69fc347-c3c8-49bc-b452-dc89a1efdf7b/ebac64c8271dab3b9b1e87c72ef47374/dotnet-hosting-6.0.1-win.exe
- For 14.3 and higher, verify Node.js is installed as required. This can be downloaded here: https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi

2. Obtain information from the existing Accelerator server:

2.1. Copy the Accelerator License from the \Program Files\Enterprise Vault Business Accelerator\Installed Licenses\ folder to a safe location. Also review the %ProgramData%\Symantec Shared\Licenses\ (and %ProgramData%\Veritas Shared\Licenses\ for 14.x and higher) folder for any installed licenses.
Note - This is an important step. A valid Accelerator license is required to run Searches, Exports, Random Sampling (CA only), Analytics (DA only), and Legal Holds (DA only with a valid DA license also needed on all EV servers). Without a valid license, the Accelerator Customer will essentially be in read-only mode. For example, items in the Review set can be previewed but cannot be Exported, Searches can be created and submitted but will not run.

2.2. Make a copy of the configuration files (*.config) from the existing Accelerator installation folder on the Accelerator server.

2.2.1. Open PowerShell and navigate to the Accelerator Server installation folder on the Accelerator server.

2.2.2. Run the following PowerShell command to list all the .config files:

Get-ChildItem *.config -Recurse | Select-Object FullName

Alternately, if the Accelerator Server installation path is known, edit the path in the following command and run the command in PowerShell:

Get-ChildItem "C:\Program Files (x86)\Enterprise Vault Business Accelerator" *.config -Recurse | Select-Object FullName

To output the list of .config files to a text file, append >> <path>\<filename> to the end of the command. Note the path must exist. For example:

Get-ChildItem *.config -Recurse | Select-Object FullName >> C:\Temp\ConfigFilesList.txt

Or

Get-ChildItem "C:\Program Files (x86)\Enterprise Vault Business Accelerator" *.config -Recurse | Select-Object FullName >> C:\Temp\ConfigFilesList.txt

2.2.3. Make a copy of each .config file, being sure to note its folder location. It is recommended to create a folder in which to store the .config files, then recreate the Accelerator folder structure as listed in the output and store the .config files in that folder structure. For example, the web.config file may be listed in multiple locations and each file can have different content, therefore it is important not to over-write one web.config with another.

To make this task easier, below is a PowerShell script to copy all .config and  json files from the installation folder, including paths. Edit the output folder and source folder path as listed in the commented lines, then run the PowerShell script to copy all .config and all .json files to the output folder with their folder structures.

# Create the folder if it does not exist
$folderPath = "E:\ConfigFiles" # Edit output folder here
if (!(Test-Path -Path $folderPath -PathType Container)) {
    New-Item -ItemType Directory -Path $folderPath
    Write-Host "Folder '$folderPath' created successfully."
} else {
    Write-Host "Folder '$folderPath' already exists."
}
# Define source and destination paths
$SourcePath = "C:\Program Files (x86)\Enterprise Vault Business Accelerator" # Replace with your source folder path
$DestinationPath = "E:\ConfigFiles" # Replace with your destination folder path
# Create the destination folder if it doesn't exist
if (-not (Test-Path $DestinationPath)) {
    New-Item -ItemType Directory -Path $DestinationPath | Out-Null
}
# Find and copy .config and .json files while preserving folder structure
Get-ChildItem -Path $SourcePath -Include *.config, *.json -Recurse | ForEach-Object {
    # Construct the relative path from the source to the current file
    $RelativePath = $_.FullName.Replace($SourcePath, "")
    # Construct the full destination path for the current file
    $NewDestination = Join-Path $DestinationPath (Split-Path $RelativePath -Parent)
    # Create the necessary subdirectories in the destination if they don't exist
    if (-not (Test-Path $NewDestination)) {
        New-Item -ItemType Directory -Path $NewDestination | Out-Null
    }
    # Copy the file to the new destination
    Copy-Item -Path $_.FullName -Destination $NewDestination -Force
}
Write-Host "Copy operation complete."

Important Note

The .config files can contain valuable information regarding any customised ports in use in the environment. These ports will need to be edited in the same files after the reinstall, using the backed up .config files' data as references. Not editing any customised ports can lead to issues connecting to the EVBAAdmin administration website and/or issues with Client connectivity. Here are some examples of port locations with default port numbers:

AcceleratorManager.exe.config:

<add key="Remoting Channel Configuration" value="name=Client Port, port=8085,suppressChannelData=false, machineName=, priority=1, secure=true, protectionLevel=EncryptAndSign, useIpAddress=true,  bindTo=0.0.0.0, rejectRemoteRequests=false, exclusiveAddressUse=true, impersonate=false, authorizationModule=, typeFilterLevel=Full" />

AcceleratorAdminWeb\web.config:

<add key="RemotePort" value="8085" />

2.3. Go to the EVBAAdmin page and make a note of all of the Customers' information. Take screenshots of all of the configuration settings for each Customer. Be sure to include the following:
- Customer Type
- Name
- Vault ID(s) (CA only)
- Directory DNS Aliases
- Administrator User or Group
- Enable Customer's Tasks (checked or unchecked)
- IIS Virtual Directory
- IIS server
- SQL server (note the details of any Always On information if present)
- Database
- Database Location For Analytics

2.4. Stop and disable the Enterprise Vault Accelerator Manager Service (EVAMS) on the existing server.

2.5. Run SQL backups of all Configuration/Customer/Custodian databases.

3. Prepare the databases for the new Accelerator server:

3.1. Run the ConfigurationDBReport against the Configuration database to capture the existing Customer information and Configuration Settings. The Report can be found in the Enterprise Vault, Compliance Accelerator and Discovery Accelerator Environment Reports Article as listed in the Related Articles section below.

3.2. Obtain the following information:

- Old Accelerator server NetBIOS name.
- Old Accelerator server IP address.
- Old Accelerator server FQDN (fully qualified domain name).
- New Accelerator server NetBIOS name.
- New Accelerator server IP address.
- New Accelerator server FQDN.

3.3. If the new Accelerator Server will have the same Hostname (NetBIOS name), Fully Qualified Domain Name (FQDN) and IP address as the original Accelerator server, it will not be necessary to edit the Configuration database. In this case, continue to step 4.

However, if the new Accelerator Server will have a different Hostname (NetBIOS name) and/or a different FQDN and/or a different IP address from the original Accelerator server, the Configuraiton database will need to be modified to edit the entries for the old Accelerator server to point to the new Accelerator server.

3.3.1. Edit the following SQL query with the information as collected above as indicated in the query.

DECLARE
-- All edits below
@OldName nvarchar(100) = 'Old_Accelerator_server_NetBIOS_name' -- edit old Accelerator server NetBIOS name here
, @OldIPAddress nvarchar(39) = 'Old_Accelerator_server_IP_address' -- edit old Accelerator server IP address here
, @OldFQDN nvarchar(500) = 'Old_Accelerator_server_FQDN' -- edit old Accelerator server FQDN here
, @NewName nvarchar(100) = 'New_Accelerator_server_NetBIOS_name' -- edit new Accelerator server NetBIOS name here
, @NewIPAddress nvarchar(39) = 'New_Accelerator_server_IP_address' -- edit new Accelerator server IP address here
, @NewFQDN nvarchar(500) = 'New_Accelerator_server_FQDN' -- edit new Accelerator server FQDN here
-- All edits above
, @NewGroupID int;
IF EXISTS (SELECT 1 FROM tblServer WHERE Name = @NewName)
BEGIN;
    IF (SELECT COUNT(GroupID) FROM tblGroup WHERE Name = @NewName) = 1
    BEGIN;
        SET @NewGroupID = (SELECT TOP 1 GroupID FROM tblGroup WHERE Name = @NewName ORDER BY GroupID ASC);
    END;
    ELSE BEGIN;
        PRINT 'There are multiple or no entries in tblGroup for ' + @NewName + '. This is an unexpected condition and should be fixed before continuing.';
        RETURN;
    END;
END;
ELSE BEGIN;
    IF (SELECT COUNT(GroupID) FROM tblGroup WHERE Name = @OldName) = 1
    BEGIN;
        SET @NewGroupID = (SELECT TOP 1 GroupID FROM tblGroup WHERE Name = @OldName ORDER BY GroupID ASC);
    END;
    ELSE BEGIN;
        PRINT 'There are multiple or no entries in tblGroup for ' + @OldName + '. This is an unexpected condition and should be fixed before continuing.';
        RETURN;
    END;
END;
SELECT [State] = 'tblCustomer Previous Entries', * FROM tblCustomer
SELECT [State] = 'tblGroup Previous Entries', * FROM tblGroup;
SELECT [State] = 'tblServer Previous Entries', * FROM tblServer;
SELECT [State] = 'tblAnalyticsServers Previous Entries', * FROM tblAnalyticsServers;
BEGIN TRY
    BEGIN TRANSACTION;
    UPDATE tblCustomer SET IIS = @NewName, GroupID = @NewGroupID WHERE Type != 52 /*System*/ AND IIS = @OldName;
    UPDATE tblGroup SET Name = @NewName WHERE Name = @OldName;
    UPDATE tblServer SET Name = @NewName WHERE Name = @OldName;
    IF EXISTS (SELECT 1 FROM tblAnalyticsServers WHERE ServerName = @OldName) UPDATE tblAnalyticsServers SET ServerName = @NewName WHERE ServerName = @OldName;
    IF EXISTS (SELECT 1 FROM tblAnalyticsServers WHERE IPAddress = @OldIPAddress) UPDATE tblAnalyticsServers SET IPAddress = @NewIPAddress WHERE IPAddress = @OldIPAddress;
    IF EXISTS (SELECT 1 FROM sys.columns WHERE name = 'IR_ServerAlias')
    BEGIN;
        DECLARE @UpdateIR_ServerAlias nvarchar(max) = 'UPDATE tblServer SET IR_ServerAlias = ''REPLACEMENTNewFQDN'' WHERE IR_ServerAlias = ''REPLACEMENTOldFQDN''';
        SET @UpdateIR_ServerAlias = REPLACE(@UpdateIR_ServerAlias, 'REPLACEMENTNewFQDN', @NewFQDN);
        SET @UpdateIR_ServerAlias = REPLACE(@UpdateIR_ServerAlias, 'REPLACEMENTOldFQDN', @OldFQDN);
        EXEC sp_executesql @UpdateIR_ServerAlias;
    END;    
    COMMIT TRANSACTION;
END TRY
BEGIN CATCH
    IF @@TRANCOUNT <> 0 ROLLBACK TRANSACTION;
    DECLARE @ErrorMessage NVARCHAR(4000), @ErrorSeverity INT, @ErrorState INT;
    SELECT     @ErrorMessage = ERROR_MESSAGE(), @ErrorSeverity = ERROR_SEVERITY(), @ErrorState = ERROR_STATE();
    RAISERROR (@ErrorMessage, @ErrorSeverity, @ErrorState);
END CATCH
SELECT [State] = 'tblCustomer Current Entries', * FROM tblCustomer
SELECT [State] = 'tblGroup Current Entries', * FROM tblGroup;
SELECT [State] = 'tblServer Current Entries', * FROM tblServer;
SELECT [State] = 'tblAnalyticsServers Current Entries', * FROM tblAnalyticsServers;
GO

3.3.2. Open a new query window in SQL Server Management Studio focused on the appropriate Accelerator Configuration database and execute the edited query against the Configuration database. The output should indicate the previous and current Accelerator server name entries.

4. Install the EV Binaries on the new Accelerator server.

4.1. Run the EV Server installation for the major version of EV on the Accelerator server.

4.2. At the "Installation complete. The InstallShield Wizard has successfully installed Enterprise Vault. Click Finish to exit the wizard." screen, uncheck the 'Show configuration information' or 'Show information on configuring installed components' box and then click on Finish.

4.3. Reboot as prompted.

4.4. Repeat to install any applicable cumulative hotfixes or release updates.

5. Install CA or DA.

5.1. Run the Accelerator server installation for the major version of the Accelerator.

5.1.2. Reboot as prompted.

5.1.3. Repeat to install any applicable cumulative hotfixes or release updates.

5.2. When the installation has completed, connect to the EVBAAdmin website at http://localhost/EVBAAdmin.

5.3. Click on the "Use Existing Database" option.

Note - If this option is not seen, it is usually due to installing the base version and then immediately installing a release update before connecting to the existing Configuration database when at the base version. To remedy this, search for all .config files with the following line: <add key="State" value="Upgraded" />. The number of files will vary from  version to version. Edit this line in each of these lines to change the word Upgraded to Uninstalled, as follows: <add key="State" value="Uninstalled" />. Restart the EVAMS and IIS, then connect to the EVBAAdmin website.Also note it may be required to upgrade the Customer databases if the databases show the icon indicating an upgrade is required. Simply right-click each database, open the Properties and click on the button stating to upgrade the database (button name may vary).

5.4. Enter the remaining information.

The SQL server and Configuration database name can be determined by reviewing the following line from the AcceleratorManager.exe.config file.  In this example, the SQL server name is SQLserver1 and the Configuration database name is EVCAConfiguration:
     <add key="DSNConfiguration" value="server='SQLserver1';Integrated Security=true;Initial Catalog='EVCAConfiguration';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" />

If the Configuration database is a member of a SQL Always On Availability Group, enter the Always On information.

5.5. Click Browse and navigate to the Accelerator License File location.

5.6. Verify all settings are correct and save the changes. If the Configuration database is a member of a SQL Always On Availability Group, verify the information before proceeding.

5.7. At the The update is complete. Restart the Accelerator Manager Service and then click 'OK' prompt, please be sure to restart the EVAMS before clicking on the OK button.
If the prompt states The update is complete. Restart the Accelerator Manager Service and Internet Information Service (IIS). Click 'OK' to continue., please be sure to stop the EVAMS,  run the iisreset command in an administrative (elevated) command prompt, then start the EVAMS before clicking on the OK button.
If the prompt states Restart the Accelerator Manager Service, IR Classifier Service, IR Model Builder Service, and Internet Information Service (IIS). Click OK to continue., please be sure to stop the EVAMS, stop the Enterprise Vault IR Classifier Service, stop the Enterprise Vault IR Model Builder Service, run the iisreset command in an administrative (elevated) command prompt, then start the EVAMS, start the Enterprise Vault IR Classifier Service and start the Enterprise Vault IR Model Builder Service before clicking on the OK button.

5.8. At this point, the EVBAAdmin website should show the previously existing Accelerator Customers. Right-click each Accelerator Customer and click on Check Virtual Directory option to create the required IIS virtual directories.

Notes:

1. It is critical to install the same versions of CA/DA and EV on the new CA/DA server as are present on the original CA/DA server. Installing a newer version of the EV binaries or EV API can cause issues with the Enterprise Vault Accelerator Manager Service start-up and with accessing the EVBAAdmin administration website in the steps below. In such cases, Event ID 40966 may be logged in the EV Event Logs on the Accelerator server referencing one or more assembly errors, such as the following:

Could not load file or assembly 'KVS.EnterpriseVault.Interop.DirectoryConnection, Version=11.0.1.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Diagnostic:
Type: System.IO.FileLoadException

If it is needed to in-place upgrade CA/DA and/or EV, either perform an upgrade prior to moving to the new server or after moving to the new server. Do not attempt to perform an upgrade by installing newer versions of EV and/or CA/DA and then copying over the existing configuration files from a different version of CA/DA or EV. 

2. If installing an Update Release version, such as 14.1.1, the base version must first be installed before the Update Release version is installed.  Failure to install the point release, such as 14.1.0, can cause an Event ID 372 error referencing one of more missing DLL files such as the following:

Error When Starting the Accelerator Service. System.IO.FileNotFoundException: Could not load file or assembly 'KVS.Accelerator.Sampling, Version=12.5.0.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c' or one of its dependencies. The system cannot find the file specified.
File name: 'KVS.Accelerator.Sampling, Version=12.5.0.0, Culture=neutral, PublicKeyToken=26c5e2ccf2b9267c'
   at KVS.Accelerator.Server.CommonStarter.StartApplicationThreads(CustomerType custType)
   at KVS.Accelerator.Server.CommonStarter.Start()
   at KVS.Accelerator.Server.AcceleratorServiceProcessor.MainThread()

5. If started, stop the EVAMS on the new Accelerator server.

6. Copy all configuration files with a .config extension from the root of the Accelerator server installation on the original server to the installation folder of the new Accelerator server
(by default: C:\Program Files\Enterprise Vault Business Accelerator for 32-bit systems, or C:\Program Files (x86)\Enterprise Vault Business Accelerator for 64-bit systems). Examples include:

Log4net.config
accelerator.config
AcceleratorLegalHold.dll.config
AcceleratorManager.exe.config
AcceleratorManagerConsole.exe.config
AcceleratorManagerRemoting.config
AcceleratorRBO.dll.config
AcceleratorService.exe.config
AcceleratorService64.exe.config
AcceleratorServiceRemoting.config
ADSynchroniser.exe.config
AnalyticsConversationAnalyserTask.exe.config
AnalyticsIngesterTask.exe.config
AnalyticsServerApp.exe.config
ImportExport.exe.config
KVS.Accelerator.Sampling.dll.config

Not all of the above files may be present, depending on the product version.

If moving from a 32-bit to 64-bit operating system, these files must be edited to reflect the new path to the Reports and Reports\Share folders as well as the new path to the Enterprise Vault files noted within these files when those references exist.  For example, if moving from the default installation path on a Microsoft Windows 2003 (32-bit) server to the default installation path on a Microsoft Windows Server 2008 R2 X64 server, the following lines would need to be edited as follows for the Reports and Reports\Share folders:

From

<add key="ReportSourceLocation" value="C:\Program Files\Enterprise Vault Business Accelerator\Reports" />
  <add key="ReportShare" value="C:\Program Files\Enterprise Vault Business Accelerator\Report\Share" />

To

<add key="ReportSourceLocation" value="C:\Program Files (x86)\Enterprise Vault Business Accelerator\Reports" />  
  <add key="ReportShare" value="C:\Program Files (X86)\Enterprise Vault Business Accelerator\Report\Share" />

There are other lines within each of these files that must be updated with the new path for EV or CA/DA.  If the default installation paths were selected for both Enterprise Vault and CA or DA, then edit these files to replace all instances of Program Files\Enterprise Vault with Program Files (x86)\Enterprise Vault .

7. Start theEVAMS on the new server.

8. The CA/DA IIS virtual directories will need to be manually created on the new server using the following steps:

• Open the EVBAAdmin web page

• Right click on the Customers (one at a time)

• Select Check Virtual Directory

• Click the OK button to confirm the Virtual Directory has been successfully checked.

9. Verify the license is installed under \Program Files (x86)\Enterprise Vault Business Accelerator\Installed Licenses\. If not installed, can upload the license from the EVBAAdmin administration website.

10. Uninstall CA or DA from the original server.