If point-in-time recovery (PITR) is enabled, a write-ahead log (WAL) continuously records every change made to the database while the database is running. In the event of a failure, you can replay the WAL to restore the database to its state at a point in time within the retention period of the database backups.

The WAL logs are archived and are subject to a retention period that you set. The time range for point-in-time recovery is from the time of your oldest backup to the present. The oldest backup can be an external backup or a snapshot.

By default, PITR is disabled. If you enable PITR, consider the following points.

Because every change to the database is recorded, PITR requires additional storage. Depending on how large your database is and how many transactions occur during the WAL archive retention time, the amount of storage needed can be large.

PITR has a performance impact on the database and on Data Director as a whole. The impact depends on the size of the database and the volume of database activity.

Start with a conservative storage allocation. You cannot decrease the storage allocation, but you can increase it. Monitor the size of the PITR logs until you understand the workload and storage needed, and adjust the storage amount.

You can specify whether to suspend the database or automatically increase the log retention period if PITR runs out of space.

When you enable PITR, Data Director creates a baseline external backup. The default retention period is forever. You can change the baseline backup's retention period from the database Properties dialog box's Backup tab.