This page provides an overview of restoring Cassandra in Apigee hybrid.
Why use restore?
You can use backups to restore Apigee infrastructure from the ground up in the event of
catastrophic failures, such as irrecoverable data loss in your Apigee hybrid instance from a disaster.
Restoration takes your data from the backup location and restores the data into a new Cassandra
cluster with the same number of nodes. No cluster data is taken from the old Cassandra cluster.
The goal of the restoration process is to bring an Apigee hybrid installation back to a
previously operational state using backup data from a snapshot.
The use of backups to restore is not recommended for the following scenarios:
Cassandra node failures.
Accidental deletion of data like apps, developers, and api_credentials.
One or more regions going down in a multi-region hybrid deployment.
Apigee Cassandra deployments and operational architecture take care of redundancy and fault tolerance for a single region.
In most cases, the recommended multi-region production implementation of hybrid means that a region failure can be recovered from
another live region using region decommissioning and expansion procedures
instead of restoring from a backup.
Before you begin implementing a restore from a Cassandra backup, be aware of the following:
Downtime: There will be downtime for the duration of the restoration.
Data loss: There will be data loss between the last valid backup and the time the
restoration is complete.
Restoration time: Restoration time depends on the size of the data and cluster.
Cherry-picking data: You cannot select only specific data to restore. Restoration
restores the entire backup you select.
How to restore?
Cassandra's restoration steps differ slightly depending on whether your Apigee hybrid is
deployed in a single region or multiple regions. For the detailed restoration steps,
see the following documentation:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis document outlines the process of restoring Apigee hybrid infrastructure using Cassandra backups in case of catastrophic failures and irrecoverable data loss.\u003c/p\u003e\n"],["\u003cp\u003eRestoring from backups is not recommended for Cassandra node failures, accidental data deletion, or region failures in multi-region deployments, as Apigee's architecture handles these scenarios with redundancy and multi-region procedures.\u003c/p\u003e\n"],["\u003cp\u003eRestoration involves downtime and data loss between the last valid backup and completion, and the process cannot be selective, restoring the entire backup.\u003c/p\u003e\n"],["\u003cp\u003eIt is crucial that the backup file used for restoration is from the same Apigee hybrid version as the installation, as a version mismatch will cause issues that Apigee does not support.\u003c/p\u003e\n"],["\u003cp\u003eRestoration steps differ for single-region and multi-region deployments, detailed in their respective documentation pages.\u003c/p\u003e\n"]]],[],null,["# Cassandra restore overview\n\n| You are currently viewing version 1.6 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.6/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.6/restore-cassandra-single-region)\n- [Restoring in a multi-region](/apigee/docs/hybrid/v1.6/restore-cassandra-multi-region)"]]
