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

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?

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.

Can we run the worker against both databases during validation?

Avoid duplicate side effects. Keep outbound jobs and email disabled in the validation environment, and control which system is allowed to process live work.

Measure restore provisioning, validation and application recovery separately. Those intervals explain the operational recovery time better than the backup retention setting alone.

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

Sources & further reading

2 answers

Your perspective belongs here.

0 question comments