Backups Unavailable

no-backup-destination · 409

The platform has nowhere to store backups, so the API took no backup and started no restore.

It is the platform's setting, not the database's or the caller's, so no change to the request gets past it.

This type adds no members to the ones every error carries.

Common causes

  • A backup was asked for, by hand or from the console, on a platform with no place for backups.
  • A restore was asked for on the same platform: a restore reads from that place too.

How to fix the call

  • Tell the user that backups can't be taken here, quoting detail.
  • Don't retry: the answer stays the same until the platform has a place for backups.

Example response

json
{
  "type": "no-backup-destination",
  "title": "Backups Unavailable",
  "detail": "Backups are not available on this platform yet. Nothing was taken.",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/backups",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/backups",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/no-backup-destination"
}