Halaman ini memberikan ringkasan tentang cara memulihkan Cassandra di Apigee hybrid.
Mengapa menggunakan pemulihan?
Anda dapat menggunakan cadangan untuk memulihkan infrastruktur Apigee dari awal jika terjadi
kegagalan besar, seperti kehilangan data yang tidak dapat dipulihkan di instance hybrid Apigee Anda akibat bencana.
Pemulihan mengambil data Anda dari lokasi cadangan dan memulihkan data ke cluster Cassandra baru dengan jumlah node yang sama. Tidak ada data cluster yang diambil dari cluster Cassandra lama.
Tujuan proses pemulihan adalah mengembalikan penginstalan campuran Apigee ke
status operasional sebelumnya menggunakan data cadangan dari snapshot.
Penggunaan cadangan untuk memulihkan tidak direkomendasikan untuk skenario berikut:
Kegagalan node Cassandra.
Penghapusan data yang tidak disengaja seperti apps, developers, dan api_credentials.
Satu atau beberapa region mengalami gangguan dalam deployment hybrid multi-region.
Deployment Cassandra Apigee dan arsitektur operasional menangani redundansi dan fault tolerance untuk satu region.
Pada umumnya, penerapan produksi multi-region hybrid yang direkomendasikan berarti kegagalan region dapat dipulihkan dari
region aktif lainnya menggunakan prosedur penghentian dan perluasan region,
bukan memulihkan dari cadangan.
Sebelum Anda mulai menerapkan pemulihan dari cadangan Cassandra, perhatikan hal-hal berikut:
Periode nonaktif: Akan ada periode nonaktif selama durasi pemulihan.
Kehilangan data: Akan ada kehilangan data antara pencadangan terakhir yang valid dan waktu
pemulihan selesai.
Waktu pemulihan: Waktu pemulihan bergantung pada ukuran data dan cluster.
Memilih data tertentu: Anda tidak dapat memilih hanya data tertentu untuk dipulihkan. Pemulihan
akan memulihkan seluruh cadangan yang Anda pilih.
Bagaimana cara memulihkan?
Langkah-langkah pemulihan Cassandra sedikit berbeda, bergantung pada apakah hybrid Apigee Anda di-deploy di satu region atau beberapa region. Untuk mengetahui langkah-langkah pemulihan yang mendetail,
lihat dokumentasi berikut:
[[["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-05 UTC."],[[["\u003cp\u003eThis document outlines the process of restoring Cassandra in Apigee hybrid using backups, primarily for catastrophic failures leading to irrecoverable data loss.\u003c/p\u003e\n"],["\u003cp\u003eRestoration is not recommended for node failures, accidental data deletion, or regional outages in multi-region deployments, as the architecture offers redundancy and region failover in those scenarios.\u003c/p\u003e\n"],["\u003cp\u003eRestoring from a backup will result in downtime and data loss between the last backup and the completion of the restore, and the restore process cannot be used to selectively restore certain data.\u003c/p\u003e\n"],["\u003cp\u003eThe restoration process requires using a backup file created from the same Apigee hybrid version as the installation to avoid compatibility issues.\u003c/p\u003e\n"],["\u003cp\u003eRestoration steps differ based on whether the Apigee hybrid is deployed in a single or multi-region setup, with specific documentation available for each scenario.\u003c/p\u003e\n"]]],[],null,["# Cassandra restore overview\n\n| You are currently viewing version 1.8 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis page provides an overview of restoring Cassandra in Apigee hybrid.\n\nWhy use restore?\n----------------\n\nYou can use [backups](/apigee/docs/hybrid/v1.8/cassandra-backup-overview) to restore Apigee infrastructure from the ground up in the event of\ncatastrophic failures, such as irrecoverable data loss in your Apigee hybrid instance from a disaster.\nRestoration takes your data from the backup location and restores the data into a new Cassandra\ncluster with the same number of nodes. No cluster data is taken from the old Cassandra cluster.\nThe goal of the restoration process is to bring an Apigee hybrid installation back to a\npreviously operational state using backup data from a snapshot.\n\nThe use of backups to restore is not recommended for the following scenarios:\n\n- Cassandra node failures.\n- Accidental deletion of data like `apps`, `developers`, and `api_credentials`.\n- One or more regions going down in a multi-region hybrid deployment.\n\nApigee Cassandra deployments and operational architecture take care of redundancy and fault tolerance for a single region.\nIn most cases, the recommended multi-region production implementation of hybrid means that a region failure can be recovered from\nanother live region using [region decommissioning and expansion procedures]()\ninstead of restoring from a backup.\n\nBefore you begin implementing a restore from a Cassandra backup, be aware of the following:\n\n- **Downtime:** There will be downtime for the duration of the restoration.\n- **Data loss:** There will be data loss between the last valid backup and the time the restoration is complete.\n- **Restoration time:** Restoration time depends on the size of the data and cluster.\n- **Cherry-picking data:** You cannot select only specific data to restore. Restoration restores the entire backup you select.\n\n| **Note:** When restoring an Apigee hybrid installation from backup, ensure that the backup file is created from the same hybrid version as the installation. For example, if you have a backup file created from Apigee hybrid 1.5.x, use it to restore only an Apigee hybrid 1.5.x installation. If there is version mismatch between the backup file and the hybrid installation, the restoration might not work and Apigee does not support any issues that arise because of such restoration.\n\nHow to restore?\n---------------\n\nCassandra's restoration steps differ slightly depending on whether your Apigee hybrid is\ndeployed in a single region or multiple regions. For the detailed restoration steps,\nsee the following documentation:\n\n- [Restoring in a single region](/apigee/docs/hybrid/v1.8/restore-cassandra-single-region)\n- [Restoring in a multi-region](/apigee/docs/hybrid/v1.8/restore-cassandra-multi-region)"]]
