ZFS dedup and replication
Zaphod Beeblebrox
zbeeble at gmail.com
Thu Dec 1 21:35:27 UTC 2011
On Thu, Dec 1, 2011 at 11:42 AM, krad <kraduk at gmail.com> wrote:
> On 1 December 2011 13:03, Peter Maloney
> <peter.maloney at brockmann-consult.de>wrote:
>
>> On 12/01/2011 11:20 AM, krad wrote:
>> On my system with 12 TiB used up, what I do in a script is basically:
>> -generate a snap name
>> -make a recursive snapshot
>> -ssh to the remote server and compare snapshots (find the latest common
>> snapshot, to find an incremental reference point)
>> -if a usable reference point exists, start the incremental send like
>> this (which wipes all changes on the remote system without confirmation):
>> zfs send -R -I ${destLastSnap} ${srcLastSnap} | ssh ${destHost}
>> zfs recv -d -F -v ${destPool}
>> -and if no usable reference point existed, then do a full send,
>> non-incremental:
>> zfs send -R ${srcLastSnap} | ssh ${destHost} zfs recv -F -v
>> ${destDataSet}
>> The part about finding the reference snapshot is the most complicated
>> part of my script, and missing from anything else I found online when I
>> was looking for a good solution. For example this script:
>> http://blogs.sun.com/clive/resource/zfs_repl.ksh
>> found on this page:
>> http://blogs.oracle.com/clive/entry/replication_using_zfs
Not that everyone doesn't enjoy inventing their own wheel, but would
you mind sharing your snapshot parser?
More information about the freebsd-fs
mailing list