Dokploy can schedule automatic backups of your databases, but it does not turn them on by itself: you have to tell it where to store them. Your VPS already has daily server backups; Dokploy's own backups let you restore a single database or take it elsewhere.
What to keep
- Your applications' databases: the most important part.
- The code: if you deploy from Git, it is already in your repository.
- Data your applications store in volumes (files uploaded by users, for example).
1. Add an S3 destination
Dokploy backups are stored in S3-compatible storage that you sign up for (Amazon S3, Cloudflare R2, Backblaze B2 or another).
- In Dokploy, open Settings → S3 Destinations.
- Add the destination with its endpoint, bucket and access keys, and test it.
2. Schedule a backup for each database
- Open the database and go to the Backups tab.
- Create a scheduled backup: choose the S3 destination, the frequency and how many backups to keep.
- Run one manually the first time to check that it reaches the destination.
You can restore a backup from that same tab whenever you need it. More detail in the Dokploy documentation.
3. Your applications' volumes
If an application stores files in its own volume, back it up yourself. You can list volumes with docker volume ls and download their contents over SFTP logging in as root.
Tip: a backup that only lives on the server itself does not protect you if you reinstall it. That is why the S3 destination should be outside your VPS.
Related
- Reinstall or change the application on your VPS
- How to update Dokploy on your VPS
- Getting started with your Dokploy VPS
Order: Dokploy VPS in Frankfurt · in Miami
Was this article helpful?
Need more help?
Open a ticket and the support team goes through it with you.