public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Gabriele Bulfon <gbulfon@sonicle.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: zfs double replica
Date: Fri, 9 Aug 2024 16:36:14 +0200 (CEST)	[thread overview]
Message-ID: <1752433163.1594.1723214174653@www> (raw)
In-Reply-To: 


[-- Attachment #1.1: Type: text/plain, Size: 1005 bytes --]

Hi,
 
I have some production systems doing a daily sync replica on a dedicated storage backup system.
They're all organized into datasets of the main backup pool.
Sync is via ssh using "zfs send -R -i ... | ssh host " zfs receive -Fduv ...".
The destination machine is always aligned to the same snaps existing at the source, removing old ones when no more at the source.
Is there a way to change this behaviour and let the destsination sync to new snaps but keep older ones?
The aim is to have another process on the backup machine to do its own send to another backup machine, with its own timings, and this second process will take care of removing old snaps when they're no more needed.
Znapzend is not an option, because it's not a real replica tool for zone datasets as it is not replicating all properties.
 
Thanks,
G
 
 
Sonicle S.r.l. : http://www.sonicle.com
Music: http://www.gabrielebulfon.com
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
 


[-- Attachment #1.2: Type: text/html, Size: 2545 bytes --]

             reply	other threads:[~2024-08-09 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 14:36 Gabriele Bulfon [this message]
2024-08-09 18:45 ` [developer] " Michael Zeller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1752433163.1594.1723214174653@www \
    --to=gbulfon@sonicle.com \
    --cc=developer@lists.illumos.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).