complete clone/restore from a ZFS-based system replication stream

[Dean E. Weimer]

On 2016-09-27 10:53 am, Mike Tancsa wrote:
> On 9/27/2016 4:53 AM, Victor Sudakov wrote:
>> 
>> 1. When you boot from this pool later on a restored system, don't the
>> "-o altroot=/mnt2 -O canmount=off" options prevent it from
>> working normally? I gather that "altroot" is not persistent across
>> reboots, but "canmount" probably is.
> 
> Its been a while, but when you do the zfs recv, I am guessing the
> properties are restored with it ?
> 
>> 
>> 2. If you wanted to check "zfs recv" without actually restoring it,
>> what what you do? I keep getting the "cannot receive incremental 
>> stream" error:
> 
> Not sure. When you did this, perhaps you are restoring from an
> incremental send as opposed to a full send ?
> 
> eg
> 
> zfs snapshot -r zroot at backup
> zfs send -R zroot at backup > 
> /nfs-mount-on-backup-server/zroot-full-snap.zfs
> 
> 
> 
> 	---Mike

I believe you should be using a -p on the zfs send comand to have it 
send properties, otherwise you need to first create the dataset with the 
properties and use zfs receive -F to restore the dataset over the 
existing dataset which will then inherit those properties.

-- 
Thanks,
    Dean E. Weimer
    http://www.dweimer.net/