Backup Ente
Is there a recommended way to backup selfhosted ente with multiple users? As far as I know I can only backup with cli, but need to do it manually for each user
5 Replies
For self-hosted Ente with multiple users, you can use Ente's CLI tool or desktop app to export data to a local drive. This allows you to have a copy of the original photos and videos.
For automated backups, you can use Ente's CLI to export data in a cron job to a location of your choice. The exports are incremental and handle interruptions gracefully. See the CLI NAS sync guide for detailed setup.
Another option is to use Ente's continuous export and sync to an external drive, then upload it to a service like B2 using Kopia. You can find more information on backup recommendations at https://ente.io/help/self-hosting/administration/backup.
-# If your issue is resolved, feel free to use the /solved command to close this thread. If you'd like to ask me another question use /docsearch
CLI (Command Line Interface) | Ente Help
Ente's command-line tool for advanced users
If you are self-hosted imo you should be snapshotting the database +backing up the entire S3 storage
no need to do it via. ente
If you run your Ente compose files, db and storage all within a single folder like the QuickStart script creates then Restic will work great as an incremental backup mechanism. This video will get you started: https://youtu.be/WBBTC5WfGis?si=LFxMK6glKBQnyrxh
Jim's Garage
YouTube
Docker Backup and Restore Made EASY with Restic
This video shows you how to backup and restore your Docker data/volumes easily using Restic. Restic is a lightweight, efficient tool for creating snapshots of your data that enables you to recover when you need to.
Restic: https://restic.net/
Longhorn: https://longhorn.io/
GitHub File: https://github.com/JamesTurland/JimsGarage
Discord: https...
Thank you both, will look into it!
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Thread marked as solved. It will be closed in <t:1761133800:R>.
This thread is now closed.