I’m currently setting up a large TrueNAS Scale 25.10.1 system as a long-term archive and backup storage. It’s intended to replicate from several primary TrueNAS and Ubuntu/ZFS storages to back them up. This backup system is, of course, off-site, meaning the replication needs to pass through multiple firewalls and packet filters.
This isn’t a problem in itself, but with the amount of data being large (hundreds of terabytes), the transfer takes a long time. If something restarts on the firewalls or filters during that time, the replication appears to hang. It then remains permanently listed as a running job in the job list.
Unfortunately, there’s no way to cancel or “kill” this job. Restarting middlewared is no option - this would kill all other running tasks as well.
Would it be possible to offer this functionality? At least for replication jobs where no data has arrived for 5 or 10 minutes, it would make sense.
Alternatively (or additionally), it would be helpful if the job list or job log indicated the PID under which the replication was started. That would allow me to specifically terminate that job from the console.