Troubleshooting Backup Service errors

Common solutions to errors encountered when using the Backup Service.

If you encounter errors when backing up or restoring using the Backup Service, follow these instructions to make sure your environment is configured correctly.

Amazon S3 errors 

If you are using an Amazon S3 location for storing backups or commitlogs, you might encounter errors if the permissions or authentication keys have been changed since the backup job was created. Input updated authentication tokens with permissions to write to the specified bucket name.

Insufficient privileges as an AWS IAM (Identity Access Management) user causes an authentication error that displays the message "Unable to authenticate against AWS with the provided key and secret." Ensure the user has base privileges as well as the privilege for the ListAllMyBuckets action:
"Action": "s3:ListAllMyBuckets"
Actions to consider for granting AWS IAM user privileges:
  • CreateBucket
  • GetBucketLocation
  • ListBucket
  • ListAllMyBuckets
  • PutObject
  • GetObject
  • DeleteObject
For more information, refer to Amazon AWS IAM documentation.

Agent errors 

All the nodes in your cluster must use Java 7+ for the Backup Service to work.

The agent and DataStax Enterprise user either must be the same (the default, starting in OpsCenter 5.1), or the agent user must have the correct permissions to read and modify the files owned by the DataStax Enterprise user.

Error starting restore for a table using UDT 

(Applicable to Cassandra version 2.1+ and DSE version 4.7+ only) Automatically recreating a schema is not currently supported when using User Defined Types (UDTs). When restoring a table using UDTs, please ensure the table exists before starting the restore operation. Future versions of OpsCenter will support automatic schema creation for UDTs.