Upgrade Guide for Cisco Unity Connection Release 8.x
Reverting Cisco Unity Connection 8.x Servers to the Version on the Inactive Partition
Downloads: This chapterpdf (PDF - 132.0KB) The complete bookPDF (PDF - 3.95MB) | Feedback

Reverting Cisco Unity Connection 8.x Servers to the Version on the Inactive Partition

Table Of Contents

Reverting Cisco Unity Connection 8.x Servers to the Version on the Inactive Partition

About Reverting from Connection 8.x to the Version on the Inactive Partition

Reverting a Connection 8.x Server to the Version on the Inactive Partition

Reverting the Servers in a Connection 8.x Cluster to the Version on the Inactive Partition

Reverting a Connection 8.x Member Server in a Cisco Voicemail Organization to the Version on the Inactive Partition

Reverting a Connection 8.x Site Gateway Server in a Cisco Voicemail Organization to the Version on the Inactive Partition


Reverting Cisco Unity Connection 8.x Servers to the Version on the Inactive Partition


This chapter contains the following sections:

About Reverting from Connection 8.x to the Version on the Inactive Partition

Reverting a Connection 8.x Server to the Version on the Inactive Partition

Reverting the Servers in a Connection 8.x Cluster to the Version on the Inactive Partition

Reverting a Connection 8.x Member Server in a Cisco Voicemail Organization to the Version on the Inactive Partition

Reverting a Connection 8.x Site Gateway Server in a Cisco Voicemail Organization to the Version on the Inactive Partition

About Reverting from Connection 8.x to the Version on the Inactive Partition

Revised November 16, 2010

After upgrading, you can revert to the software version that was running before the upgrade by switching to the software version on the inactive partition.


Caution If you revert to the version on the inactive partition, you cannot later switch to the newest version. Instead, you must reinstall the upgrade as documented in this guide.

Note the following effects on data and messages of reverting to the version on the inactive partition:

Users that were added after you upgraded to the new version will no longer exist after you revert to the version on the inactive partition. You will have to add the new users again.

All messages are preserved. However, users that were added after the upgrade no longer exist, so their messages are orphaned. These messages are moved to the undeliverable messages folder.

If you moved mailboxes from one mailbox store to another after upgrading, those mailboxes will be moved back to the mailbox stores they were in before the upgrade.

If you created mailbox stores after upgrading, the new mailbox stores will be deleted.

Connection 8.5 only: If the version on the inactive partition does not support single inbox, note the following:

Messages that have been synchronized with mailboxes in Exchange will continue to exist both in Connection and in Exchange, but they will no longer be associated with one another. Messages must be deleted from both locations, and status changes (for example, from unread to read), changes to the subject line, and changes to the priority are no longer replicated. Status changes in Exchange (for example, from unread to read) no longer change message waiting indicators.

The settings for message actions that were in effect for the version on the inactive partition will again be in effect.

When you re-upgrade to Connection 8.5 or later, any messages that still appear in both places will be reassociated. Messages that have been deleted from Exchange but that still exist in Connection will be resynchronized into Exchange mailboxes.

If the version on the inactive partition does not support dispatch messages (any version earlier than Connection 7.0(1) ), dispatch messages in the new version of Connection are converted to standard messages in the older version. The subject line still includes "DISPATCH." (Dispatch messages are messages sent to a distribution list, either from a call handler or from an interview handler, that only one user in the group needs to act on. For more information, see the "Dispatch Messages" section in the "Messaging in Cisco Unity Connection 8.x" chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx.html.)

If message recall is configured, and if the version on the inactive partition does not support message recall (any version earlier than Connection 8.x), messages in the sent-items folder for the new version of Connection are deleted.

The sent-items folder is created the first time a user sends a message after message recall is configured. If you revert to a version that supports message recall but the sent-items folder had not yet been created for the user, messages in the sent-items folder for the new version are moved to the undeliverable messages folder.

When speech to text is configured, if you revert to Connection 7.x or earlier and reupgrade to Connection 8.x, you will hear an additional prompt for speech-to-text messages that were left before the revert and reupgrade.

Each voice message that has been transcribed has an attached text file that contains the text of the message. For most voice messages that have attachments, Connection plays the prompt "with attachments," so you know that a message has attachments. The "with attachments" prompt is unnecessary when the attachment is the text transcription of the voice message, so Connection suppresses that prompt for voice messages that have been transcribed. However, the field that tracks whether an attachment is a transcription did not exist in Connection 7.x and earlier, and when you revert to the earlier version, the information is lost for existing messages. After the reupgrade to Connection 8.x, Connection plays the "with attachments" prompt for all voice messages that existed before the revert and that have attachments, including those for which the attachment is a transcription. New messages that are transcribed after the reupgrade will not have this problem.

