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
> The Single to Flex Migration tool is available in all Azure regions and currently supports **Offline** migrations. Support for **Online** migrations is currently available in select regions - India Central, India South, Australia Southeast and South East Asia.
120
-
121
-
If **Online** migration is selected, it requires Logical replication to be turned on in the source Single server. If it isn't turned on, the migration tool automatically turns on logical replication at the source Single server. Replication can also be set up manually at the source using the below command. Note that either approach of turning on logical replication restarts the source Single server.
The `migration-name` argument used in the `create` command is used in other CLI commands, such as `update`, `delete`, and `show.` In all those commands, it uniquely identifies the migration attempt in the corresponding actions.
136
119
137
120
Finally, the `create` command needs a JSON file to be passed as part of its `properties` argument.
@@ -186,6 +169,29 @@ Note these important points for the command response:
186
169
- The time that the `Migrating Data` substate takes to finish depends on the size of databases that are migrated.
187
170
- The migration moves to the `Succeeded` state as soon as the `Migrating Data` substate finishes successfully. If there's a problem at the `Migrating Data` substate, the migration moves into a `Failed` state.
188
171
172
+
> [!NOTE]
173
+
> The Single to Flex Migration tool is available in all Azure regions and currently supports **Offline** migrations. Support for **Online** migrations is currently available in select regions - India Central, India South, Australia Southeast and South East Asia.
174
+
175
+
#### Setup replication
176
+
177
+
If **Online** migration is selected, it requires Logical replication to be turned on in the source Single server. If it isn't turned on, the migration tool automatically turns on logical replication at the source Single server when the `SetupLogicalReplicationOnSourceDBIfNeeded` parameter is passed with a value of `true` in the accompanying JSON file. Replication can also be set up manually at the source after starting the migration, using the below command. Note that either approach of turning on logical replication restarts the source Single server.
This command is required to advance the migration when the flexible server is waiting in the `WaitingForLogicalReplicationSetupRequestOnSourceDB` state.
186
+
187
+
:::image type="content" source="./media/concepts-single-to-flexible/az-postgres-flexible-server-migration-logical-replication.png" alt-text="Screenshot of logical replication set up." lightbox="./media/concepts-single-to-flexible/az-postgres-flexible-server-migration-logical-replication.png":::
188
+
189
+
To perform Online migration in any of the above regions, use:
> Gentle reminder to [allowlist the extensions](./concepts-single-to-flexible.md#allowlist-required-extensions) before you execute **Create** in case it is not yet done. It's important to allow-list the extensions before you initiate a migration using this tool.
0 commit comments