Does Azure PostgreSQL point-in-time restore replace the original server?

0 reputation · 01 Jan 2022, 08:03 UTC

62.3K views2

In this fictional recovery exercise, an operator selects a point before an accidental data change. The team expects existing application connections to switch automatically when restore completes. The database is Azure PostgreSQL Flexible Server. What should the recovery runbook include?

Environment

Editorial worked example. See the question for the scenario and assumptions.

Keep exploring this topic

A restored PostgreSQL database opens successfully; what should we validate before cutover?

An example team restores a database containing user accounts, posts and a reputation ledger. Basic SQL queries work. They are about to switch the application but have only compared table counts. What additional checks would make the recovery decision more meaningful?

The only Entra administrator cannot complete MFA; can a new account recover the tenant?

This original scenario reflects a general problem seen on Microsoft Q&A: the sole authorized tenant administrator loses access to the configured authentication method, and no other administrator can help. An employee suggests creating a new Microsoft account with a similar email address. Would that provide tenant authority?

S3 object downloads work, but listing the bucket returns AccessDenied

An example service can retrieve a known object key but cannot enumerate the same bucket. The role policy was written specifically for object reads, and the application recently added a directory-style browser. Does successful GetObject access imply that the list request should also work?

A rotated Key Vault secret is correct, but App Service still uses the previous value

A fictional application uses a Key Vault reference without a version in its URI. A new secret version has been created and is enabled. Requests from an authorized diagnostic client use the new value successfully, but the application behaves as if it has the old credential. Is this necessarily a permissions failure, and how should refresh behavior be checked?

Point-in-time restore creates a new server; it does not rewind the original server in place. Plan how the application will reach the destination, obtain its connection configuration and establish authorized access. Validate the target time and the relevant records before redirecting writes.

A recovery runbook should include a write-pause decision, database validation, network and DNS checks, application cutover and rollback criteria. Review monitoring and availability settings on the restored destination explicitly. A server creation success message does not establish that the application recovered.

Does Azure PostgreSQL point-in-time restore replace the original server?

2 answers

Your perspective belongs here.

0 question comments

Good answers start here.