Stay organized with collections
Save and categorize content based on your preferences.
Data residency organizational policy is not supported on workloads that
require a management server and backup/recovery appliance.
This page describes the data residency support for backup vault,
including supported workloads and limitations.
Data residency for backup vault meets compliance and regulatory
requirements by allowing you to limit the geographic locations (regions)
where Google Cloud data is stored at rest according to
Service Specific Terms. With data residency, organization
policy administrators can enforce geographic locations where backup data can be
stored.
Organizations with data residency requirements can set up a
Resource Locations
organization policy constraint that restricts the location of new backup
resources at the organization, project, or folder level of their resource
hierarchy.
Data residency scope and behavior
Data residency enforcement against the organization policy is checked only when
new resources are created. For example, if the organization policy is
set after some Backup vault have already been created, only new
resources that violate the constraint will be blocked and the existing resources
will be unaffected. Existing Backup Plans will continue to function normally,
however manually triggered restore operations or creation of new Backup Plans
that violate data residency constraints will fail if the restore location is not
permitted by the policy.
Data residency compatibility
Data residency enforcement can be used with all workloads that don't depend
on a management server and backup/recovery appliance.
Customers still have complete control over the location of backups managed
by management servers and backup/recovery appliances, through the configuration options
in the management server. However, these workloads are not constrained by the
organizational policies.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Data residency for Backup vault\n\nData residency organizational policy is not supported on workloads that require a management server and backup/recovery appliance.\n\nThis page describes the data residency support for backup vault,\nincluding supported workloads and limitations.\n\nData residency for backup vault meets compliance and regulatory\nrequirements by allowing you to limit the geographic locations (regions)\nwhere Google Cloud data is stored at rest according to\n[Service Specific Terms](/terms/service-terms). With data residency, organization\npolicy administrators can enforce geographic locations where backup data can be\nstored.\n\nOrganizations with data residency requirements can set up a\n[Resource Locations](/resource-manager/docs/organization-policy/defining-locations)\norganization policy constraint that restricts the location of new backup\nresources at the organization, project, or folder level of their resource\nhierarchy.\n\nData residency scope and behavior\n---------------------------------\n\nData residency enforcement against the organization policy is checked only when\nnew resources are created. For example, if the organization policy is\nset after some Backup vault have already been created, only new\nresources that violate the constraint will be blocked and the existing resources\nwill be unaffected. Existing Backup Plans will continue to function normally,\nhowever manually triggered restore operations or creation of new Backup Plans\nthat violate data residency constraints will fail if the restore location is not\npermitted by the policy.\n\nData residency compatibility\n----------------------------\n\nData residency enforcement can be used with all workloads that don't depend\non a management server and backup/recovery appliance.\n\nCustomers still have complete control over the location of backups managed\nby management servers and backup/recovery appliances, through the configuration options\nin the management server. However, these workloads are not constrained by the\norganizational policies."]]
