Skip to content

Commit f30197a

Browse files
Update pages/platform/databases/postgresql_09_concept_high_availability/guide.de-de.md
wording improvement suggestion Co-authored-by: OVH-Team-Guides <[email protected]>
1 parent d038dcc commit f30197a

File tree

1 file changed

+1
-1
lines changed
  • pages/platform/databases/postgresql_09_concept_high_availability

1 file changed

+1
-1
lines changed

pages/platform/databases/postgresql_09_concept_high_availability/guide.de-de.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ No intervention is required from the customer.
107107
OVHcloud also detects when a whole datacenter is lost. As a user, your cluster will still be visible in API and Control Panel.
108108

109109
Automatic backups are first performed on-site (i.e. in the same region as the service), then replicated off-site, to another datacenter.
110-
In case of Datacenter failure, the recovery strategy involves creating a new service in another region, either using the fork from backup feature from an automatic backup that was replicated off-site, or restoring from backups performed manually (e.g. `pg_restore` a previously performed `pg_dump`).
110+
In case of a Datacenter failure, the recovery strategy involves creating a new service in another region, either using the fork (from the backup feature) from an automatic backup that was replicated off-site, or restoring from backups performed manually (e.g. `pg_restore` as previously performed `pg_dump`).
111111
You will then need to configure the freshly created service (e.g. adding users, IP restrictions, ..) and reconfigure applications consuming the database service to use new services URIs and credentials.
112112

113113
In both cases the Recovery Time Objective will vary, depending of multiples parameters such as the amount of data to restore, network congestion and latency or node performances. It can go from a few hours up to a few days.

0 commit comments

Comments
 (0)