Backups

Purpose

Run and review backups for services that have them set up in Dokploy - apps, databases, volumes. This screen is admin-only.

---

Roles

• Dokploy admin/owner - full access to the list and triggering.
• Other roles - the screen stays hidden.

---

User Flow

Review backup state

Step 1: Open Backups

1. Open Settings → Backups. Each row shows the service name, its project, the last result (success, failed, or never), when it last ran, and a Trigger button.

Result:

• You know what's protected and what never ran.

---

Start a backup

Step 2: Trigger and confirm

1. Find the service and tap Trigger, then confirm. The button needs Pro on top of the admin role - without it, the list is read-only.
2. Dokploy runs it on the server. "Backup triggered" confirms it started; a push arrives when it's done if backup notifications are on.
3. Backups can also be deleted from their rows ("Backup deleted" confirms) - deleting needs Pro like triggering does.

Result:

• The backup runs on schedule-plus-now; history updates on refresh.

---

Screens Involved

• Backups list (status, last run, Trigger per row)

---

Inputs

User Inputs:

• Trigger + confirm per service

---

Outputs

• Backup job started on Dokploy; result message (and optional push)

---

Error Handling and Edge Cases

Scenario	System Behavior
"No backups configured"	Nothing to back up for visible projects - set up schedules in Dokploy Web first
Screen hidden entirely	Not a Dokploy admin - ask an owner for the role
Trigger fails	Usually sign-in trouble - sign in again (see Troubleshooting)