AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

Home > Manage the Backup Scopes for Virtual Machines > Create a New Backup Scope for Google VM Instance > Use the CAP Gateway Mode

Export to PDF

Use the CAP Gateway Mode

To create a new backup scope, follow the steps below:

  1. Go to the Backup page on the new UI.

Click on the Virtual Machine service tile or click the More actions button on the upper-right corner of the Virtual Machine service tile and click Configure backup scope from the drop-down list.

In the Configure backup scope for virtual machines page, all the existing backup scopes for Azure virtual machines, Amazon EC2 instances, and Google VM instances are listed in the table. You can use the search box to search for the backup scopes by name and manage the columns to adjust the view of the backup scopes.

> ***Note**: You can click the Refresh button in the upper-right corner of this page to retrieve the latest data list for Azure VMs, Amazon EC2 instances, and Google VM instances. The **Last refreshed time** is displayed next to the Refresh button. Additionally, the data list will be automatically refreshed daily at 00:00 local time.

  1. Click the Create button and select Google VM instance

  2. Select CAP Gateway mode and click Next.

  3. In the Select VM instances step, select the project and instances that you want to add to the backup scope. You can use Filters to find the instances you want to protect or use the Search box to search for the instances via the keywords in the name. The number of your selection will be displayed on the row of the tenant name.

  4. Click Next, and you will go to the Configure storage and gateway based on zone step to configure a storage profile and CAP Gateway for each zone. Currently, the only supported storage type is Google Cloud Storage.

    • You can use an existing storage profile or create a new storage profile to store the backup data for the storages in the same region. For details on configuring storage location, refer to Manage Your Storage.

    • For details on configuring CAP Gateways, refer to Manage CAP Gateways.

    *Note: If you have enabled a firewall for your Google VM instances, you need to add the AvePoint IP addresses to your Google VM instance account firewall.

After you finish the storage configuration for each region, click Next to configure the scope information, schedule, and data retention settings. Refer to the following:

![A screenshot of a computer

AI-generated content may be incorrect.](/en/iaas-paas/manage-the-backup-scopes-for-virtual-machines/create-a-new-backup-scope-for-google-vm-instance/images/image37.png "A screenshot of a computer

AI-generated content may be incorrect.")

Scope information – Enter a name and description for the scope you are creating. The description is optional.

- **Application consistency** – Select the **Enable application-consistent snapshots** option if you want to achieve a consistent backup without requiring VM shutdown. For details on how to enable application-consistent snapshots, refer to [Enable Application-consistent Snapshots for Windows VMs](#missing-link) or [Enable Application-consistent Snapshots for Linux VMs](#missing-link). - **Generate index for file-level** **data export** – Select this option if you want to perform file-level data export using the backup data. Otherwise, keep this option deselected. The backup job will take longer to finish to generate an index. The retention period to keep the index will follow the retention policy configured for the backup data. - Note the following: - To generate index for file-level data export, the **OS Config Viewer** role is required for your service account. For details on how to grant the role, refer to [Create a Service Account in Google Cloud Platform](#missing-link). - To generate index for file-level data export, the user of your CAP Gateway service need to be updated to root user: For details, refer to [Required Configurations for Index Generation](#missing-link). - **Schedule** – Select **days**, **weeks**, **months**, or **years** as the unit of time for the backup interval, enter a number in the text box after **Every**, and then configure the start time for your first backup job. - **Notification** – Check the notification profiles which will be applied to the backup scope. - **Retention policy** – Configure when to prune the snapshots from Google Cloud Platform and the backup data from the storage location. Note that if you are using AvePoint storage, the retention policy for backup data is subject to your agreement and you can configure a retention period up to the retention policy in your subscription. - For snapshots in Google Cloud Platform – You can choose the number of the latest snapshots to retain or choose for how long the snapshots will be retained after generation. - > ***Note**: The number of the latest snapshots to retain must be less than 500. - For backup data in storage – Configure the retention period to keep the backup data in the storage. - **Daily/Hourly recovery point** – Enter a number in the text box and select **days** or **weeks** from the drop-down list. The retention period must be between 7 and 28 days. - **Weekly recovery point** – Enter a number in the text box and select **weeks** or **months** from the drop-down list. The retention period must be between 2 and 12 weeks. - **Monthly recovery point** – Enter a number in the text box. The retention period must be between 1 and 12 months. - **Yearly recovery point** – If you are using **AvePoint default storage** with unlimited retention period, the **Unlimited** option is selected automatically. If you want to use a custom retention period, select **Custom**.

  1. Click Next to review your settings.

  2. Click Save to save this backup scope. The backup for the storages in this backup scope will roll out as scheduled. For more details about monitoring the backups, refer to Monitor Your Backup.

Required Configurations for Index Generation

Follow the steps below to update the user of your CAP Gateway to root user.

  1. Execute the following command:

    sudo systemctl edit --full CAPGatewayService.service

  2. Update the value of User and Group to root.

    Update the value of User and Group to root.

  3. Execute the following command lines:

    sudo systemctl daemon-reexec

    sudo systemctl daemon-reload

    sudo systemctl restart CAPGatewayService.service

  4. Execute the following command to check results to make sure the user of your CAP Gateway is root user:

    ps -ef | grep CapGatewayService

    Sample results.