From: "iank at fsf dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29644] Offsite backup/system
Date: Mon, 03 Oct 2022 04:18:58 +0000 [thread overview]
Message-ID: <bug-29644-14326-GJ3LMvDgXO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29644-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29644
--- Comment #1 from iank at fsf dot org ---
mark at klomp dot org via Overseers <overseers@sourceware.org> writes:
> https://sourceware.org/bugzilla/show_bug.cgi?id=29644
>
> Bug ID: 29644
> Summary: Offsite backup/system
> Product: sourceware
> Version: unspecified
> Status: NEW
> Severity: normal
> Priority: P2
> Component: Infrastructure
> Assignee: overseers at sourceware dot org
> Reporter: mark at klomp dot org
> Target Milestone: ---
>
> Sourceware currently has a life backup system (running in the same rack as the
> main machine) that could take over the main server if it goes down. But we
> don't have a full offsite backup system (even though most project data is
> mirrored in various places).
>
> We should make a plan and budget for having a full system backup offsite. How
> much data changes per hour/day which needs to be stored offsite. And write up
> procedures for how to (re)create a life system from that in case of emergency.
At the FSF, we do nightly backups to a physical machine we run with all
free software including the bios, and monthly backups to tape that are
manually stored offline in a separate location for disaster recovery. I
bet we have plenty of storage room to backup sourcware's data too (how
much are we talking?). I presume it would make sense to allow the
sourceware servers to write and read backups, but not delete them
without a human being involved.
Note: I think the right term is "live system" instead of "life system".
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-10-03 4:18 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 ` iank at fsf dot org [this message]
2022-10-03 16:37 ` [Bug Infrastructure/29644] " fche at redhat dot com
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-GJ3LMvDgXO@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).