CMS : Backup HA CMS server is not syncing data with Primary CMS server


Doc ID    SOLN295837
Version:    5.0
Status:    Published
Published date:    18 Nov 2019
Created Date:    01 Sep 2016
Author:   
nmokhle
 

Details

For  reference Matrix case#INC000011079961
Backup HA CMS server is not syncing data with Primary CMS server since upgrade.

CMS version cms-R18.0.0.1-fb.g.x86_64

Problem Clarification

Backup HA CMS server is not syncing data with Primary CMS server

 

Cause

ON checking CMS can see nightly push is all working fine on primary
2016-08-12 03:18:36 nightly_push - Sorting passwd and shadow files.
2016-08-12 03:18:37 nightly_push - Doing housekeeping on the Primary system.
2016-08-12 03:18:37 housekeeping - Done
2016-08-12 03:18:37 nightly_push -  --- FINISHED NIGHTLY PUSH ---
(amc-vcc-cms02)-(Primary)=#

and Secondary HA CMS is in mutli user mode .

there is no historical data on HA CMS but it's available on Primary.customer had 3 ACDs
8/12/16  08:49  Avaya(TM) CMS                       Windows: 1 of 10   ^^^
     Maintenance: Error Log Report                              McKinsey_US_ACD1

                                  Error Log Report
                                                   Printed:  8/12/16  8:49 AM

      Error   Date      Time      # Times   ACD   Severity
      Code    Occurred  Occurred  Occur
              SPI session error: data collection session is down
      1400     8/ 4/16  10:55 AM  2        1      ERROR
              SPI session error: data collection session is down
      1400     8/ 4/16  10:26 AM  1        1      ERROR
              SPI session error: data collection session is down

Solution

To restore CMS backup from Primary to HA sec CMS below are steps:
1:Check CMS data in primary /CMS_Backup
-rw-rw-rw-. 1 root cms   160662861 Aug 27 01:35 CMS-160827-01-LSAC-00-F-01-13-amc-vcc-cms0200
-rw-rw-rw-. 1 root cms   158908372 Aug 28 01:35 CMS-160828-01-LSAC-00-F-01-13-amc-vcc-cms0200
-rw-r--r--. 1 root root 6017105920 Aug 28 04:15 CMSADM-R18.0.0.1fb.g-160828041145-amc-vcc-cms02
-rw-r--r--. 1 root root 6018385920 Aug 28 05:08 CMSADM-R18.0.0.1fb.g-160828050232-amc-vcc-cms02
-rw-rw-rw-. 1 root cms   157149795 Aug 29 01:36 CMS-160829-01-LSAC-00-F-01-13-amc-vcc-cms0200
-rw-rw-rw-. 1 root cms   157301648 Aug 30 01:35 CMS-160830-01-LSAC-00-F-01-13-amc-vcc-cms0200
-rw-rw-rw-. 1 root cms   157481366 Aug 31 01:35 CMS-160831-01-LSAC-00-F-01-13-amc-vcc-cms0200
-rw-rw-rw-. 1 root cms   157743550 Sep  1 01:35 CMS-160901-01-LSAC-00-F-01-13-amc-vcc-cms0200

(amc-vcc-cms02)-(Primary)=# pwd
/CMS_Backup

2: Go to Secondary CMS and (euc-vcc-cms02)-(Secondary)=# cd /storage/

(euc-vcc-cms02)-(Secondary)=# pwd
/storage

3:Do sftp to primary  from secondary to get latest "CMS-160901-01-LSAC-00-F-01-13-amc-vcc-cms0200" file
(euc-vcc-cms02)-(Secondary)=#sftp primary
sftp>cd /CMS_Backup
sftp>put CMS-160901-01-LSAC-00-F-01-13-amc-vcc-cms0200

4:Once you have CMS file in secondary then we need restore in secondary CMS
i,e restoring the historical backup from Primary to HA secondary CMS server.
go to menu page and select Data Summarization Time Zone
9/ 1/16  05:37  Avaya(TM) CMS                                                 

  lMainMenuqqqqqqqqqqqqqqqqqqqqqk
  x Reports>                    x
  x Dictionary>                 x
  x Exceptions>                 x
  x Forecast>                   x
  x Agent Administration>       x
  x Call Center Administration> x
  x Tenant Administration>      x
  x Custom Reports>             x
  x User Permissilqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
  x System Setup>x Switch Setup                 x
  x Maintenance> x Pseudo-ACD Setup             x
  x HAusermenu>  x Load Pseudo-ACD Data         x
  x Admin Paging>x Data Storage Allocation      x
  x RT_Socket>   x Free Space Allocation        x
  x ECH Handler> x Storage Intervals            x
  x Logout       x Main Menu Addition           x
  x ;            x CMS State                    x
  mqqqqqqqqqqqqqqx Data Collection              x
                 x External Application Status  x
                 x Data Summarizing             x
                 x R3 Migrate Data              x
                 x Data Summarization Time Zone x

5:then in Data Summarization Time Zone put below detaisl and leave rest as it is on page:
Share snapshot in the notes
Device name:Do not USE
Data Type:put x on Historical data
ACD put x on all ACDs
and the "run"
6:Check secondary historical data will get restored

Attachment Description

Share snapshot in the notes for with Data Summarization Time Zone parameter

Attachment File

CMS restore data 12Aug 16.docx
1.8MB • 5 minute(s) @ 56k, < 1 minute @ broadband


Additional Relevant Phrases

Unable to resync data from HA CMS to Primary CMS HA historical sync usage consultation

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy