> This page is for Data Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.eon.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.eon.io/_mcp/server.

# Cloud Storage: Restore a Bucket

This article explains how to restore a Google Cloud Storage bucket from your Eon snapshots.

## Restore a bucket

#### Before you start

Before you restore a bucket, make sure:

[restore account has been connected]: /data-protection/restoring/restore-accounts/about-restore-accounts

* A [restore account has been connected] to your Eon account.

* The restore account contains a bucket in the same region as the vault you're restoring from.

#### Find the snapshot you want to restore

1. In your

   inventory

   , select the Google Cloud Storage bucket you want to restore.
   The **Resource details** panel opens.

2. Click the **Eon snapshots** tab.
   You'll see a calendar view with colored dots on the days when snapshots were taken.
   There can be more than one snapshot per day.

   When you click a day, a list of Eon snapshots taken that day is displayed below the calendar.

3. When you find the snapshot you want to restore, click **Restore**.
   The **Restore GCS** wizard opens.

#### Choose the restore account

In the **Restore GCS** wizard, you're taken through a two-step process.
The first step is to choose a restore account.

Choose the cloud account you want to restore to, and then click **Next**.

#### Set the restored bucket and prefix details

In the **Configuration** step, you'll set the restored data details.

1. Select the destination bucket you want to restore to.
   The bucket needs to exist already, and the restore account needs to have IAM permissions that grant write access to the bucket.
   The bucket doesn't need to be empty.

2. Optionally, you can provide a **Prefix** if you want to restore the data to a specific location in the bucket.
   If you don't provide a prefix, the data is restored to the bucket root.

   > **Warning**
   >
   > If there are naming conflicts with existing objects, Eon overwrites the existing data.
   > Use a unique prefix to avoid overwrites.

3. Click **Start** to start the asynchronous restore job.

#### Monitor the restore job

You can see your list of restore jobs on the

Restore jobs tab

in the Jobs page.

After the job is completed, the status changes to **SUCCESS**, and you can work with the restored data as normal.