Doing the entire zones pool is probably superfluous. Really, the only important 
data is the contents of /opt/custom, /usbkey/config and the individual zone 
datasets (including origin images). Copying the entire zones zpool will 
duplicate things like /var, which will have duplicate mount points off of / and 
cause conflicts when the pool imports.

Brian Bennett
Systems Engineer, Cloud Operations
Joyent, Inc. | <>

> On Feb 12, 2018, at 6:16 AM, Gareth Howell <> wrote:
> Further to previous posts on upgrading my two home servers, I seem to have 
> hit an intractable problem on the main server and now need to restore it from 
> the backup server. I use ZnapZend to send `zones` and all descendents to the 
> other server so I have a good replica of the main server on the backup.
> I’ve cloned the backup server’s `zones` hierarchy on to an eSATA disk and 
> connected it to the main server as `zznew`; which now has a virgin `zones` 
> pool after a reinstall of SmartOS.
> I’m guessing there needs to be some combination of -e or -f in the `zfs send 
> -R zznew/backup/deneb/zones | zfs recv` command and that this needs to be run 
> with the server in recovery mode and with both pools on alternate mountpoints 
> with no datasets mounted.
> Any clues: the `zfs` manual is a bit light on the -e and -f options to the 
> `recv` sub-command.
> Gareth

Attachment: smime.p7s
Description: S/MIME cryptographic signature

RSS Feed:
Modify Your Subscription:
Powered by Listbox:

Reply via email to