-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cloud Manager, Ops Manager
-
Labels:
-
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
*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
-
0.3
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.
- is documented by
-
-
- Closed
-
