Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recover dropped postgres server update #251

Closed
wants to merge 3 commits into from
Closed

Recover dropped postgres server update #251

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
381e8ce
Update how-to-restore-dropped-server.md
paulhaefeli Mar 18, 2025
6d060ce
Update how-to-restore-dropped-server.md
paulhaefeli Mar 18, 2025
ea7b506
Merge branch 'MicrosoftDocs:main' into patch-2
paulhaefeli Mar 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions articles/postgresql/flexible-server/how-to-restore-dropped-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,28 +43,28 @@ To restore a dropped Azure Database for PostgreSQL flexible server instance, you

1. Provide the **resourceGroupName**, **serverName** (Target server name), **subscriptionId** properties, based on the resourceId attribute JSON value captured in the preceding step 3. The api-version property is prepopulated and can be left alone.

1. Go to **Request Body** section and paste the following replacing the "Dropped server Location"(for example, CentralUS, EastUS etc.), "submissionTimestamp", and "resourceId". For "pointInTimeUTC", specify a value of "submissionTimestamp" plus **5 minutes** to ensure the command doesn't error out.
1. Go to **Request Body** section and paste the following replacing the "Dropped server Location"(for example, CentralUS, EastUS etc.), "submissionTimestamp", and "resourceId". For "pointInTimeUTC", specify a value of "submissionTimestamp" minus **10 minutes** to ensure the command doesn't error out.

```json
{
"location": "Dropped Server Location",
"properties":
{
"pointInTimeUTC": "submissionTimestamp + 10 minutes",
"pointInTimeUTC": "submissionTimestamp - 10 minutes",
"createMode": "ReviveDropped",
"sourceServerResourceId": "resourceId"
}
}
```

For example, if the submission timestamp is 2023-06-15T15:58:02Z, we recommend adding a minimum of 10 minutes to restore point in time 2023-06-15T16:05:02Z and ensure that you're changing three parameters (location,pointInTimeUTC,sourceServerResourceId) as per your restore requirements.
For example, if the submission timestamp is 2023-06-15T15:58:02Z, we recommend subtracting a minimum of 10 minutes to restore point in time 2023-06-15T15:48:02Z and ensure that you're changing three parameters (location,pointInTimeUTC,sourceServerResourceId) as per your restore requirements.

```json
{
"location": "WestUS",
"properties":
{
"pointInTimeUTC": "2023-06-15T16:08:02Z",
"pointInTimeUTC": "2023-06-15T15:48:02Z",
"createMode": "ReviveDropped",
"sourceServerResourceId": "/subscriptions/ffffffff-ffff-ffff-ffff-ffffffffffff/resourceGroups/SourceResourceGroup-Name/providers/Microsoft.DBforPostgreSQL/flexibleServers/SourceServer-Name"
}
Expand Down