1. Articles
  2. Platform as a Service
  3. Managed Databases
  4. General Guides

Articles in this section

See more

Cloud Databases - Automated Backups

Avatar
Stephanie R.
  • Updated

Learn the technical descriptions of the automated backup methods and routines for each Managed Databases (also called Cloud Databases) 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 managed cloud databases 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
PostgreSQL PITR on object storage On-Site, Off-Site Continuous Few minutes Yes
MySQL BPITR on object storage On-Site, Off-Site Continuous Few minutes Yes
Caching Backup on object storage On-Site, Off-Site 2 times a day 12h Yes
OpenSearch Incremental On-Site, Off-Site Hourly 1h Yes
M3 Backup on object storage On-Site, Off-Site Daily 24h Yes
Cassandra Backup on object storage On-Site, Off-Site Daily 24h Yes
Kafka N/A N/A N/A N/A N/A

 

Off-site backup

Replication mechanism

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 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 database creation follows this format:

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

Backup settings must respect the following rules:

  • 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 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 Cloud Databases support guides or explore the guides for other OVHcloud products and services.

Related articles