How to Configure Greenplum Backup User

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a greenplum backup user by creating a role with read rights. You also grant this role lock permissions across all schemas and tables. Most teams skip this careful work and use the main admin account instead. That shortcut gives backup scripts full power to drop tables or change data. If an attacker steals that admin key, they control the whole data warehouse. How to set up a greenplum backup user Greenplum splits data across one coordinator node and many worker segments. When you r

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 greenplum backup user by creating a role with read rights. You also grant this role lock permissions across all schemas and tables. Most teams skip this careful work and use the main admin account instead. That shortcut gives backup scripts full power to drop tables or change data. If an attacker steals that admin key, they control the whole data warehouse.

How to set up a greenplum backup user

Greenplum splits data across one coordinator node and many worker segments. When you run a parallel backup, the tool reads from every segment at once. Your backup role must log in through the coordinator first. Then it must read table data across all worker hosts at the same time.

To build a safe greenplum backup user, start with a standard database role. Do not give this role full superuser rights if you can avoid it. Instead, grant usage rights on every target schema in the database. Next, grant select rights on all existing tables, views, and sequences. You must also set default privileges for the schemas. This step lets the backup role read new tables that teams create later.

Backups also need a stable view of the data while they run. The backup role must lock tables briefly to sync the parallel dump. Without lock rights, active writes from other apps will break the backup job. You also need to update the host access file on the coordinator node. Add a rule so the backup role can log in from the backup server. If you use parallel segment tools, add rules on the segment hosts too. Store the role password in a local file with strict read rules. Set file permissions so only the system account running the job can read it.

What native backup roles solve and what they miss

A dedicated role limits what a stolen script key can do. If someone steals the backup password, they cannot delete your core tables. They cannot create new admin accounts or change database settings either. Separating backup jobs from admin work also makes your system logs cleaner. You can see right away when a backup job starts and ends.

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

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Still, native database roles only check who logs in at the start. Once the session starts, the role can read every row in every table by default. Native permissions cannot inspect individual queries while they run in flight. A person who gets hold of the backup key can dump raw customer data. They can pull emails, phone numbers, card numbers, and national IDs at will. Native roles also depend on static passwords stored on disk. Those files often sit on servers for months without any key rotation. And if an engineer uses the backup account to run manual queries, native logs miss the human identity behind the shared role.

Managing permissions for automated maintenance jobs

Good backup security requires tight network rules alongside database role limits. Bind the backup role to specific source IP addresses in your host rules. Never allow the backup account to log in from developer laptops. Review schema rights once a month to check for permission drift. As teams add new schemas, check that default read rules still apply. Test your restore process in a staging setup with a separate role. A role that creates backups should not have rights to overwrite production data.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Does a Greenplum backup user need superuser rights?

No, standard data dumps only need schema usage, table select, and lock rights. Restoring full cluster globals or system catalogs still requires an admin role.

How do new tables get included in automated backups?

You alter the default privileges on each schema for the backup role. This grants select rights on new tables as soon as teams create them.

Why do parallel backups fail on segment nodes?

Parallel tools often need host access rules on both coordinator and segment nodes. Check that every host allows the backup user from the backup server IP.

The query runs. The emails stay hidden.