Re: zfs replication tool
- Reply: mike tancsa : "Re: zfs replication tool"
- In reply to: mike tancsa : "Re: zfs replication tool"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 20 Sep 2022 14:10:06 UTC
On Tue, Sep 20, 2022 at 09:39:37AM -0400, mike tancsa wrote: > > On 9/20/2022 9:23 AM, Steve O'Hara-Smith wrote: > > On Tue, 20 Sep 2022 14:51:54 +0200 > > Julien Cigar <julien@perdition.city> wrote: > > > > > as of 0.5.0 it is possible to transfer properties I think > > Ooh time to RTFM again :) > > Its kind of a messy problem (properties) and has lots of foot shooting > possibilities. > > https://zrepl.github.io/configuration/sendrecvoptions.html?highlight=properties#job-note-property-replication I agree, fortunately we have zfs delegations and jailed zfs datasets which (could) help to mitigate some of those devastating consequences > > 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 > > ---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.