ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

ICA environment migration

book

Article ID: 171902

calendar_today

Updated On:

Products

Information Centric Analytics Data Loss Prevention Core Package

Issue/Introduction

This document outlines the process to move an existing Symantec Information Centric Analytics (ICA) installation to a new environment.

Resolution

Destination Application Server Preparation

These are the steps to prepare the destination Application Server for migration.

  • Install all Risk Fabric prerequisite software
  • Install Risk Fabric
    • Create a new RiskFabric database on the SQL Server (this will be removed in the steps below and replaced with the backups from the steps below)
    • Create a new RiskFabric database on the SQL Analysis Server (this will be removed in the steps below and replace with the Backups from the steps below)
  • Create a backup of the Risk Fabric Server application folders on the new server
  • Copy the Risk Fabric Server application folders from the existing server to the new server, overwriting the existing files (to preserve any file changes made in DEV and ensure bug fixes in DEV exist in new system)
  • Open the RiskFabric web.config file and edit the connection string to point to the new database server name. Save and close the file.

Destination SQL Server Preparation (Requires DBA)

These are the steps to prepare the destination SQL Server for migration. These steps should be followed the destination application server preparation steps have been completed.

  • Install .Net Framework 4.5.1 (required for import utilities)
  • Delete existing Risk Fabric SQL database
  • Delete existing Risk Fabric SQL Analysis Server Database

Previous SQL Server – Backup Creation (Requires DBA)

These steps should be completed on the existing SQL Server.

  • Create new backups for the following SQL databases:
    • RiskFabric
  • Create new backups for the following SQL Analysis Server databases:
    • RiskFabric
  • Backup Linked Servers
    • Expand Server Objects and click the Linked Servers folder, then press F7
    • CTRL+Click on any Risk Fabric linked servers including:
      • RISKFABRIC_ASDB
      • RISKFABRIC_DLP_RISKFABRIC_PROTECT
      • RISKFABRIC_EPO_RISKFABRIC_[Database Instance]_[Database Name]
    • Right click the highlighted areas, select Script Linked Servers as, Create To, New Query Editor Window
    • This query will be manipulated in the steps below.
  • Backup SQL Server Agent Jobs
    • Expand SQL Server Agent and click the Jobs folder, then press F7
    • CTRL+Click on each of the jobs listed below:
      • RiskFabric Intraday Processing
      • RiskFabric Processing
    • Right click the highlighted areas, select Script Job as, Create To, New Query Editor Window
    • This query will be manipulated in the steps below.

Destination SQL Server – Backup Restore (Requires DBA)

  • Restore the following SQL Databases:
    • RiskFabric

 

  • Execute the below script against the newly restored RiskFabric SQL database, Replacing 'XXXXXX' with the new server name and 'OLDSERVER' with the previous server name.

-- Metrics Table
update Metrics
set ServerName = 'XXXXXX'
 
-- DetailsGridQueries
update DetailsGridQueries
set [Server] = 'XXXXXX'
 
-- PortalSettings
update PortalSettings
set ASDBServer = 'XXXXXX'
 
-- MetricDashboards
UPDATE MetricDashboards
SET DashboardXml =  CAST(REPLACE(CAST(DashboardXml AS NVARCHAR(MAX)),'OLDSERVER','XXXXXX')AS NTEXT)

  • Restore the following SQL Analysis Server Databases:
    • RiskFabric
  • After the SQL Analysis Server databases have been restored, the database’s Data Source needs to be modified to point to the new destination SQL Server in the connection string.
  1. Open SQL Server Management Studio
  2. In the Connect to Server dialog box, select Analysis Services, enter the Server name for the server hosting the RiskFabric analysis server database to be moved and select Connect.
  3. Expand the Databases, then for each database listed above, expand the database, and Data Sources.
  4. Right click the data source name, select Script Data Source as, ALTER to, New Query Editor Window.
  5. Replace the existing Data Source with the name of the server and instance of the destination server.
  6. Press F5 to execute the query.
  • Restore linked servers. When restoring Oracle based linked servers, passwords will have to be entered. This is only applicable for the Oracle linked servers (DLP Connections).
    • If @provider=N’OraOLEDB.Oracle’, then replace the @rmtpassword=’########’ with the Oracle password for the @rmtuser specified for the connection.
    • Press CTRL+H, in the Find what line enter the previous SQL Server Name, in the Replace with line enter the name of the destination SQL Server Name, the press Replace All and execute the query.

 

  • Restore SQL Server Agent Jobs.
    • Verify all operators are the same on both systems, correct any discrepancies before continuing.
    • Verify all logons in the script exist on both systems, correct any discrepancies before continuing.
    • Verify all credentials are the same on both systems, correct any discrepancies before continuing.
    • Press CTRL+H, in the Find what line enter the previous SQL Server Name, in the Replace with line enter the name of the destination SQL Server Name, the press Replace All and execute the query.

Copying Import Utilities from Previous SQL Server to New SQL Server (Requires DBA)

  • Copy the folder “[Installed Location]\Bay Dynamics\” from the existing SQL Server to the new SQL Server.
    • Place it in the same location
    • Expose the same shares and permissions so the logs can be monitored, if appropriate. The application identity will need to be able to read and write to the path so logs can be generated and configuration files can be read.

Verify Risk Fabric Functionality

  • Verify RiskFabric can be loaded
  • Create a test KPI and add it as a metric
  • Verify SQL Agent jobs are functioning
  • Monitor all jobs