> Starfox wrote:
> > 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 PROTECTED]
>
Okay, that makes a lot more sense now.
> I'd say either (a) have your script check to see if
> the send|recv was
> successful, or (b) have it check what snapshots are
> available at the other
> side, and start sending incrementals from there. Eg:
>
> $lastsnap = ssh remote zfs list -o name $fs | tail -1
> | cut '@' ...
> do {
> zfs snapshot [EMAIL PROTECTED]
> zfs send -i $lastsnap [EMAIL PROTECTED] | ssh remote zfs
> s recv -d pool/recvd
> } while (no errors)
>
None of the scripts that I looked at seemed to offered any sort of error
recovery. I think I'll be able to use this as a starting point (and maybe the
man pages can be updated to include that you can use any common snapshot to
send -i - that fact is not obvious to those who are unfamiliar with the
capabilities of ZFS).
> > Another question is if I wanted to send a snapshot
> as a snapshot, I can
> > do: zfs snapshot master/[EMAIL PROTECTED] zfs send
> master/[EMAIL PROTECTED] | ssh
> > mirror zfs recv backup/[EMAIL PROTECTED]
> >
> Yes. But this will create a new filesystem
> backup/mirrorfs on the receiving
> side. I'm not sure I understand your goal -- zfs
> send always sends a
> snapshot, whether incremental or full.
>
I guess I'll have to play around with when I get the systems up and running.
But my request to allow two zfs boxes to sync "a" filesystem still stands.
-- Starfox
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
