Custom command before and after backup

[JonMikelV]

@martindeveloper

Also this warning appears for every operation like listing backups etc. Also I use the conditions to check for event and operation name so the whole “logic” of script runs only for BEFORE Backup.

Yeah, this is a known issue (though I can’t find the topic for it right now). At present the best way to handle this is to have your script \use the Duplicati environment variables to check that %DUPLICATI_OPERATIONNAME% = Backup otherwise abort the job:

Duplicati Environment Variables

Do you mean the PDF documentation that’s not quite done? The variables should be the same in all environments and are basically DUPLICATI followed by the parameter name (as it would be used with a command line call) with any dashes replaced by underscores. Some examples are: if you want to access the --dbpath parameter you’d use DUPLICATI__dbpath if you want to access the --dblock-size parameter you’d use DUPLICATI__dblock_size if you want to access the --backup-name parameter you’d use DU…

---

@martindeveloper

not recognized as an internal or external command

Are you test running your commands through the web GUI Command line feature? If so, this is also a known issue where some of the pre-filled parameters are passed even if not needed for the selected command. I usually make it a point to blank out all fields not needed for my specific command and it seems to run OK.

Nothing done in the Command line window is “saved” so don’t worry - you won’t be wiping out your backup job settings or anything like that.