You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(DOCSP-29921) Push live migration backed by c2c: changes on the Cloud Manager side (#5106) (#5140)
* (DOCSP-29921) Push live migration backed by c2c, changes on the cloud manager side
* Added info, added copy review comments, ready for a tech review
* Edits, ready for a tech review
* Periodic commit, tech review, to be continued
* Tech review completed, ready for a second round of review by Pia
* Tech review, second round
* Tech review from Pia, after the meeting. Adjusted the deprecation note to shorten it and only indicate deprecation of OM support for push LM, also revamped the top-most migration topic in CM and OM docs to account for c2c-based LM options, organized that content similar to Atlas, to be version-centric until further revisions when c2c starts supporting all needed versions. Ready for a final review I hope.
* Fix typo and move two more options into the 6.0.5 section, per comments from Pi
* Final copy review, ready for merge
* Fix the font for the deprecation note
If both the source and destination clusters are running MongoDB 6.0.5 or
21
+
later, you can migrate your data from a source cluster into a destination
22
+
MongoDB cluster in |service-short| using one of the following types of
23
+
guided live migration in the |service| UI:
24
+
25
+
- Live migration (push). For instructions, see :atlas:`Live Migrate Your MongoDB 6.0.5+ Cluster Monitored by Cloud Manager to Atlas <c2c-push-live-migration>`.
26
+
- Live migration (pull). For instructions, see :atlas:`Live Migrate (Pull) a MongoDB 6.0.5+ Cluster into Atlas <c2c-pull-live-migration>`.
27
+
28
+
The choice between push and pull live migrations depends on whether the
29
+
network for your deployment allows flexibility in ingress rules and allows
30
+
access through the firewall.
31
+
32
+
In addition, you can use these migration methods for MongoDB 6.0.5 and later
33
+
deployments:
34
+
35
+
- If your data is in a MongoDB deployment and you don't have access to the :term:`oplog`,
36
+
You can use :binary:`mongorestore <bin.mongorestore>` to run a self-managed migration.
37
+
To learn more, see :atlas:`Seed with mongorestore </import/mongorestore/>`.
38
+
39
+
.. cond:: cloud
40
+
41
+
- If your data is in |mms| and you have a :term:`snapshot`, you can
42
+
:ref:`restore a backup of a deployment to an Atlas deployment <restore-deployment-to-atlas>`.
43
+
44
+
45
+
.. _mongomirror-based-live-migration-choices:
46
+
47
+
Earlier MongoDB Versions: Live Migrate to Atlas
48
+
-----------------------------------------------
49
+
50
+
If you are migrating MongoDB versions earlier than 6.0.5, use one of the
51
+
following migration methods, depending on your deployment's requirements
52
+
and configuration.
18
53
19
54
.. cond:: onprem
20
55
@@ -24,42 +59,38 @@ configurations into |service|.
24
59
25
60
* - Deployment Configuration
26
61
- Migration Strategy
27
-
28
-
* - Your data is in |mms| and your network allows flexibility in
62
+
63
+
* - Your data is in a cluster running MongoDB earlier than 6.0.5,
64
+
is managed or monitored by |mms| and your network allows flexibility in
29
65
ingress rules.
30
66
31
67
- :atlas:`Pull data into Atlas </migration-live-atlas-managed>`
32
-
from |mms|. In this type of Live Migration, |service| requires
68
+
from |mms|. In this type of live migration, |service| requires
33
69
access to the source deployment in |mms| through
34
70
the deployment's firewall.
35
71
36
-
* - Your data is in |mms| and your network doesn't allow
37
-
flexibility in ingress rules.
72
+
* - Your data is in a cluster running MongoDB earlier than 6.0.5,
73
+
your cluster is managed or monitored by |mms|, and your network doesn't
74
+
allow flexibility in ingress rules.
38
75
39
76
- :ref:`Push your data into Atlas <migrate-to-atlas>` from |mms|.
40
-
In this type of Live Migration, |service| receives data from
77
+
In this type of live migration, |service-short| receives data from
41
78
|mms| without requiring access through the firewall.
42
79
43
-
* - Your data is in MongoDB Community and your network doesn't
44
-
allow flexibility in ingress rules.
80
+
* - Your data is in a MongoDB Community cluster running MongoDB earlier than 6.0.5,
81
+
and your network doesn't allow flexibility in ingress rules.
45
82
46
83
- :ref:`Push your MongoDB Community data into Atlas <migrate-community-to-atlas>`
47
-
after adding your Community deployment to |mms|.
48
-
In this type of Live Migration, |service| receives data from
84
+
after adding your Community deployment to |cloud-short| for monitoring.
85
+
In this type of live migration, |service-short| receives data from
49
86
|mms| without requiring access through the firewall.
50
87
51
-
52
-
53
-
* - Your data is in a MongoDB deployment and you don't have access
54
-
to the :term:`oplog`.
55
-
- Use :binary:`mongorestore <bin.mongorestore>` to run a
56
-
self-managed migration. To learn more, see
57
-
:atlas:`Seed with mongorestore </import/mongorestore/>`.
88
+
* - Your data is in a MongoDB deployment and you don't have access to the :term:`oplog`.
89
+
- Use :binary:`mongorestore <bin.mongorestore>` to run a self-managed migration.
90
+
To learn more, see :atlas:`Seed with mongorestore </import/mongorestore/>`.
58
91
59
-
You can also migrate a MongoDB deployment from one |mms| project
60
-
to another project. To learn more, see
61
-
:ref:`Migrate a MongoDB Deployment to a New Project
62
-
<migrate-deployment-to-new-project>`.
92
+
You can also migrate a MongoDB deployment from one |mms| project to another
93
+
project. To learn more, see :ref:`Migrate a MongoDB Deployment to a New Project <migrate-deployment-to-new-project>`.
63
94
64
95
.. cond:: cloud
65
96
@@ -70,39 +101,41 @@ configurations into |service|.
70
101
* - Deployment Configuration
71
102
- Migration Strategy
72
103
73
-
* - Your data is in |mms|, and your network allows flexibility in
104
+
105
+
106
+
* - Your data is in a cluster running MongoDB earlier than 6.0.5,
107
+
is managed or monitored by |mms| and your network allows flexibility in
74
108
ingress rules.
75
109
76
110
- :atlas:`Pull data into Atlas </migration-live-atlas-managed>`
77
-
from |mms|. In this type of Live Migration, |service|
111
+
from |mms|. In this type of live migration, |service-short|
78
112
requires access to the source deployment in |mms| through
79
113
the deployment's firewall.
80
114
81
-
* - Your data is in |mms|, and your network doesn't allow
82
-
flexibility in ingress rules.
83
-
115
+
* - Your data is in a cluster running MongoDB earlier than 6.0.5,
116
+
your cluster is managed or monitored by |mms|, and your network doesn't
117
+
allow flexibility in ingress rules.
118
+
84
119
- :ref:`Push your data into Atlas <migrate-to-atlas>` from |mms|.
85
-
In this type of Live Migration, |service| receives data from
120
+
In this type of live migration, |service-short| receives data from
86
121
|mms| without requiring access through the firewall.
87
122
88
-
* - Your data is in MongoDB Community and your network doesn't
89
-
allow flexibility in ingress rules.
90
-
123
+
* - Your data is in a MongoDB Community cluster running MongoDB earlier than 6.0.5,
124
+
and your network doesn't allow flexibility in ingress rules.
125
+
91
126
- :ref:`Push your MongoDB Community data into Atlas <migrate-community-to-atlas>`
92
-
after adding your Community deployment to |mms|.
93
-
In this type of Live Migration, |service| receives data from
127
+
after adding your Community deployment to |cloud-short| for monitoring.
128
+
In this type of live migration, |service-short| receives data from
94
129
|mms| without requiring access through the firewall.
95
130
96
131
* - Your data is in |cloud-short| and you have a :term:`snapshot`.
97
132
98
133
- :doc:`Restore a backup of a deployment to an Atlas deployment
99
134
</tutorial/restore-deployment-to-atlas>`.
100
135
101
-
* - Your data is in a MongoDB deployment and you don't have access
102
-
to the :term:`oplog`.
103
-
- Use :binary:`mongorestore <bin.mongorestore>` to run a
104
-
self-managed migration. To learn more, see
105
-
:atlas:`Seed with mongorestore </import/mongorestore/>`.
136
+
* - Your data is in a MongoDB deployment and you don't have access to the :term:`oplog`.
137
+
- Use :binary:`mongorestore <bin.mongorestore>` to run a self-managed migration.
138
+
To learn more, see :atlas:`Seed with mongorestore </import/mongorestore/>`.
0 commit comments