Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menunjukkan cara menyelesaikan masalah dengan Layanan Pencadangan dan DR untuk resource yang dicadangkan dalam vault cadangan menggunakan rencana pencadangan. Untuk menemukan solusi bagi resource yang dilindungi menggunakan
template cadangan
di konsol pengelolaan, lihat ID peristiwa dan pesan error.
PERMISSION_DENIED masalah
Tugas pencadangan gagal karena tidak memiliki izin di project sumber dan
pesan error berikut ditampilkan:
Backup and DR agent or backup vault service agent is missing the permissions required to take backups of resources in the source project.
Untuk mengatasi masalah tersebut, lakukan langkah berikut:
Jika vault cadangan dan resource berada dalam project yang sama,
tetapkan peran IAM agen Backup dan DR (roles/backupdr.serviceAgent)
ke
agen layanan backup dr,
yang dalam format service-<project-number>@gcp-sa-backupdr..
Jika brankas cadangan dan resource yang akan dilindungi berada dalam project yang berbeda, tetapkan peran IAM Compute instance admin (v1) (roles/compute.instanceAdmin.v1) ke agen layanan backup dr, yang berada dalam format service-<project-number>@gcp-sa-backupdr..
FAILED_PRECONDITION masalah
Pekerjaan pencadangan gagal saat resource yang dilindungi dihapus dan pesan error berikut ditampilkan:
Backup job failed due to unmet conditions. Check for source resource deletion or backup misconfigurations.
Untuk menyelesaikan masalah ini, lakukan tindakan berikut:
Pastikan resource yang dilindungi masih ada dari halaman instance VM.
Error 412 terjadi saat upaya mencadangkan Persistent Disk atau Google Cloud Hyperdisk
gagal karena pelanggaran batasan kebijakan organisasi selama pembuatan cadangan,
sehingga menghasilkan pesan error yang menyatakan
Error 412: Constraint constraints/compute.storageResourceUseRestrictions violated for project aaaaa. projects/aaax/zones/aa-aaaaa-a/disks/aaaa can't be used within your project., conditionNotMet
Backup and DR membuat cadangan Persistent Disk dan Google Cloud Hyperdisk Anda.
Backup berada di project Google Cloud Anda (juga dikenal sebagai project tenant)
yang dikelola oleh Google Cloud. Project tenant ada dalam organisasi google.com, terpisah dari organisasi Anda sendiri.
Kebijakan organisasi Anda menentukan tempat Anda dapat membuat resource penyimpanan.
Error The Constraint constraints/compute.storageResourceUseRestrictions violated
berarti resource atau cadangan melanggar kebijakan karena dibuat
di project tenant yang bukan bagian dari struktur organisasi yang diizinkan.
Karena project tenant berada dalam organisasi google.com, project tersebut berada di luar kebijakan yang Anda tetapkan, sehingga menyebabkan pencadangan gagal.
Untuk mengatasi error ini, gunakan petunjuk berikut:
Temukan kebijakan organisasi yang menerapkan batasan
constraints/compute.storageResourceUseRestrictions. Untuk mengetahui informasi selengkapnya tentang cara melihat kebijakan organisasi menggunakan konsol Google Cloud , lihat Melihat kebijakan organisasi.
Ubah kebijakan constraints/compute.storageResourceUseRestrictions untuk
menyertakan folder project tenant folders/238813353932 yang digunakan oleh
Backup untuk GKE dalam daftar yang diizinkannya.
Simpan perubahan kebijakan setelah Anda menambahkan folder ke daftar yang diizinkan.
Uji ulang operasi pencadangan setelah kebijakan organisasi diperbarui dan diterapkan, yang biasanya memerlukan waktu beberapa menit. Pencadangan harus dilanjutkan
tanpa melanggar batasan penggunaan resource penyimpanan. Jika operasi masih gagal, hubungi Cloud Customer Care untuk mendapatkan bantuan lebih lanjut.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["# Troubleshoot backup failure issues\n\nThis page shows you how to resolve issues with Backup and DR Service for\nresources that are backed up within the backup vault using the\n[backup plan](/backup-disaster-recovery/docs/cloud-console/backup-plan). To find\nsolutions for resources protected using the\n[backup template](/backup-disaster-recovery/docs/create-plan/create-template)\nin the management console, see [Event IDs and error messages](/backup-disaster-recovery/docs/event-codes).\n\n`PERMISSION_DENIED` issue\n-------------------------\n\nThe backup job failed due to missing permissions in the source project and\nthe following error message is displayed: \n\n Backup and DR agent or backup vault service agent is missing the permissions required to take backups of resources in the source project.\n\nTo resolve the issue, do the following:\n\n1. If the backup vault and the resource are in the same project, assign the Backup and DR agent (`roles/backupdr.serviceAgent`) IAM role to the [backup dr service agent](/backup-disaster-recovery/docs/cloud-console/backup-vault-create#agent), which is in the `service-\u003cproject-number\u003e@gcp-sa-backupdr.iam.gserviceaccount.com` format.\n2. If the backup vault and the resource to protect are in different projects, assign the Compute instance admin (v1) (`roles/compute.instanceAdmin.v1`) IAM role to the [backup dr service agent](/backup-disaster-recovery/docs/cloud-console/backup-vault-create#agent), which is in the `service-\u003cproject-number\u003e@gcp-sa-backupdr.iam.gserviceaccount.com` format.\n\n`FAILED_PRECONDITION` issue\n---------------------------\n\nThe backup job failed when the protected resource was deleted and the following\nerror message is displayed: \n\n Backup job failed due to unmet conditions. Check for source resource deletion or backup misconfigurations.\n\nTo resolve this issue, do the following:\n\n- Verify that the protected resource still exists from the **VM instances** page.\n\n [Go to VM instances](https://console.cloud.google.com/compute/instances)\n- If the deletion was intentional, [unprotect the Compute Engine instance](/backup-disaster-recovery/docs/cloud-console/compute/compute-instance-backup#unprotect).\n\nError 412: constraints/compute.storageResourceUseRestrictions violated\n----------------------------------------------------------------------\n\nError 412 occurs when an attempt to back up a Persistent Disk or Google Cloud Hyperdisk\nfails due to an organization policy constraint violation during backup creation,\nresulting in an error message stating\n`Error 412: Constraint constraints/compute.storageResourceUseRestrictions violated for project aaaaa. projects/aaax/zones/aa-aaaaa-a/disks/aaaa can't be used within your project., conditionNotMet`\n\nBackup and DR creates backups of your Persistent Disks and Google Cloud Hyperdisks.\nThe backups reside in your Google Cloud project (also known as the tenant project)\nthat is managed by Google Cloud. The tenant project exists within the\ngoogle.com organization, separate from your own organization.\n\nYour organization policy dictates where you can create storage resources.\n`The Constraint constraints/compute.storageResourceUseRestrictions violated`\nerror means that a resource or backup is violating the policy by being created\nin a tenant project that isn't part of your allowed organizational structure.\nBecause the tenant project is within the google,com organization, it falls outside of\nyour defined policy, which leads to the backup failure.\n\nTo resolve this error, use the following instructions:\n\n1. Locate the organization policy that implements the\n `constraints/compute.storageResourceUseRestrictions` constraint. For more\n information about how to view organization policies using the Google Cloud console,\n see [Viewing organization policies](/resource-manager/docs/organization-policy/creating-managing-policies#viewing_organization_policies).\n\n2. Modify the `constraints/compute.storageResourceUseRestrictions` policy to\n include the `folders/238813353932` tenant project folder used by\n Backup for GKE in its allowlist.\n\n | **Note:** Make sure the specified folder ID is added to the list of allowed locations to permit Backup for GKE to create snapshots within its tenant projects, even though they are outside your organizational hierarchy.\n3. Save the policy changes after you add the folder to the allowlist.\n\n4. Retest the backup operation after the organization policy updates and\n propagates, which usually takes a few minutes. The backup should proceed\n without violating the storage resource use restrictions. If the operation is\n still unsuccessful, contact Cloud Customer Care for further assistance."]]
