[indiana-discuss] replicating snapshots from time-slider to a remote server

[Tom Georgoulias]

Nicolas Williams wrote:
> On Thu, Jan 08, 2009 at 04:04:55PM -0500, Tom Georgoulias wrote:
>> Renames *were* hard--I never got that working so I gave up.  I was 
>> encouraged to see your suggestion of a user-defined properties, I was 
>> trying to use them to get around the renaming problem and wasn't sure if 
>> that was too much of a brute force approach.
> 
> Thinking about it, user-defined properties are probably the right place
> to store backup status (i.e., whether this snapshot was backed up, when
> was the last time this dataset was backed up, ...).
> 
> Might as well add a snapshot ID (monotonically increasing is fine, UUID
> is better), and use that for rename detection.
> 
> Deletion of the last backed up snapshot should be discouraged, since
> recovering from that requires a bigger zfs send to the backup pool.

This is the script I put together as a proof of concept.  It has some 
hard coded bits in there, assumes a few things, and doesn't really run 
except at steady state, but it does seem to work OK.  You have to do the 
first snapshot sends to the remote server and setup ssh key trust 
between the two before this will run on its own.

I dunno what else to say, just thought I'd share it in case someone else 
wanted to see what I was testing.

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: indiana-list-archive-replication.sh
Type: application/x-sh
Size: 1516 bytes
Desc: not available
URL: <http://mail.opensolaris.org/pipermail/indiana-discuss/attachments/20090112/eb2de2ff/attachment.sh>