Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Overview

The purpose of the migration is to import the historical recordings from the Verint v11, v15.1 Legacy systems to the Verba platform. 

...

  • Supported platforms:

    • IMR Financial Trading Recorder (IPC Media Recorder)
    • BT Financial Trading Recorder
    • Verint Financial Trading Recorder
  • Migration of historical recordings from Verint v11.1 and v11.2 and v15.1 Legacy systems

  • Support for archived calls only
  • Supported archive mediums: SMB folder or EMC Centera, Hitachi Content Platform (tapes, DVDs, or any other removable media is not supported)
  • Storage targets are automatically created based on the archive configuration in Verint
  • All Verint file formats and codecs are supported: wave file using G.729, G.723.1, or G.726
  • Encrypted calls are not supported
  • Both back office and front office (trader voice) calls can be imported
  • Users, Groups, and Extension can be migrated only from v15.2 systems. The Users' conversation access scope is not migrated.
  • Migrated calls are assigned to users defined in Verba based on their associated recorded extensions (Trader ID / Extension or Phone Number / SIP URI)

Migration process

See Migration from Verint for more information on the migration process.

Archive Considerations

See Migration from Verint for more information on limitations of the archive features.

Prerequisites

Before you begin the migration, the following items must be completed and checked:

  • The Verba system is deployed, configured, and tested.
  • The Verba database is properly sized to accommodate the imported calls. Sizing estimate: ~5 KByte / imported call 
  • Sufficient time is planned for the migration. We recommend running the migration tool out of business hours to minimize the impact on the Verba database.
    Front-office migration time estimate: ~5 million calls / hour
    Back-office migration time estimate: ~3.5 million calls / hour
  • All calls in Verint are archived, calls cannot be in the call buffer on the Verint recorders.
  • The user configuration is complete in the Verba system for historical calls.
  • The metadata mapping is checked and confirmed for both front-office and back-office calls.
  • The SQL Servers are linked:

    The Verint database has to be configured as a linked server on the Verba database server so the system can run queries on both systems during the migration. Server Options / RPC Out needs to be set to True in the Linked Server configuration. Once the migration is finished, the linked server configuration can be removed.
    Alternatively, the Verint databases (Archive, BPMAINDB, EWareCalls, and EWareConfig) can be backed up and restored on the Verba database server. 
    For more information on configuring a linked server, see https://docs.microsoft.com/en-us/sql/relational-databases/linked-servers/create-linked-servers-sql-server-database-engine
  • The recording functionality is turned off on the Verint recorders. This step is to ensure that no new calls are created on the Verint platform, so the system can migrate all historical calls. The migration supports partial migrations by defining date ranges. However, it has to be very carefully designed and tested to ensure all calls are migrated. 
  • All 3rd party database maintenance tools are disabled on both the Verint and the Verba database servers.
  • The Verba Maintenance Job is disabled. For more information on disabling SQL Server jobs, see https://docs.microsoft.com/en-us/sql/ssms/agent/disable-or-enable-a-job.
  • Verba database backup is created to be able to restore the system in the event of a fatal system error during the migration 
  • The necessary SQL scripts are executed on the Verba and the Verint databases (see below).
  • The Verint system is upgraded to 11.1 HFR 9 or later.

Running the SQL scripts

SQL scripts have to be executed on both the Verba and Verint databases before the migration can be started. The SQL scripts can be executed using the Microsoft SQL Server Management Studio which can be downloaded from https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms.

Running the SQL scripts on the Verba database

In order to run the SQL scripts on the Verba database, the SQL user requires the ALTER ANY LINKED SERVER permission or the sysadmin role to run these scripts. If you need help granting the permission, follow the article at https://docs.microsoft.com/en-us/sql/t-sql/statements/grant-server-permissions-transact-sql.

...

1. update-programs-verintmig-aaa-common.sql
2. update-programs-verintmig-aaa-common-inum.sql
4. update-programs-verintmig-bo.sql
5. update-programs-verintmig-fo-cti.sql
6. update-programs-verintmig-fo-cti-15.sql (only from Verba 9.6)
7. update-programs-verintmig-fo-vox.sql
8. update-programs-verintmig-fo-vox-15.sql (only from Verba 9.6)
9. update-programs-verintmig-us.sql (only from Verba 9.6)
10. update-programs-verintmig-zzz-common.sql

Running the SQL scripts on the Verint database

Additionally, another SQL script must be executed on the Verint EWareCalls database. This script is located at c:\Program Files\Verba\tomcat\webapps\verba\WEB-INF\verintmig\verintmig-download\verba-verint-ewarecalls.sql or verba-verint-centralcontact.sql, or can be downloaded from the Verba UI at the Verint Migration Source Database configuration page.

Migration tool

The migration tool, available through the Verba user interface, provides the following features:

...

The Back-Office and Front-Office database migrations move records from the EWareCalls/CentralContact and Archive databases into the Verba database and associate the calls with the existing users when available. The users must exist in the Verba database before the migration begins. Depending on the customer and the number of calls in the Verint database, data migration can encompass several million or more records.

Enabling the migration tool

The migration tool has to be enabled before the migration can take place.

...

Step 5 - The Data / Verint Migration menu item will be visible when the logged-in user has Verint Migration permission.

Source databases

The menu opens the list of the Verint Migration Source Databases. In most cases, there will be one Source Database, but the system allows migrating from multiple databases.

...

The Back Office Subsets in the case of v11 and v15.1 are summed by the system and compared to the “Total # of Back-Office records”. A mismatch will generate a warning.

Back Office (Telephony and Unified Communication)


First of all, a Database VIEW has to be selected. Then the system reads the columns of the view and displays the Column Mapping setup.

...

You can optionally set From and To times to narrow down the migrated time interval.

Front Office (Trader Voice)

The process is similar to the Back Office, but instead of a VIEW, a Datasource has to be selected, and the column mapping is not configurable on the GUI.

...

The column mapping is actually similar to the Back Office mapping, but it is shipped with the product. If it has to be changed, then the new XML mapping file can be uploaded in the Verint Migration Source Databases List screen, using the Upload New Front Office Mapping link at the top right corner.

Data preview

A preview of the data (the first 100 records) is available on the Preview tab:

Running the migration

When the setup is complete and the Preview looks good, then use the Save and Run button to start the migration. The system will migrate one month at a time.

...

If a process is still running, then starting another one will throw an error: “Error during pr_verintmig_bo: Cannot acquire lock (Lock State: -1), probably another migration is still running (16, 1)”.

Post-migration tasks

After the migration completed, the following items must be completed and checked:

  • If the media files are stored on EMC Centera, then copy the PEA file to a location accessible by the Verba Media Repository Servers and change the configuration of the Verba Storage Targets to point to the new PEA file location
  • If the media files are stored on the Hitachi Content Platform, then the Verba Storage Targets have to be configured with the correct API User and Password, because the Password was not copied from the Verint database
  • Verify that calls are searchable and accessible through the Verba system.
  • Verify that all Verint archive locations are available as storage targets in the Verba system.
  • Verify that all calls are migrated by checking the information displayed on the subsets page.

Removing imported calls from Verba and resetting the import

If the migrated calls should be deleted and the Subset status should be "Planning", then use the manual-verintmig-delete-subset-calls.sql can be found on the Verba server in the Verba\resources\db\util folder. Set the ID of the Subset at the beginning of the file:

...