La fonctionnalité est simple: Quand un backup échoue, recevoir une alerte pour être prévenu que Gladys Plus n’arrive pas à backup l’instance locale.
Ca permet d’éviter toute catastrophe si jamais les backups sont cassées pendant plusieurs semaines à cause d’une raison diverse (problème d’espace disque, etc…)
Okay, I know only 9 of us voted for it, but it seems to me this feature is pretty important from a user peace-of-mind point of view.
Here’s what I just discovered…
Rather unfortunate!
Gladys is running smoothly and I trust it. As a result, there was no reason to go and check that the backups had run.
Now I’m in trouble. It’s a disk space issue that’s preventing the backup (11 GB database + copy + compression; it no longer fits on a 32 GB partition).
I have to modify the partitions so I need to make a backup, and I won’t be able to use the system I’m paying for without losing two months of data.
A simple notification (a banner, an email, a Telegram message, a chat…) would have allowed me to take the bull by the horns earlier!
In short, I’m disappointed.
I would even say that the alert (or another) should appear before this kind of issue. In your case @GBoulvin (and I believe this has already happened to others before you) there should be an alert with a calculation of the space required for the backup leaving 1 or 2 GB free to warn that the backup will soon no longer be possible…
For my part I also voted, even though it shouldn’t happen to me for a while; the failed backup alert remains useful for other cases.
But for me this mainly raises what should be done upstream: warn the user who installs Gladys that a minimum amount of disk space is recommended (something like 64 or 128 GB).
Because in this specific case, someone with too small a partition will set about resizing it. Needless to say, this kind of operation will require skills that will also allow them to recover their production DB and back it up / restore it manually (that’s what I had to do a few months ago).
So the goal isn’t really to be warned in my opinion, even if that can be useful, the goal is to never have this problem, so to have allocated space in advance!
Hi @GBoulvin ! I understand your frustration and it’s true that it’s hard to trust the backup system if it doesn’t alert in case of backup errors.
I’ll see if I can do something in the next few days, Gladys
However, as @Terdious said, in your case you need more than 2 times the size of your DB (database) in disk space, so ideally there should also be an alert when you approach 50% of available disk space (another topic in my opinion)
I really recommend mini-PCs, you get a beast at a low price, with a 512 GB NVMe SSD, you never have to ask yourself the question
In my case, I’ve always made a habit of installing my Linux distributions with separate partitions for / and for /home, as well as other storage partitions.
And I had a system partition that was too small… even though my SSD is 512GB … the irony! That’s why I think it should be noted somewhere in the docs.