Stay organized with collections
Save and categorize content based on your preferences.
The following is a list of known behaviors encountered when attempting to run
some concurrent operations.
Concurrent backup operations
Backupdelete operations associated with the same
source instance must be performed one at a time.
Bulk backup delete operations within a backup chain are not supported. While
a delete operation is pending, any new delete operations within the same
backup chain return a RESOURCE_EXHAUSTED error. This is regardless of
whether the source instance has been deleted.
If the source instance has been deleted, users receive a similar
FAILED_PRECONDITION error.
This limitation applies to every service tier but basic SSD and basic HDD.
Note that Filestore does support concurrent backup delete
operations when backups reference separate source instances.
For example, an instance labeled Source1 has backup data referenced in
Backup1 and Backup2. Source2 has backup data referenced in Backup3
and Backup4. Backup1 and Backup2 can't be deleted in parallel,
however, Backup2 and Backup3 can.
Backup create and backup delete operations initiated within the same
backup chain can run concurrently. However, users can't complete a backup
create operation while the most recent backup is being deleted.
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.
The following backups operations have a rate limit of once per 10 minutes in
the steady state:
Creating a backup of Filestore instance
Restoring a Filestore instance from a backup (in-place restore)
[[["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-07 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)"]]
