[prev in list] [next in list] [prev in thread] [next in thread]
List: zfs-discuss
Subject: Re: [zfs-discuss] scripting incremental replication data streams
From: Karl Wagner <karl () mouse-hole ! com>
Date: 2012-09-19 8:35:19
Message-ID: 4c459dc40ca038748ce7a27a8f88cf00 () mouse-hole ! com
[Download RAW message or body]
Hi Edward,
My own personal view on this is that the simplest option is the best.
In your script, create a new snapshot using one of 2 names. Let's call
them SNAPSEND_A and SNAPSEND_B. You can decide which one by checking
which currently exists.
As manual setup, on the first run, create SNAPSEND_A and send it to
your target. This can, obviously, be done incrementally from your last
replication/last common snapshot.
Now in your script, you would:
* Check your source dataset for the existence of SNAPSEND_A and
SNAPSEND_B. Let's assume this is the first run after manual setup, so
SNAPSEND_A will exist.
* Create SNAPSEND_B. Replicate this over to your receiving dataset.
* Remove SNAPSEND_A on both sides. This will leave all intermediate
snapshots.
Next run, it will create SNAPSEND_A again, and remove B when finished.
Hope this helps.
Karl
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic