[[["容易理解","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 (世界標準時間)。"],[[["\u003cp\u003eThis page provides instructions on how to delete an AlloyDB backup using the \u003ccode\u003egcloud\u003c/code\u003e command-line interface.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an AlloyDB backup requires specific IAM roles, including \u003ccode\u003eroles/alloydb.admin\u003c/code\u003e, \u003ccode\u003eroles/owner\u003c/code\u003e, or \u003ccode\u003eroles/editor\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud alloydb backups delete\u003c/code\u003e command is used to delete a backup, specifying the \u003ccode\u003eBACKUP_ID\u003c/code\u003e, \u003ccode\u003eREGION_ID\u003c/code\u003e, and \u003ccode\u003ePROJECT_ID\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eWhile on-demand and automated backups can be deleted at any time, deleting continuous backups is restricted to certain conditions, such as when continuous backup and recovery are disabled, or the backup is older than the cluster's recovery window.\u003c/p\u003e\n"],["\u003cp\u003eDeletion of an AlloyDB backup is not permitted if other backups rely on its existence, such as in the case of incremental backups.\u003c/p\u003e\n"]]],[],null,["# Delete a backup\n\nThis page describes how to delete an AlloyDB backup.\n\n\nBefore you begin\n----------------\n\n- The Google Cloud project you are using must have been [enabled to access AlloyDB](/alloydb/docs/project-enable-access).\n- You must have one of these IAM roles in the Google Cloud project you are using:\n - `roles/alloydb.admin` (the AlloyDB Admin predefined IAM role)\n - `roles/owner` (the Owner basic IAM role)\n - `roles/editor` (the Editor basic IAM role)\n\n If you don't have any of these roles, contact your Organization Administrator to request\n access.\n\n\u003cbr /\u003e\n\nProcedure\n---------\n\n### gcloud\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\nUse the `backups delete` command to delete\nan AlloyDB backup. \n\n```\ngcloud alloydb backups delete BACKUP_ID \\\n --region=REGION_ID \\\n --project=PROJECT_ID\n```\n\n- \u003cvar translate=\"no\"\u003eBACKUP_ID\u003c/var\u003e: The ID of the backup. You can find a backup's ID by [viewing a list of backups](/alloydb/docs/backup/list).\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: The ID of the region where the backup is placed.\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of the project where the backup is placed.\n\nRestrictions on deleting backups\n--------------------------------\n\nYou can delete on-demand or automated backups at any time, but\nAlloyDB limits the circumstances under which you can\ndelete continuous backups. AlloyDB requires the presence\nof these backups for [continuous backup and\nrecovery](/alloydb/docs/backup/overview#continuous) to work.\n\nAlloyDB lets you delete a continuous backup only if\nat least one of these circumstances is true:\n\n- You have [disabled continuous backup and\n recovery](/alloydb/docs/backup/configure#disable-continuous) on this\n cluster.\n\n- The backup that you want to delete is older than the cluster's\n configured recovery window for continuous backup and recovery.\n\nIn addition, AlloyDB doesn't let you delete any backup\nthat has continuous or automated backups based on it.\nThese backups are incremental backups, and they rely on the existence of\nspecific previous backups in order to keep your data safe and restorable."]]
