This chapter section describes the standard upgrade procedure which is that should be used when minimizing it is important to minimize downtime and ensuring ensure that persisted data is retained. The Standard upgrades must be performed stepwise , i.e. to the next consecutive main or minor version.
...
Note!
Read the Documentation
Ensure to read through all the documentation for the Standard Upgrade Procedure and check out the Release Notes
...
for Important information and Known Issues before proceeding with the Upgrade.
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
This chapter includes the following sections:section contains the following subsections: |
If you plan to upgrade several versions, repeat the steps on the next page and onwards for each version. Use the setup.sh script provided for each version during the upgrade.
| Note |
|---|
Note!There may be changes to certain agents and functions in the new version. Before upgrading, you should take note of any changes or updates that may have happened to your components, as you may have to modify your configuration before it can work with the newer version. See MediationZone Release Information for detailed information about changes in each release. |
| Note |
|---|
Note!If you have a High Availability setup, you are advised to deactivate the failover functionality in the HA cluster daemon. You must ensure that no HA activities can impede the upgrade procedure. |
| Note |
|---|
Note! If you have any of the following configurations in your system:
you will have to perform some additional steps, see the respective page describing the steps for more information. |