[DOCS-11157] Do not backup mongodb_version_manifest.json when upgrading Ops Manager Created: 27/Dec/17 Updated: 29/Oct/23 Resolved: 30/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Joanna Cheng | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 2 weeks ago | ||||
| Epic Link: | DOCSP-1743 | ||||
| Description |
|
https://docs.opsmanager.mongodb.com/current/tutorial/upgrade-on-prem-from-archive/ In step 2 the user is requested to backup the conf folder, and in step 5 to restore it. However this means they will have an older version of mongodb_version_manifest.json. I think this file should be excluded from the backup. |
| Comments |
| Comment by Githook User [ 01/Feb/18 ] |
|
Author: {'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 01/Feb/18 ] |
|
Author: {'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 01/Feb/18 ] |
|
Author: {'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone', 'username': 'atsansone'}Message: ( |
| Comment by Allison Reinheimer Moore [ 28/Dec/17 ] |
|
Pinging tony.sansone on this one to finish triaging the tweak. |