This page describes how to schedule backups for Cassandra in Cloud Storage.
In this method, backups are stored in the specified Cloud Storage bucket.
To schedule Cassandra backups, perform the following steps:
Run the following create-service-account
command to create a Google Cloud service account (SA) with the standard
roles/storage.objectAdmin role.
This SA role allows you to write backup data
to Cloud Storage. Execute the command in the
$APIGEE_HELM_CHARTS_HOME/apigee-operator/etc/ directory.
This command creates a single service account named
apigee-non-prod for use in non-production environments and
places the downloaded key file in the ./
directory.
The create-service-account command saves a JSON file containing the
service account private key. The file is saved in the same directory
where the command executes. You will need the path to this file
in the following steps.
Backup jobs are triggered automatically according to the cron schedule set in
cassandra.backup.schedule in your
overrides.yaml file. However, you can also initiate a backup job manually if needed
using the following command:
[[["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-20 UTC."],[[["\u003cp\u003eThis guide explains how to schedule Cassandra backups to Cloud Storage for Apigee Hybrid.\u003c/p\u003e\n"],["\u003cp\u003eA Google Cloud service account with the \u003ccode\u003eroles/storage.objectAdmin\u003c/code\u003e role is required to write backup data to a designated Cloud Storage bucket.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eoverrides.yaml\u003c/code\u003e file must be updated to enable backups, specifying the service account path, Cloud Storage bucket, backup schedule, and \u003ccode\u003eGCP\u003c/code\u003e as the cloud provider.\u003c/p\u003e\n"],["\u003cp\u003eApplying the backup configuration will trigger a rolling restart of Cassandra pods, and it's important to avoid scheduling the initial backup immediately afterward to prevent failure.\u003c/p\u003e\n"],["\u003cp\u003eBackups can be initiated manually using a \u003ccode\u003ekubectl\u003c/code\u003e command, or they will automatically run according to the defined cron schedule in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file.\u003c/p\u003e\n"]]],[],null,[]]