---
title: "Databases & Analytics - Restore a backup"
description: "Learn how to restore a backup of a Cloud Database or Analytics service in the OVHcloud Control Panel."
url: https://docs.us.ovhcloud.com/en/public-cloud/databases/restore-backup
lang: en
---
> For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt.

# Databases & Analytics - Restore a backup

**Learn how to restore a backup of a Cloud Database or Analytics service in the OVHcloud Control Panel.**

Cloud Database and Analytics services allow you to focus on building and deploying cloud applications while OVHcloud takes care of the engine infrastructure and maintenance.

We continuously improve our offers. You can follow and submit ideas to add to our [roadmap](https://github.com/orgs/ovh/projects/16/views/5?filterQuery=main-product%3A%22Managed+Databases%22%2C%22Data+Platform%22%2C%22Data+Processing%22%2C%22Data+Integration%22).

 

## Requirements

- Access to the [OVHcloud Control Panel](https://manager.us.ovhcloud.com/)
- A [Cloud Database or Analytics service](https://us.ovhcloud.com/public-cloud/databases/) up and running

 

## Instructions

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

First, go to the service overview page from which you want to restore the backup via the `Public Cloud` and `Databases` (or `Data Streaming` or `Data Analysis`) menus.

 

### Step 2: Go to the backup tab

Click on the `Backups` tab.

 

### 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 in the **Creation date** column.

Click on the _more options_ `...` button in the row of the chosen backup. Then click on `Duplicate (Fork)` to go to the configuration page of the new service.

**Warning:**

**NOTE:** The MongoDB[®](#go-further) 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 cause data loss.

 

### Step 4: Configure the target service

As seen before, when restoring a backup, you create a new, separate service on which the backup data will be imported. You can configure this new service as you wish.

#### Immutable options

For obvious reasons, you cannot change the engine; this option is not offered. The same goes for the engine version, you will be able to update it once the new service is running.

You will find a reminder of all these options in the order summary on the right-hand side of the page.

 

#### Restore point

Choose a restore point from which the service will be duplicated.

##### **Backup**

The most common option is to restore from a backup.

##### **Specific date**

If your service supports point-in-time recovery (see our [Databases & Analytics - Automated backups](https://docs.us.ovhcloud.com/en/public-cloud/databases/automated-backups.md) guide for more details), you will also be offered the option to restore from a specific date and time.

##### **Newest**

You will also be offered the ease of choosing the most recent date.

 

#### Plan

When restoring a backup, you can select another service plan.

 

#### Region

You can choose a different region for your new service.

 

#### Nodes

You can choose to upgrade the node to a bigger flavor.

**Note:**

The flavor downgrade will soon be offered. The limitation is that the targeted flavor must have enough storage to restore the backup.

 

#### Sizing

Additional storage can be ordered while forking the service.

**Note:**

The storage reduction will soon be offered. The limitation is that the targeted total storage must be large enough to restore the backup.

 

#### Options

You can update the network options.

Now, click `Order`, 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

You now just have to 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:**

**NOTE:** The newly created service does not duplicate IP restrictions or users that were created on the old service. You will have to recreate those before using your new service.

 

## Go further

Browse all the [Databases guides](https://docs.us.ovhcloud.com/en/public-cloud/databases/landing-page-databases.md).

Browse the rest of the [OVHcloud US documentation](https://docs.us.ovhcloud.com/en/index.md) for guides on our other products and services.

Learn more about [Managed Databases](https://us.ovhcloud.com/public-cloud/databases/) on the OVHcloud US website.

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.
