Find unprotected resources with Protection Summary

The protection summary dashboard helps you manage and verify the data protection status of your Google Cloud resources. It provides a centralized, at-a-glance view of backup configurations for your Compute Engine instances and disks, and Cloud SQL instances across all supported regions in your project.

This centralized dashboard is essential for your data protection strategy because you can find unprotected resources that lack a backup or have misconfigured protection policies. By highlighting these gaps, Protection summary helps you make informed decisions to prevent data loss and ensure business continuity.

Some of the key benefits of protection summary include the following:

  • Holistic protection visibility: Get a centralized overview of your entire backup configuration across all your supported workloads in one place.
  • Readily find protection gaps: Quickly pinpoint resources with missing or misconfigured backups, allowing you to address deviations from your data protection policies.
  • Seamless integration: Protection summary works with your existing Google Cloud environment and running workloads, providing immediate value without requiring complex configurations or impacting performance.

Protection summary is supported for the following resource types:

  • Compute Engine instance
  • Compute Engine disk
  • Cloud SQL instance

What 'configured for backup' means

Protection summary reports a resource as "configured for backup" based on its association with built-in Google Cloud data protection tools. This view does not include data from any third-party backup tools.

A resource is considered configured in the following cases:

  • Compute Engine instance: The instance has a backup plan OR at least one of its attached disks has a Google Cloud snapshot schedule.
  • Compute Engine disk: The disk meets any of the following conditions:
    • It has a Google Cloud snapshot schedule.
    • It is associated with a backup plan.
    • It is attached to a VM that has a backup plan which covers the disk.
  • Cloud SQL instance: The instance has a backup plan or built-in Cloud SQL automated backups.

Before you begin

Enable the Backup and DR API in the project where you are viewing the protection summary.

Enable the API

For information about protection summary in the Backup and DR API see API Reference.

Required IAM permissions

The following permissions are required to view protection summary:

  • IAM Role: Backup and DR Backup Config Viewer
  • IAM permissions:
    • backupdr.resourceBackupConfigs.list
    • backupdr.resourceBackupConfigs.get
    • backupdr.locations.list

View protection summary for a project and region

To view the protection summary for a project and region, do the following:

  1. In the Google Cloud console, go to the Backup and DR protection summary page.

    Go to Protection summary

  2. Select the Region and the Resource type and click View.

    The resources in that region are listed in two tabs. The Unprotected Resources tab is the quickest way to identify unprotected resources in the selected region.

    Resources with Protected Resources are categorized into two statuses:

    • Vaulted: shows a list of resources being backed up in a backup vault.
    • Not vaulted: shows a list of all resources that are backed up without a backup vault.
  3. The following fields are displayed for the selected project and region:

    • Resource name: the display name of the resource.
    • Resource type: the type of resource. It can be a Compute Engine instance, Compute Engine disk, Compute Engine regional disk, or Cloud SQL instance.
    • Backup schedule type: the type of backup schedule applied to a resource. For example backup template or snapshot schedules.
    • Backup plan name: the name of the resource that is providing backup scheduling configuration. For automated, unnamed backup schedules, this field is empty.
    • Configuration state: values are Not configured, Not vaulted, and Vaulted.
    • Backup schedule state: the status of the backup schedule. It can be Active or Inactive.
    • Backup scope: the scope of the specific resource considered for backup, either Full instance or Disk name.
    • Backup location: the zonal regional or multi-regional locations where the backups are located.
    • Latest successful backup: for example, mediumLongdate Aug 21, 2025, 8:45:18 PM.
    • Backup vault: the name of the backup vault used for backups.
    • PITR Configuration: the name of the point-in-time-recovery configuration used for backups.
    • Public IP address: the public IP address assigned to a resource.
    • Private IP address: the private IP address assigned to a resource.

Protection summary supported regions

Protection summary is supported in the following regions.

