[DOCS-5812] Add page on migrating a config server to new hardware for both Cloud/Ops Manager using Automation Agent Created: 10/Jul/15  Updated: 11/Jan/17  Resolved: 27/Jul/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: Eoin Brazil Assignee: Anthony Sansone (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Cloud and Ops Manager


Issue Links:
Documented
Duplicate
is duplicated by DOCS-5943 Move config servers that were both Au... Closed
is duplicated by DOCS-6399 Migrating config servers when Cloud/O... Closed
Related
Participants:
Days since reply: 7 years, 29 weeks ago
Epic Link: docs-automation-agent
Story Points: 4

 Description   

Hi All,

The pages on migrating a member to new hardware in Cloud and Ops Managers (https://docs.cloud.mongodb.com/tutorial/migrate-member-to-new-hardware/ or https://docs.opsmanager.mongodb.com/current/tutorial/migrate-member-to-new-hardware/) only refer to a replica set member. Please add a page documenting how to do so for a config server (see https://jira.mongodb.org/browse/MMS-2194 and https://jira.mongodb.org/browse/MMS-2751).

Kindest regards,
Eoin



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Comment by Allison Reinheimer Moore [ 24/Sep/15 ]

Unassigning from me – with config servers are replica sets coming up, we'll need to look at scoping on this ticket to cover both config server strategies.

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