Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Autopilot
Standard
Penetapan harga Pencadangan untuk GKE didasarkan pada tiga dimensi berbeda:
Pengelolaan cadangan: dimensi ini dihitung pada tingkat BackupPlan
dan didasarkan pada jumlah Pod yang dilindungi oleh BackupPlan
(jumlah Pod yang terdapat dalam Backup terbaru untuk paket tersebut).
Penyimpanan cadangan: dimensi ini dihitung pada tingkat Backup dan
didasarkan pada jumlah byte yang disimpan untuk setiap Backup dari waktu ke waktu.
Traffic keluar jaringan: dimensi ini dihitung pada level Backup dan didasarkan pada jumlah byte yang ditransfer di berbagai region selama operasi pencadangan. Perhatikan bahwa biaya ini hanya berlaku jika cluster sumber dan BackupPlan berada di dua region yang terpisah.
Harga untuk pencadangan dan pemulihan lintas project
Untuk skenario pencadangan dan pemulihan lintas project, ada tiga project yang berpotensi terlibat:
cluster_project: project yang berisi cluster yang ingin Anda cadangkan.
backup_project: project tempat Anda ingin menyimpan cadangan.
restore_project: project yang berisi cluster target
pemulihan.
Ketiga dimensi tersebut ditagih dalam backup_project di item baris
Pencadangan untuk GKE.
Biaya transfer data jaringan
Mirip dengan operasi pencadangan dan pemulihan project tunggal, biaya transfer data
jaringan berlaku untuk operasi pencadangan dan pemulihan lintas region. Selain itu, ada perubahan transfer data jaringan untuk Config backup selama operasi pencadangan, antar-region pencadangan, dan antar-region pemulihan saat memulihkan volume. Biaya ini tercantum di bagian Compute Engine.
Menyesuaikan penagihan mendatang
Untuk menghentikan penagihan mendatang untuk Pencadangan untuk GKE, hapus resource Backup yang ada, lalu hapus atau nonaktifkan BackupPlansapa pun.
[[["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-09-01 UTC."],[],[],null,["# Backup for GKE pricing\n\nAutopilot Standard\n\n*** ** * ** ***\n\nBackup for GKE pricing is based on three different dimensions:\n\n- **Backup management** : this dimension is calculated at the `BackupPlan`\n level and is based on the number of Pods that are protected by the `BackupPlan`\n (the number of Pods contained in the most recent `Backup` for that plan).\n\n- **Backup storage** : this dimension is calculated at the `Backup` level and is\n based on the number of bytes stored for each `Backup` over time.\n\n- **Network egress** : this dimension is calculated at the `Backup` level and is\n based on the number of bytes that's transferred across regions during the\n backup operation. Note that these charges apply only when the source cluster\n and the `BackupPlan` are in two separate regions.\n\nPricing details may be found on the GKE [pricing page](/kubernetes-engine/pricing#backup-for-gke).\n\nPricing for cross-project backups and restores\n----------------------------------------------\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nFor any cross-project backup and restore scenarios, three projects are\npotentially involved:\n\n- **`cluster_project`**: the project that contains the cluster that you\n want to back up.\n\n- **`backup_project`**: the project where you want your backups to be\n stored.\n\n- **`restore_project`**: the project that contains the restore's\n target cluster.\n\nAll three dimensions are billed in the `backup_project` under the\nBackup for GKE line item.\n\n### Network data transfer charges\n\nSimilar to single-project backup and restore operations, network data transfer\ncharges apply for cross-region backup and restore operations. Additionally,\nthere are network data transfer changes for `Config backup` during\nbackup operations, between backup regions, and between restore regions when\nrestoring a volume. These charges are listed under Compute Engine.\n\nAdjust future billing\n---------------------\n\nTo stop any future billing for Backup for GKE, delete any existing `Backup`\nresources and then delete or disable any `BackupPlans`."]]
