overview for jakkos

Advice for tiny NAS to store backups? in c/selfhosted

[–] jakkos 1 points 1 year ago

If it absolutely has to be Linux (does it?)

It's just what I'm familiar with, what would you suggest?

Why SFTP? Wouldn’t SCP be enough?

SFTP seemed like the simplest thing that Restic supported

Automatic updates are risky for a device that is supposed to run always. Instead, I would recommend sending update notifications and then manually applying an update from time to time. If the device no longer boots up, you often don’t even notice it.

Risky from a perspective of it crashing? I think I'm okay with that as I would notice it erroring out when I try and push the backups

Advice for tiny NAS to store backups? in c/selfhosted

[–] jakkos 1 points 1 year ago (1 children)

If you’ve got a copy of the data that’s local, why are you opening up ports? Just run the backup job internally.

I'm often not at home for weeks at a time.

but man do I not trust a USB interface at all.

Trust?

I also recommend not relying on email for notifications - too unreliable. I use the healthchecks.io docker image and have it send me notifications via Pushover when something fails.

I'll look into this thanks!

13

Advice for tiny NAS to store backups? (self.selfhosted)

submitted 1 year ago by jakkos to c/selfhosted

7 comments fedilink

My backup game is pretty bad, I only have my primary copy of my data and a cloud storage copy. I was trying to think of a cheap way to have another backup, and then realized I have an Orange Pi Zero 2 and a 1TB USD SSD lying around. So I was thinking of:

installing Debian on the OPZ2, and setting up key-authenticated SFTP (no password auth)
connect the OPZ2 on my home network and expose a non-standard (e.g. not 22) port for SFTP
have a subdomain point to my home network ip, and use DDNS to keep it in sync
using Restic to remotely push password-encrypted backups to the OPZ2 via SFTP using the subdomain
set a cron job to check diskhealth and send myself email on bad
enable auto updates on debian and email on fail

Is this setup a bad idea? Is this a security nightmare? Any better suggestions?

112

Self hosting a Lemmy instance for just myself? (self.selfhosted)

submitted 1 year ago by jakkos to c/selfhosted

26 comments fedilink

Heya, I'm trying out Lemmy and kinda like the idea of hosting a Lemmy instance just for me.

I was wondering:

What are the hardware/bandwidth requirements for a single user instance?
I know different instances can black list each other, but can they whitelist each other too? I don't want to be automatically unable to see interact with certain instances.
Has anyone else done this and have thoughts to share?
What about doing the same for Mastodon?