[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-03。"],[],[],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."]]