Halaman ini menjelaskan cara mencantumkan dan memulihkan bucket yang dihapus sementara.
Ringkasan
Setelah dihapus sementara, bucket akan dipertahankan oleh Cloud Storage hingga waktu penghapusan permanennya, dan tidak dapat diubah saat dalam status dihapus sementara. Waktu penghapusan
permanen setidaknya sama dengan waktu penghapusan permanen terbaru objek
bucket. Setelah waktu penghapusan permanen berlalu, Cloud Storage akan menghapus bucket secara permanen. Saat Anda memulihkan bucket yang dihapus sementara, bucket tersebut akan dikembalikan ke status aktif, dan objek yang ada di bucket pada saat penghapusan juga dapat dipulihkan.
Pertimbangan
Untuk melindungi dari penghapusan berbahaya, bucket yang dihapus sementara tidak dapat dihapus secara permanen hingga bucket tersebut dipertahankan selama durasi retensi data penghapusan sementara penuh.
Setelah bucket dihapus sementara, Anda harus memulihkan bucket tersebut sebelum dapat mencantumkan atau memulihkan objek yang dihapus sementara di dalamnya.
Untuk memulihkan bucket yang dihapus sementara, Anda harus memiliki nomor generasi bucket. Untuk mengambil nomor generasi bucket yang dihapus sementara,
lihat Mencantumkan bucket yang dihapus sementara.
Bucket yang dihapus sementara hanya dapat dipulihkan jika tidak ada bucket aktif dengan nama yang sama. Jika Anda atau orang lain membuat bucket dengan nama yang sama dengan bucket yang dihapus sementara, Anda tidak dapat memulihkan bucket yang dihapus sementara hingga bucket baru dihapus.
Operasi pemulihan bucket tidak memulihkan objek yang dihapus sementara yang ada di bucket pada saat penghapusan. Untuk memulihkan objek yang dihapus sementara setelah bucket yang dihapus sementara dipulihkan, Anda harus melakukan operasi pemulihan objek.
Pengikatan tag mungkin tidak dipulihkan saat Anda memulihkan bucket yang dihapus sementara dengan tag. Untuk menghindari kehilangan data, saat Anda memulihkan bucket yang dihapus sementara dengan
binding tag, sebaiknya periksa untuk memastikan binding tag bucket dipulihkan. Jika binding tag bucket tidak dipulihkan, Anda harus
mengikat tag yang tidak dipulihkan ke bucket secara manual.
Izin yang diperlukan
Untuk mendapatkan izin yang
diperlukan untuk memulihkan bucket yang dihapus sementara,
minta administrator Anda untuk memberi Anda
peran IAM Storage Admin (roles/storage.admin)
di project Cloud Storage.
Peran bawaan ini berisi
izin yang diperlukan untuk memulihkan bucket yang dihapus sementara. Untuk melihat izin yang benar-benar diperlukan, luaskan bagian Izin yang diperlukan:
Izin yang diperlukan
Izin berikut diperlukan untuk memulihkan bucket yang dihapus sementara:
storage.buckets.list
storage.buckets.restore
Mencantumkan bucket yang dihapus sementara
Anda dapat melakukan operasi daftar untuk mengambil metadata bucket yang dihapus sementara.
Gunakan petunjuk berikut untuk mencantumkan semua bucket yang dihapus sementara di project Anda:
Command line
Untuk mencantumkan semua bucket yang dihapus sementara, gunakan perintah
gcloud storage ls:
BUCKET_NAME: nama bucket yang dihapus sementara
yang ingin Anda pulihkan.
GENERATION_NUMBER: nomor pembuatan unik dan permanen bucket yang dihapus sementara yang ingin Anda pulihkan.
Untuk mendapatkan nomor generasi bucket Anda, lihat
Mencantumkan bucket yang dihapus sementara.
BUCKET_NAME adalah nama bucket yang ingin Anda pulihkan. Contoh, my-bucket.
GENERATION_NUMBER adalah nomor pembuatan unik permanen bucket yang dihapus sementara yang ingin Anda pulihkan. Untuk mendapatkan nomor generasi bucket Anda, lihat
Mencantumkan bucket yang dihapus sementara.
Cloud Storage memulihkan bucket yang dihapus sementara ke status aktif. Perhatikan bahwa
memulihkan bucket tidak akan memulihkan objek yang ada di bucket pada
saat penghapusan sementara. Untuk memulihkan objek yang dihapus sementara yang ada di bucket pada saat penghapusan, lihat Memulihkan objek yang dihapus sementara.
[[["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."],[],[],null,["# Use soft-deleted buckets\n\n[Soft delete feature overview](/storage/docs/soft-delete)\n\nThis page describes how to list and restore a soft-deleted bucket.\n\nOverview\n--------\n\nAfter a bucket is soft-deleted, it's retained by Cloud Storage until its\nhard delete time, and cannot be modified while in a soft-deleted state. The hard\ndelete time is at least as long as the latest hard delete time of the bucket's\nobjects. After the hard delete time has elapsed, Cloud Storage permanently\ndeletes the bucket. When you restore a soft-deleted bucket, it is returned to a\nlive state, and objects that were in the bucket at the time of deletion can also\nbe restored.\n\nConsiderations\n--------------\n\n- To protect against malicious deletion, a soft-deleted bucket cannot\n be permanently deleted until the bucket has been retained for its full\n soft delete retention duration.\n\n- Once a bucket is a soft-deleted, you must restore the bucket before you\n can list or restore the soft-deleted objects in it.\n\n- To restore a soft-deleted bucket, you must have the bucket's\n generation number. To retrieve a soft-deleted bucket's generation number,\n see [List soft-deleted buckets](#list-soft-deleted-buckets).\n\n- A soft-deleted bucket can only be restored if there is no\n live bucket with the same name. If you or anyone else creates a bucket\n with the same name as a soft-deleted bucket, you cannot restore the\n soft-deleted bucket until the new bucket is deleted.\n\n- Bucket restore operations don't restore the soft-deleted objects that were\n in the bucket at the time of deletion. To restore soft-deleted objects after\n the soft-deleted bucket has been restored, you'll need to perform an object\n restore operation.\n\n- Tag bindings might not be recovered when you restore a soft-deleted bucket\n with tags. To avoid data loss, when you restore a soft-deleted bucket with\n tag bindings, we recommend checking to ensure the bucket's tag bindings were\n recovered. If the bucket's tag bindings weren't recovered, you'll need to\n [manually bind the unrecovered tags to the bucket](/resource-manager/docs/tags/tags-creating-and-managing#attaching).\n\nRequired permissions\n--------------------\n\n\nTo get the permissions that\nyou need to restore soft-deleted buckets,\n\nask your administrator to grant you the\n\n\n[Storage Admin](/iam/docs/roles-permissions/storage#storage.admin) (`roles/storage.admin`)\nIAM role on the Cloud Storage project.\n\n\nThis predefined role contains\n\nthe permissions required to restore soft-deleted buckets. To see the exact permissions that are\nrequired, expand the **Required permissions** section:\n\n\n#### Required permissions\n\nThe following permissions are required to restore soft-deleted buckets:\n\n- `storage.buckets.list`\n- `storage.buckets.restore`\n\nList soft-deleted buckets\n-------------------------\n\nYou can perform list operations to retrieve your soft-deleted buckets'\nmetadata.\n| **Note:** A bucket cannot be listed if its hard delete time has elapsed.\n\nUse the following instructions to list all soft-deleted buckets in your project: \n\n### Command line\n\nTo list all soft-deleted buckets, use the\n[`gcloud storage ls`](/sdk/gcloud/reference/storage/buckets/list) command: \n\n```\ngcloud storage ls --buckets --soft-deleted --full\n```\n\n### REST APIs\n\n### JSON API\n\n1. Have gcloud CLI [installed and initialized](/sdk/docs/install), which lets\n you generate an access token for the `Authorization` header.\n\n\n2.\n\n Use [`cURL`](http://curl.haxx.se/) to call the [JSON API](/storage/docs/json_api) with a\n [`GET` Bucket](/storage/docs/json_api/v1/buckets/list) request:\n\n```\ncurl -X GET \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json\" \\\n \"https://storage.googleapis.com/storage/v1/b?softDeleted=true\"\n```\n\nRestore a soft-deleted bucket\n-----------------------------\n\nUse the following instructions to restore a soft-deleted bucket: \n\n### Command line\n\nTo restore a soft-deleted bucket, use the [`gcloud storage restore`](/sdk/gcloud/reference/storage/restore)\ncommand: \n\n```\n gcloud storage restore gs://BUCKET_NAME#GENERATION_NUMBER\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e: the name of the soft-deleted\n bucket you want to restore.\n\n- \u003cvar translate=\"no\"\u003eGENERATION_NUMBER\u003c/var\u003e: the permanent, unique\n generation number of the soft-deleted bucket you want to restore.\n To get your bucket's generation number, see\n [List soft-deleted buckets](#list-soft-deleted-buckets).\n\n### REST APIs\n\n### JSON API\n\n1. Have gcloud CLI [installed and initialized](/sdk/docs/install), which lets\n you generate an access token for the `Authorization` header.\n\n\n2.\n\n Use [`cURL`](http://curl.haxx.se/) to call the [JSON API](/storage/docs/json_api) with a\n [`POST` Bucket](/storage/docs/json_api/v1/buckets/restore) request: \n\n ```\n curl -X POST \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json\" \\\n \"https://storage.googleapis.com/storage/v1/b/BUCKET_NAME/restore?generation=GENERATION_NUMBER\n ```\n\n Where:\n - \u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e is the name of the bucket\n you want to restore. For example, `my-bucket`.\n\n - \u003cvar translate=\"no\"\u003eGENERATION_NUMBER\u003c/var\u003e is the permanent,\n unique generation number of the soft-deleted bucket you want\n to restore. To get your bucket's generation number, see\n [List soft-deleted buckets](#list-soft-deleted-buckets).\n\nCloud Storage restores the soft-deleted bucket to a live state. Note that\nrestoring the bucket doesn't restore the objects that were in the bucket at the\ntime of soft deletion. To restore the soft-deleted objects that were in the\nbucket at the time of deletion, see [Restore a soft-deleted object](/storage/docs/use-soft-deleted-objects#restore).\n\nWhat's next\n-----------\n\n- [Restore soft-deleted objects in your bucket](/storage/docs/use-soft-deleted-objects#restore)."]]