I’m having trouble getting replication running from my primary truenas to my backup truenas. My primary is on electric eel and the backup is on fang tooth rc.
On both machines my pool is named zvol. zvol on the backup is completely empty, no datasets and no data. I’ve setup the replication task to push all snapshots to zvol on the backup. When I try to run the replication task on my primary machine to push, I get this error:
[EFAULT] Active side: cannot unmount ‘/mnt/zvol’: pool or dataset is busy.
I thought replication pushed snapshots, why does it have to unmount my pool?
John
Hi John,
Are you replicating to the root dataset of your backup system? May I suggest you create a least one other dataset called whatever and try replicating into there.
PS: It doesn’t matter how this dataset is configured it’s just a holding point. I call them stub datasets. When replicating I like to point my primary system at this stub dataset and then in the replication window enter /nameofzol. This will then create a tree that looks like zvol/whatever/nameofzvol.
Thanks, I’ve done that creating a zvol/backups dataset on my backup truenas and the replication is running. zvol/backups isn’t currently mounted on the backup machine. Is this because the replication is currently running? If so, I presume that the error I got earlier was because zfs send was trying to unmount my root dataset? Just trying to understand this and thanks for your help!
Yes this won’t look right until replication has completed. I think you’ll be good now.
Indeed, it’s best to avoid the root dataset as the system uses this for other things.
1 Like
