On Thu, Jul 8, 2010 at 2:21 PM, Edward Ned Harvey <solar...@nedharvey.com> wrote: > Can I "zfs send" from the fileserver to the backupserver and expect it to be > compressed and/or dedup'd upon receive? Does "zfs send" preserve the > properties of the originating filesystem? Will the "zfs receive" clobber or > ignore the compression / dedup options on the destination filesystem?
If you set a property on the dataset that you're sending, then it'll overwrite what's on the receiving end if you used 'zfs send -R' or 'zfs send -p'. You can get around this by sending only a snapshot without -R or -p, then using -I to get intermediate snapshots for every dataset. If the destination dataset has the property set on it, then it'll be overwritten if you used 'zfs send -R' or 'zfs send -p'. If the source inherited the property from a parent and the destination inherits the property, then it won't be overwritten. Personally, I've started organizing datasets in a hierarchy, setting the properties that I want for descendant datasets at a level where it will apply to everything that I want to get it. So if you have your source at tank/export/foo and your destination is tank2/export/foo, you'd want to set compression, etc at tank/export or tank2/export. If you're going to have a newer zfs version on the destination, be aware that you can't receive from datasets with a higher version than the destination. -B -- Brandon High : bh...@freaks.com
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