If the version on the inactive partition does not support draft messages (any version earlier than Connection 8.x), draft messages in the new version of Connection are deleted.

The drafts folder is created the first time a user saves a draft message after the feature is configured. (You must either configure Connection to automatically save draft messages when users are disconnected or hang up, or configure Connection to allow users to save draft messages.) If you revert to a version that supports draft messages but the drafts folder had not yet been created for the user, messages in the drafts folder for the new version are moved to the undeliverable messages folder.

If you revert to Connection 2.x, which does not support future-delivery messages, messages that are queued for future delivery are not deleted from the hard disk, but they will not be delivered, and the sender cannot access them.

The future delivery folder is created the first time a users marks a message for future delivery. If you revert to a version that supports future delivery but the future delivery folder had not yet been created for the user, messages in the future delivery folder for the new version are moved to the undeliverable messages folder.

Reverting a Connection 8.x Server to the Version on the Inactive Partition

Revised November 16, 2010

Use the procedure in this section only if the server is not in a cluster, is not a member server in a Connection site, and is not a gateway server between Connection sites or between a Connection site and a Cisco Unity site.


Caution Do not revert to the version on the inactive partition during regular business hours unless doing so is necessary. Reverting causes the Connection server to restart, and Connection will not function for about 15 minutes, until the restart completes.

To Revert a Connection 8.x Server to the Version on the Inactive Partition


Step 1 Sign in to Cisco Unified Operating System Administration.

Step 2 From the Settings menu, select Version.

The Version Settings window displays.

Step 3 Select the Switch Versions button.

After you confirm that you want to restart the system, the system restarts, which might take up to 15 minutes.

Step 4 Confirm that the version switch was successful:

a. Sign in to Cisco Unified Operating System Administration.

b. From the Settings menu, select Version. The Version Settings window displays.

c. Confirm that the correct product version is now running on the active partition.

d. Confirm that all activated services are running.

e. Sign in to Cisco Unity Connection Administration.

f. Confirm that the configuration data exists.


Reverting the Servers in a Connection 8.x Cluster to the Version on the Inactive Partition

Revised November 16, 2010

To revert the servers in a Connection cluster to the version on the inactive partition, do the following three procedures.

Use the procedure in this section only if the server is not a member server in a Connection site, and is not a gateway server between Connection sites or between a Connection site and a Cisco Unity site.


Caution You must revert both servers and reset database replication, or the cluster will not function properly.


Caution Do not revert to the version on the inactive partition during regular business hours unless doing so is necessary. Reverting causes the Connection server to restart, and Connection will not function for about 15 minutes, until the restart completes. In addition, voice messages left on the subscriber server while you are reverting the publisher server will be lost.

To Revert the Publisher Server in a Connection Cluster to the Version on the Inactive Partition


Step 1 Sign in to Cisco Unified Operating System Administration.

Step 2 From the Settings menu, select Version.

The Version Settings window displays.

Step 3 Select the Switch Versions button.

After you confirm that you want to restart the system, the system restarts, which might take up to 15 minutes.

Step 4 Confirm that the version switch was successful:

a. Sign in to Cisco Unified Operating System Administration.

b. From the Settings menu, select Version. The Version Settings window displays.

c. Confirm that the correct product version is now running on the active partition.

d. Confirm that all activated services are running.

e. Sign in to Cisco Unity Connection Administration.

f. Confirm that the configuration data exists.


To Revert the Subscriber Server in a Connection 8.x Cluster to the Version on the Inactive Partition


Step 1 Sign in to Cisco Unified Operating System Administration.

Step 2 From the Settings menu, select Version. The Version Settings window displays.

Step 3 Select the Switch Versions button.

After you confirm that you want to restart the system, the system restarts, which might take up to 15 minutes.

Step 4 Confirm that the version switch was successful:

a. Sign in to Cisco Unified Operating System Administration on the subscriber server.

b. From the Settings menu, select Version. The Version Settings window displays.

c. Confirm that the correct version is now running on the active partition.

d. Confirm that all activated services are running.


To Reset Database Replication in a Connection 8.x Cluster After Reverting the Servers to the Version on the Inactive Partition


On the publisher server, run the CLI command utils dbreplication reset all.


Reverting a Connection 8.x Member Server in a Cisco Voicemail Organization to the Version on the Inactive Partition

