[DOCS-5462] Ops Manager Local Mode does not include necessary steps for modifying daemon config files Created: 19/May/15  Updated: 11/Jan/17  Resolved: 08/Jan/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Major - P3
Reporter: Rachelle Palmer Assignee: Bob Grabar
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: 8 years, 38 weeks, 1 day ago

 Description   

on this page https://docs.opsmanager.mongodb.com/current/tutorial/configure-local-mode/ we have a very good step by step tutorial on how to configure local mode.
however we are missing the critical additional step that if a customer is running backup, they will also need to update the conf-daemon.properties file fiels

  • mongodb.release.directory=/opt/mongodb/mms-backup-daemon/mongodb-releases/
  • mongodb.release.autoDownload=true

and populate that release directory manually as well.

This is actually discussed in the documentation here https://docs.opsmanager.mongodb.com/current/reference/configuration/#conf-daemon-properties for the two fields, but never referenced in the local mode instructions.



 Comments   
Comment by Andrew Davidson [ 26/May/15 ]

This would be best handled in a informational box that introduces the concept:

Ops Manager has two processes that require the ability to access MongoDB binaries:

  • Automation agents
  • Backup daemons

By default, both will try to download the necessary version from the internet, when required.
However, both can also be configure to utilize local binaries instead:

  • Ops Manager can be configured so that Automation agents download compressed binaries from Ops Manager. See the settings described here and tutorial below
  • The Backup daemon can be configured to be pre-seeded with the extracted binaries it requires, as described here
Generated at Thu Feb 08 07:50:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.