Skip to main content

Databases & Analytics - Automated backups

Stephanie R.
Updated

Learn the technical descriptions of the automated backup methods and routines for each Cloud Database or Analytics engine.

We continuously improve our offers. You can follow and submit ideas to add to our roadmap.

 

Backup Methods

  • Daily remote site backup:

We back up our Cloud Databases and Analytics services every 1 (incremental snapshots), 12, or 24 hours (backups) — depending on the product — with the ability to restore from the latest point in time, based on the retention period of the chosen customer plan.

  • PITR:

Whether you run into a problem or you just want to see what your data looked like at a prior date, you can restore your data to any point in time within the retention period of the chosen customer plan for PostgreSQL® and MySQL®.

 

Engine Specifications*

Engine Backup Method(s) Location(s) Frequency RPO Encrypted
MongoDB® Backup on object storage Off-Site Daily 24 h Yes
PostgreSQL® PITR on object storage On-Site, Off-Site Continuous Few minutes Yes
MySQL® PITR on object storage On-Site, Off-Site Continuous Few minutes Yes
Valkey Backup on object storage On-Site, Off-Site 2 times a day 12h Yes
OpenSearch™ Incremental backup on object storage On-Site, Off-Site Hourly 1h Yes
Kafka® (including Connect and MirrorMaker) N/A N/A N/A N/A N/A

 

Off-site backup

Replication mechanism

For MongoDB, backup data gets shipped directly to the remote region.

For other engines, backups are first prepared on-site and then replicated to another region. The on-site backup data persists once it gets replicated to the other region.

 

Default location

Cloud Databases and Analytics services provide a default configuration for remote backups based on the region the service is running in:

Service location Off-site default backup location
US-EAST-VA (Vint Hill, Virginia) US-WEST-OR (Hillsboro, Oregon)
US-WEST-OR (Hillsboro, Oregon) US-EAST-VA (Vint Hill, Virginia)

 

Custom settings

Backup default location and time could be overridden by setting the backups attribute either when creating or updating your service. As an example, the following settings define HIL (Hillsboro, Oregon) as the backup location and 01:00:00 as the daily backup time:

"backups": {
  "regions": ["HIL"],
  "time": "01:00:00"
}

As a reminder, the API endpoint for engine creation follows this format:

POST /cloud/project/{serviceName}/database/{database_engine_name}/

Backup settings must respect the following rules:

  • For MongoDB®, the regions array only accepts one element. You are free to define the backup location in the same region as the service, though this could be considered unwise.
  • The regions array accepts one or two elements. If only one element is specified, it must match the region the service is running in. If two elements are specified, one of these elements must match the region the service is running in, while the other element could be set to any other region. It is recommended to use two regions for your backups.

Be aware that the backup time can only be customized on MongoDB®, MySQL®, and PostgreSQL®.

 

Lexicon

PITR: Point In Time Recovery

RPO: Recovery Point Objective

Off-Site: on a different region

On-Site: within the same region

 

Go further

For more information and tutorials, please see our other Managed Databases & Analytics or Platform as a Service guides. You can also explore the guides for other OVHcloud products and services.

OVHcloud Managed Databases and Analytics:

  • Grafana® is a registered trademark of Grafana Labs and is used with the permission of Grafana Labs. OVH SAS and its subsidiaries are not affiliated with or endorsed by Grafana Labs.
  • Kafka® is a registered trademark of The Apache Software Foundation and has been licensed for use by OVHcloud, who has no affiliation with and is not endorsed by The Apache Software Foundation.
  • MongoDB® is a registered trademark of MongoDB, Inc.
  • MySQL® is a registered trademark of Oracle and/or its affiliates.
  • PostgreSQL® is a registered trademark of the PostgreSQL Community Association of Canada.

Related articles