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
- The Brave New World of NVMe: The On-Premise IT Roundtable - July 18, 2017
- Cisco Announces “The Network. Intuitive.” - July 10, 2017
- This is Inbox Hell - July 10, 2017
- Broadcom Gets Regulatory Approval on Brocade Acquisition - July 5, 2017
- Cloud Extensions, NVMesh, and Backup Awareness in Gestalt Storage News 17.3 - July 5, 2017
- Not The Cisco of John Chambers Anymore - July 3, 2017
- Is Kubernetes a Flash in the Pan? The On-Premise IT Roundtable - July 3, 2017
- HyperThreading Bug in Intel Skylake and Kaby Lake CPUs - June 30, 2017
- Trove puts the A.I. in Email - June 30, 2017
- VMware NSX, Figuring Out Intent-Based Networking, and Career Management in Gestalt Networking News 17.7 - June 27, 2017