Edit

Migrate or replicate from Premium SSD to Premium SSDv2

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.

Steps to migrate or replicate from Premium SSD to Premium SSDv2

Using the Azure portal:

  1. Select your Azure Database for PostgreSQL flexible server instance.

  2. In the resource menu, select Settings go to Replication and select the Create replica button.

    Screenshot showing the Replication page.

  3. Provide Server name and Select Configure server.

    Screenshot showing the Compute + storage page.

  4. Choose Premium SSD v2 for the Storage type Field.

    Screenshot showing the Premium SSDv2 storage type button selected.

  5. Once the replica server is configured to your needs, select Review + create.

    Screenshot showing the Add Replica page.

  6. 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.

  7. When the deployment completes, go to newly created Premium SSDv2 server and select Compute + Storage button, and validate your Storage type.

    Screenshot that shows new server created using new storage type.

  8. 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.

    Screenshot that shows promoting new server ssd v2 server as standalone.

  9. 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.

    Screenshot that shows new server using virtual endpoint.

Note

  • 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.
  • Wait for the first automated backup to complete before configuring in-region replicas, as replica creation depends on an existing backup.

Related content

  • Last updated on