Revised November 16, 2010

If an intersite link is configured between a Cisco Unity Connection site and a Cisco Unity site or between two Connection sites, do the following tasks to revert a Connection member server or cluster in a site to the version of Connection on the inactive partition.


Caution Do not revert to the version on the inactive partition during regular business hours unless doing so is necessary. Reverting causes the Connection server to restart, and Connection will not function for about 15 minutes, until the restart completes.

1. If you added this server to the Connection site before you upgraded to the version on the active partition, skip to Task 2. You do not need to remove this member server from the site before you revert.

If you added this server to the Connection site after you upgraded to the version on the active partition, remove this member server from the site. If a cluster is configured, do the task on the publisher server. For more information, see the "Removing a Location From a Cisco Unity Connection Site" section in the "Making Changes to the Networking Configuration in Cisco Unity Connection 8.x" chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

2. If no cluster is configured, revert the server. See the "Reverting a Connection 8.x Server to the Version on the Inactive Partition" section.

If a cluster is configured, revert both servers, and reset database replication. See the "Reverting the Servers in a Connection 8.x Cluster to the Version on the Inactive Partition" section.

3. If you removed the server from a Connection site in Task 1., if the version you reverted to supports networking, and if you still want the server to be part of a Cisco voicemail organization, set up networking again. See the "Setting Up Networking Between Cisco Unity Connection 8.x Servers" chapter of the Networking Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

Reverting a Connection 8.x Site Gateway Server in a Cisco Voicemail Organization to the Version on the Inactive Partition

Revised November 16, 2010

If an intersite link is configured between a Cisco Unity Connection site and a Cisco Unity site or between two Connection sites, do the following tasks to revert a Connection site gateway server or cluster to the version of Connection on the inactive partition.


Caution Do not revert to the version on the inactive partition during regular business hours unless doing so is necessary. Reverting causes the Connection server to restart, and Connection will not function for about 15 minutes, until the restart completes.

1. If you configured an intersite link before you upgraded to the version on the active partition, skip to Task 4. You do not need to remove the gateway server from the Connection site before you revert.

If you configured an intersite link after you upgraded to the version on the active partition, and if the Connection site gateway is the link to another Connection site, remove the intersite link between the two Connection sites. If a cluster is configured, do the task on the publisher server. For more information, see the "Removing an Intersite Link Between Two Cisco Unity Connection Sites" section in the "Making Changes to the Networking Configuration in Cisco Unity Connection 8.x" chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

If you configured an intersite link after you upgraded to the version on the active partition, and if the Connection site gateway is the link to a Cisco Unity site, remove the intersite link between the Connection site and the Cisco Unity site. If a cluster is configured, do the task on the publisher server. For more information, see the "Removing an Intersite Link Between a Cisco Unity Connection Site and a Cisco Unity Site" section in the "Making Changes to the Networking Configuration in Cisco Unity Connection 8.x" chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

2. If you removed an intersite link in Task 1., in Connection Administration, on the Tools > Task Management page, change the schedule for the Remove Objects Associated With Deleted Remote Sites task to run in a few minutes. (By default, this task runs every day at 10 pm.)

3. If you removed an intersite link in Task 1., watch the progress of the task in two locations:

On the Task Definition Basics page for the Remove Objects Associated With Deleted Remote Sites task, where errors, if any, are displayed.

On the Intersite Links page (Networking > Links > Intersite Links in Connection Administration). When the link disappears from this page, the task is complete, and the server is no longer a bridgehead server.


Caution Do not continue reverting the server until the task is complete.

4. If you added this server to the Connection site before you upgraded to the version on the active partition, skip to Task 5. You do not need to remove this member server from the site before you revert.

If you added this server to the Connection site after you upgraded to the version on the active partition, remove this member server from the site. If a cluster is configured, do the task on the publisher server. For more information, see the "Removing a Location From a Cisco Unity Connection Site" section in the "Making Changes to the Networking Configuration in Cisco Unity Connection 8.x" chapter of the Networking Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

5. If no cluster is configured, revert the server. See the "Reverting a Connection 8.x Server to the Version on the Inactive Partition" section.

If a cluster is configured, revert both servers, and reset database replication. See the "Reverting the Servers in a Connection 8.x Cluster to the Version on the Inactive Partition" section.

6. If you removed an intersite link in Task 1. or removed the server from a Connection site in Task 4., if the version you reverted to supports networking, and if you still want the server to be part of a Cisco voicemail organization, set up networking again. See the applicable chapter in the Networking Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.