public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29644] Offsite backup/system
Date: Mon, 03 Oct 2022 16:37:13 +0000	[thread overview]
Message-ID: <bug-29644-14326-NPb1AhlHDK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29644-14326@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29644

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fche at redhat dot com

--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
Due to an rsyncd setup in effect on sourceware, it is possible to read-only
rsync the entire corpus of sourceware data to an off-site backup volume.  In
fact I have such a thing going as we speak, and <2TB of live data updates
within an hour or so.  (It's comforting that the system does not store
confidential data, so user privacy is not seriously at risk.)

I'll experiment with a local VM restore and report & write up a SOP on the
sourceware-wiki, at which point I think we're done.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-10-03 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 21:39 [Bug Infrastructure/29644] New: " mark at klomp dot org
2022-10-03  4:10 ` Ian Kelling
2022-10-03  4:18 ` [Bug Infrastructure/29644] " iank at fsf dot org
2022-10-03 16:37 ` fche at redhat dot com [this message]
2022-10-06 17:40 ` mark at klomp dot org

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=bug-29644-14326-NPb1AhlHDK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).