Geographic Area Region Name Region Description
North America
northamerica-northeast1 * Montrรฉal leaf icon Low CO2
northamerica-northeast2 Toronto leaf icon Low CO2
us-central1 Iowa leaf icon Low CO2
us-east1 South Carolina
us-east4 Northern Virginia
us-east5 Columbus
us-south1 Dallas leaf icon Low CO2
us-west1 Oregon leaf icon Low CO2
us-west2 Los Angeles
us-west3 Salt Lake City
us-west4 Las Vegas
northamerica-south1 * Querรฉtaro
South America
southamerica-east1 Sรฃo Paulo leaf icon Low CO2
southamerica-west1 Santiago leaf icon Low CO2
Europe
europe-central2 Warsaw
europe-north1 Finland leaf icon Low CO2
europe-southwest1 Madrid leaf icon Low CO2
europe-west1 Belgium leaf icon Low CO2
europe-west2 London leaf icon Low CO2
europe-west3 Frankfurt
europe-west4 Netherlands leaf icon Low CO2
europe-west6 Zรผrich leaf icon Low CO2
europe-west8 Milan
europe-west9 Paris leaf icon Low CO2
europe-west10 Berlin leaf icon Low CO2
europe-west12 Turin
Middle East
me-central1 Doha
me-central2 Dammam
me-west1 Israel
Africa
africa-south1 Johannesburg
Asia Pacific
asia-east1 Taiwan
asia-east2 Hong Kong
asia-northeast1 Tokyo
asia-northeast2 * Osaka
asia-northeast3 Seoul
asia-southeast1 Singapore
asia-southeast2 Jakarta
australia-southeast1 Sydney
australia-southeast2 Melbourne
India
asia-south1 Mumbai
asia-south2 Delhi

* Querรฉtaro, Montrรฉal and Osaka each have three zones housed in one or two physical data centers. In the rare event of a disaster, data stored in these regions can be lost.

Limitations

The limitations of the protection summary view are as follows:

  • It is only compatible with resources located in regions that have support for the Backup and DR management console. See Supported regions for a list of supported regions.
  • You can access it only from a project where Backup and DR Service is enabled.
  • Data is periodically refreshed every couple of hours, but in some cases it can take around 24 hours.

Sort and filter protection summary backup configuration information

This section describes how you can sort and filter the backup configurations that are returned by the ListResourceBackupConfigs API call in the protection summary service.

Sorting support

Sort (ASC, DESC) is supported only for target_resource_display_name. By default, the ListResourceBackupConfigs API call returns the resource backup configurations ordered alphabetically by the resource name.

Filtering support

The following fields can be used for filtering the resource backup configurations returned by the ListResourceBackupConfigs API call:

Field Name Field Type Supported Filtering operators
target_resource_display_name string both : and =
target_resource_type string :
backup_configs_details.backup_config_source_display_name string :
backup_configs_details.type string :
backup_configured bool =
vaulted bool =

Wildcard matching (using *) is supported only for the target_resource_display_name field.

Filtering syntax

The filtering syntax is following the API filtering guidance set in AIP 160 with the following limitations:

  • Only the AND operator and nesting are supported. Everything else is not supported (including OR, NOT and any combination of these operators).

    Examples

    Valid: Filter uses AND operator: target_resource_display_name=\"vm-instance1\" AND target_resource_type=CLOUDSQL_INSTANCE

    Valid: Filter uses nesting and only AND operator: (target_resource_display_name=\"vm-instance1\" AND target_resource_type=CLOUDSQL_INSTANCE) AND backup_configured=true

    Invalid: Filter uses OR operator: target_resource_display_name=\"vm-instance1\" OR target_resource_type=CLOUDSQL_INSTANCE

  • Prefix match is supported only for target_resource_display_name

    Examples

    Valid: Filter using prefix match: target_resource_display_name:\"vm-instance1*\"

    Invalid: Filter compares a suffix match: target_resource_display_name:\"*vm-instance1\"

    Invalid: Filter compares a suffix match: target_resource_display_name=\"vm-instance1*\"