Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Berikut adalah daftar perilaku umum yang ditemukan saat mencoba menjalankan
beberapa operasi serentak.
Operasi pencadangan serentak
Operasi deletePencadangan yang terkait dengan instance sumber
yang sama harus dilakukan satu per satu.
Operasi delete pencadangan massal dalam rantai pencadangan tidak didukung. Saat
operasi delete tertunda, setiap operasi delete baru dalam rantai
pencadangan yang sama akan menampilkan error RESOURCE_EXHAUSTED. Hal ini terlepas dari
apakah instance sumber telah dihapus.
Jika instance sumber telah dihapus, pengguna akan menerima error FAILED_PRECONDITION yang serupa.
Batasan ini berlaku untuk setiap tingkat layanan, kecuali SSD dasar dan HDD dasar.
Perhatikan bahwa Filestore mendukung operasi delete cadangan serentak saat cadangan mereferensikan instance sumber terpisah.
Misalnya, instance yang diberi label Source1 memiliki data cadangan yang dirujuk di
Backup1 dan Backup2. Source2 memiliki data cadangan yang dirujuk di Backup3
dan Backup4. Backup1 dan Backup2 tidak dapat dihapus secara paralel,
tetapi Backup2 dan Backup3 dapat.
Operasi pencadangan create dan pencadangan delete yang dimulai dalam rantai pencadangan
yang sama dapat berjalan secara serentak. Namun, pengguna tidak dapat menyelesaikan operasi
create pencadangan saat pencadangan terbaru sedang dihapus.
Jika pengguna mencoba membuat cadangan baru instance saat cadangan terbaru sedang dihapus, mereka akan menerima error FAILED_PRECONDITION. Misalnya, jika Source1 memiliki rantai cadangan yang terdiri dari Backup1
dan Backup2, dan pengguna memulai operasi create untuk Backup3, mereka
tidak akan dapat menghapus Backup2 hingga operasi create selesai.
Hal ini karena cadangan terbaru berisi data paling penting
yang diperlukan untuk berhasil menyelesaikan operasi create cadangan.
Operasi pencadangan berikut memiliki batas kapasitas sekali per 10 menit dalam
status stabil:
Membuat cadangan instance Filestore
Memulihkan instance Filestore dari cadangan (pemulihan di tempat)
[[["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-08-18 UTC."],[[["\u003cp\u003eBackup \u003ccode\u003edelete\u003c/code\u003e operations for the same source instance must be performed sequentially, and attempting to delete multiple backups in the same chain concurrently will result in a \u003ccode\u003eRESOURCE_EXHAUSTED\u003c/code\u003e error, or \u003ccode\u003eFAILED_PRECONDITION\u003c/code\u003e if the source has been deleted.\u003c/p\u003e\n"],["\u003cp\u003eWhile backup \u003ccode\u003ecreate\u003c/code\u003e and \u003ccode\u003edelete\u003c/code\u003e operations within the same backup chain can run concurrently, you cannot delete the most recent backup while a new backup is being created, as this will trigger a \u003ccode\u003eFAILED_PRECONDITION\u003c/code\u003e error.\u003c/p\u003e\n"],["\u003cp\u003eConcurrent backup \u003ccode\u003edelete\u003c/code\u003e operations are possible if the backups are associated with different source instances.\u003c/p\u003e\n"],["\u003cp\u003eCreating a new backup, restoring from a backup, and creating a new Filestore instance from a backup all have a rate limit of once per 10 minutes.\u003c/p\u003e\n"]]],[],null,["# Operations concurrency\n\nThe following is a list of known behaviors encountered when attempting to run\nsome concurrent operations.\n\nConcurrent backup operations\n----------------------------\n\n- [Backup](/filestore/docs/backups) `delete` operations associated with the same\n source instance must be performed one at a time.\n\n Bulk backup `delete` operations within a backup chain are not supported. While\n a `delete` operation is pending, any new `delete` operations within the same\n backup chain return a `RESOURCE_EXHAUSTED` error. This is regardless of\n whether the source instance has been deleted.\n - If the source instance has been deleted, users receive a similar\n `FAILED_PRECONDITION` error.\n\n - This limitation applies to every service tier but basic SSD and basic HDD.\n\n - Note that Filestore does support concurrent backup `delete`\n operations when backups reference separate source instances.\n\n For example, an instance labeled `Source1` has backup data referenced in\n `Backup1` and `Backup2`. `Source2` has backup data referenced in `Backup3`\n and `Backup4`. `Backup1` and `Backup2` can't be deleted in parallel,\n however, `Backup2` and `Backup3` can.\n- Backup `create` and backup `delete` operations initiated within the same\n backup chain *can* run concurrently. However, users can't complete a backup\n `create` operation while the most recent backup is being deleted.\n\n - If the user attempts to create a new backup of the instance while the most recent backup is being deleted, they will receive a `FAILED_PRECONDITION` error. For example, if `Source1` has a backup chain composed of `Backup1` and `Backup2`, and the user begins a `create` operation for `Backup3`, they won't be able to delete `Backup2` until the `create` operation completes. This is because the most recent backup contains the most critical data needed to successfully complete the backup `create` operation.\n- The following backups operations have a rate limit of once per 10 minutes in\n the steady state:\n\n - Creating a backup of Filestore instance\n - Restoring a Filestore instance from a backup (in-place restore)\n - Creating a new Filestore instance from a backup\n\n For more information, see [Rate limits for backups](/filestore/docs/limits#rate-limits-backups).\n\nWhat's next\n-----------\n\n- [Known issues](/filestore/docs/known-issues)\n- [List of Filestore-specific response error codes and messages](/filestore/docs/response-errors)"]]
