Re: zfs replication tool

On Fri, Sep 23, 2022 at 10:03:09AM +0200, Julien Cigar wrote:
> On Tue, Sep 20, 2022 at 10:15:13AM -0400, mike tancsa wrote:
> > On 9/20/2022 10:10 AM, Julien Cigar wrote:
> > > In our case, for our bare metal restoration, we have a separate config
> > > file
> > > > to do restorations per server/vm where there are "special cases". Thankfully
> > > > there are not many and its all scriptable for restoration.
> > > > 
> > > > For the A --> B -->C when we do are offload from B to C, we pick the
> > > > snapshots we want to send, place a hold on that snapshot and then do the
> > > > send (1.5 day process). Zrepl cries that it cant prune the snapshot. Once
> > > > the B-C process is complete, we remove the holds and zrepl happily deletes
> > > > the snapshots it thinks its supposed to delete.
> > > I see, is it necessary to place holds manually? I thought zrepl already
> > > does this by default
> > 
> > zrepl does indeed manages its own holds/releases. But without my holds that
> > I place, I run the risk of having the snapshot pruned out from underneath me
> > since the process of replicating to temporarily attached storage (C) takes
> > longer than a day.
> 
> I'm still getting replication errors with zrepl on my test installation, 
> see https://github.com/zrepl/zrepl/issues/631 for details. The initial
> transfer works, but after that I'm getting weird "cannot receive
> incremental stream: destination ..." messages, despite all snapshots
> have been well preserved on both side

See https://github.com/zrepl/zrepl/issues/631#issuecomment-1255899616 

> 
> > 
> >     ---Mike
> > 
> > 
> > 
> 
> -- 
> Julien Cigar
> PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
> 
> No trees were killed in the creation of this message.
> However, many electrons were terribly inconvenienced.



-- 
Julien Cigar
PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0

No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.