On Sat, Jun 20, 2009 at 9:18 AM, Dave Ringkorno-re...@opensolaris.org wrote:
What would be wrong with this:
1) Create a recursive snapshot of the root pool on homer.
2) zfs send this snapshot to a file on some NFS server.
3) Boot my 220R (same architecture as the E450) into single user mode
Cindy, my question is about what system specific info is maintained that
would need to be changed? To take my example, my E450, homer, has disks that
are failing and it's a big clunky server anyway, and management wants to
decommission it. But we have an old 220R racked up doing nothing, and
The device tree for your 250 might be different, so you may need to
hack the path_to_inst and /devices and /dev to make it boot sucessfully.
On Jun 20, 2009, at 10:18 AM, Dave Ringkor no-re...@opensolaris.org
wrote:
Cindy, my question is about what system specific info is
maintained
On Thu, Jun 18, 2009 at 10:56 AM, Dave Ringkorno-re...@opensolaris.org wrote:
But what if I used zfs send to save a recursive snapshot of my root pool on
the old server, booted my new server (with the same architecture) from the
DVD in single user mode and created a ZFS pool on its local
Hi Dave,
Until the ZFS/flash support integrates into an upcoming Solaris 10
release, I don't think we have an easy way to clone a root pool/dataset
from one system to another system because system specific info is still
maintained.
Your manual solution sounds plausible but probably won't work
So I had an E450 running Solaris 8 with VxVM encapsulated root disk. I
upgraded it to Solaris 10 ZFS root using this method:
- Unencapsulate the root disk
- Remove VxVM components from the second disk
- Live Upgrade from 8 to 10 on the now-unused second disk
- Boot to the new Solaris 10 install
