User guide

Introduction

CentreVu

CMS R3V8 High Availability User Guide

Overview 1-5

b. non-disruptive R3 migration - non-disruptive R3 migration is the

ability to perform any of the R3 migrations with data collection

turned on during the entire migration process. R3 migration is

critical to synchronizing data during the upgrade process (e.g.,

R3V6 to R3V8 or R3V8.1 to R3V8.2 when database schema

changes are required).

3. Capability to turn External Call History (ECH) on and off: The

ECH feature can be independently started and stopped on the two

HA servers. How ECH is managed depends on your particular CMS

configuration:

●

if you do not use any customized CMS reporting solutions

(developed by the PSO), ECH data should be active only on

the primary server under normal operating conditions. If the

primary server fails, ECH can be started on the other CMS

server.

●

if you do use customized CMS reporting solutions developed

by the PSO, ECH data should be active on both CMS servers.

Consult with your PSO representative for details.

Increased Data

Availability

The R3V8 CMS High Availability offer builds on the availability and

serviceability improvements implemented in the standard R3V8 CMS

offer described above. Below is a summary of how the R3V8 CMS High

Availability offer increases the availability of your CMS data.

1. ACD link failures: In the recommended HA configuration, ACD

data is transmitted across different C-LAN cards within the

DEFINITY® and across different network subnets, thereby reducing

the number of potential single points of failure. If one ACD link fails,

data collection continues on the second R3V8 CMS server. You will

use the maintenance backup and restore process to recover the

missing data onto the R3V8 CMS server that was connected to the

down ACD link.

2. CMS hardware failures: The R3V8 CMS server is duplicated. If a

hardware failure occurs on one R3V8 CMS server, data collection

continues on the second R3V8 CMS server. You will use the

maintenance backup and restore process to recover the missing

data onto the R3V8 CMS server that failed. If the R3V8 CMS

system fails, you may need to restore the cmsadm backup. Since

the cmsadm backup can now be performed with data collection on,

it is more likely that you will have a good cmsadm backup and the

system can be recovered more quickly.