Starfox wrote:
First time around, create a snapshot and send it to remote: zfs snapshot
master/[EMAIL PROTECTED] zfs send master/[EMAIL PROTECTED] | ssh mirror zfs recv
backup/mirrorfs
Once that's done, [EMAIL PROTECTED], correct?
More accurately, master/[EMAIL PROTECTED] == backup/[EMAIL PROT
Starfox wrote:
I don't need fail-over or anything. All I want is for what I consider important (ie,
Documents, settings, etc.) off a portion of a pool to be replicated onto another machine,
so if a catastrophic failure happens where I lose both mirrors due to PS frying or ZFS
bit-rotting an i
Yes, I've read through tons of blogs.sun.com/* entries, went through the
mailing list looking for the proper way to do it, etc. Unfortunately, zfs
send/recv remains a hack that requires an elaborate script wrapper precisely
because zfs send/recv is by nature a send-only/recv-only operation (whi
Oddly I posted a script that does what you want all be ti without sending it to
a remote system on friday to my blog
(http://blogs.sun.com/chrisg/entry/rolling_incremental_backups) which i use to
backup my system to an external USB drive.
--chris
This message posted from opensolaris.org
___
I'm curious as well. I'm trying to set up a near-line backup using two
ZFS-based machines, and am a bit confused on how to set it up properly.
First time around, create a snapshot and send it to remote:
zfs snapshot master/[EMAIL PROTECTED]
zfs send master/[EMAIL PROTECTED] | ssh mirror zfs recv
