Browse backup history

Backup keeps a record of every job for the lifetime of your account. Use the history views to confirm scheduled backups are running, spot failures early, and answer "what backups do we have for X?".

Per data source

The fastest way to audit one database:

1. Open the data source in app.norcube.com → Backup.
2. Scroll to Backup jobs.

You see the most recent jobs by default, with cursor-paginated Load more. Each row shows:

• Status – success / failed / partial / canceled / running / queued. Failed rows reveal the underlying reason on hover.
• Trigger – schedule or manual.
• Scheduled time vs started time.
• Duration.
• Bytes written.
• Actions – combined Download / Delete cell. Download is disabled on expired and unsuccessful jobs.

Click a row to open job detail with the full storage path.

Click Refresh (top-right of the card) to re-fetch without reloading the page.

Cross-database overview

To see backups across every database in the organization:

1. Open Backup → Backups (top-level page).
2. Filter by data source, status, or time range.

Useful for:

• "Did anything fail last night?" – filter status = failed.
• "How much did we back up this week?" – sort by bytes written.

Run a backup now

Don't want to wait for the next scheduled time?

1. Open the data source page.
2. Click Run backup now.
3. If multiple policies are attached, pick the one to run from the dialog. Default = the highest-priority enabled attachment.
4. Confirm.

A new job appears in Backup jobs with trigger manual. The worker picks it up within a few seconds.

Manual runs of the same data source can overlap with each other and with scheduled runs – the worker tolerates parallel jobs.

Download a backup

In Backup jobs, click Download on a successful, non-expired row. The dashboard generates a short-lived signed URL and streams the download to your browser. The same flow works for both managed and BYO destinations.

Delete a backup

Click Delete in the row's action cell. Confirm in the dialog. The S3 object is removed; the job stays in history marked deleted.

Behaviour and edge cases

• Failed jobs are not retried automatically within a scheduled tick. The next scheduled time fires a new attempt.
• Job records survive policy deletion – detaching or deleting a policy keeps the historical job records, only stops future runs.
• Job records are deleted when their data source is deleted. If you're decommissioning a database but want to keep the audit trail, export the history via the API first.
• Expired backups stay listed but their Download action is disabled because the underlying S3 object has been deleted by the retention worker.

Related

• Backup jobs – the concept page.
• Audit log – every backup job lifecycle event shows up here too.