[DOCS-9171] Missing an explanation on how to stop/start the backup agent if managed by automation Created: 19/Oct/16 Updated: 01/Feb/18 Resolved: 30/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tomer Yakir | Assignee: | Robert Justice (Inactive) |
| Resolution: | Won't Fix | Votes: | 8 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 2 weeks, 1 day ago |
| Epic Link: | DOCSP-1743 |
| Story Points: | 0.4 |
| Description |
|
Hi, It seems like the current documentation doesn't explain how to stop and start the backup agent if it's installed via the automation agent. Can this be fixed please? Thanks, |
| Comments |
| Comment by Timothy Olsen (Inactive) [ 30/Jan/18 ] |
|
If managed by the automation agent, then there should be no command line commands for starting/stopping the monitoring and backup agents. Instead, those agents should be managed via the Cloud/Ops Manager UI or by adding/removing them to/from the automation agent config file (via the public API). If a user tries to manage them by the command line then the automation agent will undo what the user did. |
| Comment by Tomer Yakir [ 31/Jan/17 ] |
|
While at it, we need the same for the Monitoring Agent |