I noticed that the backup-files by calling “/var/ipfire/backup/bin/backup.pl exclude” and “/var/ipfire/backup/bin/backup.pl iso” are created in different locations:
/var/ipfire/backup
and
/var/tmp/backupiso/
Is that by design or is this a bug present in core 163?
I plan to automate the backup-creation so I need to know where I can collect the created backup files later.
TIA!
Hi,
a bit of both, I guess. 
Indeed, /var/tmp/ and similar locations should not be used for long-term storage of files. See also the discussion to this patch. In the future, you will hopefully see the backup scripts using consistent directories for storing backups.
Thanks, and best regards,
Peter Müller
Hi Peter,
thanks for the clarification. For now, I’m fine to use /var/tmp/backupiso/ for the ISOs.
Hopefully I will remember to change the path when it got fixed. 
cheers,
Chris
Hi,
since you are probably not the only one expecting /var/tmp/ to be stable (because it has always been in the past), I believe we would announce such a change in the release notes of the corresponding Core Update, so people can check and adjust their custom scripts, if necessary.
Thanks, and best regards,
Peter Müller