Best practice for high availability ZFS pool

[Bob Friesenhahn]

On Tue, 17 May 2016, Ben RUBSON wrote:
>>
>> Without completely isolated systems there is always the risk of total failure.  Even with zfs send there is the risk of total failure if the sent data results in corruption on the receiving side.
>
> In this case rollback one of the previous snapshots on the receiving side ?
> Did you mean the sent data can totally brake the receiving pool making it unusable / unable to import ? Did we already see this ?

There is at least one case of zfs send propagating a problem into the 
receiving pool. I don't know if it broke the pool.  Corrupt data may 
be sent from one pool to another if it passes checksums.  With any 
solution, there is the possibility of software bugs.

Adding more parallel hardware decreases the chance of data loss but it 
increases the chance of hardware failure.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/