Getting started
Connect your first database and take a backup on a schedule.
This guide walks you through connecting a Postgres database, creating a backup policy, attaching them, and verifying that the first backup ran. About five minutes.
Prerequisites
- A Norcube account (sign up).
- A reachable PostgreSQL or MongoDB database. Your firewall / security
group must allow inbound connections on the database port from
Backup's egress IP
18.196.207.101. See Network access. - A user on the database with read access to everything you want backed up.
Connect the database
- Open app.norcube.com and switch to Backup from the product switcher.
- Go to Datasources → New datasource.
- Fill in:
- Name – a label (
production-db,analytics-staging). - Engine – Postgres or MongoDB.
- Environment – production / staging / dev / test.
- Region – the AWS region your backups will land in.
- Name – a label (
- Click Create. You'll land on the credentials page.
Add credentials
Choose how you want to provide credentials:
Paste a complete URI:
- Postgres:
postgresql://user:pass@host:5432/dbname?sslmode=require - Mongo:
mongodb://user:pass@host:27017/dbname?tls=true&authSource=admin
Fill in host, port, user, password, database name, plus engine-specific
extras (Mongo: authSource, scheme).
Click Save credentials. The dashboard auto-verifies them right after save – a green badge means you're good. They're encrypted with AWS KMS before storage; see Encryption and security.
Create a backup policy
A policy bundles a schedule, retention, and destination.
- Go to Backup policies → New backup policy.
- Fill in:
- Name –
daily-7day,hourly-prod, etc. - Schedule – a 5-field cron expression (
0 3 * * *= every day at 03:00). The form shows a plain-English translation as you type. - Timezone – the timezone the schedule is interpreted in.
- Retention – keep backups for N days, or keep the last N backups, or both (whichever cap is hit first).
- Destination – a managed bucket or a BYO destination you've already created.
- Name –
- Click Create.
Attach the policy to the data source
- Go back to the data source page.
- In the Backup policies card, click Attach backup policy.
- Pick the policy you just created and click Attach.
Backup schedules the first run based on the cron expression. You don't need to manually trigger anything.
Watch (or trigger) the first backup
When the next scheduled time arrives, a backup job appears in Backup jobs on the data source page with status Queued → Running → Success. Click the job for details: bytes written, duration, S3 location.
Don't want to wait? Click Run backup now on the data source page and a manual job kicks off immediately.
Next steps
Reuse a policy across databases
One schedule + retention + destination, attached to many data sources.
Browse backup history
Filter, download, delete, manually re-run.
Bring your own S3 bucket
Land backups in your own AWS account – you control retention pipelines.
Audit every action
Who did what, when, against which resource.