How Restore to Google Compute Engine Works

In this article

    You can perform restore to Google Compute Engine from backups of virtual and physical machines, and Google Compute Engine VM instances. To upload backed-up data to Google Compute Engine, Veeam Backup & Replication may use an auxiliary Google Compute Engine instance — a proxy appliance. Veeam Backup & Replication 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:

    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.

    The workflow of the restore process depends on whether the proxy appliance is used or not.

    Note

    If you add the Google Compute Engine appliance to the Veeam Backup & Replication infrastructure and plan to restore Google Compute Engine virtual machines from restore points that were created using the appliance, you do not need to configure the proxy appliance. Also, restore to Google Compute Engine works as described in the Performing Instance Restore section in the Veeam Backup for Google Cloud Platform User Guide.

    Restoring to Google Compute Engine with Proxy Appliance

    If the proxy appliance is used for restore to Google Compute Engine, Veeam Backup & Replication performs the following operations:

    1. Veeam Backup & Replication creates a proxy appliance in Google Compute Engine.

    During the restore process, the proxy appliance communicates with backup infrastructure components over the SSH protocol and the network redirector that is deployed on the proxy appliance.

    1. For every disk of a backed-up machine, Veeam Backup & Replication creates a disk in Google Compute Engine.
    2. Veeam Backup & Replication hot-adds empty disks to the proxy appliance and restores backed-up data to the disks.
    3. Veeam Backup & Replication creates a target instance in Google Compute Engine.
    4. Veeam Backup & Replication detaches the disks from the proxy appliance and attaches them to the target instance.
    5. After the restore process is complete, Veeam Backup & Replication removes the proxy appliance from Google Compute Engine.

    Restoring to Google Compute Engine without Proxy Appliance

    If the proxy appliance is not used for restore to Google Compute Engine, Veeam Backup & Replication performs the following operations:

    1. Veeam Backup & Replication uploads disks of a backed-up machine to Google Cloud Storage bucket.

    In Google Cloud Storage bucket, the uploaded disks are stored to the temporary bucket in the RAW format.

    1. Veeam Backup & Replication imports the backed-up data from the temporary bucket in Google Cloud Storage to disks in Google Compute Engine.
    2. Veeam Backup & Replication creates a target instance in Google Compute Engine and attaches disks to the target instance.
    3. After the import process is complete, Veeam Backup & Replication removes the temporary bucket from Google Cloud Storage.