Restore a backup
Find out how to restore a backup
Find out how to restore a backup
Last updated May 4th, 2022
OVHcloud Databases as-a-service (DBaaS) allow 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 Control Panel.
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at https://github.com/ovh/public-cloud-roadmap/projects/2.
In this guide we will use a Postgresql database engine as an example, but the procedure is exactly the same for all other engines.
You can learn more about how backups works on the Automated backups guide.
Restoration of a backup is done by creating a new service and pushing the backup data to this new service. This full process is called forking and is fully automated. Once this process is done, you will have two independent service running, the one from which the backup comes from, and a new one on which the backup data has been imported.
First you need to go on the overview page of the service you want to restore the backup from.
In the tab list click on
Select the backup from which you want to restore from. To help you choose, observe the dates at which the backups have been performed in the "Creation date" column.
Click on the
... button corresponding to the chosen backup. Then click on
Duplicate (Fork) to go on the configuration page of the new service.
The MongoDB service has the option to restore a backup in place, meaning restoring the backup on the same service. This option will rollback ALL data to the state it was in when the backup was done. This can induce data loss.
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.
For obvious reasons, you can not change the engine, this option is greyed. Same goes for the engine version, you will be able to update engine version once the new service is running.
When restoring a backup you can select another service plan.
We currently don't allow changing the region. Your new service must be on the same region as the old one.
You are able to change the node flavor of the service. Please note that the selection is restricted, depending on backup size. You can't restore a 400 GB data set on a node with only 320 GB of disk space.
You can update the database name.
Now click on
Create a database service 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.
You now just have to wait for your service to be ready. This new service is now completly independent from the one you forked the backup from. You can safely delete the old service without impacting the new one.
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.
We would love to help answer questions and appreciate any feedback you may have.
Are you on Discord? Connect to our channel at https://discord.gg/PwPqWUpN8G and interact directly with the team that builds our databases service!
Zachęcamy do przesyłania sugestii, które pomogą nam ulepszyć naszą dokumentację.
Obrazy, zawartość, struktura - podziel się swoim pomysłem, my dołożymy wszelkich starań, aby wprowadzić ulepszenia.
Zgłoszenie przesłane za pomocą tego formularza nie zostanie obsłużone. Skorzystaj z formularza "Utwórz zgłoszenie" .
Dziękujemy. Twoja opinia jest dla nas bardzo cenna.
Dostęp do OVHcloud Community Przesyłaj pytania, zdobywaj informacje, publikuj treści i kontaktuj się z innymi użytkownikami OVHcloud Community.Porozmawiaj ze społecznością OVHcloud