On 04/ 6/11 11:42 AM, Paul Kraus wrote:
On Wed, Apr 6, 2011 at 1:14 PM, Brandon High<bh...@freaks.com> wrote:
The only thing to watch out for is to make sure that the receiving datasets
aren't a higher version that the zfs version that you'll be using on the
replacement server. Because you can't downgrade a dataset, using snv_151a
and planning to send to Nexenta as a final step will trip you up unless you
explicitly create them with a lower version.
I thought I saw that with zpool 10 (or was it 15) the zfs send
format had been committed and you *could* send/recv between different
version of zpool/zfs. From Solaris 10U9 with zpool 22 manpage for zfs:
The format of the stream is committed. You will be able
to receive your streams on future versions of ZFS.
correct.
-or- does this just mean upward compatibility ? In other words I can
send from pool 15 to pool 22 but not the other way around.
It does mean upward compatibility only, but I believe that it's the
dataset version that matters, not the pool version, and the dataset
version has not changed as often as the pool version:
root@v40z-brm-02:/home/lalt/ztest# zfs get version rpool/export/home
NAME PROPERTY VALUE SOURCE
rpool/export/home version 5 -
root@v40z-brm-02:/home/lalt/ztest# zpool get version rpool
NAME PROPERTY VALUE SOURCE
rpool version 32 default
(someone still on the zfs team please correct me if that's wrong.)
Lori
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
