Skip to main content

Overview

Backup endpoints allow you to start manual backups, monitor progress, view job history, and cancel running operations.

Start Backup

Start a manual backup operation. Endpoint: POST /api/backup/start
string
required
Repository path to back up
Example Request:
Response:
integer
ID of the created backup job
string
Initial job status: pending
string
Human-readable message

Get All Backup Jobs

Retrieve backup job history with progress details. Endpoint: GET /api/backup/jobs
integer
default:200
Maximum number of jobs to return
boolean
default:false
Only return jobs triggered by scheduled tasks
boolean
default:false
Only return manual backup jobs
Example Request:
Response:
array
Array of backup job objects
string
Job status: pending, running, completed, completed_with_warnings, failed, or cancelled
integer
Original size in bytes before compression
integer
Compressed size in bytes
integer
Deduplicated size in bytes (actual storage used)
integer
Number of files processed
number
Backup speed in MB/s

Get Backup Status

Get detailed status for a specific backup job. Endpoint: GET /api/backup/status/{job_id} Example Request:
Response:

Cancel Backup

Cancel a running backup job. Endpoint: POST /api/backup/cancel/{job_id} Example Request:
Response:
boolean
Whether the backup process was successfully terminated

Stream Backup Logs

Get incremental logs for real-time streaming (for failed/cancelled backups only). Endpoint: GET /api/backup/logs/{job_id}/stream
integer
default:0
Line number to start from for incremental updates
Example Request:
Response:

Download Backup Logs

Download complete logs as a text file (for failed/cancelled backups only). Endpoint: GET /api/backup/logs/{job_id}/download
string
required
Access token (passed as query parameter for download links)
Example Request:
Response: Plain text file with complete backup logs

Progress Tracking

Backup progress is tracked in real-time with the following metrics:
  • Progress Percent: Overall completion percentage (0-100)
  • Original Size: Total size of data being backed up
  • Compressed Size: Size after compression
  • Deduplicated Size: Actual storage used after deduplication
  • Files Processed: Number of files backed up
  • Current File: File currently being processed
  • Backup Speed: Current throughput in MB/s
  • Estimated Time Remaining: Seconds until completion

Status Values

Backup jobs can have the following statuses:
  • pending - Job created, waiting to start
  • running - Backup in progress
  • completed - Backup completed successfully
  • completed_with_warnings - Backup completed but with warnings
  • failed - Backup failed with errors
  • cancelled - Backup was cancelled by user

Maintenance Operations

Backups can include automatic maintenance:
  • Prune: Remove old archives based on retention policy
  • Compact: Free up space by compacting repository segments
Maintenance status is tracked in the maintenance_status field.