Caution
You're viewing documentation for a previous version of Scylla Manager. Switch to the latest stable version.
Go to Google Cloud Storage and create a new bucket in a region where Scylla nodes are. If your cluster is deployed in multiple regions create a bucket per region. You may decide to backup only a single datacenter to save on costs, in that case create only one bucket in a region you want to backup.
This procedure is required so that Scylla Manager can access your bucket.
Choose how you want to configure access to the bucket. If your application runs inside a Google Cloud environment we recommend using automatic Service account authentication. Otherwise you can add your credentials to the agent configuration file. The later method is less secure as you will be propagating each node with this security information and in cases where you need to change the key, you will have to replace it on each node.
Procedure
Collect list of service accounts used by each of the Scylla nodes.
Make sure that each of service account has read/write access scope to Cloud Storage.
For each service account from the list, add Storage Object Admin role in bucket permissions settings.
Use this instruction to get the service account file.
Note that this procedure needs to be repeated for each Scylla node.
Procedure
Edit the /etc/scylla-manager-agent/scylla-manager-agent.yaml
Uncomment the gcs: line, for parameters note the two spaces in front, it’s a yaml file.
Uncomment and set service_account_file with the path to the service account credentials file.
For each service account used by the nodes, add Storage Object Admin role in the bucket permissions settings.
Validate that the manager has access to the backup location. If there is no response, the bucket is accessible. If not, you will see an error.
scylla-manager-agent check-location --location gcs:<your GCS bucket name>
To troubleshoot Node to bucket connectivity issues you can run:
scylla-manager-agent check-location --debug --location gcs:<your GCS bucket name>