Filter
Top Products
Upgrading CMS to the High Availability Option
CentreVu
CMS R3V8 High Availability
Connectivity, Upgrade and Administration
HA Upgrade Scenarios 3-4
5. On the day of the upgrade, the Lucent technician arrives onsite and
performs a backup of system and ACD-specific admin data on the
original server.
Note:
At this point in the upgrade process, CMS users must not
attempt to make administrative changes on the system until the
HA upgrade is completed.
6. The new HA server is installed, configured, CMS is put into single
user mode and the backup tape (created in Step 5
) is used to
migrate the System Administration data and Agent/Call Center
Admin data onto the new HA server.
7. After the most recent intrahour interval archive completes on the
original server, busy out all ACD links at their respective switches
and re-administer them for CMS R3V8 and dual ACD links. When
the switches are re-administered, release the busy out for the links.
8. As soon as the switch is re-administered and the ACD links for the
new HA server come up, verify that CMS data collection on the new
HA server is active for all ACDs.
9. Perform an incremental maintenance backup on the original server
(historical data only), then power it down to install the new drives
from the Speed Centre.
10. After the Speed Centre disks are installed and the new CMS
software has been set up, restart CMS data collection on the original
server. Verify that data is collected from all ACDs.
11. Migrate the CMS historical data from the incremental maintenance
backup (Step 9
) to the new HA server. When the migration
completes, replace the incremental tape with the original full
maintenance tape (Step 4
) and migrate all of the remaining
historical data to the new HA server.
12. Use the CMS system administration and ACD-specific admin data
backup tape (Step 5
) to migrate that data back onto the newly
upgraded original CMS server.
13. Run a full maintenance backup on the new HA server.
14. Restore the historical data from the full maintenance backup tape
(created in the preceeding step) onto the original server.
The two servers now share the same initial set of administrative
data; CMS users can now resume (or start) making
administrative changes to whichever CMS system is
designated as the primary server.