- Deploy and Configure MongoDB Database Resources >
- Edit a Database Resource >
- Upgrade Ops Manager and Backing Database Versions
Upgrade Ops Manager and Backing Database Versions¶
On this page
Update the major and minor versions of your Ops Manager instance and backing databases in the Ops Manager Resource Specification that Kubernetes Operator uses to manage your deployment.
Prerequisites¶
Warning
To maintain existing settings and availability, back up the following in your current Ops Manager instance:
- Your
conf-mms.properties
to a secure location. Theconf-mms.properties
stores settings for the Ops Manager instance. - Your
gen.key
files to a secure location. The gen.key provides details to encrypt and decrypt Ops Managers backing databases and user credentials. Ops Manager might delete these files as part of the upgrade process. - Your application database. If the upgrade fails, you need a current backup to restore your Ops Manager instance.
- Upgrade Ops Manager by following the considerations, prerequisites, and procedure in Upgrade Ops Manager.
- Reference Use a Compatible MongoDB Version to ensure your backing databases use a MongoDB version that is compatible with the new Ops Manager version.
- If you need to upgrade your backing databases to a compatible MongoDB version, see Upgrade MongoDB Version and FCV.
Procedure¶
In your Ops Manager Resource Specification, set the following:
- Set
spec.version
to the new Ops Manager version. - If you upgraded your application database, set
spec.applicationDatabase.version
to the compatible MongoDB version. Consider settingspec.featureCompatibilityVersion
to give yourself the option to downgrade if necessary.
For example, the following resource updates Ops Manager from 4.0 to 5.0 and the application database to MongoDB
4.2.11-ent
.- Set
Reapply the configuration to Kubernetes:
Kubernetes automatically reconfigures your deployment with the new specifications. You can see these changes reflected in your Ops Manager or Cloud Manager application.