|
| 1 | +--- |
| 2 | +title: Migrate SSD Server to SSDv2 Using Replicas |
| 3 | +description: This article describes how to migrate a Premium SSD server to Premium SSDv2 using replicas in Azure Database for PostgreSQL flexible server instance. |
| 4 | +author: kabharati |
| 5 | +ms.author: kabharati |
| 6 | +ms.reviewer: maghan |
| 7 | +ms.date: 04/06/2026 |
| 8 | +ms.service: azure-database-postgresql |
| 9 | +ms.subservice: compute-storage |
| 10 | +ms.topic: concept-article |
| 11 | +# customer intent: As a user, I want to learn how to migrate from Premium SSD server to Premium SSDv2 in Azure Database for PostgreSQL flexible server instance. |
| 12 | +--- |
| 13 | + |
| 14 | +# Migrate or replicate from Premium SSD to Premium SSDv2 |
| 15 | + |
| 16 | +This article provides step-by-step instructions to migrate from Premium SSD to Premium SSDv2 using replication in Azure Database for PostgreSQL flexible server instance. |
| 17 | + |
| 18 | +## Steps to migrate or replicate from Premium SSD to Premium SSDv2 |
| 19 | + |
| 20 | +### [Portal](#tab/portal-create-virtual-endpoints) |
| 21 | + |
| 22 | +Using the [Azure portal](https://portal.azure.com/): |
| 23 | + |
| 24 | +1. Select your Azure Database for PostgreSQL flexible server instance. |
| 25 | + |
| 26 | +1. In the resource menu, select **Settings** go to **Replication** and select the **Create replica** button. |
| 27 | + |
| 28 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/create-replica.png" alt-text="Screenshot showing the Replication page." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/create-replica.png"::: |
| 29 | + |
| 30 | +1. Provide Server name and Select **Configure server**. |
| 31 | + |
| 32 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/configure-server-page.png" alt-text="Screenshot showing the Compute + storage page." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/configure-server-page.png"::: |
| 33 | + |
| 34 | +1. Choose **Premium SSD v2** for the **Storage type** Field. |
| 35 | + |
| 36 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/premium-storage.png" alt-text="Screenshot showing the Premium SSDv2 storage type button selected." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/premium-storage.png"::: |
| 37 | + |
| 38 | +1. Once the replica server is configured to your needs, select **Review + create**. |
| 39 | + |
| 40 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/add-replica-validation.png" alt-text="Screenshot showing the Add Replica page." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/add-replica-validation.png"::: |
| 41 | + |
| 42 | +1. A new deployment is created to provision an Azure Database for PostgreSQL flexible server instance using Premium SSD v2 storage, with the latest data replicated from the source server. |
| 43 | + |
| 44 | +1. When the deployment completes, go to newly created Premium SSDv2 server and select **Compute + Storage** button, and validate your **Storage type**. |
| 45 | + |
| 46 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/validate-storage.png" alt-text="Screenshot that shows new server created using new storage type." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/validate-storage.png"::: |
| 47 | + |
| 48 | +1. Select **Replication** and select **Switch over or promote to standalone**. Select **Promote to standalone server and remove from replication. This won't impact primary server** for **Action**. And select **Planned - sync data before promoting**. You have to mark the **I understand that this read replica will become an independent standalone server and this action can't be undone.** checkbox to acknowledge. Finally, select **Promote to standalone**. |
| 49 | + |
| 50 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/promote-primary.png" alt-text="Screenshot that shows promoting new server ssd v2 server as standalone." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/promote-primary.png"::: |
| 51 | + |
| 52 | +1. Optionally, once the promotion is complete, you can point your virtual endpoint pairs from the Premium SSD flexible server instance to the new Premium SSD v2 instance. |
| 53 | + |
| 54 | + :::image type="content" source="media/concepts-storage-ssd-v2-migration-using-replication/recreate-virtual-endpoint.png" alt-text="Screenshot that shows new server using virtual endpoint." lightbox="media/concepts-storage-ssd-v2-migration-using-replication/recreate-virtual-endpoint.png"::: |
| 55 | +--- |
| 56 | + |
| 57 | +> [!NOTE] |
| 58 | +> - Once the migration is complete, you can stop the original server, allow the required backup retention to be satisfied on the new server, and then safely decommission the old server. |
| 59 | +> - Wait for the first automated backup to complete before configuring in-region replicas, as replica creation depends on an existing backup. |
| 60 | +--- |
| 61 | + |
| 62 | +## Related content |
| 63 | + |
| 64 | +- [Restore to paired region (geo-restore)](../backup-restore/how-to-restore-paired-region.md) |
| 65 | +- [Restore a dropped server](../backup-restore/how-to-restore-dropped-server.md) |
0 commit comments