ChojinDSL

Technology is complicated. Period. Anything that "seems" simple is in reality extremely complicated underneath the hood. A GUI is nice as long as it works. But if for some reason it doesn't, you're shit out of luck.

I hear ya.

I'm an old school linux sysadmin. Been at it since 2003. I always groan when some higher-up wants us to host stuff on AWS and kubernetes, because they have no idea how stuff works, they just like the buzzwords and how everybody else is doing it this way.

And I'm just thinking, great. Instead of renting a very affordable beefy server with Hetzner or OVH, we instead use AWS which costs us 3-5x as much for less performance. And I try to explain to them, that not every application is like Netflix where you can just throw more nodes at it in order to scale.

Docker I like, since it can make things easier, with regards to ensuring a consistent environment, once you know your way around it. But kubernetes and AWS I hate with a passion. With AWS I can never truly know how much it's gonna cost in advance, since their pricing structure is so mind boggingly complicated and you get billed even if so much as a fly farts in one of their server rooms.

Another thing is, every server provider that I've ever worked with, provides you with a means to boot a rescue mode if something goes wrong, so that you can fix it and reboot. No, with AWS, you need to make a snapshot, fire up another instance, attach that snapshot as a volume and mount it, then try and fix stuff, then shutdown that instance, detach that volume, then re-attach it using the same device name as the root device on your original instance. Oh, doesn't boot? Rinse/Repeat. This shit can take hours. Whereas with a "normal" root server and a IPMI console and a rescue boot, it's a question of minutes (usually).

Same with backups. I always ensure to create a backup system, so that I can restore certain files individually. Yeah, you can have automated snapshots of your EC2 Instance. But guess what, if something goes wrong, you boot the entire snapshot. So even if you just need to recover a single file, you still need to go through the process of reverting the entire system to a previous snapshot.

Bah, I could go on and on, but honestly the whole thing just seems to create more and more abstraction layers that just makes it difficult to figure stuff out when something doesn't work.

The only thing, that I can somewhat appreciate with AWS is the ease with which you can migrate to a more powerful instance if you need it. Or how quickly you can launch a new instance. But thats about it.

In previous companies, we would have a couple of beefy servers that would run multiple apps on a single server, with perhaps a failover server being at the ready. Our server Budget was maybe 1-2k € per month.

With AWS it's like 5x that.

I use qownnotes in combination with nextcloud.

Personally I'm fine with 30fps when a game is designed with that in mind.

Obviously, with really fast paced twitchy games, that's not really an option. But for something like this, I think it's fine.

The Game isn't even out yet. Apart from that, who knows how much wiggle room on performance there will be by adjusting the settings.

I mean who ever imagined that Cyberpunk 2077 would be payable on the deck?

But, let's see.

Ich sollte hier hinzufügen, es ist ne Weile her seitdem ich crashplan benutzt hatte. Es kann natürlich sein das es sich mittlerweile geändert hat. Aber was die voraussetzungen für einen Business account sind, kann ich da nicht sagen.

Wieviel Daten willst du denn backuppen?

P.S. Ich sollte hierbei noch erwähnen, falls du irgendwo einen günstigen Provider findest der dir nur s3 als protokoll anbietet. Dann kannst du "restic" verwenden, falls du an borg gewöhnt bist. Borg ist ein fork von Restic. Aber restic kann z.b. direkt zu s3 speichern, erlaubt mehrere clients gleichzeitig ins gleiche Repo zu speichern und unterstützt natürlich auch verschlüsselung, compression und deduplication so wie borg.

Ich hatte vor langer Zeit crashplan verwendet. Also erstens, ist der backupvorgang bei denen ziemlich lahm und von dem was ich von anderen Usern gehört hatte, ist die restore prozedur noch langsamer. Also gerade wenn man mehr als nur ein paar GB hin und her scheffeln will. Aber das ist halt alles sehr subjektiv.

Du musst dich halt fragen,

1. wie wichtig sind die daten dich backuppe?
2. Wie schnell muss der backup/recovery prozess passieren können und in welcher menge von daten?
3. Preis/Leistungs verhältnis.

Hängt halt alles etwas auch vom eigenen Technik wissen ab. Manche user erzählen immer von Amazon Glacier storage, weil da der preis zum speichern relativ günstig pro TB ist, allerdings ist der restore prozess teuer und dauert sehr lange.

Es gibt z.b. auch Backblaze die relativ gut sind. Ansonsten noch borgbase, sofern man borg als backup client verwendet. Vorteil ist halt, das die datenblöcke auch innerhalb eines backups dedupliziert werden, so dass borg backup ein der am speichereffizientesten lösungen ist.

Es gibt dann z.b. auch noch bei Hetzner.d die storagebox. Das ist ein backup speicher in verschiedenen größen, wo z.b. borg, rsync, sftp und so weiter machbar sind, mit snapshots.

Wer das nötige know-how hat, für den lohnt es sich vielleicht sich sogar einen Server zu mieten über die Hetzner Server Börse.

Da sind manchmal konfiguration dabei für "relativ" günstiges Geld mit ziemlich viel speicherplatz.

Aber wie gesagt, das hängt alles ab von deinem Use Case.

Mailcow definitely makes it very easy. Their official docs pretty much walk you through every step and tell you which DNS entries you need.

Bonus with mailcow is, that you basically get a self-hosted equivalent of an Exchange server. So, contacts+calender and so on. Plus some really good antispam features.

Westerners in this case refers to Americans.

Fruit loops.

I've been hosting my own mail server, ever since I got into Linux. Most companies where I worked before, used self hosted email.

I've since migrated to using mailcow, which takes a lot of the headache out of it.

When you first start, it's a bit daunting. But easily manageble, once you've gained some experience.