Types of upgrades
There are two types of upgrades:
-
standard upgrades
-
refresh upgrades
The server automatically determines whether you need to perform a standard upgrade or a refresh upgrade.
Standard upgrades
Standard upgrades are upgrades that do not require upgrades to the operating system. You can install upgrade software on your server while the system continues to operate.
For standard upgrades, you install the upgrade software as an inactive version. The system continues to function normally while you are installing the software. When the upgrade is complete, you can choose to automatically reboot the system to the upgraded software or you can manually switch to the new software at a later time. When you reboot to the new software, the old software version remains on the system. This allows you to revert to the old version in the unlikely event of issues with the new software. During an upgrade your configuration information migrates automatically to the upgraded version.
Note |
You can only make any provisioning changes to the database on the active software. The database for the inactive software is not updated. If you make changes to the database after an upgrade, you must repeat those changes after switching to the new software. |
Note |
See Resuming a Failed Upgrade section of the Troubleshooting chapter for more details. |
Refresh upgrades
Refresh upgrades are required in situations where incompatibilities exist between the old and new software releases. For example, a refresh upgrade is required when the major version of the embedded operating system changes between the version you are upgrading from and the version that you are upgrading to. Refresh upgrades require multiple reboots during installation to upgrade the underlying operating system, causing a temporary server outage while the software is installed. The duration of this outage will depend on your configuration and the size of the database.
Note |
You must perform all refresh upgrades during a maintenance window because the system will not be available during the upgrade. |
For refresh upgrades, the upgrade wizard allows you to choose whether or not to automatically run the new upgraded software when the upgrade completes. If you select not to run the new software, the system will reboot to the old software version when the upgrade is complete and you can manually switch to the new software at a later time.
If for any reason you decide to revert to the prior software version, you can switch versions to the older version of the software. This switch version requires a reboot. Be aware that any configuration changes that you made after upgrading the software will be lost.
COP Files
When you perform a refresh upgrade, you must install COP files before you begin upgrading from any of the following releases:
-
upgrades from Cisco Unified Communications Manager 8.5(x) and older to Cisco Unified Communications Manager 10.0(x)
-
upgrades from Cisco Unified Presence 8.5(4) to IM and Presence 10.0(x)
You can download the following COP files from Cisco.com:
COP file | Purpose | ||
---|---|---|---|
ciscocm.refresh_upgrade_v<latest_version>.cop.sgn |
Required. Install this file on all Unified Communications Manager nodes to update the operating system so that it supports the new release. |
||
ciscocm.cup.refresh_upgrade_v<latest_version>.cop |
Required. Install this file on all IM and Presence Service nodes to update the operating system so that it supports the new release. |
||
ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn |
Optional. This COP file expands the vDisk size. Install this COP file on either Unified Communications Manager nodes or IM and Presence Service nodes if you need to increase the vDisk space to meet the space requirements of a refresh upgrade. This option requires a reboot. |
||
ciscocm.free_common_space_<latest_version>.cop.sgn |
Optional. This COP file removes the inactive side in the common partition to increase available disk space without requiring a system rebuild. Install this COP file on Unified Communications Manager nodes or IM and Presence Service nodes as required to perform an upgrade. You can use this COP file as an alternative to the COP file listed above, or in conjunction with it. This option does not require a reboot.
|
To find COP files on Cisco.com, navigate to
.Caution |
If you do not install the COP file on all nodes for the required releases, the upgrade will fail. |
COP File Installation
The following guidelines apply to installing COP files. If the documentation for a specific COP file contradicts these general guidelines, follow the COP file documentation:
-
Install the appropriate COP file on every node in a cluster. Perform this task before you install new software on each node in the cluster and set up the database.
-
After you install a COP file, you must restart the node.
-
Restart Cisco Unified Communications Manager to ensure that configuration changes that are made during the COP file installation get written into the database.
-
Restart the IM and Presence Service to ensure that configuration changes that are made during the COP file installation get written into the database.