
Chapter 14: Upgrade fundamentals
This chapter describes the following upgrade paths:
• Release 2.x to Release 3.0 upgrade
• Release 3.0 to Release 3.1 upgrade
• Service Upissue upgrade
• Converting to a redundant configuration
Important:
Use the server system console for installations and upgrades. Do not use a remote terminal.
Warning:
During upgrades, users are logged out of the server being upgraded and redirected to the standby
system (if available). Schedule the upgrade during off-peak hours to minimize user impact.
In redundant systems, you upgrade one server and return it to service before upgrading the second server.
Where possible, do not change the way that users access the system (for example, the IP address or
Fully Qualified Domain Name).
When the mobile client applications require updating, you should instruct your users to record their login
configuration, so that they can restore their configuration after the upgrade completes.
If the initial installation is a standalone configuration you can convert to a redundant configuration.
Navigation
•
Upgrade work flow on page 136
•
Upgrading from Release 2.x to Release 3.0 on page 136
• Upgrading from Release 3.0 to Release 3.1 on page 139
• Upgrading for a Service Upissue on page 147
• Converting to a redundant configuration on page 148
Deployment Guide October 2010 135
Komentáře k této Příručce