백업 체인 내에서 대량 백업 delete 작업은 지원되지 않습니다. delete 작업이 보류 중일 때 동일한 백업 체인 내에서 새 delete 작업을 수행하면 RESOURCE_EXHAUSTED 오류가 반환됩니다. 이는 소스 인스턴스가 삭제되었는지 여부와 관계가 없습니다.
소스 인스턴스가 삭제된 경우 사용자에게 유사한 FAILED_PRECONDITION 오류가 표시됩니다.
이 제한사항은 기본 SSD 및 기본 HDD를 제외한 모든 서비스 계층에 적용됩니다.
백업이 별도의 소스 인스턴스를 참조할 때 Filestore는 동시 백업 delete 작업을 지원합니다.
예를 들어 Source1이라는 라벨의 인스턴스에 Backup1 및 Backup2에서 참조되는 백업 데이터가 포함됩니다. Source2에는 Backup3 및 Backup4에서 참조되는 백업 데이터가 포함됩니다. Backup1 및 Backup2를 동시에 삭제할 수 없지만 Backup2 및 Backup3은 삭제할 수 있습니다.
동일한 백업 체인 내에서 시작된 백업 create 및 백업 delete 작업을 동시에 실행할 수 있습니다. 그러나 사용자는 최신 백업을 삭제하는 동안 백업 create 작업을 완료할 수 없습니다.
최신 백업을 삭제하는 동안 인스턴스의 새 백업을 만들려고 시도하면 FAILED_PRECONDITION 오류가 표시됩니다. 예를 들어 Source1에 Backup1 및 Backup2로 구성된 백업 체인이 있고 사용자가 Backup3에 대한 create 작업을 시작하면 create 작업이 완료될 때까지 Backup2를 삭제할 수 없습니다.
가장 최근의 백업에는 백업 create 작업을 성공적으로 완료하는 데 필요한 가장 중요한 데이터가 포함되어 있기 때문입니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(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)"]]
