[[["容易理解","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-07-10 (世界標準時間)。"],[[["Apigee hybrid's backup and restore feature creates backups of hybrid data, allowing restoration to previous states in disaster scenarios, with backup availability and retention dependent on the user's infrastructure."],["Only Cassandra data requires backing up, as other Apigee hybrid components are stateless and can be reinstalled using existing overrides during recovery, and data backups should not be stored within Kubernetes nodes of the hybrid cluster."],["Cassandra backups are crucial for disaster recovery, creating snapshots of data, schema, and metadata, and they are not enabled by default but should be for protection against data loss from catastrophic failures."],["Backups are created based on a schedule defined in the `overrides.yaml` file, which then triggers a backup script on each Cassandra node, archiving data and sending it to Cloud Storage or a remote server."],["Apigee hybrid supports two backup methods: one using Kubernetes CSI snapshots (recommended for Google Cloud, AWS, or Azure) and another non-CSI method for on-prem installations, and in both the user configures backup in the `overrides.yaml` file."]]],[]]