Point-in-time recovery allows you to recover your database from a destructive or unwanted action or change. You can recover a service to any point within the period defined by your pricing plan.
Initiating a point-in-time recovery of your service creates a fork of your service that matches the state of your database at the specified time of recovery. The original service stays untouched to avoid losing data created since the time of recovery.
Since the point-in-time recovery is done in a fork, to migrate your application to the point of recovery, switch out the connection strings in your application to use the fork. The provision time for the recovery fork is typically less than twenty minutes, but can take longer depending on the amount of WAL to be replayed.
To avoid paying for compute for the recovery fork and the original service, you can pause the original to only pay storage costs.
- In the Timescale console, from the
Serviceslist, ensure the service you want to PITR has a status ofRunningorPaused. - Navigate to the
Operationstab. - In the
Service managementsection, clickCreate recovery fork. In the creation page, select the time you would like to recover to, ensuring the correct time zone (UTC offset). - OptionalYou can also add an HA replica, change the compute, and add a connection pooler as part of this process. It is recommended to match the same configuration you had at the point you want to recover to.
- Confirm by clicking
Create recovery fork. A fork of the service is created to the point-in-time specified. - The recovered service shows in the
Servicesdashboard with a label stating which service it has been forked from. - If you would like to use your application to use the recovered fork, ensure you update your connection strings to the fork throughout your app.
Keywords
Found an issue on this page?Report an issue or Edit this page in GitHub.