At Gestalt IT, we’ve already covered that the IT infrastructure used by the Empire in Rogue One would be a personal hellscape. But it seems like it stood out to a lot of people. W. Curtis Preston took a more positive approach in this writeup, using it as a jumping off point for how to improve your archiving policies.
If there’s one takeaway from the piece, I think we should all remember:
Sometimes a Death Star shows up unexpectedly and blows up your offsite storage location.
A life lesson indeed.
Storage Switzerland comments:
SPOILER ALERT!!! If you have not seen Rogue One: A Star Wars Story, and don’t want me to ruin the most crucial part of the climax, and you are craving a blog on archiving then go read this blog. You’ve…
Read more at: Archive Lessons from Rogue One: A Star Wars Story
- Google Drops a SHA-1 Collision Course - February 23, 2017
- Arris Acquires Ruckus From Brocade Who’s Getting Acquired by Broadcom - February 22, 2017
- How Much Data is Used For Open Mesh Cloud Management? - February 21, 2017
- Azure Gets a Win with Flipkart, Platform9 Simplifies the Cloud, and IBM Brings the Brains in Gestalt Cloud News 17.3 - February 21, 2017
- Platform9 Simplifies Cloud Infrastructure - February 21, 2017
- Understanding CNI (Container Networking Interface) - February 20, 2017
- Flipkart Adopting Microsoft Azure - February 20, 2017
- Intel’s Altera Acquisition Bears Fruit: Cyclone 10 FPGAs - February 20, 2017
- Dell EMC: When Two Hearts Beat As One - February 17, 2017
- Alternatives to Intel’s New $8898 Top Dog Xeon - February 15, 2017