[DOCS-7571] Inconsistency on Oplog Stores Page Created: 04/Apr/16  Updated: 12/Apr/16  Resolved: 11/Apr/16

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

Type: Task Priority: Major - P3
Reporter: Rachelle Palmer Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 45 weeks, 2 days ago
Epic Link: C/OM Backup

 Description   

Text:
Do not modify the oplog store’s connection string to point to a different replica set. Doing so requires all Ops Manager components to be restarted. Existing data will not be copied automatically.

Then...
WARNING
After you save changes to the oplog store’s connection string, you must restart all the Ops Manager instances, including those running activated Backup Daemons, for the changes to take effect.

page: https://docs.opsmanager.mongodb.com/current/core/administration-interface/#oplog-stores-page

So... don't modify it, but... modify it and make sure to save?


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