[DOCS-9840] Need of monitoring agent during an automatic restore Created: 31/Jan/17 Updated: 27/Mar/17 Resolved: 27/Mar/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Diana Esteves (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | restore | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Cloud Manager group with two clusters on different AWS VPCs such that the Monitoring agent in cluster A cannot ping nodes in cluster B. |
||
| Participants: | |
| Days since reply: | 6 years, 46 weeks, 2 days ago |
| Epic Link: | C/OM Backup |
| Story Points: | 0.3 |
| Description |
|
https://docs.cloudmanager.mongodb.com/core/restore-overview/#automated-restore The documented requirements on performing an automated restore need to be updated to also include a monitoring agent at least for the environment described above to work. We had to bring another monitoring agent in cluster B and shut down the one in cluster A in order for the automatic restore option to become available. |
| Comments |
| Comment by Githook User [ 27/Mar/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |
| Comment by Githook User [ 27/Mar/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |
| Comment by Githook User [ 27/Mar/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |