On 2013-07-04 10:50, Jonathan Adams wrote:
I'm assuming that the zone on the originator computer is not ZFS, and that
is why you are using tar.
root@salmon190-90:~# zfs list -r /zones
NAME USED AVAIL REFER MOUNTPOINT
rpool1/export/zones 7.84G 207G 35K /zones
rpool1/export/zones/cupszone 1.20G 207G 33K
/zones/cupszone
rpool1/export/zones/cupszone/ROOT 1.20G 207G 31K legacy
rpool1/export/zones/cupszone/ROOT/zbe 2.96M 207G 717M legacy
rpool1/export/zones/cupszone/ROOT/zbe-1 1.20G 207G 1.01G legacy
Adding to Jonathan's answer, I'd underline that in OI each zone's
root storage is a separate dataset heirarchy - which was recommended,
at least to have one dataset for the zone, but not enforced in other
OSes (Solaris 10, SXCE). Here the current roots (matching the GZ BE
related to package updates) are legacy-mounted into the zoneroot,
i.e. /export/zones/cupszone/root.
So to untar your zone's backup, you have to recreate a similar
structure, including a number of ZFS dataset attributes. Or make
a recursive zfs-send stream and transfer that.
HTH,
//Jim
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
