Proxy appliance is an auxiliary Linux-based VM instance. It is used to upload backed-up data to Google Compute Engine. Veeam Backup & Replication automatically deploys the proxy appliance in Google Compute Engine only for the duration of the restore process and removes it immediately after that.
Depending on the type of backups you are restoring from and their location, the proxy appliance may be required or optional. The proxy appliance is required when you restore from:
- Backups of Google Compute Engine VM instances that are stored in external repositories.
- Backups of virtual and physical machines that are stored in object storage repositories.
The proxy appliance is optional when you restore from backups of virtual and physical machines stored in backup repositories, or backups of Google Compute Engine virtual machines copied to backup repositories with backup copy jobs. It is recommended, however, to use the proxy appliance in scenarios where it is optional, as the proxy appliance may significantly improve restore performance. You can specify the proxy appliance settings at the Proxy Appliance step of the Restore to Google Compute Engine wizard.
Requirements for Proxy Appliance
When configuring a proxy appliance, mind the following:
- If you want to restore from backups in an on-premise object storage repository, the proxy appliance machine must have access to the source object storage repository. To provide access to object storage repositories, you can use VPN or Google Dedicated Interconnect. For more information, see the Google Cloud documentation.
- To upload one machine disk to Google Compute Engine, the proxy appliance requires 1 GB RAM. Make sure that the type of Google Compute Engine instance selected for the proxy appliance offers enough memory resources to upload all machine disks. Otherwise, the restore process may fail.
- The VPC route table must contain a route from the IP address of the Veeam Backup & Replication server to an active Google Cloud internet gateway. For more information on internet gateways and how to create route tables, see the Google Cloud documentation.