[DOCS-5465] Restore from backup doesn't integrate potential automation users Created: 19/May/15 Updated: 27/Jul/16 Resolved: 21/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | mms-1.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Daniels (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 7 years, 43 weeks ago | ||||||||||||||||
| Epic Link: | docs-restore-data | ||||||||||||||||
| Story Points: | 2 | ||||||||||||||||
| Description |
|
For example, see https://docs.opsmanager.mongodb.com/v1.6/tutorial/restore-replica-set/. These steps have no context of using Automation. If I were to follow the steps for existing hardware and make new directories, this would invalidate the automation config for the deployment. There should be a guide on how to restore if you are using automation. |
| Comments |
| Comment by Eric Daniels (Inactive) [ 21/Apr/16 ] |
|
Yep! |
| Comment by Eric Daniels (Inactive) [ 20/Apr/16 ] |
|
I agree |
| Comment by Eric Daniels (Inactive) [ 19/Apr/16 ] |
|
I didn't see that before. Maybe this is Gone Away |
| Comment by Steve Briskin (Inactive) [ 19/Apr/16 ] |
|
eric.daniels@10gen.com, can you clarify what steps would clash with automation? Instruction say that automated deployments must be stopped before following these steps and there are no new directories created. |
| Comment by Ian Bentley [ 15/Apr/16 ] |
|
If you use the restore with automation option, and the destination is automated, then it's simple. Otherwise, you probably need to bring everything down with automation, follow the normal restore procedure, and then bring everything back up. This is essentially what they are asking for here: https://jira.mongodb.org/browse/DOCS-5420 |