-
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.5
These steps should include that the automation agent needs to be stopped on all replica members. Otherwise when the mongod is started to initialize the repl set and/or seeding the secondary, automation will stop it.
- is documented by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
DOCS-8194 Cloud Manager docs on restoring from backup should mention disabling automation.
-
- Closed
-