Edit

Point-in-time restore of a cluster

  • Article
  • 2 minutes to read

APPLIES TO: PostgreSQL

This article provides step-by-step procedures to perform point-in-time recoveries for a cluster using backups. You can restore either to the earliest backup or to a custom restore point within your retention period.

Important

If the Restore option isn't present for your cluster, open an Azure support request to restore your cluster.

Restore to the earliest restore point

Follow these steps to restore your cluster to its earliest existing backup.

  1. In the Azure portal, from the Overview page of the cluster you want to restore, select Restore.

  2. On the Restore page, select the Earliest restore point, which is shown.

  3. Provide a new cluster name in the Restore to new cluster field. The subscription, resource group, and location fields aren't editable.

  4. Select OK. A notification shows that the restore operation is initiated.

  5. When the restore completes, follow the post-restore tasks.

Restore to a custom restore point

Follow these steps to restore your cluster to a date and time of your choosing.

  1. In the Azure portal, from the Overview page of the cluster you want to restore, select Restore.

  2. On the Restore page, choose Custom restore point.

  3. Select a date and provide a time in the date and time fields, and enter a cluster name in the Restore to new cluster field. The other fields aren't editable.

  4. Select OK. A notification shows that the restore operation is initiated.

  5. When the restore completes, follow the post-restore tasks.

Post-restore tasks

After a restore, you should do the following to get your users and applications back up and running:

  • If the new server is meant to replace the original server, redirect clients and client applications to the new server
  • Ensure an appropriate server-level firewall is in place for users to connect. These rules aren't copied from the original cluster.
  • Adjust PostgreSQL server parameters as needed. The parameters aren't copied from the original cluster.
  • Ensure appropriate logins and database level permissions are in place.
  • Configure alerts, as appropriate.

Next steps