For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/pl/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/pl/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/pl/guides/public-cloud/databases/restore-backup.md.
Przejdź do treści

Restore a backup of Public Cloud Databases

Pokaż jako Markdown

Find out how to restore a backup

Objective

OVHcloud Databases as-a-service (DBaaS) allows you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance.

This guide explains how to restore a backup of a database solution in the OVHcloud Console.

We continuously improve our offers. You can follow and submit ideas to add to our roadmap at https://github.com/orgs/ovh/projects/16/views/5.

Requirements


OVHcloud Console Access

  • Direct link:
  • Navigation path: Public Cloud > Select your project > Databases

Instructions

Step 1: Select the database service you want to restore data from

In the left-hand menu of your Public Cloud project, click your engine under Databases, then click the name of the service you want to restore the backup from.

Step 2: Go to the backup tab

In the tab list, click on Backups.

Step 3: Select the backup to restore from

Select the backup from which you want to restore. To help you choose, observe the dates at which the backups have been performed.

Click on the ... button corresponding to the chosen backup, then click on Fork to open the Fork a cluster panel. You can also click the Fork button above the list.

Warning

Some engines, such as MongoDB, also offer to restore a backup in place, meaning restoring the backup on the same service (Restore a backup). This option will rollback ALL data to the state it was in when the backup was done. This can induce data loss.

Step 4: Configure the target service

As seen before, when restoring a backup, you create a new separate database service on which the backup data will be imported. You are able to configure this new service as you wish in the Fork a cluster panel.

Name

Enter a New cluster name.

Restore point

In Fork source, choose the restore point from which the service will be duplicated:

  • From a backup: the most common option, restore from one of the listed backups (Backup field).
  • Point in time: if your service supports point in time recovery (see Automated Backup guide for more details), restore from a specific date and time.
  • Latest state: restore from the most recent data.

New cluster configuration

You cannot change the engine. In the New cluster configuration section, you can choose the Version, a different Region, another service Plan, a bigger Node type, the Number of nodes and additional Storage for your new service.

Info

The targeted node type and storage must be large enough to restore the backup.

The estimated price of the new service is displayed at the bottom of the panel. Now click on Create fork and the new service will be created. Please note that depending on the backup size, it can take some time before the service is available.

Step 5: Wait for service creation

Now all you have to do is wait for your service to be ready. This new service is now completely independent from the one you forked the backup from. You can safely delete the old service without impacting the new one.

Warning

The newly created service does not duplicate IP restrictions nor users which were created on the old service. You will have to recreate those before using your new service.

Go further

Join our community of users.

Czy ta strona była pomocna?