0
This is a pleasant reminder to check your backups. I don’t mean, “Hey, did the backup run last night? Yes? Then all is well.” That’s slightly better than nothing, but not really what you’re checking for. Instead, you’re determining your ability to return a system to a known state by verifying your backups regularly.
Backups are a key part of disaster recovery, where modern disasters include ransomware, catastrophic public cloud failures, and asset exposure by accidental secrets posting.
For folks in IT operations such as network engineers, systems to be concerned about include network devices such as routers, switches, firewalls, load balancers, and VPN concentrators. Public cloud network artifacts also matter. Automation systems matter, too. And don’t forget about special systems like policy engines, SDN controllers, wifi controllers, network monitoring, AAA, and…you get the idea.
Don’t confuse resiliency for backup.
When I talk about backups, I’m talking about having known good copies of crucial data that exist independently of the systems they normally live on.
- Distributed storage is not backup.
- A cluster is not backup.
- An active/active application delivery system spread over geographically diverse data centers is not backup.
The points above are examples of distributed computing. Distributed computing Continue reading