On 04/ 6/11 07:14 PM, Brandon High wrote: > On Tue, Apr 5, 2011 at 12:38 PM, Joe Auty <j...@netmusician.org > <mailto:j...@netmusician.org>> wrote: > > How about getting a little more crazy... What if this entire > server temporarily hosting this data was a VM guest running ZFS? I > don't foresee this being a problem either, but with so > > > 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. Yes, that is exactly why one thinking about using something with more liberal license then Solaris11 with payed license, should first install latest OpenSolaris form snv_134 (Or 2009.06 then upgrade to /dev Opensolaris 134) and then it can choose upgrade path to Both openIndiana oi_148(b) and S11Ex on same zpool.
That way, zpool and zfs versions can stay on versions supported by OI and Nexenta (and Schillix and FreeBSD and ZFS-Fuse on Linux and Zfs Native on Linux in development) and one can experiment with more systems supporting ZFS then only being locked in S11Ex. If you sadly choose to install from closed S11Ex disc and not from Osol snv_134 CD (www.genunix.org snv_134 .ISO) and upgrade to OpenIndiana OI_xxx dev. release and/orS11ex, then you might loose ability to use anything but closed Solaris from Oracle, so be clever and you can use upgrade path explained. Of course, you can have as much Boot Environments (BE) on same zpool as you like, since they basically behave like separate OS installs to boot from the same zpool, that is the beauty of ZFS/(Open)Solaris based distributions. Just do NOT do upgrade to newest closed zpool/zfs version from S11Ex!
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
