Problem/Justification
Currently, TrueNAS allows setting up ZFS Replication Tasks to pull data from or push data to remote ZFS-capable systems. However, Periodic Snapshot Tasks can only be scheduled for local datasets. If a remote target or source (e.g., a Linux server, Proxmox host using ZFS, or secondary ZFS system) does not have automated snapshot scripts configured locally, replication tasks require manual setup of cron jobs or 3rd-party tools (like Sanoid) on the remote node.
Proposed solution:
Extend Periodic Snapshot Tasks (or integrate directly into Replication Tasks) with the ability to target a Remote SSH Connection. TrueNAS would execute the snapshot creation remotely via SSH prior to pulling the ZFS stream.
Impact
Centralized Data Protection: TrueNAS becomes a single pane of glass for scheduling both local and remote ZFS snapshots and replications.
Reduced Operational Overhead: Administrators do not need to install or maintain custom snapshot scripts on edge hosts or secondary ZFS-based VMs/hypervisors.
User Story
As a TrueNAS Administrator, when configuring a Periodic Snapshot Task or a Pull Replication Task, I want to select a saved SSH Connection and specify a remote dataset path, so TrueNAS automatically triggers crash-consistent ZFS snapshots on the remote host before initiating replication.
Benefits: Streamlined backup management across multi-node environments; zero extra dependencies on remote nodes beyond standard SSH and ZFS privileges.
Risks / Mitigation: Executing commands on remote hosts could fail if permissions are misconfigured. Mitigation: Require explicit selection of an authorized SSH key and limit remote commands to zfs snapshot / zfs list.