> [!CAUTION]
> **Caution:** Support for backing up and restoring workloads managed using the legacy appliance management console is deprecated. For more information, see [Feature deprecations](https://docs.cloud.google.com/backup-disaster-recovery/docs/deprecations.md.txt) in the Backup and DR documentation.

This page describes how to back up Google Cloud VMware Engine into a
backup vault using the appliance management console.

Google Cloud VMware Engines are captured in their entirety using VMware
API calls. You can manage a VM by assigning a template and a resource profile to
it to define the backup plan and capture the entire VM.

When a backup/recovery appliance associates a backup template with an entire
VM it is not aware of VM content, so no application-specific actions are performed.

When an entire virtual server is captured, a fully functional virtual server,
including the operating system, and applications with their data is captured.
Having a copy of the entire virtual server ensures that the data can be
accessed quickly and without issues. Capturing entire virtual servers allows
groups of virtual servers and their applications to be managed with a single
backup template. See
[Application backup or capture wizard](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/onboarding-wizard.md.txt)
for information on how to discover VMs.

You can use a backup vault to store Google Cloud VMware Engine backups.
Sending backups to a backup vault provides protection against
modification (immutability) and deletion (indelibility). For more information
about backup vault, see [backup vault for immutable and
indelible backups](https://docs.cloud.google.com/backup-disaster-recovery/docs/concepts/backup-vault).

With a backup vault, you can store backups in a single region. If you
need backups in multiple regions, consider the following options:

- You can define a backup plan and resource profile that sends backups to two or more OnVault pools with two or more backup vaults. You can create these backup vaults in different regions, which provides dual-region protection for your backups. Note that you will be charged for the storage in each backup vault separately.
- You can define an OnVault pool that uses a multi-regional Cloud Storage bucket. Note that this option doesn't provide the protection against modification and deletion that a backup vault provides.

Backing up Google Cloud VMware Engine into a backup vault involves the following steps.

1. [Create a backup vault](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-gcve-into-backup-vault.md.txt#vault)

2. [Register a backup/recovery appliance as an authorized accessor for a backup vault](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-gcve-into-backup-vault.md.txt#register)

3. [Create an OnVault pool associated with backup vault](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-gcve-into-backup-vault.md.txt#onvault)

4. [Create a profile associated with the backup vault](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-gcve-into-backup-vault.md.txt#profile)

5. [Create a template](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-gcve-into-backup-vault.md.txt#template)

6. [Apply a backup plan to protect a Google Cloud VMware Engine](https://docs.cloud.google.com/backup-disaster-recovery/management-console/backup/backup-gcve-into-backup-vault.md.txt#plan)

## Create a backup vault

A backup vault is a container to store backups. To back up Google Cloud VMware Engine
to a backup vault, you need to create a
[backup vault](https://docs.cloud.google.com/backup-disaster-recovery/docs/concepts/backup-vault.md.txt).
For instructions, see [Create and manage a backup vault in the Google Cloud console](https://docs.cloud.google.com/backup-disaster-recovery/docs/cloud-console/backup-vault-create.md.txt).


## Register a backup/recovery appliance as an authorized accessor for a backup vault

You can access a backup vault from the backup/recovery appliance project only
after the appliance service account is granted with the
Backup and DR Backup Vault Accessor (`roles/backupdr.backupvaultAccessor`)
IAM role in the backup vault project. Without this role,
you cannot access the backup vault to complete the setup to enable
backup creation. For instructions, see
[Grant roles to the backup/recovery appliance service account](https://docs.cloud.google.com/backup-disaster-recovery/docs/cloud-console/backup-vault-create.md.txt#service-account).

> [!NOTE]
> **Note:** The backup/recovery appliance and the backup vault don't need to be in the same project.

## Create an OnVault pool associated with a backup vault

OnVault pools created with the backup vault type store data
in the backup vault. A backup vault with a minimum enforced
retention period prevents the deletion of backups before the enforced retention
period is met.

Backup/recovery appliances that are registered with the backup vault pool type
are displayed for selection.

Use the following instructions to create an OnVault pool that points to a
backup vault.

1. In the Backup and DR appliance management console, click **Manage** and select **Storage pools** from the menu.
2. Click **Add OnVault pool**.
3. Enter a name for the pool. Valid characters are letters, numbers, spaces, hyphens (-), and underscores (_).
4. Check that the **Pool type** is set to **Backup vault**.
5. From the **Appliance** list, select the appliance you want to add the OnVault pool to. If your appliance is not available to select, you will need to [updated the appliance](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/update-appliance) to the latest version.
6. In the **Project ID** field, enter the Google Cloud project that contains your backup vault.
7. From the **Region** list, select the region that contains your backup vault.
8. From the **Choose a backup vault** section, select a backup vault.
9. Click **Save**.

## Create a profile associated with a backup vault based OnVault pool

A resource profile specifies the storage medium for Google Cloud VMware Engine
backups. You can use a backup vault, a specialized storage for
Backup and DR backups, designed with features that support resilience
against malicious or accidental deletion of backups. After the profile is
created and designated for use with backup vaults, the profile cannot
be edited to use a different storage pool type and a backup vault
must always be specified. Also, if the resource profile is in use to protect
an application, the specified backup vaults cannot be changed.


Use the following instructions to create a resource profile which points to
a backup vault.

1. In the Backup and DR appliance management console, click **Backup plans** and select **Profiles** from the menu.
2. Click **Create profile**.
3. Enter a name and optional description for the resource profile.
4. Select **Use OnVault pools that point to backup vaults (Recommended)**.
5. In the **Primary appliance** section, from the **Appliance** list, select the appliance type that the backup pool type is associated with.
6. From the **Snapshot pool** list, select a snapshot pool type.
7. From the **OnVault pool 1** list, select the OnVault pool associated with your backup vault.
8. Optional. From the **OnVault pool 2** list, select the OnVault pool associated with your backup vault that is created in a different region.
9. Click **Save profile**.

## Create a template with the backup policies

A backup plan template defines backup creation and management details, such as
the backup schedule and the timeline for backup deletion. Backup plan
templates are created within the appliance management console. Create a
backup template using the instructions in
[Manage backup templates](https://docs.cloud.google.com/backup-disaster-recovery/docs/create-plan/create-template).

## Apply a backup plan to protect a Google Cloud VMware Engine

Use the following instructions to apply a backup plan to protect Google Cloud VMware Engine VM.

1. Click the **App Manager** tab and select the **Applications** option from
   the drop-down list. The **Applications** page opens.

2. Select the VM that you want to manage, and then choose
   **Manage Backup Plan** from the drop-down list at the bottom right corner of
   the page. The **Manage Backup Plan** page opens.

3. From the **Manage Backup Plan** page, choose from the **Template** and
   **Profile** drop-down lists:

   - **Template.** An existing backup template that includes policies to define
     the snapshot, direct to onvault, or replication of the application data.

   - **Profile.** An existing resource profile that defines the resources
     used to store the data of the application as snapshot or replicated images.

     The **Manage Backup Plan** page shows a view of the policies assigned to the
     selected applications in the backup plan policy map. Management comes from the
     template policies and profiles that you designed in the backup plans.
4. Click **Apply Backup Plan** . The **Apply backup plan** page opens.

5. Configure the application's details and settings or policy overrides settings.

   - **Application Settings** . Apply application-specific settings when managing
     a VM. Application settings may be useful or required in certain
     circumstances. See
     [Configure application settings for protecting VM data](https://docs.cloud.google.com/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm) for details.

   - **Policy Overrides** . Override specific policy settings previously
     configured in the selected backup template. See [Configure policy overrides](https://docs.cloud.google.com/backup-disaster-recovery/docs/create-plan/policy-settings) for details.

   > [!NOTE]
   > **Note:** You can override policy settings only if the policy template **Allow Overrides on Policy Settings** property has been set to **Yes** .

6. Click **Apply Backup Plan** to apply the backup template and resource
   profile. A success message opens.

7. Click **Okay**.

   If you back up a workload to a backup/recovery appliance that would exceed its
   recommended storage capacity or snapshot limit, you will see a notification
   with a recommendation to back up the data to a different backup/recovery appliance.

   > [!CAUTION]
   > **Caution:** Exceeding the capacity of a backup/recovery appliance can lead to failed jobs and unprotected data and failed restore operations.

   The application may not get backed up until the scheduled job runs according
   to the hours of operations defined in the backup template.
   For example, if at 10:00 (UTC) you assign a template that has hours of
   operation from 02:00 to 05:00 (UTC), then the first job won't start
   until the appliance has an available job slot at 02:00 (UTC) of the following day.
   To run a job immediately, see [perform an on-demand capture](https://docs.cloud.google.com/backup-disaster-recovery/docs/monitor-reports/monitor-jobs#run).

   > [!NOTE]
   > **Note:** All policies start and end times are in UTC time zone.

   To change backup plan settings for the application,
   see [Modify backup plan management of a managed application](https://docs.cloud.google.com/backup-disaster-recovery/docs/access-data/states-of-an-application#remove).
   To disable a backup plan, see [Removing backup plan management of an application](https://docs.cloud.google.com/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm).

> [!NOTE]
> **Note:** To reset one or more application settings back to its default state, click the **Reset to Default** checkbox to the right of the selection you want to reset, or click **Reset All to Default** to reset all application selections back to their default state.