I have just upgraded my system from Core to Scale.
With Core, I used a replication task to copy the snapshots from my main pool to a local backup pool on a single disk that was exported each week and replaced with another. All of the backup disks hosted a single pool called “Backup”, and I could import the next disk - giving me a “Backup” pool that the replication task would happily use.
However, after upgrading to Scale, the replication task is deleted when I export the “Backup” pool. During export I get told that the replication service will be disrupted if the pool is detached (which makes sense).
Is it possible to stop a replication task from being deleted when the destination is exported?
Chris