Worksheet for synchronizing the CMS servers after turning data collection on/off

Last Updated : Apr 05, 2024 |
Prolog information
Metadata
Keywords:
Synchronizing the CMS servers after turning data collection on/off
Date/Time
At Time A, (see the) tell users to log off the primary CMS server.
Put the primary CMS server in single-user mode. For more information, see Administering Avaya Call Management System.
Turn off data collection on the primary CMS server for all ACDs. Record the stop date and time.
Date/Time
________
Do the desired administrative function (For example, Changing Data Storage Allocation).
Turn data collection back on, on the primary CMS server, and verify that all the links come back up. For more information, see Administering Avaya Call Management System. Record the date and time when the links come back up.
Date/Time
________
Return the primary CMS server to multi-user mode.
Wait until the most recent archive interval has completed. Verify that the interval has been archived on the secondary CMS server by doing the following:
Using Maintenance: Archiving Status, run the report for interval archiving for all ACDs. Verify from the report that the interval archive for the interval ending at time B (see the Synchronizing CMS Servers after Data Collection Is Turned On/Off) has run.
At Time B (see the Synchronizing CMS Servers after Data Collection Is Turned On/Off), do an incremental historical backup of all ACDs on the secondary CMS server.
Restore the historical data of specific start/stop and dates/times of all ACDs to the primary CMS server. Use the time at the beginning of the interval during which the interruption occurred on the primary CMS server (for example, if the interval is 30 minutes long and occurs on the hour, and the link went down at 5:13, enter 5:00, not 5:13 as the start time.) Also enter the stop time for the end of the interval during which the interruption occurred (for example, if the link went down at 5:13 and came back up at 5:19, enter 5:29 as the stop time).
Put the secondary CMS server in single-user mode.
Turn data collection off on the secondary CMS server. Record the date and time.
Date/Time
________
Do the same administrative function you did above for the primary CMS server on the secondary CMS server.
Turn data collection on on the secondary CMS server. Record the date and time when the links come back up.
Date/Time
________
Put the secondary CMS server in multi-user mode.
After the ACD links come back up, wait for the end of that interval.
At Time C (see the Synchronizing CMS Servers after Data Collection Is Turned On/Off), verify that the interval you are backing up has been archived on the secondary CMS server.
At Time C’ (see the Synchronizing CMS Servers after Data Collection Is Turned On/Off), do an incremental backup of all ACDs on the primary CMS server.
Note:
If a daily/weekly/monthly archive occurred before you synchronized data at time B’ or time C’, then after you synchronize the data (at time B or C) you must run the appropriate daily/weekly/monthly archive. Using System Setup…Data summarizing, rerun the daily/weekly/monthly archive to recreate the data.
Restore the Historical data of specific start/stop and dates/times of all ACDs to the secondary CMS server. For example, if the interruption on the secondary CMS server occurred at 5:35 and ended at 5:42, enter 5:30 for the start time and 5:59 for the stop time.
Date/Time
________
Wait until the most recent interval during which the link came back up has been archived before doing the backup and restore process. In the scenario described above, the link was down for only a single interval for both the primary and secondary CMS servers. If the link is down for multiple intervals, wait until the link has come back up before doing the backup and restore process.