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

keep backups of mixxxdb #14233

Open
ronso0 opened this issue Jan 26, 2025 · 5 comments
Open

keep backups of mixxxdb #14233

ronso0 opened this issue Jan 26, 2025 · 5 comments

Comments

@ronso0
Copy link
Member

ronso0 commented Jan 26, 2025

Feature Description

Pretty much like log rotate: store the old db either with # or date/time suffix.
Just as a safety net in addition to manual/automatic backups.

(other data is also valuable, of course, but mappings and effects don't change that often so they are likely covered by backups)


Motivation:
yesterday I started Mixxx and was asked for a music directory. Whaaaat?
Quickly check the settings dir: mixxxdb.sqlite was ~170 kB Whaaaat?
The symlink to my external analysis directory was also gone.
In the log there where also complaints about missing effect chain presets.
The rest of the settings directory seems to be intact 🤷

So there might have been some some data corruption or whatever but I didn't notice any event lately that might have caused this.
My backup routine is 'manual', i.e. I make a backup after every important session and when rebuilding Mixxx.
Here, however it has been "just" preparation sessions lately (so no backup of them) and for some reason some earlier backups (on the same disk) are also.. gone.
Some weeks must have passed since that, so data recovery didn't yield any valuable results.

I have metadata export enabled, and since I use the comment for tagging (not crates) I might "only" have lost my pratice playlists, not my valuable filtering properties.

@daschuer
Copy link
Member

I have put my productive .mixxx directory under git.

@Swiftb0y
Copy link
Member

mixxxdb's are likely larger than logfiles. Would it make sense to rotate them less often then? Instead of on every startup, only rotate on every version upgrade?

@ronso0
Copy link
Member Author

ronso0 commented Jan 26, 2025

Are you worried about delays during startup with slow disks?
With ~16k tracks my db is ~20 MB

I'd be fine with a backup per day, i.e. keep the oldest backup of a day when starting Mixxx multiple times.

@ronso0
Copy link
Member Author

ronso0 commented Jan 26, 2025

I have put my productive .mixxx directory under git.

Me too, but then I excluded the db because "I have my database backups, why deal with these binary diffs?" 🤦

@Eve00000
Copy link
Contributor

I hope you retrieved all your data.
As a great fan of data-security I can only encourage an automatic BU (I have script making a daily BU), but I've read about some users make changes / remove tracks without a BU.

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

4 participants