On 07/24/10 09:47 AM, Bill Sommerfeld wrote:
On 07/23/10 14:23, Ian Collins wrote:
I guess that's with an older or same ZFS version not newer in order to
be able to zfs send the filesystem. It could work for recent Solaris 10
updates as well, assuming there's another update with a zfs upgrade.
When I did this I migrated systems from nevada build 130 to
opensolaris build 130 so this wasn't a consideration.
I'm just downloading the b117 CD dorm genunix to try this with my b117
SXCE system.
The following is somewhat speculative (I haven't needed to migrate
from s10 to opensolaris):
Being the weekend, I'm going to see how far I get with a Solaris 10
update 8 system. One thing that can be done with a Solaris host and not
a nevada one is to create a FLAR of the box and import it as a branded
zone on it's new self. That would make post-upgrade configuration
porting easier (I'm bound to forget something!). It will also provide a
home for application that don't support OpenSolaris.
- remember that there are separate pool versions and filesystem
versions.
- You can, in general, zfs send a filesystem to a lower-revision
pool; the filesystem version is what matters for zfs send.
- You can create down-rev pools and filesystems using appropriate
options to the zpool create and zfs create commands.
That's right, but I don't think you can specify the zfs or zpool version
to the installer (an RFE maybe?) so the root pool will always be the
latest version.
--
Ian.
_______________________________________________
opensolaris-discuss mailing list
[email protected]
