Backup
Managed, scheduled, encrypted backups for your PostgreSQL and MongoDB databases.
Backup takes scheduled backups of your PostgreSQL and MongoDB databases and stores them encrypted in S3 – either in Norcube-managed storage or in your own bucket. You connect a database, attach a backup policy (cron schedule + retention + destination), and Backup handles execution, encryption, downloads, and cleanup.
What you can do with Backup
Connect a database
Postgres or MongoDB, with credentials stored KMS-encrypted and verified automatically on save.
Schedule recurring backups
Define a cron schedule, retention window, and destination once; reuse the policy across databases.
Run a backup on demand
Don't wait for the next scheduled time – kick off an ad-hoc backup with one click.
Download or delete a backup
Short-lived signed URLs for managed and BYO destinations alike. Delete individual files when you don't need them.
Bring your own S3 bucket
Point Backup at a bucket in your AWS account; you control retention pipelines and pay AWS directly.
Audit every action
Read-only timeline of who did what to your data sources, policies, and backup jobs.
Core concepts in one minute
- Data source – a database you've connected. Has credentials, an environment tag (prod / staging / dev), and a region.
- Backup policy – a reusable schedule + retention + destination. Define once, attach to many databases.
- Backup job – one execution. Created automatically on the schedule (or manually via Run backup now), records what was backed up, where it landed, and how long it took.
- Storage destination – an S3 bucket. Either Norcube-managed or bring-your-own (BYO). Picked per policy.
- Audit log – append-only timeline of every sensitive action, across data sources, policies, backup jobs, destinations, and restore requests.
How it works
When a backup fires – scheduled or manual – Backup launches a short-lived, isolated worker container that:
- Decrypts your database credentials inside the container.
- Streams
pg_dumpormongodumpoutput directly to S3 – no local disk, no intermediate files. - Encrypts at rest in S3 with a KMS key scoped to your organization.
- Reports the result back to the Backup control plane.
The container is torn down at the end of the job. Each backup runs in its own container with minimal cloud-provider permissions. See Encryption and security.
Pricing
Backup bills on two dimensions:
- Storage – per GB of backups retained per month (only for Norcube-managed destinations; you pay AWS directly for BYO buckets).
- Compute – per second of job runtime.
Both have a free tier and volume discounts. See pricing for current rates.