Skip to content

Commit 082d4ee

Browse files
authored
Merge pull request #278336 from MicrosoftDocs/release-postgresql-migrations
[PostgreSQL] New Content for migration service for online migrations and updates with runtime sever added with new images -- 06/18/2024 3PM
2 parents e1c8348 + 4d03e56 commit 082d4ee

File tree

158 files changed

+2033
-1215
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

158 files changed

+2033
-1215
lines changed

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

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1619,6 +1619,26 @@
16191619
"source_path_from_root": "/articles/postgresql/flexible-server/concepts-compute-storage.md",
16201620
"redirect_url": "/azure/postgresql/flexible-server/concepts-compute",
16211621
"redirect_document_id": false
1622+
},
1623+
{
1624+
"source_path_from_root": "/articles/postgresql/migrate/migration-service/tutorial-migration-service-aws.md",
1625+
"redirect_url": "/azure/postgresql/migrate/migration-service/tutorial-migration-service-aws-offline",
1626+
"redirect_document_id": true
1627+
},
1628+
{
1629+
"source_path_from_root": "/articles/postgresql/migrate/migration-service/tutorial-migration-service-iaas.md",
1630+
"redirect_url": "/azure/postgresql/migrate/migration-service/tutorial-migration-service-iaas-offline",
1631+
"redirect_document_id": true
1632+
},
1633+
{
1634+
"source_path_from_root": "/articles/postgresql/migrate/migration-service/concepts-migration-service-postgresql.md",
1635+
"redirect_url": "/azure/postgresql/migrate/migration-service/overview-migration-service-postgresql",
1636+
"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
16221642
}
16231643
]
16241644
}

articles/postgresql/TOC.yml

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -543,32 +543,40 @@
543543
- name: Migration Service
544544
items:
545545
- name: Overview
546-
href: migrate/migration-service/concepts-migration-service-postgresql.md
546+
href: migrate/migration-service/overview-migration-service-postgresql.md
547547
- name: Tutorials
548548
items:
549549
- name: Migrate from Single Server
550550
href: migrate/migration-service/tutorial-migration-service-single-to-flexible.md
551-
- name: Migrate from on-premises or Azure VM
552-
href: migrate/migration-service/tutorial-migration-service-iaas.md
553-
- name: Migrate from AWS RDS
554-
href: migrate/migration-service/tutorial-migration-service-aws.md
551+
- name: Migrate from an Azure VM or an on-premises PostgreSQL server offline
552+
href: migrate/migration-service/tutorial-migration-service-iaas-offline.md
553+
- name: Migrate from an Azure VM or an on-premises PostgreSQL server online
554+
href: migrate/migration-service/tutorial-migration-service-iaas-online.md
555+
- name: Migrate from AWS RDS offline
556+
href: migrate/migration-service/tutorial-migration-service-aws-offline.md
557+
- name: Migrate from AWS RDS online
558+
href: migrate/migration-service/tutorial-migration-service-aws-online.md
555559
- name: Concepts
556560
items:
557561
- name: Premigration validation
558562
href: migrate/migration-service/concepts-premigration-migration-service.md
559563
- name: User roles and permissions
560564
href: migrate/migration-service/concepts-user-roles-migration-service.md
565+
- name: Runtime Server
566+
href: migrate/migration-service/concepts-migration-service-runtime-server.md
561567
- name: Best practices
562568
href: migrate/migration-service/best-practices-migration-service-postgresql.md
563569
- name: Known issues and limitations
564570
href: migrate/migration-service/concepts-known-issues-migration-service.md
565571
- name: How-to guides
566572
items:
567-
- name: Network setup
573+
- name: How to set up Azure CLI
574+
href: migrate/migration-service/how-to-setup-azure-cli-commands-postgresql.md
575+
- name: How to set up the network
568576
href: migrate/migration-service/how-to-network-setup-migration-service.md
569577
- name: Troubleshoot
570578
items:
571-
- name: Premigration error codes
579+
- name: Troubleshoot errors
572580
href: migrate/migration-service/troubleshoot-error-codes-premigration.md
573581
- name: Migrate data with pg_dump
574582
href: migrate/how-to-migrate-using-dump-and-restore.md

articles/postgresql/migrate/migration-service/concepts-known-issues-migration-service.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,8 @@ Here are common limitations that apply to migration scenarios:
5353

5454
- Migration to burstable SKUs isn't supported; databases must first be migrated to a non-burstable SKU and then scaled down if needed.
5555

