Protection summary 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, Cloud SQL instances and Filestore instances across all supported regions. You can use protection summary to view backup configurations at the project, folder, or organization level.
Benefits
When you utilize protection summary, you get the following benefits:
Holistic protection visibility: get a centralized overview of your entire backup configuration across all your supported workloads in one place.
Find protection gaps: pinpoint resources with missing or misconfigured backups and address deviations from your data protection policies.
Seamless integration: integrate seamlessly with your existing Google Cloud environment and running workloads, providing immediate value without requiring complex configurations or impacting performance.
Supported resource types
Protection summary is supported for the following resource types:
Compute Engine instances
Compute Engine disks
Cloud SQL instances
Filestore instances
Understanding the Configured for backup status
Protection summary reports a resource as configured for backup based on its association with built-in Google Cloud data protection tools. This view doesn't 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 virtual machine (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.
Filestore instance: the instance has a backup plan or built-in Filestore automated backups.
Before you begin
Enable the Backup and DR API in the project where you are viewing the protection summary.
For information about protection summary in the Backup and DR API see API Reference.
Required IAM permissions
The following permissions are required to view the protection summary:
IAM role: Backup and DR Backup Config Viewer
IAM permissions:
backupdr.resourceBackupConfigs.listbackupdr.resourceBackupConfigs.getbackupdr.locations.list
View protection summary across a project, folder, or organization
To view the protection summary for your data resources, do the following:
In the Google Cloud console, go to the Backup and DR protection summary page.
Select the scope for which you want to view the protection summary, either Project, Folder, or Organization.
Select the Resource type from the drop-down menu, and then click View.
The Unprotected resources tab is the quickest way to identify unprotected resources.
Protected resources, which are displayed under the Protected resources tab, are categorized into two Configuration states:
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.
The following fields are displayed in the protection summary:
Resource name: the display name of the resource.
Project: the project associated with the resource.
Resource type: the type of resource—for example, a Compute Engine instance, Compute Engine disk, Compute Engine regional disk, Cloud SQL instance, or Filestore instance.
Backup schedule type: the type of backup schedule applied to a resource, such as a backup template or snapshot schedule.
Backup plan name: the name of the resource that provides the backup scheduling configuration. For automated, unnamed backup schedules, this field is empty.
Configuration state: the backup configuration state. The possible values are Not configured, Not vaulted, and Vaulted.
Backup schedule state: the status of the backup schedule. The possible values are Active and 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 location where the backups are stored.
Latest successful backup: the timestamp of the latest successful backup—for example,
Mar 1, 2026, 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 the resource.
Private IP address: the private IP address assigned to the resource.
For projects with the Backup and DR API enabled, you can use the Schedule backup option to enhance the resource protection using vaulted backups.
If the Backup and DR API is not enabled for a project, the Schedule backup option is unavailable. To enable the API, hover over the Schedule backup option and onboard to the Introductory Trial (if applicable). Once the Backup and DR API is enabled, you can enhance resource protection using vaulted backups.
Protection summary supported regions
Protection summary is supported in the following regions.
| Geographic Area | Region Name | Region Description | |
|---|---|---|---|
| North America | |||
northamerica-northeast1 * |
Montréal |
|
|
northamerica-northeast2 |
Toronto |
|
|
us-central1 |
Iowa |
|
|
us-east1 |
South Carolina | ||
us-east4 |
Northern Virginia | ||
us-east5 |
Columbus | ||
us-south1 |
Dallas |
|
|
us-west1 |
Oregon |
|
|
us-west2 |
Los Angeles | ||
us-west3 |
Salt Lake City | ||
us-west4 |
Las Vegas | ||
northamerica-south1 * |
Querétaro | ||
| South America | |||
southamerica-east1 |
São Paulo |
|
|
southamerica-west1 |
Santiago |
|
|
| Europe | |||
europe-central2 |
Warsaw | ||
europe-north1 |
Finland |
|
|
europe-north2 |
Stockholm |
|
|
europe-southwest1 |
Madrid |
|
|
europe-west1 |
Belgium |
|
|
europe-west2 |
London |
|
|
europe-west3 |
Frankfurt | ||
europe-west4 |
Netherlands |
|
|
europe-west6 |
Zürich |
|
|
europe-west8 |
Milan | ||
europe-west9 |
Paris |
|
|
europe-west10 |
Berlin | ||
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 (northamerica-south1), Montréal (northamerica-northeast1), and Osaka (asia-northeast2) don't support zone separation. This means the multiple zones within each of these regions may not be located in physically separate data center campuses. Consequently, a single, localized physical disaster event could potentially impact multiple zones within the same region, increasing the risk of data loss compared to regions that support zone separation.
Limitations
Protection summary 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.
Data is periodically refreshed, usually within an hour, but in some cases it can take up to 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 follows the API filtering guidance set in AIP 160, with the following limitations:
Only the
ANDoperator and nesting are supported. All other operators and combinations, includingORandNOT, are not supported.Examples
Valid: The filter uses the
ANDoperator:target_resource_display_name="vm-instance1" AND target_resource_type=CLOUDSQL_INSTANCEValid: The filter uses nesting and only the
ANDoperator:(target_resource_display_name="vm-instance1" AND target_resource_type=CLOUDSQL_INSTANCE) AND backup_configured=trueInvalid: The filter uses the
ORoperator:target_resource_display_name="vm-instance1" OR target_resource_type=CLOUDSQL_INSTANCEPrefix match is supported only for
target_resource_display_name.Examples
Valid: The filter uses a prefix match:
target_resource_display_name:"vm-instance1*"Invalid: The filter compares a suffix match:
target_resource_display_name:"*vm-instance1"Invalid: The filter compares a suffix match:
target_resource_display_name="vm-instance1*"
What's next
- Read about best practices for defending against ransomware with Backup and DR.