Programing changes missing

[gene]

When doing an upgrade of callmanager for 7.1.x to 7.1.x

the software was loaded early in the week and switched into service on the weekend. All programing changes made between those times was lost. Is this normal. Seems like it has happened to me before but I do not see it documented anywhere.

[Rob Huffman · Accepted solution]

Hi Gene,

Yes, sadly this is expected behavior;

Overview of the Software Upgrade Process

With this version of Cisco Unified Communications Manager, 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.

---

Note If you have users logging in and logging out of Cisco Extension Mobility, this could cause the upgrade to fail. Before starting the upgrade, you must disable the Cisco Extension Mobility service. For more information, see the "Pre-Upgrade Tasks" section.

---

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. 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.

When you upgrade a cluster, you start by upgrading the first node. You can begin upgrading subsequent nodes in parallel after the first node reaches a specified point in the upgrade, as described in the "Upgrading a Cluster in Parallel" section.

All servers in a cluster must run the same release of Cisco Unified Communications Manager. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed.

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.

---

Note 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.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/7_1_2/cucos/iptpch7.html#wp1179676

Cheers!

Rob

[gene]

Thanks very much

[gene]

Just thought of one other thing. Does this mean the call forward se

ttings would revert back to where they were when the software was loaded?

Just curious since that is part of the database but users change it from the phone.

[Rob Huffman · Accepted solution]

Hey gene,

User facing features like Call Forward All are preserved during an upgrade. This

behavior changed with the release of CUCM 6.1 I believe

For upgrades from Cisco Unified Communications Manager Release 6.x, changes that are made to the following user-facing features get preserved after the upgrade completes:

•Call Forward All (CFA)

•Message Waiting Indication (MWI)

•Privacy Enable/Disable

•Do Not Disturb Enable/Disable (DND)

•Extension Mobility Login (EM)

•Hunt Group Logout

•Device Mobility

•CTI CAPF status for end users and application users

•Credential hacking and authentication

•Recording enabling

•Single Number Reach enabling

My understanding is that right as the "switch-version" is done during an upgrade a "snapshot" of

these features is taken and migrated to the new version.

Cheers!

Rob

[gene]

Thanks again

[Rob Huffman]

Hi Gene,

You are most welcome my friend

Cheers!

Rob