I did have a look at it during the weekend. Nice tool and easy to use.
It did, for some reason, kept too many snapshots (my retention was 1min=>1min
on SRC and 1min=>1min,10min=>10min,1h=>1h on DST). What I got was 2 minute’s
snapshots, 2 10 minutes’s snapshots and 1 hourly snapshot on the DST.
Hey there,
how come I didn’t find this earlier:)
It does look good after initial testing. I like the option of saving datasets
and zvols to files instead of zvol on dst system. Better space usage.
Is it possible to run multiple instances of agents on one server? Currently I
can transfer up to
try www.znapzend.org
cheers
tobi
Tobias Oetiker
t...@oetiker.ch
062 775 9902
> On 21 Jan 2017, at 19:00, Richard Elling
> wrote:
>
>
>
>> On Jan 21, 2017, at 8:07 AM, Dale Ghent wrote:
>>
>> We developed Zetaback for this.
>
> +1 for zetaback. There are perhaps hundreds of implementation
> On Jan 21, 2017, at 8:07 AM, Dale Ghent wrote:
>
> We developed Zetaback for this.
+1 for zetaback. There are perhaps hundreds of implementations of this over the
years. I think you'll find that zetaback is one of the best designs.
-- richard
> As for how you exactly want your snapshots
We developed Zetaback for this. As for how you exactly want your snapshots to
be in number and how long they should stay around, you might be able to
configure a backup policy which covers that.
https://github.com/omniti-labs/zetaback
The documentation is perdoc within the zetaback script.
/da
Hello,
I would like to implement backup for one of my servers with zfs send/recv. My
scenario would be the following:
For each dataset:
- keep one daily snapshot on src server
- copy daily snapshot from src server to backup server
- on backup server, I would like to have one daily, one weekly an