Soo, someone was backing up their @homeassistant on its own local disk, instead of something outside the VM which runs HA 🤦‍♂️ #homelab fails

Was it me? I was also doing that until very recently.

Thanks for the reminder, I've subscribed to their cloud service since day 1. Time to actually use that backup feature.

I back mine up to my own local disk, but about once every three months or so, I pull a copy from the disk onto my phone. That way I have another copy of it that's not on the local disk.

My setup doesn't change that much in that amount of time, so I'm not particularly worried about losing a bunch of data.

I prefer reflinks.

@root @homeassistant It me. I don't see the issue.

I’m not even backing up.

Happened to me as well! Backed up to some local folder in /mnt because the NAS share wasn't mounted properly. Fortunately noticed before anything bad happened.

Zero chance of backups failing if you don’t have any.

🤔

This reminds me, I use the internal ha backup (to a network drive). But I'm using Linux kvm, so I could be doing snapshots instead, which in theory are easier to restore.

@limelight79 I would still advise doing an alternate method(along with snapshot) of copy i.e tarred config directory as done by HA. I am not sure what happened(error message indicated disk corruption)but I couldn’t recover from the vm snapshots I had.

Do both, you're saying? Maybe keep the daily backup and then do a weekly snapshot, something like that.

@limelight79 I am saying two different methods of backup i.e one at file system level.. which the home assistant provides (to a cloud or local object storage) and one at block level (which I think where the snapshots you were referring to come into play)

I like to dump the whole VM every so often.
Overkill? Maybe. But I like knowing that no matter how hard I cock it up, I can spin an old version up.