SwisherSweet
Contributor
- Joined
- May 13, 2017
- Messages
- 139
Hi,
I have created a zvol, which is connected via iSCSI from a Mac. I setup auto-snapshots and a local replication task to a external backup drive. I have done the same procedure on a regular dataset and I received no errors. The data (non zvol replication) appears intact.
However, when I created the zvol replication, it appeared to kick-off and replicate to the backup drive. I thought nothing of it. Later, checking my email I received this email:
Browsing the volumes in the web gui, it appears the backup used space (602.3GiB) is very close to the source dataset size (602.1GiB). I have daily snapshots setup on the zvol, and here is my replication config:
A little more setup information:
My questions are:
Thank you.
I have created a zvol, which is connected via iSCSI from a Mac. I setup auto-snapshots and a local replication task to a external backup drive. I have done the same procedure on a regular dataset and I received no errors. The data (non zvol replication) appears intact.
However, when I created the zvol replication, it appeared to kick-off and replicate to the backup drive. I thought nothing of it. Later, checking my email I received this email:
Hello,
The replication failed for the local ZFS primary/mac-data while attempting to
send snapshot auto-20170614.1558-1y to localhost
Browsing the volumes in the web gui, it appears the backup used space (602.3GiB) is very close to the source dataset size (602.1GiB). I have daily snapshots setup on the zvol, and here is my replication config:
A little more setup information:
- Mac Pro, 2 x 6 Core 3.46Hz Xeons, 64gb ECC RAM
- FreeNAS-9.10.2-U3 (e1497f269)
- 7 x 3TB Toshiba drives in "primary" data pool in raidz2
- 5 x 2TB Seagate drives in "backup1" backup pool (externally attached) in raidz1
My questions are:
- I assume one can replicate a zvol just like a regular dataset. Is my assumption correct?
- Is there any way to tell that the replication did in-fact fail or succeed? My research suggested others have received similar errors but all data transferred fine.
- How can I determine what caused this error and troubleshoot it to ensure a reliable replication is consistently executing?
Thank you.
Last edited: