Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide
7-2
Cisco Unified Communications Operating System Administration Guide for Cisco Unifed CCX Release 8.0(1)
Chapter 7 Software Upgrades
Software Upgrade Considerations
Software Upgrade Considerations
This section contains the following topics:
•
•
•
•
•
Overview of the Software Upgrade Process
Unified CCX 8.0(1) software upgrade process consists of successful installation of the upgrade software
to the inactive partition followed by the switch version process.
to the inactive partition followed by the switch version process.
You can install upgrade software on your server while the system continues to operate. Two partitions
exist on your system: an active, bootable partition and an inactive, bootable partition. The system boots
up and operates entirely on the partition that is marked as the active partition.
exist on your system: an active, bootable partition and an inactive, bootable partition. The system boots
up and operates entirely on the partition that is marked as the active partition.
When you install upgrade software, you install the software on the inactive partition. The system
continues to function normally while you are installing the software. When you are ready, you activate
the inactive partition and reboot the system with the new upgrade software by running the switch version
process. The current active partition will then get identified as the inactive partition when the system
restarts. The current software remains in the inactive partition until the next upgrade. Your configuration
information migrates automatically to the upgraded version in the active partition.
continues to function normally while you are installing the software. When you are ready, you activate
the inactive partition and reboot the system with the new upgrade software by running the switch version
process. The current active partition will then get identified as the inactive partition when the system
restarts. The current software remains in the inactive partition until the next upgrade. Your configuration
information migrates automatically to the upgraded version in the active partition.
If for any reason you decide to back out of the upgrade, you can restart the system to the inactive partition
that contains the older version of the software. However, any configuration changes that you made since
you upgraded the software will get lost.
that contains the older version of the software. However, any configuration changes that you made since
you upgraded the software will get lost.
You can only make changes to the database on the active partition. The database on the inactive partition
does not get updated. If you make changes to the database after an upgrade, you must repeat those
changes after switching the partition.
does not get updated. If you make changes to the database after an upgrade, you must repeat those
changes after switching the partition.
You can install a patch or upgrade version from a DVD (local source) or from a network location (remote
source) that the server can access. While upgrading the Operating System in a single node deployment
of Unified CCX, you should upgrade the publisher node
source) that the server can access. While upgrading the Operating System in a single node deployment
of Unified CCX, you should upgrade the publisher node
1
. After the upgrade is complete, initiate switch
version on the publisher node. Ensure that the publisher comes up successfully after the switch version
and shows appropriate active and inactive versions.
and shows appropriate active and inactive versions.
Caution
In a High Availability (HA) deployment of Unified CCX, you should upgrade both the nodes with
publisher being the first and then the subscriber. After the upgrade is complete on both the nodes, initiate
switch version on the Publisher first and after the publisher comes up successfully, initiate switch version
on the subscriber. Ensure both the publisher and subscriber come up successfully after the switch version
and shows appropriate active and inactive versions.
publisher being the first and then the subscriber. After the upgrade is complete on both the nodes, initiate
switch version on the Publisher first and after the publisher comes up successfully, initiate switch version
on the subscriber. Ensure both the publisher and subscriber come up successfully after the switch version
and shows appropriate active and inactive versions.
Data migration happens only when a switch version is done from a lower to the higher version; when the
switch version is done from a higher to a lower version the data migration does not happen.
switch version is done from a higher to a lower version the data migration does not happen.
1. In a single node deployment of Unified CCX, the node will be a publisher node by default.