Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database / config backup #521

Open
frakkingtoaster opened this issue Dec 28, 2020 · 8 comments
Open

Database / config backup #521

frakkingtoaster opened this issue Dec 28, 2020 · 8 comments

Comments

@frakkingtoaster
Copy link

Describe the solution you'd like
Requesting a scheduled and on-demand database backup and restore feature that backups the database and the config.

Describe alternatives you've considered
Just copying the db file but that needs to separately be set up on a schedule and isn't always helpful if something happens to the app.

@sct
Copy link
Owner

sct commented Dec 29, 2020

Should this really be the responsibility of Overseerr? You can set up another tool to backup your config folder however often you like.

@frakkingtoaster
Copy link
Author

frakkingtoaster commented Dec 29, 2020

Hmm, I think it should, given that almost all other apps have this functionality (all the *arrs, plex, tautulli). I guess it's debatable.
edit: not necessarily a responsibility, as in it doesn't have to create backups by default, but it would be great if it did have the ability to.

@sct
Copy link
Owner

sct commented Dec 29, 2020

Okay. We can make this happen. Will be a lower priority but not entirely against creating a folder of backups at an interval.

@frakkingtoaster
Copy link
Author

Awesome! Totally fine, definitely not expecting it with any priority. Btw the way I run these is by creating a volume just for the backup folder that sits on my nas, so this would be great!

@douglasparker
Copy link
Contributor

Lots of apps will do a quick db backup before an update, which I admit is nice for when updates go wrong.

However, in my opinion that is not a true backup because if your drive dies or you get hit with ransomware, you're pretty much screwed. Sure, you could throw in some redundancy somewhere but once again ransomware or any kind of natural disaster or really bad luck with hardware failure and you're screwed.

Which brings me around to the 3-2-1 backup rule, which indeed falls on the system administrator. When following best practice to protect your data, you're put in a position where you need to handle backups on your own; including offsite backups.

This is very easily done in a cronjob on Linux or task scheduler on Windows.

Literally all you need is a script that stops Overseerr, copies the Overseerr directory to a temp backup directory, compress & archive, and then send to whatever storage provider offsite using a tool like rclone.

I think documenting examples of how this might be done in the Wiki is worthwhile. It's super easy and trivial to do, it just looks daunting from someone who isn't familiar with using the command-line.

@stale

This comment was marked as resolved.

@stale stale bot added the stale label Feb 28, 2021
@stale stale bot closed this as completed Mar 8, 2021
@ver151set

This comment was marked as spam.

@TheCatLady TheCatLady reopened this Apr 27, 2023
@stale stale bot removed the stale label Apr 27, 2023
@stale
Copy link

stale bot commented Jul 15, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants