Selfhosted

59935 readers

259 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How do you manage you DB in a docker environment? (sh.itjust.works)

submitted 3 days ago by Croquette@sh.itjust.works to c/selfhosted@lemmy.world

34 comments fedilink hide all child comments

Hello,

As the title suggests, how do you manage your DBs for docker services.

Do you spin a new DB for every new docker cluster or do you have a centralized DB that is accessible to the docker clusters.

What are the pros and cons of both method?

For the moment, I spin a new DB for every services as I feel it is easier to backup the service in case of a problem.

you are viewing a single comment's thread
view the rest of the comments

[–] Mertn33@lemmy.world 1 points 1 day ago (1 children)

My backup tooling just shuts down the container and associated db, then rysncs it all somwhere safe and restarts the container. Am I missing somethoing critical by not doing a db dump in the middle of that?

[–] Zikeji@programming.dev 0 points 1 day ago (1 children)

Most of the time that's perfectly fine, but if the database were in the middle of an operation you risk corruption.

[–] Mertn33@lemmy.world 1 points 1 day ago (1 children)

The last thing I want is database corruption. That is why I "docker compose down" before I make a backup then "docker compose up" when the backup is complete. Is that not good enough? Do I have to do something else?

[–] Zikeji@programming.dev 1 points 21 hours ago* (last edited 21 hours ago)

Yes that's good enough! Sorry I missed your statement about shutting down first. To clarify I leave mine running since a dump can recover if it gets corrupt.

Basically my backup contains the database and the SQL dump (or equivalent) - that way I don't need to shutdown the service.