Skip to content

Commit 72d5a7c

Browse files
authored
Merge pull request #278324 from markingmyname/single
[PostgreSQL] [Migration Service] Single Server updates
2 parents 3f1cb2b + 757e998 commit 72d5a7c

18 files changed

+43
-21
lines changed

articles/postgresql/.openpublishing.redirection.postgresql.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1634,6 +1634,11 @@
16341634
"source_path_from_root": "/articles/postgresql/migrate/migration-service/concepts-migration-service-postgresql.md",
16351635
"redirect_url": "/azure/postgresql/migrate/migration-service/overview-migration-service-postgresql",
16361636
"redirect_document_id": true
1637+
},
1638+
{
1639+
"source_path_from_root": "/articles/postgresql/migrate/migration-service/troubleshoot-error-codes-premigration.md",
1640+
"redirect_url": "/azure/postgresql/migrate/migration-service/troubleshoot-error-codes",
1641+
"redirect_document_id": true
16371642
}
16381643
]
16391644
}

articles/postgresql/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -576,7 +576,7 @@
576576
href: migrate/migration-service/how-to-network-setup-migration-service.md
577577
- name: Troubleshoot
578578
items:
579-
- name: Known errors
579+
- name: Troubleshoot errors
580580
href: migrate/migration-service/troubleshoot-error-codes-premigration.md
581581
- name: Migrate data with pg_dump
582582
href: migrate/how-to-migrate-using-dump-and-restore.md

articles/postgresql/migrate/migration-service/how-to-setup-azure-cli-commands-postgresql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ All the CLI commands start with `az postgres flexible-server migration`. There a
3131
Once the CLI is installed, open the command prompt and log into the Azure account using the below command.
3232

3333
```azurecli-interactive
34-
`az login`
34+
az login
3535
```
3636

3737
## Migrate commands
@@ -43,7 +43,7 @@ The migration service provides the following commands to help you migrate your P
4343
The `--help` command in Azure CLI is a valuable option that provides detailed documentation about the commands and their subcommands, including the required verbs for operations. The `–-help`command displays the necessary commands and their associated actions for migration service in Azure Database for PostgreSQL.
4444

4545
```azurecli-interactive
46-
`az postgres flexible-server migration –-help`
46+
az postgres flexible-server migration –-help
4747
```
4848

4949
The output guides you through the necessary steps and parameters required to manage your database migrations effectively using the Azure CLI.

articles/postgresql/migrate/migration-service/includes/single-server/postgresql-single-server-portal-migrate.md

Lines changed: 24 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ Alternatively, you can initiate the migration process from the Azure Database fo
6161

6262
After deploying the Flexible Server, follow the steps 3 to 5 under [Configure the migration task.](#configure-the-migration-task)
6363

64-
### Setup tab
64+
### Setup
6565

6666
The first tab is **Setup**. In case you missed it, allowlist necessary extensions as shown in It's essential to allowlist these extensions before you initiate a migration.
6767

@@ -82,7 +82,15 @@ If the **Online** migration is selected, Logical replication must be turned on i
8282

8383
Select the **Next : Connect to Source** button.
8484

85-
### Source tab
85+
### Runtime Server
86+
87+
The Migration Runtime Server is a specialized feature within the [migration service in Azure Database for PostgreSQL](../../overview-migration-service-postgresql.md), designed to act as an intermediary server during migration. It's a separate Azure Database for PostgreSQL - Flexible Server instance that isn't the target server but is used to facilitate the migration of databases from a source environment that is only accessible via a private network.
88+
89+
:::image type="content" source="../../media/tutorial-migration-service-single-to-flexible/02-portal-offline-runtime-server-migration-single-server.png" alt-text="Screenshot of the Migration Runtime Server page.":::
90+
91+
For more information about the Runtime Server, visit the [Migration Runtime Server](../../concepts-migration-service-runtime-server.md).
92+
93+
### Connect to source
8694

8795
The **Source** tab prompts you to give details related to the Single Server, which is the source of the databases.
8896

@@ -96,7 +104,7 @@ After filling out all the fields, select the **Connect to source** link. This va
96104

97105
Select the **Next : Select migration target** button to continue.
98106

99-
### Target tab
107+
### Select migration target
100108

101109
The **Target** tab displays metadata for the Flexible Server target, such as subscription name, resource group, server name, location, and PostgreSQL version.
102110

@@ -106,7 +114,7 @@ For **Server admin login name**, the tab displays the admin username used during
106114

107115
Select the **Next** button to select the databases to migrate.
108116

109-
### Select Databases for the migration tab
117+
### Select database for migration
110118

111119
Under this tab, there's a list of user databases inside the Single Server. You can select and migrate up to eight databases in a single migration attempt. If there are more than eight user databases, the migration process is repeated between the source and target servers for the next set of databases. By default, selected databases with the same name on the target are overwritten.
112120

@@ -232,7 +240,7 @@ Alternatively, you can initiate the migration process from the Azure Database fo
232240

233241
After deploying the Flexible Server, follow the steps 3 to 5 under [Configure the migration task.](#configure-the-migration-task)
234242

235-
### Setup tab
243+
### Setup
236244

237245
The first tab is **Setup**. In case you missed it, allowlist necessary extensions as shown in It's essential to allowlist these extensions before you initiate a migration.
238246

@@ -253,7 +261,15 @@ If the **Online** migration is selected, Logical replication must be turned on i
253261

254262
Select the **Next : Connect to Source** button.
255263

256-
### Source tab
264+
### Runtime Server
265+
266+
The Migration Runtime Server is a specialized feature within the [migration service in Azure Database for PostgreSQL](../../overview-migration-service-postgresql.md), designed to act as an intermediary server during migration. It's a separate Azure Database for PostgreSQL - Flexible Server instance that isn't the target server but is used to facilitate the migration of databases from a source environment that is only accessible via a private network.
267+
268+
:::image type="content" source="../../media/tutorial-migration-service-single-to-flexible/02-portal-online-runtime-server-migration-single-server.png" alt-text="Screenshot of the Migration Runtime Server page.":::
269+
270+
For more information about the Runtime Server, visit the [Migration Runtime Server](../../concepts-migration-service-runtime-server.md).
271+
272+
### Connect to source
257273

258274
The **Source** tab prompts you to give details related to the Single Server, which is the source of the databases.
259275

@@ -267,7 +283,7 @@ After filling out all the fields, select the **Connect to source** link. This va
267283

268284
Select the **Next : Select migration target** button to continue.
269285

270-
### Target tab
286+
### Select migrfation target
271287

272288
The **Target** tab displays metadata for the Flexible Server target, such as subscription name, resource group, server name, location, and PostgreSQL version.
273289

@@ -277,7 +293,7 @@ For **Server admin login name**, the tab displays the admin username used during
277293

278294
Select the **Next** button to select the databases to migrate.
279295

280-
### Select Databases for the migration tab
296+
### Select database for the migration
281297

282298
Under this tab, there's a list of user databases inside the Single Server. You can select and migrate up to eight databases in a single migration attempt. If there are more than eight user databases, the migration process is repeated between the source and target servers for the next set of databases. By default, selected databases with the same name on the target are overwritten.
283299

Loading
Loading
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)