46
Soo, someone was backing up their homeassistant on its own local disk, instead of something outside the VM which runs HA 🤦‍♂️ (mastodon.raviteja.computer)
submitted 8 months ago by to c/homeassistant@lemmy.world
14 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 8 months ago (3 children)

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.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] [S] 1 point 8 months ago (2 children)

    @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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 8 months ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 8 months ago

    @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)

  • permalink
  • fedilink
  • source
  • parent