On 7/4/26 14:50, Rob Gerber wrote:
The main downside I can think of when using a time-bounded SQL query, is
the risk that something has gone wrong with cloud uploads for some
reason, and some older jobs which were never uploaded are not copied
because the SQL query excludes them because they are too old. This could
break the backup chain.
If using a time-limited SQL query like suggested by Phil, I do think it
could be wise to set up an admin job running an inverse query (select
only jobs which are OLDER than x days), and if any are found, report the
job IDs and exit 1 so the bacula admin job will show an error status to
bring this situation to an admin's attention.
That's a good idea. I would totally set up something like that in an
enterprise implementation.
For my own personal setup, if something went wrong in the infra, the
odds are I already know before Bacula does.
--
Phil Stracchino
Fenian House Publishing
[email protected]
[email protected]
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
