[DOCS-6709] Ops Manager upgrade docs don't mention anything about upgrading the backing databases Created: 03/Dec/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Bob Grabar |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-upgrade |
| Description |
|
My understanding is the backing databases should be upgraded first, and then the App / Backup daemon. This could be as easy as putting a line in the prerequisites section (e.g. https://docs.opsmanager.mongodb.com/v1.8/tutorial/upgrade-on-prem-with-deb-packages/#prerequisite) mentioning the minimum version of MongoDB required for the backing databases, and pointing at MongoDb upgrade documentation |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |