Live data from Hacker News

ThinMachine – A $25 thin client macOS Time Machine appliance

tomverbeure.github.io

51–60 of 189 posts

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#51
post #46

Earlier quoted context omitted.

CCC is great although it’s not quite as useful as it is on Intel Macs on AS ones because the whole paradigm of “clone the drive onto a USB and boot it” doesn’t work.

what about on apple silicon macs?

You can’t boot off of non internal storage because Apple

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#52
"Don’t worry, I also use BackBlaze for automated off-site backups. And all my projects are stored on GitHub and different PCs as well"

That's smart. I've had 7 catastrophic drive failure in 20 years, 4 when I was using homegrown backup.

Due to my being sloppy / lazy, I still managed to lose a lot of data in 2 of the instances.

Homegrown backup solution isn't for me. :)

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#53
post #8

I have a Raspberry Pi running Pi-hole and Time Machine, making that little board probably the best value piece of tech I've ever owned. https://saschaeggi.medium.com/use-a-raspberry-pi-4-for-time-... is what I followed.

RPis are great hobby electronics projects, but IMO they don’t have any benefit for this kind of use over a thin client? They’re more expensive, you need an extra RPi enclosure and power supply, you can’t use M.2 SSD sticks without an additional USB3 enclosure, they have a history of corrupting flash cards, and their idle power is only a little bit lower.

Can confirm about MicroSD flash cards, they're too unreliable for stuff that must be on 24/7, and get corrupt easily. Good for tinkering projects and media players, not for critical stuff where the downtime needed to pull the card and fsck/reinstall it might not be an option.

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#54

My advice to retain your sanity: stop using Time Machine and use Carbon Copy Cloner [0] instead. It works. It keeps working. It has excellent documentation for any possible backup and restore cases. It is transparent about what it is doing. Time Machine works fine until it doesn't. And it won't tell you that a backup is broken until you try to restore from it. The errors are going to be cryptic. There is going to be…

I had a weird issue with ccc and the dev and I couldn’t figure it out, so I switched to TM. I also use backblaze and local rsync’s.

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#55
Home storage is the only thing I don't do a DIY solution. I used to run a samba server with timemachine settings and pointed it to an external SSD. But now I just run a Synology NAS with a RAID configuration. Definitely more expensive than $25 but worth the peace of mind IMO.

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#57
post #41

Earlier quoted context omitted.

> My daughter thinks I'm one of those nerds that married a regular girl from college and can do magic with software because I can make her computer go back in time and bring back versions of her files. Wait until she discovers git! As an aside, I wish there was an alternative like Time Machine on Windows.

There is, it's called File History and it's built in. I think it's been available since Vista. Like TM you need an external or network drive to use it. Unlike TM it's not very intuitive and Microsoft doesn't do much to advertise it.

I mean that's 'per drive' though. If you drive goes tits up so does your history of all files on that drive.

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#58

My advice to retain your sanity: stop using Time Machine and use Carbon Copy Cloner [0] instead. It works. It keeps working. It has excellent documentation for any possible backup and restore cases. It is transparent about what it is doing. Time Machine works fine until it doesn't. And it won't tell you that a backup is broken until you try to restore from it. The errors are going to be cryptic. There is going to be…

> Time Machine works fine until it doesn't. And it won't tell you that a backup is broken until you try to restore from it. The errors are going to be cryptic. There is going to be no support and the forums are not going to help.

and

> Time Machine uses the "fuck you user" approach

apply to every piece of software or service out there by Apple. Every single one!

iCloud? The only answer you’re ever going to get anywhere is - “No, your data is getting synced”. “Why don’t you enable and disable it”. Or “restart it”. My favourite is when Apple Support asks you to reinstall or reset the iOS or reinstall macOS entirely even if something as tiny as some sync problem occurs, with such confidence and matter of fact tone that you are forced to debate whether you are talking to some kafkasque and sadist bot.

This is the Apple playbook. Naming and shaming them on social media doesn't work. Emails don’t get answered. Your customer request gets stonewalled. Sometimes you feel maybe it’s Apple paying you to use their products and not the other way round.

An ex manager was thought to be crazy by us freshers when he would say that the moment he gets a Mac, for personal or work usage, the first thing he does is install Linux on that. We used to think he was some GNU/FOSS nut. He would smile and say - give it time, you’ll understand.

And I understand now how helplessly hostile the Apple ecosystem is. You literally feel like a hostage — you can use it with such stonewalling and infuriating limits and you start feeling this is the only way!

At this point I don’t think it’s anything other than self sabotage if anyone still says

- but I use Time Machine (or any XYZ Apple thing that involves data integrity and reliability) - it works, or is “good enough”

- or relies on something like iCloud for something like “data backup and integrity” in anyway.

Can’t wait for the day when file access is easier on iOS (of course aft explicit permissions - which is the case even today actually) etc, or Android sucks less - in this glorious duopoly. I meant when they’re forced to open up their platform, because they’re not going to do it themselves!

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#59

My advice to retain your sanity: stop using Time Machine and use Carbon Copy Cloner [0] instead. It works. It keeps working. It has excellent documentation for any possible backup and restore cases. It is transparent about what it is doing. Time Machine works fine until it doesn't. And it won't tell you that a backup is broken until you try to restore from it. The errors are going to be cryptic. There is going to be…

> Time Machine works fine until it doesn’t

I have been backing up to Time Machine for years without issues. Recently I started using pnpm (Nodejs package manager) and the backup process hangs on Mui material icons files (@mui/icons-material). Using "sudo fs_usage -f filesys backupd" I see that it is looping over the same files over and over.

Re: ThinMachine – A $25 thin client macOS Time Machine appliance

#60

My advice to retain your sanity: stop using Time Machine and use Carbon Copy Cloner [0] instead. It works. It keeps working. It has excellent documentation for any possible backup and restore cases. It is transparent about what it is doing. Time Machine works fine until it doesn't. And it won't tell you that a backup is broken until you try to restore from it. The errors are going to be cryptic. There is going to be…

Carbon Copy Cloner has a mode to periodically check backup integrity, and will alert you on mismatch. Given that unlike ZFS, APFS doesn't actually checksum user data, it's worth it for that feature alone. If you use ZFS for your backup destination, then this effectively ends up giving you verification of your non-ZFS source as well. And even if you don't backup to ZFS, then you still get notified that corruption was detected, allowing you to triage and take action.

I think it's CCC5 or CCC6 that actually exposed the list of file mismatches to the user UI, but the diffs were greppable in the diagnostic logs all the way back to CCC3.

Post reply on HN