Nesta página, descrevemos como programar backups do Cassandra no Cloud Storage.
Nesse método, os backups são armazenados no bucket especificado do Cloud Storage.
Para programar backups do Cassandra, execute as seguintes etapas:
Execute o comando create-service-account
a seguir para criar uma conta de serviço (SA, na sigla em inglês) do Google Cloud com o papel padrão
roles/storage.objectAdmin.
Esse papel da SA permite gravar dados de backup
no Cloud Storage. Execute o seguinte comando no diretório
hybrid-base-directory/hybrid-files:
Esse comando cria uma única conta de serviço chamada
apigee-non-prod para uso em ambientes de
não produção e coloca o arquivo de chave salvo no diretório ./service-accounts.
Para mais informações sobre as contas de serviço do Google Cloud, consulte
Como criar
e gerenciar contas de serviço.
O comando create-service-account salva um arquivo JSON que contém a
chave privada da conta de serviço. O arquivo é salvo no mesmo diretório
em que o comando é executado. Você precisará do caminho desse arquivo
nas etapas a seguir.
O backup está desativado por padrão. É preciso definir essa propriedade como true.
backup:serviceAccountPath
SA_JSON_FILE_PATH
O caminho no seu sistema de arquivos para o arquivo
JSON da conta de serviço que foi salvo quando você
executou o comando ./tools/create-service-account.
Você também pode fornecer um caminho de arquivo relativo. O caminho é relativo ao
diretório hybrid-base-directory/hybrid-files.
backup:dbStorageBucket
CLOUD_STORAGE_BUCKET_PATH
O caminho do bucket do Cloud Storage neste formato: gs://BUCKET_NAME.
O gs:// é obrigatório.
backup:cloudProvider
GCP/HYBRID
Para um backup do Cloud Storage, defina a propriedade como GCP. Exemplo,
cloudProvider: "GCP".
Para um backup remoto do servidor, defina a propriedade como HYBRID. Exemplo,
cloudProvider: "HYBRID".
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-28 UTC."],[[["\u003cp\u003eThis document provides instructions on how to schedule Cassandra backups to Cloud Storage for Apigee hybrid version 1.8, which is end-of-life.\u003c/p\u003e\n"],["\u003cp\u003eTo enable backups, you must create a Google Cloud service account with storage object admin permissions and a Cloud Storage bucket to store the backup data.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration for the backup is managed in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file, where you'll enable backups, provide the service account path, specify the Cloud Storage bucket location, the backup schedule, and the cloud provider.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ebackup:schedule\u003c/code\u003e property in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file determines when the backup starts, using standard crontab syntax.\u003c/p\u003e\n"],["\u003cp\u003eApplying the configuration will result in a rolling restart of the Cassandra pods, and it's recommended to avoid starting backups immediately after applying the configuration to prevent initial failures.\u003c/p\u003e\n"]]],[],null,["# Scheduling backups in Cloud Storage\n\n| You are currently viewing version 1.8 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 describes how to schedule backups for Cassandra in Cloud Storage.\nIn this method, backups are stored in the specified Cloud Storage bucket.\n| **Note:** After applying the backup configuration on the existing cluster, the Cassandra pods will restart one after another (rolling restart) from last to first.\n\nTo schedule Cassandra backups, perform the following steps:\n\n1. Run the following `create-service-account` command to create a Google Cloud service account (SA) with the standard [`roles/storage.objectAdmin`](https://cloud.google.com/storage/docs/access-control/iam-roles) role. This SA role allows you to write backup data to Cloud Storage. Execute the following command in the \u003cvar translate=\"no\"\u003ehybrid-base-directory\u003c/var\u003e`/hybrid-files` directory: \n\n ```\n ./tools/create-service-account --env non-prod --dir ./service-accounts\n ```\n 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 `./service-accounts` directory. **Note:** If you prefer to create all the individual service accounts for a production environment, use the following command: \n |\n | ```\n | ./tools/create-service-account --env prod --dir ./service-accounts\n | ```\n For more information about Google Cloud service accounts, see [Creating\n and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts).\n2. 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.\n3. [Create a Cloud Storage bucket](https://cloud.google.com/storage/docs/creating-buckets). Specify a reasonable data [retention policy](https://cloud.google.com/storage/docs/bucket-lock#retention-policy) for the bucket. Apigee recommends a data retention policy of 15 days.\n4. Open your `overrides.yaml` file.\n5. Add the following `cassandra.backup` properties to enable backup. Do not remove any of the properties that are already configured.\n\n ### Parameters\n\n ```scdoc\n cassandra:\n ...\n\n backup:\n enabled: true\n serviceAccountPath: SA_JSON_FILE_PATH\n dbStorageBucket: CLOUD_STORAGE_BUCKET_PATH\n schedule: BACKUP_SCHEDULE_CODE\n cloudProvider: \"GCP\" # For remote server backup set this to HYBRID (all caps)\n\n ...\n \n ```\n\n ### Example\n\n ```carbon\n ...\n\n cassandra:\n storage:\n type: gcepd\n capacity: 50Gi\n gcepd:\n replicationType: regional-pd\n auth:\n default:\n password: \"abc123\"\n admin:\n password: \"abc234\"\n ddl:\n password: \"abc345\"\n dml:\n password: \"abc456\"\n nodeSelector:\n key: cloud.google.com/gke-nodepool\n value: apigee-data\n backup:\n enabled: true\n serviceAccountPath: \"/Users/myhome/.ssh/my-cassandra-backup-sa.json\"\n dbStorageBucket: \"gs://myname-cassandra-backup\"\n schedule: \"45 23 * * 6\"\n cloudProvider: \"GCP\"\n \n\n\n ... \n ```\nWhere:\n\n6. Apply the configuration changes to the new cluster. For example: \n\n ```\n $APIGEECTL_HOME/apigeectl apply --datastore -f YOUR_OVERRIDES_FILE\n ```\n\n\n Where \u003cvar translate=\"no\"\u003eYOUR_OVERRIDES_FILE\u003c/var\u003e is the path to the overrides file you just edited.\n7. Verify the backup job. For example: \n\n ```\n kubectl get cronjob -n apigee\n ``` \n\n ```component-pascal\n NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE\n apigee-cassandra-backup 33 * * * * False 0 \u003cnone\u003e 94s\n ```"]]
