Repository navigation
What should I backup? #701
Replies: 2 comments
|
hey, your instinct is right - Postgres is the main thing to backup. thats where all your monitors, incidents, historical uptime data, user accounts, and settings live. a scheduled for Redis you can skip it tbh. looking at the docker-compose, Redis is used for BullMQ queues, caching, and the scheduler. all of that is transient/ephemeral stuff that gets rebuilt when kener starts up. if you lose your Redis data the worst that happens is some in-flight notification jobs or pending monitoring checks get dropped, but kener will just re-queue everything on the next cycle. not worth the backup complexity imo. one thing I'd add to your list though - make sure you're also backing up your environment variables, specifically
for the pg_dump in swarm you can just run something like: on a daily cron and ship it to s3 or wherever. hope that helps! |
|
Lovely, thanks a ton |
Uh oh!
There was an error while loading. Please reload this page.
We are using latest version kener:4.0.23 in docker swarm with Postgres/Redis.
(btw: everything super good, so thank you for developing Kener!! (must say a great ad a much better tool of FreshStatus)
What should we backup in our setup?
I see all Kener's data is in Postgres, so I guess it's db is all we need to backup: well, of course we have to backup the stack file.
Shoud we backup redis ?
All reactions