LaserData Cloud
Deployments

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

TypeDescription
ManualCreated on demand from the Console or API
Pre-upgradeAutomatically created before deployment upgrades

Backup Status

StatusMeaning
PendingBackup requested, waiting to start
In ProgressSnapshot creation in progress
CompletedBackup finished successfully
FailedBackup encountered an error
DeletingBackup is being removed

Only one backup can be in progress per deployment at a time.

Creating a Backup

From the Console

  1. Navigate to your deployment
  2. Open the Backups tab
  3. Click Create Backup
  4. Enter a name and optional expiry (in days)
  5. 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

ResourceBasicProEnterprise
Backups per deployment-510

API Reference

List Backups

curl {supervisor_url}/deployments/{deployment_id}/backups \
  -H "ld-api-key: YOUR_API_KEY"
[
  {
    "id": 1,
    "deploymentId": 42,
    "nodeId": 1,
    "name": "pre-upgrade-backup",
    "backupType": "manual",
    "status": "completed",
    "snapshotIds": ["snap-0abc123def456789a"],
    "volumeIds": ["vol-0abc123def456789a"],
    "sizeBytes": 53687091200,
    "region": "us-west-1",
    "remarks": null,
    "startedAt": "2025-01-15T10:30:00Z",
    "completedAt": "2025-01-15T10:45:00Z",
    "expiresAt": "2025-02-14T10:30:00Z",
    "createdAt": "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",
    "expiresInDays": 30
  }'
FieldRequiredDescription
nameYesName for the backup
nodeIdNoSpecific node to back up (all nodes if omitted)
backupTypeNomanual (default), pre_upgrade
remarksNoOptional description
expiresInDaysNoAuto-delete after this many days

Returns 204 No Content on success.

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.

On this page