[DOCS-9752] Comment on: "mms/tutorial/upgrade-on-prem-with-rpm-packages.txt" Created: 10/Jan/17  Updated: 10/Jan/17  Resolved: 10/Jan/17

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

Type: Bug Priority: Major - P3
Reporter: Emilio Scalise Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/current/tutorial/upgrade-on-prem-with-rpm-packages/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36
Referrer: https://docs.opsmanager.mongodb.com/current/tutorial/nav/upgrade-application/
Screen Resolution: 1680 x 1050


Participants:
Days since reply: 7 years, 5 weeks, 1 day ago

 Description   

This is regarding the Ops Manager 3.4 upgrade guide.

Since Ops Manager upgrades from versions prior to 2.0.x this paragraph may be confusing and not needed:

If you are upgrading from a pre-2.0 Ops Manager Application, and you are also running a Backup Daemon on the machine, shut down the Backup Daemon service:
sudo service mongodb-mms-backup-daemon stop

Maybe we can say that if you have that service (mongodb-mms-backup-daemon) you would need to upgrade first to Ops Manager 2.0.x.


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