[DOCS-8155] Start Automation Agent manually Created: 23/Jun/16  Updated: 30/Nov/17  Resolved: 02/Mar/17

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mark Helmstetter Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/current/tutorial/restore-replica-set/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36
Referrer: https://docs.opsmanager.mongodb.com/current/tutorial/nav/backup-restore-deployments/
Screen Resolution: 1920 x 1200


Issue Links:
Documented
is documented by DOCS-9169 Ops Manager documentation for restori... Closed
Related
related to DOCS-8154 Stop all Automation Agents when resto... Closed
related to DOCS-8194 Cloud Manager docs on restoring from ... Closed
Participants:
Days since reply: 7 years, 34 weeks ago
Epic Link: C/OM Automation
Story Points: 0.3

 Description   

Step #8

Restart the primary as part of a replica set.
Use the following sequence:

Shut down the process using one of the following methods:
Automated Deployment:
Shut down through the Ops Manager console. See Shut Down a MongoDB Process.

This doesn't look right at this point the replica set would not have been started via automation, it would have been done manually even when using automation.

The next step:

Restart the process as part of a replica set:

Should instruct the user to start the automation agent, and then startup the member via the Ops Manager UI.


Generated at Thu Feb 08 07:55:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.