I have 11 backup jobs running on 8 different machines, and my users occasionally like to fiddle with the job settings or I update them and forget to extract the settings and store them for backup purposes (yes, I see the irony there ). That being the case, Iād like to be able to extract all the current job configuration from all the systems (ideally from a remote location) for backup storage. Does Duplicati provide a simple way to do this, either from the command line or through some Sqlite-fu?
Thatās an interesting question - are you thinking of using --run-script-before
to export the backup job to a .json file which is then included in the backup?
@JonMikelV, not sure what Iām thinking just yet. Just had an idea and searching for possible ways to go about it. Your approach sounds interesting, but that would mean including the ārun-beforeā script on every system. Iāll have to think that one through and do some testing. Thanks!
I suppose you could always make an official request for something like a checkbox to āinclude current job export on destination with each backup runāā¦
5 thumbs up for this!
Would be cool to have a āsaveā-hook to have custom script run on saving the job definition.
Automatically extracting it and then commit it to a git repo.