Upgrading AMPS
Upgrading an AMPS Installation
This chapter describes how to upgrade an existing installation of AMPS. The steps presented here focus on upgrading the installation itself, and should be the only steps you need for upgrades that change the HOTFIX version number or the FEATURE version number (as described in AMPS Versioning and Certification).
For changes that update the MAJOR or MINOR version number, AMPS may add features, change file or network formats, or change behavior. For these upgrades, you may need to make changes to the AMPS configuration file or update applications to adapt to new features or changes in behavior.
60East recommends maintaining a test environment that you can use to test upgrades, particularly when an upgrade changes MAJOR or MINOR versions and you are taking advantage of new features or changed behavior.
When the AMPS instance participates in replication, you must coordinate the instance upgrades when upgrading across AMPS versions.
AMPS supports replication to and from versions 5.2.0.0 and later for the purposes of rolling upgrade. For long-term deployment, 60East recommends that all AMPS instances that replicate to each other have the same MAJOR and MINOR version number, and preferably run the same release of AMPS.
Upgrade Steps
Upgrading an AMPS installation involves the following steps:
Stop the running instance.
Install the new AMPS binaries.
If you are upgrading from an AMPS version prior to 5.0.0.0, upgrade any data files or configuration files that you want to retain.
If necessary, update the configuration file for the instance.
If necessary, update any applications that will use new features.
Restart the service.
AMPS supports replication from version 5.2.0.0 and later to this version of AMPS for the purposes of rolling upgrade with no (or minimal) downtime. 60East recommends that production installations of AMPS have the same MAJOR and MINOR version number at a minimum, and preferably run identical versions of AMPS.
Upgrading AMPS Data Files
AMPS may change the format and content of data files when upgrading across versions, as specified by the MAJOR and MINOR version number. This most commonly occurs when new features are added to AMPS that require different or additional information in the persisted files. The HISTORY file for the AMPS release lists when changes have been made that require data file changes.
When upgrading to AMPS 5.0 or later, from a release prior to 5.0, you must upgrade the data files. For versions of AMPS 5.0 and later, backward compatibility is maintained and therefore there have been no changes to the data file formats.
The AMPS distribution includes the amps_upgrade utility to process and upgrade data files. Unless you are upgrading from a version of AMPS prior to 5.0, there is no need to use this utility when upgrading AMPS.
Downgrading AMPS Data Files
The contents of AMPS data files, including SOW topic files, transaction log journals, and the statistics database are not guaranteed to be backward compatible for versions that change the MAJOR, MINOR, or FEATURE version numbers.
Even when the file format is compatible, newer versions of AMPS may include new options or use metadata in a way that older versions of AMPS are not aware of. Downgrading an instance of AMPS while preserving data files may produce unexpected or incorrect behavior.
Last updated