2 ms·

I think the parent is suggesting you've moved out of "backup" territory, into archive and/or disaster recovery territory. I agree with you problem description

I think the parent is suggesting you've moved out of "backup" territory, into archive and/or disaster recovery territory. I agree with you problem description and approach. I'm less sure I agree with your terminology choice. I use a software raid 1 pair of external usb drives on a wifi powerpoint to take a once a week snapshot of my backups, and the drives are only powered up for ~1 hour a week. Not guaranteed protection agains ransomware, or me fat fingering a "sudo rm -rf / tmp", but "good enough" for my home/personal stuff. I also have monthly and yearly snapshots of my backups in AWS Glacier. I sometimes colloquially refer to all that as "backups", but I can see your parent posters point that I've gone way beyond what "backups" covers in this paragraph.

syshum 5y ago
I don't view backups and DR as wholely distict things. DR is a set of policies and procedures that cover backups. That are inextricably linked You use backups to perform a diaster recovery. I personally dont believe you can talk about backups with out including DR nor can you talk about DR with out talking about backups
- bigiain 5y ago
  In my head at least, backups are a subset of disaster recovery. They are linked, but you can do backups without doing disaster recovery (for example, just turning on TimeMachine backups to a usb drive on your Mac is “backups” without being “disaster recovery”), but you can’t do disaster recovery without backups. But you also need archives, and retention policies, and recovery procedures and test plans, and training and practice for the people responsible for DR, and hardware/site/network disaster recovery plans and resources, and recovery time objectives and recovery point objectives, and a whole bunch of other “not directly backup” related stuff. But I admit that colloquially that might all be assumed in certain contexts to be “backups”, but that’s a probably dangerous assumption unless everybody in that discussion is totally on the same page about just how much of that related disaster recovery stuff is actually in place and ready.

syshum 5y ago

I don't view backups and DR as wholely distict things. DR is a set of policies and procedures that cover backups. That are inextricably linked You use backups to perform a diaster recovery. I personally dont believe you can talk about backups with out including DR nor can you talk about DR with out talking about backups

bigiain 5y ago
In my head at least, backups are a subset of disaster recovery. They are linked, but you can do backups without doing disaster recovery (for example, just turning on TimeMachine backups to a usb drive on your Mac is “backups” without being “disaster recovery”), but you can’t do disaster recovery without backups. But you also need archives, and retention policies, and recovery procedures and test plans, and training and practice for the people responsible for DR, and hardware/site/network disaster recovery plans and resources, and recovery time objectives and recovery point objectives, and a whole bunch of other “not directly backup” related stuff. But I admit that colloquially that might all be assumed in certain contexts to be “backups”, but that’s a probably dangerous assumption unless everybody in that discussion is totally on the same page about just how much of that related disaster recovery stuff is actually in place and ready.