> Essential > Virtualization > Google Cloud Platform > Restores

Restoring Full Google Cloud Platform Instances Out of Place

You can restore one or more full GCP instance out of place (to a different location), from streaming backups, IntelliSnap backups, or backup copies. You can restore instances out of place to a different project, region, and/or zone.

Requirements and Considerations

  • If a passkey is configured for restores, you must have the passkey.

  • If you want to restore an instance to a different GCP project, the service account of the hypervisor must have access to the project that you want to restore the instance to.

  • Verify that your GCP service account has the appropriate roles and permissions to perform the operation. For more information, see "Create a GCP Service Account" in Configuring Backups for Google Cloud Platform Instances.

  • You can use shared virtual private cloud (VPC) networks.

  • If an instance that you are restoring includes regional disks, all the regional disks are restored to the selected zone.

  • To restore an instance that was turned off during a backup operation, you must assign that instance an external IP address using the GCP portal.

  • From streaming backups or backup copies of encrypted disks, you can restore full instances, files or folders to the same project or to a different project. During the restore operation, the Commvault software verifies whether the source encryption key ring and key are present in the project that you are restoring to. If the key ring and key are present, then Commvault assigns them to the new instance disk. If the key ring and key are not present, then Commvault generates a new key ring and key (with the same name as the source encryption key ring and key) and assigns them to the new instance disk.

Start the Restore Wizard

  1. From the Command Center navigation pane, go to Protect > Virtualization.

    The Overview page appears.

  2. On the Virtual machines tab, for the instance that you want to restore, click the action button action_button, and then select Restore.

    The Select restore type page appears.

  3. Click Full instance.

    The Full instance page appears.

  4. To select a specific MediaAgent and/or source for the restore, in the upper-right area of the page, click the Settings button gear button.

    By default, the Commvault software automatically selects the MediaAgent and source as follows:

    • MediaAgent: The software selects a MediaAgent based on availability and environment.

    • Source: The software searches for the requested data in the primary copy. If the data is not found in the primary copy, the software selects a different copy.

    For more information, see MediaAgent and Copy Precedence Considerations for Virtualization Restores.

  5. Select the instances to restore, and then click Restore.

    The restore wizard appears.

Specify the Restore Destination

  1. For Type, select Out of place.

  2. For Destination, select the hypervisor to restore the instances to.

  3. For Access node, select Automatic, an access node, or an access node group.

    If you are restoring multiple instances, select Automatic to distribute the workload across the access nodes that are assigned for the destination hypervisor. First, the instances are assigned to access nodes that are in the same zone. Then, instances are assigned to access nodes that are in the same region. If no access nodes are available in the same zone or region, then the instances are assigned to access nodes using the round-robin method. The Automatic option is available for full restore and conversion operations from both streaming backups and IntelliSnap backup copies.

    If you select an access node group to restore instances, the Commvault software distributes the workload across the access nodes that are available in the access node group.

  4. Click Next.

    The Virtual Machines page appears.

Specify the Instances and Settings

  1. Select the instances to restore.

  2. To modify the restore settings, click Edit, and then specify the following:

    • VM display name: Enter a name for the restored instance.

    • Project IDZone: Select the destination zone for the restored instance.

    • Machine type: Select the machine type for the restored instance.

    • Service account: Select the service account for the restored instance.

    • Network settings: To modify the network settings, click the action button action_button, select Edit, and then specify the following:

      • Virtual network/subnet: Select a different virtual network.

      • To use an internal IP address, leave the External IP toggle key turned off, and then select one of the following:

        • Ephemeral (Custom): Enter a custom ephemeral IP address.

        • Ephemeral (Automatic): GCP automatically assigns an ephemeral IP address.

        • Reserved static IP: Select from a user-defined set of available, reserved IP addresses.

        To use these settings, the Google Cloud account that gives Commvault access to the instances that you back up must include the compute.addresses.useinternal permission. For more information about permissions, see Service Account Permissions for Google Cloud Platform.

      • To use an external IP address, move the External IP toggle key to the right, and then select one of the following:

        • Ephemeral: GCP automatically assigns an ephemeral IP address.

        • Reserved static IP: Select from a user-defined set of available, reserved IP addresses.

    • Advanced options:

      • Sole-tenant nodes: Select the nodes or node groups that you want to associate with the restored instances.

        • If you restore an instance from a sole-tenant node to a different project or zone, Commvault restores the instance in the sole-tenant node and the resore operation operates without the sole-tenant properties.

        • The Node affinity dialog box lists all available node groups. However, you can select only node groups that are supported for the specified machine type.

        For information about sole-tenant nodes, go to the Google Cloud documentation website, and search for "sole-tenant nodes".

      • Custom metadata: Enter the custom or predefined key-value pairs for the scripts that you want to run when the instance is restored.

        The replicated instance will have the key-value pairs in the Custom metadata section on the VM instance details page on the destination VM.

        For more information about predefined key-value pairs, see the following:

      • Encryption: You can select an encryption key for the restored instances as follows:

        • Same as source (default value): The encryption key that is used for the instances that you are restoring.

        • Google-managed encryption key: Keys that are provided and managed by Google Cloud.

        • Other encryption keys: Encryption keys that customers manage, including CMEK keys, which are provided by Google Cloud and managed by customers using a cloud key management system (KMS)

        Note

        When you're restoring a VM to a project using an encryption key for the first time, ensure that the service account has the necessary permission to both encrypt and decrypt data using the selected Cloud KMS (Key Management Service). If not, grant this permission to proceed with restoring your project using the customer-managed key.

        Because customer-supplied encryption keys are not supported for restores, they are not available for selection.

        To select an encryption key from a different Google Cloud project, click Switch project, and then select the project.

        To restore with encryption, the Google Cloud account that gives Commvault access to the instances that you back up must include certain permissions. For information, see Service Account Permissions for Google Cloud Platform.

  3. Click Next.

    The Restore Options page appears.

Specify the Restore Options

Specify the following settings:

  • Power on VMs after restore: Automatically restart instances after they are restored.

    The power state of the instance does not affect subsequent backups. If the instance is powered on during backups, by default, the instance is powered on again after the restore completes (unless you clear this check box).

  • Unconditionally overwrite if it already exists: Delete an existing instance and replace it with the restored instance.

    If an existing instance with the same name exists on the destination host and you do not select Unconditionally overwrite if it already exists, the restore job fails.

  • Reuse existing VM client: Reuse the existing instance and map its information, such as client name, host name, and client ID, to the source instance.

  • Notify user on job completion: Receive an email notification that the restore is complete.

The Summary page appears.

Review the Summary and Start the Restore

  1. Review the summary to verify the settings.

  2. Click Submit to start the restore.

Loading...