this post was submitted on 17 Jan 2026
72 points (98.6% liked)

Selfhosted

60210 readers
951 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
72
Where to start with backups? (lemmy.world)
submitted 5 months ago by mapleseedfall@lemmy.world to c/selfhosted@lemmy.world
31 comments fedilink hide all child comments
 

hi peeps.

Im early on my selfhosting journey and managed to setup some things as a test in docker. the main service im looking to run is ERPNext. after a while I got it up and running so now I want to back this up including all the customization I did in the app.

where to start with this? any intuitive guide?

you are viewing a single comment's thread
view the rest of the comments
[–] bjoern_tantau@swg-empire.de 18 points 5 months ago* (last edited 5 months ago) (2 children)

In general you backup everything that cannot be recreated through external services. So that would be the configuration files and all volumes you added. Maybe logfiles as well.

If databases are involved they usually offer some method of dumping all data to some kind of text file. Usually relying on their binary data is not recommended.

Borg is a great tool to manage backups. It only backs up changed data and you can instruct it to only keep weekly, monthly, yearly data, so you can go back later.

Of course, just flat out backing up everything is good to be able to quickly get back to a working system without any thought. And it guarantees that you don't forget anything.

[–] tal@lemmy.today 6 points 5 months ago* (last edited 5 months ago)

If databases are involved they usually offer some method of dumping all data to some kind of text file. Usually relying on their binary data is not recommended.

It's not so much text or binary. It's because a normal backup program that just treats a live database file as a file to back up is liable to have the DBMS software write to the database while it's being backed up, resulting in a backed-up file that's a mix of old and new versions, and may be corrupt.

Either:

  1. The DBMS needs to have a way to create a dump

possibly triggered by the backup software, if it's aware of the DBMS

that won't change during the backup

or:

  1. One needs to have filesystem-level support to grab an atomic snapshot (e.g. one takes an atomic snapshot using something like btrfs and then backs up the snapshot rather than the live filesystem). This avoids the issue of the database file changing while the backup runs.

In general, if this is a concern, I'd tend to favor #2 as an option, because it's an all-in-one solution that deals with all of the problems of files changing while being backed up: DBMSes are just a particularly thorny example of that.

Full disclosure: I mostly use ext4 myself, rather than btrfs. But I also don't run live DBMSes.

EDIT: Plus, #2 also provides consistency across different files on the filesystem, though that's usually less-critical. Like, you won't run into a situation where you have software on your computer update File A, then does a sync(), then updates File B, but your backup program grabs the new version of File B but then the old version of File A. Absent help from the filesystem, your backup program won't know where write barriers spanning different files are happening.

In practice, that's not usually a huge issue, since fewer software packages are gonna be impacted by this than write ordering internal to a single file, but it is permissible for a program, under Unix filesystem semantics, to expect that the write order persists there and kerplode if it doesn't...and a traditional backup won't preserve it the way that a backup with help from the filesystem can.

[–] mapleseedfall@lemmy.world 4 points 5 months ago (1 children)

By everything, does this mean the docker file and its volume?

[–] bjoern_tantau@swg-empire.de 3 points 5 months ago (1 children)

The whole drive. The docker file and volumes are the bare minimum.

[–] mapleseedfall@lemmy.world 1 points 5 months ago

Sweet ill get to it