[DOCS-5034] Consider Automation deployments in backup restore instructions Created: 17/Mar/15 Updated: 24/Feb/16 Resolved: 21/Sep/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 8 years, 48 weeks, 1 day ago | ||||||||||||
| Description |
|
RE: https://docs.mms.mongodb.com/tutorial/restore-replica-set/#shut-down-the-entire-replica-set The instructions provided for shutting down the replica-set in this instance will not work for automation controlled replica-sets - the agent will simply restart them. For this case, the replica-set should be shutdown via the automation UI. Additionally, some consideration needs to be given to moving the data around on the paths - clearing the local db path for example - as the agent controls the setting of these too. |