The following is a list of known behaviors encountered when attempting to run some concurrent operations.
Concurrent backup operations
deleteoperations associated with the same source instance must be performed one at a time.
deleteoperations within a backup chain are not supported. While a
deleteoperation is pending, any new
deleteoperations within the same backup chain return a
RESOURCE_EXHAUSTEDerror. This is regardless of whether the source instance has been deleted.
If the source instance has been deleted, users receive a similar
This limitation applies to every service tier but basic SSD and basic HDD.
Note that Filestore does support concurrent backup
deleteoperations when backups reference separate source instances.
For example, an instance labeled
Source1has backup data referenced in
Source2has backup data referenced in
Backup2can't be deleted in parallel, however,
deleteoperations initiated within the same backup chain can run concurrently. However, users can't complete a backup
createoperation 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_PRECONDITIONerror. For example, if
Source1has a backup chain composed of
Backup2, and the user begins a
Backup3, they won't be able to delete
createoperation completes. This is because the most recent backup contains the most critical data needed to successfully complete the backup
- If the user attempts to create a new backup of the instance while the most recent backup is being deleted, they will receive a