- Install Ops Manager >
- Upgrade Ops Manager
Upgrade Ops Manager¶
On this page
Upgrade Path¶
The version of your existing Ops Manager installation determines your upgrade path. The following table lists upgrade paths per version:
Existing Version | Upgrade Path |
---|---|
2.0 or later | Ops Manager supports direct upgrades from version 2.0.x. Use this tutorial to upgrade directly to 3.4.0. |
1.8 or earlier |
|
There are no supported downgrade paths for Ops Manager.
Important
It is crucial that you back up the existing conf-mms.properties
and gen.key
files because the upgrade process will delete
existing data.
Advisories¶
Before upgrading Ops Manager from 2.0.x to 3.4, complete the following actions:
Upgrade backing databases to at least MongoDB 3.0.8. MongoDB 2.6 is no longer allowed as a backing store.
Ensure the data partitions for the Ops Manager Application Database have at least 50% free disk space.
Once the Ops Manager upgrade to 3.4 completes, Ops Manager begins migrating of all monitoring data to a new schema in the background. This migration requires significant free disk space.
Add necessary IP addresses or CIDR blocks for to the whitelists for any API clients connecting to the Automation configuration endpoints.
Back up the
mms.conf
file in your current installation if you have modified it.This is not a regular practice as
mms.conf
contains platform and network administration settings for Java VM and Ops Manager network port settings. You must use the newmms.conf
file the upgrade installs. Reapply any modifications from your backed up copy to the newmms.conf
after completing the upgrade.
Procedures¶
- Upgrade with RPM Package
- Upgrade Ops Manager on Red Hat, Fedora, CentOS, and Amazon AMI Linux.
- Upgrade with DEB Package
- Upgrade Ops Manager on Debian and Ubuntu systems.
- Upgrade from Archive on Linux
- Upgrade Ops Manager on other Linux systems, without using package management.
- Upgrade on Windows
- Upgrade Ops Manager on Windows systems.