Found something bad as well:
A script was written and placed into Crontab, which performs a certain backup, BUT it also cleans up old backups of the same backup action he also runs as well. Nothing wrong, you'd think.
Well, the Crontab job can be disabled - like any Crontab job really - but when you do this, this is what happens :
No new backups are written, good. But, no cleanup is occuring either. So, if you leave this job disabled for 2 years, you will have old backups sitting there for 2 years, wasting space, because these backups are useless given the age. The Crontab job is disabled for reason of not needing new backups, so old backups are unnecessary in this context. If these old backups are important, it's never intended as such, because these old backups can just be removed by running the script. Not as a Crontab job, but just as a script. Ironically, that would be to create a new backup. Becasuse, at some point you'd want to. But, this comes with the price that all old backups are deleted. Nobody ever had many thought about this script. They wrote it. yes it works, so now never change it, whatever happens !
In addition, what seems to be the case as well: the backup done via the script, can fail.
But, the cleanup occurs unconditionally.