Scheduling backups in Cloud Storage Stay organized with collections Save and categorize content based on your preferences.
HYBRID orGCP Cloud Providers. Please see theCassandra troubleshooting guide to check whether your setup is affected and for steps needed for resolution.This page describes how to schedule backups for Cassandra in Cloud Storage. In this method, backups are stored in the specified Cloud Storage bucket.
Note: After applying the backup configuration on the existing cluster, the Cassandra pods will restart one after another (rolling restart) from last to first.To schedule Cassandra backups, perform the following steps:
- Run the following
create-service-accountcommand to create a Google Cloud service account (SA) with the standardroles/storage.objectAdminrole. This SA role allows you to write backup data to Cloud Storage. E Execute the following command in the directory appropriate for your management tool:- Helm charts:
$APIGEE_HELM_CHARTS_HOME/apigee-operator/etc/ apigeectl:HYBRID_BASE_DIRECTORY/hybrid-files/
This command creates a single service account named./tools/create-service-account --env non-prod --dir ./service-accounts
apigee-non-prodfor use in non-production environments and places the downloaded key file in the./service-accountsdirectory.Note: If you prefer to create all the individual service accounts for a production environment, use the following command: For more information about Google Cloud service accounts, seeCreating and managing service accounts../tools/create-service-account--env prod --dir ./service-accounts
- Helm charts:
- The
create-service-accountcommand 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. - Create a Cloud Storage bucket. Specify a reasonable data retention policy for the bucket. Apigee recommends a data retention policy of 15 days.
- Open your
overrides.yamlfile. - Add the following
cassandra.backupproperties to enable backup. Do not remove any of the properties that are already configured.Parameters
cassandra: ... backup: enabled: true serviceAccountPath:SA_JSON_FILE_PATH dbStorageBucket:CLOUD_STORAGE_BUCKET_PATH schedule:BACKUP_SCHEDULE_CODE cloudProvider: "GCP" # required verbatim "GCP" (all caps) ...
Example
...cassandra:storage:type:gcepdcapacity:50Gigcepd:replicationType:regional-pdauth:default:password:"abc123"admin:password:"abc234"ddl:password:"abc345"dml:password:"abc456"nodeSelector:key:cloud.google.com/gke-nodepoolvalue:apigee-databackup:enabled:trueserviceAccountPath:"my-cassandra-backup-sa.json"dbStorageBucket:"gs://myname-cassandra-backup"schedule:"45 23 * * 6"cloudProvider:"GCP"...
Where: - Apply the configuration changes to the new cluster. For example:
Helm
Note: If you see an error sayinghelm upgrade datastore apigee-datastore/ \ --namespaceAPIGEE_NAMESPACE \ --atomic \ -fOVERRIDES_FILE.yaml
Error: UPGRADE FAILED: "datastore" has no deployed releases, replaceupgradewithinstalland try the command again.apigeectl$APIGEECTL_HOME/apigeectl apply -fOVERRIDES_FILE.yaml --datastore
WhereOVERRIDES_FILE is the path to the overrides file you just edited.
- Verify the backup job. For example:
kubectl get cronjob -nAPIGEE_NAMESPACE
NAMESCHEDULESUSPENDACTIVELASTSCHEDULEAGEapigee-cassandra-backup33****False0 <none>94s
| Property | Description |
|---|---|
backup:enabled | Backup is disabled by default. You must set this property totrue. |
backup:serviceAccountPath | SA_JSON_FILE_PATH The path on your filesystem to the service account JSON file that was downloaded when you ran the For installations managed with Helm, the path must be relative to the apigee-datastore chart directory. For example, For installations managed with |
backup:dbStorageBucket | CLOUD_STORAGE_BUCKET_PATH The Cloud Storage bucket path in this format: |
backup:cloudProvider |
For a backup to Cloud Storage, set the property to |
backup:schedule | BACKUP_SCHEDULE_CODE The time when the backup starts, specified instandard crontab syntax. Default: |
Launch a manual backup
Backup jobs are triggered automatically according to the cron schedule set incassandra.backup.schedule in youroverrides.yaml file. However, you can also initiate a backup job manually if needed using the following command:
kubectl create job -nAPIGEE_NAMESPACE --from=cronjob/apigee-cassandra-backupMANUAL_BACKUP_JOB_NAME
WhereMANUAL_BACKUP_JOB_NAME is the name of a manual backup job to be be created.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.