Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It sounds like they didn’t have any backups at all but rather relied on a active-active replication link to a secondary storage.

Edit: who knows it may be related to the HPE issue.

https://www.bleepingcomputer.com/news/hardware/hp-warns-that...



In other words, RAID is not backup.


What baffles me is that there seems to be no way for either the customer or a data-recovery company to flash a new firmware onto the drive after it has failed. Someone there wanted to spare the few millicents of copper trace for a JTAG port?!


Probably to prevent supply chain firmware changes for hacking, espionage, etc.


Hmm... I wonder what the "incident" was. If it involved something akin to an "rm -rf," then of course their replication link didn't protect them.


Perhaps they were depending on snapshotting and were not prepared for some kind of hardware failure taking out the entire storage system.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: