From: Anthony Sorace <a@9srv.net>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Venti backups from unix
Date: Sat, 14 Dec 2024 11:37:27 -0800 [thread overview]
Message-ID: <AF21168D-47A9-4B59-819A-A13DCB939191@9srv.net> (raw)
I use vac in Plan 9 Ports to back up a bunch of Unix hosts to a Plan 9 venti. I've talked about this several times, including on here at least once or twice, but someone asked me again a day or two ago and I realized I didn't have anything convenient to point to. So I did a lab report:
http://a.9srv.net/reports/vac-unix.pdf
(also .html or .ms if you prefer!)
There's nothing particularly novel in there, but an example in practice is often helpful. I've been using some variation on this since... 2009 (!!!) and it's been very useful.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5f59d7df5796d0cc-Mceaa0e3e5cffdbde60610dfb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2024-12-14 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 19:37 Anthony Sorace [this message]
2024-12-17 16:53 ` [9fans] " wb.kloke
2024-12-17 19:57 ` Alexander Schreiber
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=AF21168D-47A9-4B59-819A-A13DCB939191@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).