From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29644] Offsite backup/system
Date: Thu, 06 Oct 2022 17:40:45 +0000 [thread overview]
Message-ID: <bug-29644-14326-f25toCxcIP@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 #3 from Mark Wielaard <mark at klomp dot org> ---
Another option (or maybe a second backup) might be the OSUOSL Backups service
https://osuosl.org/services/hosting/details/#backups
Backups
This service is to be used for disaster recovery rather than data recovery,
meaning we keep backups for a limited period of time (usually long enough to
provide a couple of full data sets that can be used to rebuild a server as
opposed to recovering files from long ago). We currently utilize rdiff-backup
for file storage backups and a variety of other tools for database backups.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-10-06 17:40 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
2022-10-06 17:40 ` mark at klomp dot org [this message]
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-f25toCxcIP@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).