Backups
Create and manage EBS snapshots for deployment data protection
Experimental — the Backups feature is under active development and may change. API endpoints, request/response formats, and behavior are not yet stable.
Backups create point-in-time snapshots of your deployment's storage volumes. Use them to protect against data loss, or to capture state before upgrades.
Backups are available for AWS deployments with network storage only. NVMe SSD deployments do not support backups. Requires the Pro or Enterprise plan.
How It Works
Backups are EBS volume snapshots taken from your deployment nodes. When you create a backup, LaserData snapshots the storage volumes for the specified node (or all nodes if not specified). The backup runs in the background and transitions from Pending to In Progress to Completed.
Backup Types
| Type | API Value | Description |
|---|---|---|
| Manual | manual | Created on demand from the Console or API |
| Scheduled | scheduled | Created automatically on a recurring schedule |
| Pre-upgrade | pre_upgrade | Automatically created before deployment upgrades |
Backup Status
| Status | Meaning |
|---|---|
| Pending | Backup requested, waiting to start |
| In Progress | Snapshot creation in progress |
| Completed | Backup finished successfully |
| Failed | Backup encountered an error |
| Deleting | Backup is being removed |
Only one backup can be in progress per deployment at a time.
Creating a Backup
From the Console
- Navigate to your deployment
- Open the Backups tab
- Click Create Backup
- Enter a name and optional expiry (in days)
- Click Create
Managing Backups
From the Backups tab, you can view all backups for the deployment, including their status, size, and creation time. Delete backups you no longer need to free up snapshot storage.
You cannot delete backups that are currently in progress or pending. Wait for the backup to complete before deleting.
Required permission: deployment:read (view) or deployment:manage (create, delete)
Plan Limits
| Resource | Basic | Pro | Enterprise |
|---|---|---|---|
| Backups per deployment | - | 5 | 10 |
API Reference
List Backups
curl {supervisor_url}/deployments/{deployment_id}/backups \
-H "ld-api-key: YOUR_API_KEY"[
{
"id": 1,
"deployment_id": 42,
"node_id": 1,
"name": "pre-upgrade-backup",
"backup_type": "manual",
"status": "completed",
"snapshot_ids": ["snap-0abc123def456789a"],
"volume_ids": ["vol-0abc123def456789a"],
"size_bytes": 53687091200,
"region": "us-west-1",
"remarks": null,
"started_at": "2025-01-15T10:30:00Z",
"completed_at": "2025-01-15T10:45:00Z",
"expires_at": "2025-02-14T10:30:00Z",
"created_at": "2025-01-15T10:30:00Z"
}
]Create a Backup
curl -X POST {supervisor_url}/deployments/{deployment_id}/backups \
-H "ld-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "before-migration",
"remarks": "Snapshot before schema migration",
"expires_in_days": 30
}'| Field | Required | Description |
|---|---|---|
name | Yes | Name for the backup |
node_id | No | Specific node to back up (all nodes if omitted) |
backup_type | No | manual (default), scheduled, pre_upgrade |
remarks | No | Optional description |
expires_in_days | No | Auto-delete after this many days |
Returns 204 No Content on success.
Restore a Backup
Restores a deployment from a backup by swapping the current storage volumes with the backup's snapshots. The deployment is stopped during restore and restarted automatically. Only one restore can run at a time per deployment.
curl -X POST {supervisor_url}/deployments/{deployment_id}/backups/{backup_id}/restore \
-H "ld-api-key: YOUR_API_KEY"Returns 204 No Content on success.
Restoring a backup replaces the current storage volumes. Any data written after the backup was created will be lost. Consider creating a new backup before restoring.
Delete a Backup
curl -X DELETE {supervisor_url}/deployments/{deployment_id}/backups/{backup_id} \
-H "ld-api-key: YOUR_API_KEY"Returns 204 No Content on success.