David E
Contributor
- Joined
- Nov 1, 2013
- Messages
- 119
Hi All-
I have one zvol that contains a single child dataset. Recursive snapshots are configured on the zvol at multiple intervals. I have a second FreeNAS machine that is the target for a replication script set to recursively replicate all day. So far the snapshots of the zvol have been consistently kept up to date, but frequently the snapshots of the child dataset get stuck and stop replicating, and they contain the bulk of the data (what small amount it currently is) that is changing. I can manually 'catch them up', by issuing:
zfs send -R -I parent/child@auto-20140123.0943-2d parent/child@auto-20140123.1143-2d | ssh -p 50501 -i /data/ssh/replication backup1 zfs receive -F -d parent
With the proper stuck and current snapshot names... but I'm not sure why I should need to be doing this. Looking at /var/log/messages (which shows no errors btw), it looks like this stems from the replication task sending only incremental snapshots of the zvol, which in theory should contain the child dataset snapshots, but are somehow occasionally missing/falling behind, then are permanently stuck.
Any thoughts or ideas? I can write my own cron job to resolve this manually, but I'd prefer to fix the root of the system problem if possible.
I have one zvol that contains a single child dataset. Recursive snapshots are configured on the zvol at multiple intervals. I have a second FreeNAS machine that is the target for a replication script set to recursively replicate all day. So far the snapshots of the zvol have been consistently kept up to date, but frequently the snapshots of the child dataset get stuck and stop replicating, and they contain the bulk of the data (what small amount it currently is) that is changing. I can manually 'catch them up', by issuing:
zfs send -R -I parent/child@auto-20140123.0943-2d parent/child@auto-20140123.1143-2d | ssh -p 50501 -i /data/ssh/replication backup1 zfs receive -F -d parent
With the proper stuck and current snapshot names... but I'm not sure why I should need to be doing this. Looking at /var/log/messages (which shows no errors btw), it looks like this stems from the replication task sending only incremental snapshots of the zvol, which in theory should contain the child dataset snapshots, but are somehow occasionally missing/falling behind, then are permanently stuck.
Any thoughts or ideas? I can write my own cron job to resolve this manually, but I'd prefer to fix the root of the system problem if possible.