> This page is for Data Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.eon.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.eon.io/_mcp/server.

# Azure Database for PostgreSQL Flexible Server: Restore a Server

This article explains how to restore an Azure Database for PostgreSQL flexible server from your Eon snapshots.

## Restore an Azure Database for PostgreSQL flexible server

#### Before you start

Before you restore an Azure Database for PostgreSQL flexible server, make sure:

* A [restore account has been connected] to your Eon account.

[restore account has been connected]: /data-protection/restoring/restore-accounts/about-restore-accounts

* The subnet you plan to restore to has the `Microsoft.DBforPostgreSQL/flexibleServers` delegation.
  If it doesn't, Eon attempts to add it automatically during the restore.
  If the automatic attempt fails, you'll need to add the delegation manually or select a different subnet before retrying.

#### Find the snapshot you want to restore

1. In your

   inventory

   , select the Azure Database for PostgreSQL flexible server you want to restore.
   The **Resource details** panel opens.

2. Click the **Eon snapshots** tab.
   You'll see a calendar view with colored dots on the days when snapshots were taken.
   There can be more than one snapshot per day.

   When you click a day, a list of Eon snapshots taken that day is displayed below the calendar.

3. When you find the snapshot you want, click **Restore**.
   The **Restore PostgreSQL Server** wizard opens.

#### Choose the restore account

In the **Restore PostgreSQL Server** wizard, you're taken through a two-step process.
The first step is to choose a restore account.

Choose the subscription you want to restore to, and then click **Next**.

#### Set the server configuration

In the **Configuration** step, you'll set the server details.

1. Enter a **PostgreSQL server name** for the new server.
   This doesn't have to match the original server name.

2. Choose a **Region** to deploy the restored server to.

3. Choose a **Resource group** to deploy the restored server to.

4. Select the **Virtual network** and **Subnet** to use.
   The subnet must have the `Microsoft.DBforPostgreSQL/flexibleServers` delegation.
   If it doesn't, Eon attempts to add it automatically.
   If that fails, you'll be prompted to add it manually or select a different subnet.

5. If you want to retain the tags that were present when the snapshot was taken, turn **Keep original tags** on.
   Otherwise, turn **Keep original tags** off.

6. Click **Restore** to start the asynchronous restore job.

#### Monitor the restore job

You can see your list of restore jobs on the

Restore jobs tab

in the Jobs page.

After the job is completed, the restored server is available in Azure with the original PostgreSQL engine version.
For help with common restore errors, see [Azure Database for PostgreSQL Flexible Server Support](/data-protection/cloud-workloads/azure/resources/azure-database-for-postgresql-flexible-server#restore-troubleshooting).