GCP: Restore Server Requirements

This page is for Data Protection.

This article describes the network connectivity requirements for restore servers in GCP restore projects.

By default, Eon deploys the restore server using your project’s default VPC network and subnet. If these defaults exist and have the required connectivity, no additional configuration is needed. If the default VPC network resources have been deleted or have outbound limitations, customize the restore server’s network configuration. See GCP: Customize Restore Server Configuration for details.

Network requirements

The network requirements depend on the resource you’re restoring.

Compute Engine and Cloud Storage

When restoring Compute Engine instances or Cloud Storage buckets, Eon creates the restore server in the same zone as the restore destination.

The restore server requires outbound connectivity to Google APIs and services. Configure the restore account’s subnets to support one of these options:

Option 1: For subnets that block external IP addresses (via organizational policy), configure both:

• Cloud NAT on the VPC network’s Cloud Router.

• Private Google Access enabled on the subnet.

Option 2: For subnets that allow external IP addresses, Eon automatically assigns an external IP to the restore server.

To configure Cloud NAT and Private Google Access, see Configure Cloud NAT and Configure Private Google Access in the Google Cloud documentation. To customize which networks and subnets Eon uses for restore servers, see GCP: Customize Restore Server Configuration.

Cloud SQL

When restoring Cloud SQL instances, Eon creates the restore server in the same VPC network as the restored instance.

The restore server needs to create and populate databases on the restored instance. For this to happen, Private Services Access must be configured for the VPC network, and the Cloud SQL instance must use a private IP address.

With this configuration, Cloud SQL automatically authorizes connections from resources in the same VPC network using RFC 1918 private IP ranges. No additional firewall rules are required for the restore server to communicate with the Cloud SQL instance.

The restore server also requires outbound connectivity to Google APIs and services. Configure the restore account’s subnets to support one of these options:

Option 1: For subnets that block external IP addresses (via organizational policy), configure both:

• Cloud NAT on the VPC network’s Cloud Router.

• Private Google Access enabled on the subnet.

Option 2: For subnets that allow external IP addresses, Eon automatically assigns an external IP to the restore server.

To configure Cloud NAT and Private Google Access, see Configure Cloud NAT and Configure Private Google Access in the Google Cloud documentation. To customize which networks and subnets Eon uses for restore servers, see GCP: Customize Restore Server Configuration.