• 16 Posts
  • 475 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle
  • I use Borg but every now and then I mount a backup and download a few files to make sure they work correctly.

    I’ve so far only had to do this for real with my local zfs snapshots after messing up a config file or blowing away the wrong folder. Process to restore is essentially the same except I would mount the Borg repo instead of a local zfs snapshot












  • I used to use a docker container that makes db dumps of the database and drops it into the same persistent storage folder the main application uses. I use this for everything in docker that had a db.

    Immich as recently integrated this into the app itself so its no longer needed.

    All my docker persistent data is in a top level folder called dockerdata.

    In that I have sub folders like immich which get mounted as volumes in the docker apps.

    So now I have only 1 folder to backup for everything. I use zfs snapshots to backup locally (zfs auto shot) and borgmatic for remote backups (borgbase).

    All my dockers all compose files that are in git.

    I can restore he entire server by restoring 1 data folder and 1 compose file per stack.







  • How is this better than being top level folders like school, receipts, car maintenance etc and then naming your files like:

    2025-02-21 - car service receipt.PDF

    Easy to find and see what is newest since it alphabetical by age and easy to search since the file name is descriptive.

    Combine this with better search tools like powertools OK windows and it seems way more intuitive than this system.

    Combine this by having the folder in a backup solution like google drive / Nextcloud / seafile etc and you can access these files anywhere securely.