Polycom 3725-76302-001O manual Polycom, Inc 388

Caution: Upgrade Considerations

Always check the upgrade version release notes before installing an upgrade.

The upgrade installation process automatically creates a backup, which enables you to roll back an upgrade (restore the previous version) if necessary. As a precaution, however, we recommend that you download a recent backup file before you begin to install an upgrade. See Backing Up and Restoring on page 374.

You can roll back only the last applied upgrade. Rolling back an upgrade restores the database to its state prior to the upgrade, so data may be lost.

The procedure below is for applying a major or minor software upgrade (not supercluster-compatible) to a superclustered system.

To minimize the time required for an upgrade:

•Obtain the license activation key(s) ahead of time.

•On each cluster, download a recent backup and upload the upgrade package file (the first two steps below) ahead of time.

Perform the remainder of the procedure during a maintenance window when there are no calls or conferences so that you can immediately take all the clusters out of service instead of having to wait for all activity to end.

To upgrade a supercluster by taking all clusters out of service

1Put the upgrade package file somewhere on or accessible from your PC.

2On each cluster in the supercluster, do the following: a Go to Maintenance > Software Upgrade.

b In the Actions list, click Upload.

c Select the upgrade package file and click Open.

The File Upload dialog box indicates when the upload is complete.

dClick Close.

The Upgrade Package Details section displays information about the file you uploaded. The description includes an estimated install time.

eVerify that the upgrade package is correct.

3On any cluster in the supercluster, do the following:

a Go to Network > Site Topology > Territories and record each territory’s primary and backup cluster, whether it hosts conference rooms, and associated sites.

You may need this information later to restore the configuration.

bIf there are no active calls and conferences, skip to d. Otherwise, go to Network > RealPresence DMAs and busy out each cluster in the supercluster.

This permits existing calls and conferences to continue, but prevents new conferences and point-to-point calls from starting.

cOn the Dashboard, monitor the Call Server Active Calls and Conference Manager MCUs panes.

dWhen all calls and conferences have ended, go to Network > RealPresence DMAs and stop using each cluster in the supercluster.

This completely shuts down the supercluster.

Polycom, Inc. 388