How to Configure ScyllaDB Backup User

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a scylladb backup user by making a dedicated database role with read rights. You also need host permissions to run node tool snapshot commands on the storage files. Many teams reuse a default admin role to get backups running fast. That broad role lets a backup script drop tables or change live cluster data by mistake. How to set up a scylladb backup user role A safe backup setup splits cluster tasks into two parts. The first part is the database role that reads schema and table me

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up a scylladb backup user by making a dedicated database role with read rights. You also need host permissions to run node tool snapshot commands on the storage files. Many teams reuse a default admin role to get backups running fast. That broad role lets a backup script drop tables or change live cluster data by mistake.

How to set up a scylladb backup user role

A safe backup setup splits cluster tasks into two parts. The first part is the database role that reads schema and table metadata. The second part is the local host user that copies snapshot files to remote object storage.

Start by logging in to the cluster with your main admin account. Enable password checks and role controls in the cluster settings files on every node. Create a new database role just for the backup job and enable login for it. Grant read permissions on the target keyspaces so the role can inspect table structures. Never grant modify, drop, or alter permissions to this backup role.

Next, set up the operating system user on each database node. Backup agents trigger local snapshots through the node management tool and read the data directory. Give this local user read rights on the data folders and write rights on snapshot folders. Store the database password and storage keys in a safe secret store on the host.

What native roles solve and where gaps remain

Native roles stop a backup script from writing bad data or dropping production tables. Separating the backup account from app accounts also helps when you rotate keys. You can change the backup password without breaking live traffic from your main app.

Still, static database roles only check who logs in at the start of a session. Once the role logs in, the cluster trusts every read query that matches those permissions. A leaked backup key lets an attacker pull raw customer tables from any allowed network path. Native roles also cannot mask sensitive fields like emails, phone numbers, or card numbers in flight.

User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Managing host keys and audit logs for backup jobs

Backup agents run on a set schedule, so teams often leave long-lived keys on disk. If an engineer logs into a node to fix a failed job, they find those keys. Shared host accounts also make it hard to see which person ran a manual snapshot.

Database audit logs can record role logins, but they miss host shell commands. Tying a specific engineer to both a database query and a host command takes extra work. Teams need a way to check every command in real time and strip out long-lived keys.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits inline in the protocol beside the service as an open-source proxy, a sidecar for your database or API. On every production query an agent or human runs, hoop.dev decides whether to pass, mask, block, or escalate it for review.

Before a query runs, hoop.dev guardrails check the statement against your rules, an AI Analyzer you configure can score intent or hold risky calls for human approval, and hoop.dev data masking rewrites sensitive fields in responses in memory. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Does a scylladb backup user need superuser rights?

No, a backup role never needs superuser rights to copy cluster data. Read rights on the keyspaces and local access to snapshot folders are enough for backups.

How do we protect sensitive data during backup checks?

When engineers query backup data to test a restore, use data masking on the results. Masking rewrites matched fields like national IDs, emails, and card numbers before the user sees them.

How often should we rotate keys for the backup role?

If you use static passwords, rotate them at least every ninety days. Removing static keys from worker nodes and using short-lived sessions is a much safer choice.

The query runs. The emails stay hidden.