[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-12。"],[[["Apigee hybrid's backup and restore feature creates backups of hybrid data, allowing restoration to previous snapshots in disaster scenarios, with backup availability and retention dependent on the user's infrastructure."],["While most Apigee hybrid components are stateless and do not require backups, Cassandra backups are crucial for disaster recovery, providing a snapshot of the data, schema, and metadata."],["Cassandra backups are not enabled by default, but are strongly recommended in case of data loss due to catastrophic failure, and they are scheduled and executed via a Kubernetes job that archives the data and sends it to a designated storage location."],["Backups can be stored in either Cloud Storage, which offers default encryption, or on a user-specified remote server, where encryption after transfer must be managed by the user."],["Users can configure backups using either the Apigee hybrid CSI method, recommended for cloud-hosted instances, or a non-CSI method for on-prem installations, both requiring configuration within the `overrides.yaml` file, which should also be backed up."]]],[]]