You can select multiple Periodic Snapshot Tasks in the drop-down for the Replication Task configuration page. It also lets you specify multiple naming schemas.
No. One dataset.
The problem is that the snapshots on a dataset must remain in sequential order of creation. You cannot change the order or create new snapshots on the destination when it is a backup target.
Let’s say you have a replication task that only sends your daily snapshots.
@auto-daily-2026-08-13 is the latest one to be sent over.
Then you have another replication task that only sends your weekly snapshots.
@auto-weekly-2026-08-07 is the latest one that exists.
In order to replicate to the destination, the destination’s dataset must be rolled back to 2026-08-07. This will destroy any daily snapshots later than 2026-08-07.
This is why you should use a single replication task that is aware of all snapshot tasks or naming schemas, so it can handle it sequentially and properly.
The problem you have is that you won’t be able to set custom expirations for the different types of snapshots (daily, weekly, monthly). That’s why there was a feature request for this.
EDIT: If it helps, think of your snapshots as having sequential numbering. Whenever a snapshot is created, it doesn’t matter what “name” you give it. Pretend in the background it has a number.
#500 is named @auto-daily-2026-08-14
#501 is named @auto-weekly-2026-08-15
#502 is named @auto-daily-2026-08-16
If one replication task sends snapshot #502, how would a different replication task send snapshot #501 if it happens to run after the other task? It would need to rollback to #501 on the target. This is inefficient.
When you combine your intended replications into a single task, TrueNAS (zettarepl) will curate a list, based on the naming schema or selected snapshot tasks, and send them in sequential order, one after the other, incrementally. You will lose out on custom retentions for each type of snapshot.