> 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 SQL: Restore an Instance

This article explains how to restore a Cloud SQL instance from your Eon snapshots.

## Restore a Cloud SQL instance

#### Before you start

Before you restore a Cloud SQL instance, make sure:

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

* The GCP restore project has a VPC and subnet that meet [restore server connectivity requirements].
  By default, Eon uses the default VPC and subnet, but you can [customize the restore server connectivity] if needed.

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

[restore server connectivity requirements]: /data-protection/restoring/restore-accounts/about-restore-accounts#the-restore-server-and-its-network-connectivity

[customize the restore server connectivity]: /data-protection/cloud-workloads/gcp/restore-projects/gcp-customize-restore-server-configuration

#### Find the snapshot you want to restore

1. In your

   inventory

   , select the Cloud SQL resource 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 Cloud SQL** wizard opens.

#### Choose the restore account

In the **Restore Cloud SQL** 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 instance configuration

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

1. Give an **Instance ID** for the new instance.
   This doesn't have to match the original instance ID, so you can choose any name to identify the new instance.

2. Choose a **Region** and **Zone** to deploy the restored instance to.

3. Choose a **Network** to use.
   If you're using a private IP, only peered networks are available.

4. If you want to retain the labels that were present when the snapshot was taken, turn **Keep original labels** on.
   Otherwise, turn **Keep original labels** off.

   In both cases, the new instance is labeled with `eon-restore=true`.
   Labels with the `eon-` prefix aren't included in the original labels because Eon uses this prefix for internal operations.

5. Click **Restore** 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 instance as normal.
The new instance retains the original database engine, version, and configuration.

Public IP access to the new instance is off by default, regardless of what the original public access settings were.
To enable connectivity to your restored instance, you have two options:

* **Private IP**: Connect from resources within the same VPC or through VPC peering.
  This is the recommended approach for security.

* **Public IP**: Enable public IP on the instance and configure authorized networks to allow specific IP addresses or ranges.
  You'll also need to allow connections through the database port:
  * For MySQL: Port 3306
  * For PostgreSQL: Port 5432

For more information on connecting to Cloud SQL instances, see [Cloud SQL connectivity options].

[Cloud SQL connectivity options]: https://cloud.google.com/sql/docs/mysql/connect-overview