[DOCS-9380] Critical updates to upgrade instructions for Ops Manager 3.4.0 Created: 25/Nov/16  Updated: 28/Nov/16  Resolved: 28/Nov/16

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Critical - P2
Reporter: Cailin Nelson Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 7 years, 11 weeks, 5 days ago

 Description   

The following pages need some critical updates:

https://docs.opsmanager.mongodb.com/master/tutorial/upgrade-on-prem-with-rpm-packages/
https://docs.opsmanager.mongodb.com/master/tutorial/upgrade-on-prem-with-deb-packages/
https://docs.opsmanager.mongodb.com/master/tutorial/upgrade-on-prem-from-archive/
https://docs.opsmanager.mongodb.com/master/tutorial/upgrade-on-prem-windows/

Big Picture Summary

Updating from OM 1.8 -> OM 2.0 was a big update, and upgrade documentation is therefore relatively complex. Although it is technically possible to safely upgrade from OM 1.8 -> OM 3.4 directly, for the sake of having simpler upgrade documentation, I think we should document that users must upgrade to OM 2.0 first. The vast majority of customers upgrading to OM 3.4 will be coming from 2.0, so it seems like a shame to keep very complicated documentation for the sake of the few customers who would like to skip over 2.0.

Updates Needed

  1. Direct upgrades are supported to 3.4.0 from 2.0+ (not 1.6+). This appears a few places in the text, including in the Upgrade Path section
  2. Everything in the Considerations is only relevant if upgrading from 1.8 except the note about mms.conf. Remove and replace with the advisories documented in CLOUDP-19154. Please make sure that first two advisories from CLOUDP-19154 are in big red boxes.
  3. Remove the following sections (these were only relevant for upgrading from 1.8)
    1. Uninstall the Backup Daemon package
    2. Copy the connection string to the new Ops Manager instances
    3. Log into Ops Manager as a user with the Global Owner role
    4. Complete the Ops Manager configuration setup
    5. For any Backup Agents that were installed manually, update their configurations to use port 8080

Generated at Thu Feb 08 07:58:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.