[DOCS-3021] audit cluster upgrade docs to ensure config backup is a step Created: 27/Mar/14 Updated: 31/Mar/14 Resolved: 31/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-slipstream | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 46 weeks, 2 days ago | ||||||||
| Description |
|
We want to make sure the cluster upgrade docs mention that taking a backup of the config database before the upgrade is always recommended, for paranoia's sake. This may be a no-op, but is important to confirm. For 2.6.0. |
| Comments |
| Comment by Githook User [ 31/Mar/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |