-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
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
*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
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.