-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Cloud Manager, Ops Manager
-
Labels:None
There is documentation for migrating config servers
http://docs.mongodb.org/manual/tutorial/migrate-config-servers-with-different-hostnames/
http://docs.mongodb.org/manual/tutorial/migrate-config-servers-with-same-hostname/
However, this existing documentation does not say what to do if Cloud/Ops Manager Automation is being used. there should be documentation which describes how to migrate config servers in the presence of automation, ie. automation-aware versions of those docs
One possible approach would be to unmanage the cluster, make change outside Cloud/Ops Manager, then re-import it as follows
- Unmanage processes from Cloud Manager:
https://docs.cloud.mongodb.com/tutorial/unmanage-deployment/#remove-a-process-from-management - Follow the instructions on how to manually change CNAME in a sharded cluster outside Cloud Manager:
- To configure different CNAME
- To retain the same CNAME:
- Finally, re-import existing MongoDB processes for Automation.
https://docs.cloud.mongodb.com//tutorial/add-monitored-deployment-to-automation/
- duplicates
-
DOCS-5812 Add page on migrating a config server to new hardware for both Cloud/Ops Manager using Automation Agent
- Closed