Skip to content

Commit 41b5796

Browse files
committed
Add link clarifying what RPO means
1 parent 2aa02b2 commit 41b5796

File tree

1 file changed

+2
-2
lines changed
  • docs/modules/ROOT/pages/vshn-managed/postgresql

1 file changed

+2
-2
lines changed

docs/modules/ROOT/pages/vshn-managed/postgresql/backup.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ spec:
2525

2626
== Point in Time interval
2727

28-
By default, the _WALs_ (Write Ahead Logs) will be shipped every time a _WAL_ file has been completed. They grow to 16Mbs before being considered completed and be archived to the backup object store. This will result in variable RPO times.
28+
By default, the _WALs_ (Write Ahead Logs) will be shipped every time a _WAL_ file has been completed. They grow to 16Mb before being considered completed and be archived to the backup object store. This will result in variable https://en.wikipedia.org/wiki/IT_disaster_recovery#Recovery_Point_Objective[RPO] times.
2929

3030
If fixed RPO time is required, the `archive_timeout` setting can be set. It will force an archive of the _WAL_ files every given interval.
3131

@@ -44,7 +44,7 @@ spec:
4444
archive_timeout: "300" <1>
4545
...
4646
----
47-
<1> Amount of time between _WAL_ archives
47+
<1> Amount of time between _WAL_ archives in seconds
4848

4949
However, the _WAL_ files will always be 16Mb, even if it's not completed. So using this setting will most likely increase the data usage on the backup object store.
5050

0 commit comments

Comments
 (0)