[DOCS-6788] Changes to Ops Manager docs for 2.0 Created: 11/Dec/15  Updated: 11/Jan/17  Resolved: 21/Feb/16

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

Type: Bug Priority: Critical - P2
Reporter: Joanna Cheng Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-7439 step 2 in "Install a Simple Test Ops ... Closed
Participants:
Days since reply: 8 years, 3 weeks, 2 days ago

 Description   

https://docs.opsmanager.mongodb.com/current/tutorial/install-simple-test-deployment/
The repo details as specified install 2.6.11 - shouldn't we get people to go to 3.0? (This is a test deployment, so I guess it's not that important)

https://docs.opsmanager.mongodb.com/current/tutorial/install-simple-test-deployment/#if-you-will-use-the-backup-feature-configure-the-backup-daemon-and-backup-storage
No more backup daemon in Ops Manager 2.0. There are a heap of places where there are still references to the backup daemon.



 Comments   
Comment by Ronan Bohan [ 25/Jan/16 ]

For the second point, similar to initial report there are pages specifically for Ops Manager 2.0 which relate more to an Ops Manager 1.x deployment, e.g. https://docs.opsmanager.mongodb.com/current/core/deployments/ shows separate Ops Manager Application and Backup Daemon. In addition it does not show (or mention) anything about the filesystem store - all the images show and the text references just the Blockstore database.

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