Soo, someone was backing up their @homeassistant on its own local disk, instead of something outside the VM which runs HA 🤦♂️
#homelab fails
You must log in or register to comment.
- oranki@nord.pubEnglish1 month
Pro tip: use symlinks instead of copying files, the backup is near instant!
- 1 month
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. 
1 monthI 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.
@shortwavesurfer This is a good strategy until I remember to do it diligently 😅.
The first step I did with my new install is to ensure that the cloud backup works(self hosted coming soon)
The reason I do it that way is because I have my password manager in KeePass and do the database backups in the same way. So when I’m doing one of them, I do the other at the same time, just for consistency’s sake.
- limelight79@lemmy.worldEnglish1 month
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.
- limelight79@lemmy.worldEnglish1 month
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)
