From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: [9front] cfs, aan and network recommendations
Date: Mon, 15 Nov 2021 22:39:53 +0000 (UTC) [thread overview]
Message-ID: <ed7e4ca5-3c15-4f8b-a0ec-56e9760fdefc@sirjofri.de> (raw)
Hello all,
(I tried sending this mail earlier, but it seems it never reached the
mailing list.)
due to a full worm on my cwfs I'm rethinking my network setup.
Currently I have one VPS with limited storage (usually not much, the one
that's almost full). I also have a larger/more powerful computer at home
with a standard German internet connection, so the IP address can change
every day and the connection is not always up.
At the moment both machines are full file servers. The VPS (oat) is also
mail server, http server, as well as auth and secstore. The other machine
(leaf) is basically just cpu+fs, I had most of my data there.
Since I moved to another apartment and I had internet connection issues I
wasn't able to put leaf online, and I also only seem to have IPv6 here
(from outside), so I was never really able to connect to leaf from
outside. However, I believe it's possible.
My current thoughts were, I could try to make leaf my only cpu+fs for
working and configuration etc, and have oat start with leaf as a
fileserver. Since the connection is likely not reliable and potentially
slow I thought about combining cfs with aan.
Did anyone try something like that? How reliable is aan? I know it
handles short interruptions reasonably well (e.g. switching between LTE
and WiFi), but what if something more happens? How could I handle
potential rebooting (do I need to reboot oat each time I reboot leaf
then)?
I was also thinking about just removing leaf from my network and only
rely on VPS. They are always available and hardware managed, as well as
cheap enough. I'd then just like to have a good/solid filesystem setup
(cwfs vs hjfs, or potentially even fossil?). Do you have good
recommendations?
Ideally I want a dump every day for the last X months, and then free
older stuff (as in, I care about the data, but not the history). Maybe
that's a use case for classical backups (daily, weekly, monthly, ...) and
not so much for a dumping filesystem. Do you have any ideas and
recommendations?
sirjofri
next reply other threads:[~2021-11-15 23:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 22:39 sirjofri [this message]
2021-11-16 4:12 ` Xiao-Yong Jin
2021-11-16 18:18 ` Noam Preil
2021-11-16 19:04 ` Steve Simon
2021-11-17 1:51 ` hiro
2021-11-17 7:31 ` sirjofri
2021-11-17 9:45 ` hiro
2021-11-17 10:31 ` sirjofri
2021-11-17 15:31 ` hiro
2021-11-18 22:05 ` Steve Simon
2021-11-18 23:21 ` hiro
2021-11-17 21:35 ` sirjofri
2021-11-17 22:12 ` hiro
2021-11-17 22:52 ` Steve Simon
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=ed7e4ca5-3c15-4f8b-a0ec-56e9760fdefc@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.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).