Thanks for the reply. All of those sound like excellent ideas and I have tried them, lol.
We don’t go by days, because the people that actually insert the drives into the USB reader aren’t tech savvy enough to figure that out. They CAN count, however, and they know that 2 comes after 1 and when they get to 4, they put 1 back in. I agree that going by days would be the best thing to do, but, it never fails, they put Monday’s backup in on Thursday, then wonder why it didn’t backup.
The situation is #1. The backup happens just fine, from the command line, but it doesn’t update the GUI and those non-tech-savvy people really wanna see the line that says, “Last successful run:”
This topic originally came up, over on Github, and I was told to use the
--alternate-destination-marker to run all 4 backups, at once.Then I would put the corresponding file in the corresponding backup drive’s root directory. That works fine, except it records an error for the other 3 backups, that the destination marker could not be found.
--run-script-before-required is the one that looks for the zero value, right? If so, I tried that, as well. If my bash script returns a non-zero (error) value, Duplicati also terminates in error and sends me 3 emails saying so and 1 email saying the backup was successful.
--send-http-level I want it to report when the backup fails. I would rather it not run at all, if the responsible backup disk is not in place, which I can accomplish, but it doesn’t update the GUI.