56+
- The Migration Runtime Server is specifically designed to operate with the default DNS servers/private DNS zones i.e., **privatelink.postgres.database.azure.com**. Custom DNS names/DNS servers are not supported by the migration service when utilizing the migration runtime server feature. When configuring private endpoints for both the source and target databases, it is imperative to use the default private DNS zone provided by Azure for the private link service. The use of custom DNS configurations is not yet supported and may lead to connectivity issues during the migration process.
57+
5658
## Limitations migrating from Azure Database for PostgreSQL single server
5759

5860
- It's required that both the Azure Database for PostgreSQL single server and the Azure Database for PostgreSQL flexible server are in the same Azure region. Exceptions to this limitation are made for Azure Database for PostgreSQL flexible server situated in India, China, and UAE, where cross-region migrations are permitted.
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: "Introduction of migration runtime server in Migration service in Azure Database for PostgreSQL"
3+
description: "Concepts about the migration runtime server in migration service Azure Database for PostgreSQL"
4+
author: apduvuri
5+
ms.author: adityaduvuri
6+
ms.reviewer: maghan
7+
ms.date: 06/13/2024
8+
ms.service: postgresql
9+
ms.topic: conceptual
10+
---
11+
12+
# Migration Runtime Server with the migration service in Azure Database for PostgreSQL Preview
13+
14+
The Migration Runtime Server is a specialized feature within the [migration service in Azure Database for PostgreSQL](concepts-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.
15+
16+
The migration runtime server is helpful in scenarios where both the source PostgreSQL instances and the target Azure Database for PostgreSQL Flexible Server are configured to communicate over private endpoints or private IPs, ensuring that the migration occurs within a secure and isolated network space. The Migration Runtime Server handles the data transfer, connecting to the source PostgreSQL instance to retrieve data and then pushing it to the target server.
17+
18+
The migration runtime server is distinct from the target server and is configured to handle the data transfer process, ensuring a secure and efficient migration path.
19+
20+
:::image type="content" source="media/concepts-migration-service-runtime-server/private-endpoint-scenario.png" alt-text="Screenshot of migration runtime server.":::
21+
22+
## Supported migration scenarios with the Migration Runtime Server
23+
24+
The migration runtime server is essential for transferring data between different source PostgreSQL instances and the Azure Database for PostgreSQL - Flexible Server. It's necessary in the following scenarios:
25+
26+
- When the source is an Azure Database for PostgreSQL—Single Server configured with a private endpoint and the target is an Azure Database for PostgreSQL—Flexible Server with a private endpoint.
27+
- For sources such as on-premises databases, Azure VMs, or AWS instances that are only accessible via private networks, and the target Azure Database for PostgreSQL - Flexible Server with a private endpoint.
28+
29+
## How do you use the Migration Runtime Server feature?
30+
31+
To use the Migration Runtime Server feature within the migration service in Azure Database for PostgreSQL, follow these steps in the Azure portal:
32+
33+
- Sign in to the Azure portal and access the migration service (from the target server) in the Azure Database for PostgreSQL instance.
34+
- Begin a new migration workflow within the service.
35+
- When you reach the "Select runtime server" tab, use the Migration Runtime Server by selecting "Yes."
36+
Choose your Azure subscription and resource group and the location of the VNet-integrated Azure Database for PostgreSQL—Flexible server.
37+
- Select the appropriate Azure Database for PostgreSQL Flexible Server to serve as your Migration Runtime Server.
38+
39+
:::image type="content" source="media/concepts-migration-service-runtime-server/select-runtime-server.png" alt-text="Screenshot of selecting migration runtime server.":::
40+
41+
## Migration Runtime Server essentials
42+
43+
- **Minimal Configuration**—Despite being created from an Azure Database for PostgreSQL Flexible Server, the migration runtime server solely facilitates migration without the need for HA, backups, version specificity, or advanced storage features.
44+
- **Performance and Sizing**—The migration runtime server must be appropriately scaled to manage the workload, and it's recommended that you select an SKU equivalent to or greater than that of the target server.
45+
- **Networking** Ensure that the migration runtime server is appropriately integrated into the Virtual Network (virtual network) and that network security allows for secure communication with both the source and target servers. For more information visit [Network guide for migration service](how-to-network-setup-migration-service.md).
46+
- **Cleanup Post-Migration**—After the migration is complete, the migration runtime server should be decommissioned to avoid unnecessary costs. Before deletion, ensure all data has been successfully migrated and that the server is no longer needed.
47+
48+
## Related content
49+
50+
- [Migration service](concepts-migration-service-postgresql.md)
51+
- [Network setup](how-to-network-setup-migration-service.md)
52+
- [Premigration validations](concepts-premigration-migration-service.md)

0 commit comments

Comments
 (0)