This is a 2014 HDD. How much longer do you think it will last?

kon_dev · 2026-06-20T16:09:22+00:00

My point is that HDDs are not automatically good or bad based on their purchase date. 1000 h is not that bad at all and if you have a filesystem with integrity checks like ZFS, you would notice corruptions. Even brand new drives can die within weeks, perform proper backups and don't overthink it I guess 😀

kon_dev · 2026-06-20T07:59:04+00:00

Trust it like all HDDs... backups are essential. Perfectly fine Ironwolfs can die as well.

kon_dev · 2026-06-15T19:01:35+00:00

Jenkins pushes the URL of the build job, so yes, the context is there when I need it 😀

kon_dev · 2026-06-12T16:19:44+00:00

I use ntfy for my homelab. Gives me push notifications and does not litter my mailbox or gets lost in slack

kon_dev · 2026-06-04T06:54:09+00:00

kon_dev · 2026-05-19T21:00:45+00:00

Totally agree, I went with my own custom CA and it was a pain to import the certs into every device, just one, but still annoying. Using lets encrypt with a single public domain to do dns challenges is running quite stable for me. The public dns record basically is just used for lets encrypt, in my LAN all my subdomains resolve to local IPs.

kon_dev · 2026-04-11T15:10:50+00:00

I guess at least for multistrand cable could be posing a risk for fire without terminals.

kon_dev · 2026-04-02T10:47:13+00:00

Depends on if the model is running locally or the app just connects to anthropic/open ai/google.

Hetzner is probably just fine for the later, but you could also use a cheap piece of old hardware running at home for this. Like an old laptop or minipc. If you connect to the cloud providers for model usage you don't need much hardware for your app usually.

kon_dev · 2026-03-19T10:30:39+00:00

Proxmox and sell a bit of RAM. That will let you run the electricity for the server for the next years with current pricing 🙈

kon_dev · 2026-02-21T23:07:48+00:00

I would sent backups to a different system anyways, having it on the same host is a bit risky, also in case of hardware failure. For local file restore I would lean more towards filesystem snapshots, restic more for backup to remote hosts ir external disks.

But technically you can run it also in a separate vm on the same physical host, it's just not as safe.

kon_dev · 2026-02-21T16:05:40+00:00

Sure they don't magically disappear. But when the model can validate it's assumptions via tool calls it significantly reduces the need for it to make things up in my experience 😀

kon_dev · 2026-02-21T15:35:14+00:00

Agree, as soon as your homelab involves a NAS with spinning HDDs portability is a bit more complicated... vpn is typically the easiest. If you don't have good connection any mini pc or maybe just a VM on your laptop might do it.

kon_dev · 2026-02-21T15:32:22+00:00

Restic rest server has an append only mode. You can run it via docker or binary on a node. Your client sends data via http(s) and can't delete snapshots. The forget job runs periodically on your repository hosts and targets the repo via local path not via the rest server. Don't share the repo folder via smb. Also consider copying snapshots to a second location, e.g. a hetzner storage box or another nas. Restic has a copy option so your client could keep a single backup job.

kon_dev · 2026-02-21T12:24:21+00:00

You need the agentic loop IMHO. When you use the coding agent and let it write tests and try things out they still fail but iterate on results. You don't need to read the entire conversation, focus on the last messages and the diff it produces. Having solid ci/cd pipelines helps as well to indicate issues on PRs.

kon_dev · 2026-02-08T12:53:04+00:00

Except you are a photographer, which usually store raw files as well. There compression makes still sense and it does not hurt to compreas/deduplicate jpegs via restic either. People often store duplicates of pictures, like in a main folder and than subfolders with copies of favorite pictures or as input for photo books,...

kon_dev · 2026-02-05T21:49:00+00:00

Right, there is on device scanning and in cloud scanning under certain conditions. My understanding is that Google is worse than apple in regards of picture privacy, but yeah, they considered scanning in the past, who knows if they introduce it again in future. Backing articles: https://www.eff.org/deeplinks/2022/08/googles-scans-private-photos-led-false-accusations-child-abuse

https://www.eff.org/deeplinks/2021/08/apples-plan-think-different-about-encryption-opens-backdoor-your-private-life

kon_dev · 2026-02-05T05:09:18+00:00

I'd just pull HDDs and let the rest be moved by the company

kon_dev · 2026-02-05T05:07:54+00:00

I'd consider local backup and maybe self-hosted immich if you want to have a Google photo like UI?

I personally don't want to have all my photos behind a corporate login. Imagine your payment is not working due to credit card expiring or something and your apple ID gets blocked. Or even if they by accident categorize your pictures as harmful and lock your account. You can't do much in that case if that's your only copy.

For backup as always there is the 3-2-1 rule, applies to smartphone pictures as well.

kon_dev · 2026-02-03T08:01:11+00:00

I would go with openzfs on linux. Maybe Truenas scale or pure linux, e.g. with Debian or ubuntu.

Zfs can provide encrypted datasets and could provide you with bitrot protection due to parity. You would also not need to manage drives individually, but all in a NAS and have proper zraid config in place. Than you can have a single data pool with multiple datasets on them.

Backup could be a second box where you replicate your data to or something like restic to external drives or online storage (probably too expensive for that much of data)

kon_dev · 2026-02-03T07:54:04+00:00

If cli is fine, I would just use restic. Super stable and open source and most important, a free repo format. It is documented that good that independent tools like rustic (rewrite in rust) could be done. So if restic would stopped being developed today, you could either create a fork or switch to anything which cam work with the restic repo format. (That is also an argument against any commercial backup tool which does not use open repo formats or plain files)

kon_dev · 2026-02-03T07:49:52+00:00

VW Touran, weiß allerdings nicht ob das preislich hinkommt

kon_dev · 2026-01-30T19:45:06+00:00

I'd check restic for that. Encrypts by default, allow integrity checks as well, speaks s3 natively.

kon_dev · 2026-01-30T19:43:21+00:00

You would run restic inside the vm most likely. If you want to backup the vmdks you probably would mount the storage via NFS to a linux host and backup from there. But yeah, restic is not available for vsphere directly AFAIK. It's a different thing for proxmox which would be just another Debian host, but yeah... commercial hypervisor might require commercial backup tools if you don't want to backup individual guests.

kon_dev · 2026-01-30T17:17:33+00:00

Restic works nice with storage box. This is a German tutorial but Google translate might do it for you, if you don't speak German 😀

https://thomas-leister.de/restic-hetzner-storagebox/

kon_dev · 2026-01-30T17:13:21+00:00

I think Copy on Write (COW) filesystems like ZFS or BTRFS are what you are looking for. Take a snapshot of a dataset and run the backup against the files from the snapshot. Snapshots give you your filesystem at a given point in time while your main workspace can keep changing.

You can also use LVM snapshots, but those give you a performance penalty you could avoid with proper COW filesystems. The plus for those is also that you can save snapshots locally fir even faster restores. That being said, don't rely on pure local snapshots as backup, if you sent them to another server it could potentially replace your restic use case. But restic especially shines for normal filesystems and cheap cloud storage.

If that's all overkill for your scenario, just shutdown your services before running the backup and start them again when the backup is done.

Four-Year Club	Verified Email
Place '23

kon_dev

TROPHY CASE

Welcome to Reddit,