In recent days, I had to take my backup server offline a number of times as planned. What struck me then is that I didn’t receive any notifications that the backups were failing or could not be made. Did I set something up wrong, or is there no notification for this? I would like to know if my backups are failing.
No notifications for failed backups
It would be nice if this wasn't just limited to Slack and instead had some sort of webhook system. A lot of people are using other tools such as Discord, Mattermost, RocketChat etc and would be nice if it wasn't restricted to only email and slack.
- Edited
Dan You could probably poll the Enhance API and make your own. Seeing a market for third party integrations via their API coming up if Enhance continues along this path.
But this should have been feature upfront. At LEAST email notification. A "backup" strategy without failure (and success) notifications is a... cute idea... to put it politely.
It would be nice if enhance was production ready as they advertise.
That would be nice. One can dream of the day when Enhance fully builds out things and becomes production ready We should make a feature request: "Make Enhance Production Ready"
JohnB Hello John, I think we may have different definitions of what is "Production Ready".
As far as I am concerned I already have happy clients running on Enhance who all do consider it "Production Ready". I also know other serious hosts in the community who also consider Enhance production ready.
Maybe you could detail what is your personal description of a "Production Ready" control panel. All panels are constantly evolving and what one may consider Production Ready may not be someone else case.
- Edited
Adrien My definition would include reliable backup / recovery options that notify at least upon failure. If this was some Github project I would have no expectations. However, its marketed as "Production Ready" and yet until recently you had to come up with your own backup solution and now doesn't notify you on backup failure.
Untestable silently failing server backups.... Yet its "Production Ready"?
I wouldn't even release a business critical desktop app that doesn't have AT LEAST clear backup/recovery documentation. And if it had backup features its certainly not going to fail silently unless its BETA. When critical features are missing important things, it makes you look amateur and not production quality.
I imagine the backup issue doesn't affect large hosts much because they run baremetal and have a lot more flexibility in terms of bootable restore, drive swapping etc. However, if you host with VPS's you only get provider backup/snapshots which are notorious for having issues and being untestable.