[DOCS-6399] Migrating config servers when Cloud/Ops Manager Automation is used Created: 19/Oct/15  Updated: 11/Jan/17  Resolved: 13/Jan/16

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

Type: Improvement Priority: Major - P3
Reporter: Jun Wan Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-5812 Add page on migrating a config server... Closed
Related
Participants:
Days since reply: 8 years, 17 weeks, 3 days ago

 Description   

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

  1. Unmanage processes from Cloud Manager:
    https://docs.cloud.mongodb.com/tutorial/unmanage-deployment/#remove-a-process-from-management
  2. Follow the instructions on how to manually change CNAME in a sharded cluster outside Cloud Manager:
  3. Finally, re-import existing MongoDB processes for Automation.
    https://docs.cloud.mongodb.com//tutorial/add-monitored-deployment-to-automation/

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