capital

I have backed up and restored several TB of data using restic. It’s been great in my experience.

I’ve mostly used it to back up to Wasabi but if I was setting it up now, I’d take a good look at CloudFlare R2.

If you’ve already got a host, you might implement the rest server.

I just farted

lol

Okay 2 things.

1. I haven’t heard about any security issues with Rustdesk. Can you link to what you’re referring to?
2. It’s strange to see someone concerned about security recommend RDP for remote access when it’s a terrible idea to expose it to the internet. But maybe you mean to expose a VPN and then connect to RDP via that?

Edit: I see you have some info on the Rustdesk point elsewhere in the thread. I’ll read up on that part so don’t feel like you have to repeat yourself here.

No rustdesk but recommend RDP for remoting?

I’m confused on both recommendations.

That’ll work a few times

Won’t last long unless the votes actually come in.

Yeah that was fun times.

Luckily, thanks to using docker, it was easy enough to “pin” a working version in the compose file while I figured out what just broke.

For everyone’s reference, here’s my fstab to give you an idea of what works with linuxserver.io’s qbittorrent

## Media disks setup for mergerfs and snapraid

# Map cache to 1TB SSD
/dev/disk/by-id/ata-Samsung_SSD_860_EVO_1TB_S3Z8NB0K820469N-part1 /mnt/ssd1 xfs defaults 0 0

# Map storage and parity. All spinning disks.
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK39X4N-part1 /mnt/par1         xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK3TY5N-part1 /mnt/disk01       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK4806N-part1 /mnt/disk02       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK4H0RN-part1 /mnt/disk03       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT0TS-part1 /mnt/disk04 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT1YS-part1 /mnt/disk05 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT3EK-part1 /mnt/disk06 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N6CKJJ6P-part1 /mnt/disk07 xfs defaults 0 0

# Setup mergerfs backing pool
/mnt/disk* /mnt/stor fuse.mergerfs defaults,nonempty,allow_other,use_ino,inodecalc=path-hash,cache.files=off,moveonenospc=true,dropcacheonclose=true,link_cow=true,minfreespace=1000G,category.create=pfrd,fsname=mergerfs 0 0

# Setup mgergerfs caching pool
/mnt/ssd1:/mnt/disk* /mnt/cstor fuse.mergerfs defaults,nonempty,allow_other,use_ino,inodecalc=path-hash,cache.files=partial,moveonenospc=ff,dropcacheonclose=true,minfreespace=10G,category.create=ff,fsname=cachemergerfs 0 0

I do this with mergerfs.

I then periodically use their prewritten scripts to move things off the cache and to the backing drives.

I should say it’s not really caching but effectively works to take care of this issue. Bonus since all that storage isn’t just used for cache but also long term storage. For me, that’s a better value proposition.

Unless you’re the type to microwave your phone to charge it on 4chan’s recommendation, I think you’re probably fine.

Transfer charges are not restore charges - which are required when bringing files out of glacier.

Something to keep in mind.

You use it once, it asks if you want to enable, and you click literally one button.

RGB bro

My use case is basically the same as yours.

I do restic to Wasabi.

I’ve been on restic for a few years now and have never had an issue. I started out using Google Drive for the backend but that was though my college which went away eventually so I swapped over to Wasabi but I’m considering B2.

It’s actively maintained and encrypted.

There are a handful of backends it supports but can be extended by writing to an rclone backend.

Bingo knows everyone’s name-o.

Killer’s my middle name.

I do the same but I just use a script that runs periodically to update CloudFlare with my current IP with their native API.

Ubuntu Server with docker/docker-compose on top.

So many guides for Ubuntu specifically makes reading up on something a lot easier and it works just fine.

Just set a rate limit? This could have been a code change and a blog post.

Agree.

Even simple things like subs for particular cars/car brands were thriving on Reddit but don’t exist here.

Could continue with the email analogy and call it “provider”?