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
- Phoummala Schmitt – IT Origins - September 20, 2018
- Joining Microsoft’s Teams, or No More Slacking - September 20, 2018
- ARM Servers and End Times | Gestalt IT Rundown: September 19, 2018 - September 19, 2018
- NetApp Acquires StackPointCloud - September 18, 2018
- Networking Disaggregation Isn’t Ready – The On-Premise IT Roundtable - September 18, 2018
- Built for SMBs: A Look at the HPE ProLiant ML110 Gen10 - September 18, 2018
- Pure Storage and the State of VVols - September 14, 2018
- Ken Nalbone – IT Origins - September 13, 2018
- Advanced Persistent Database | Gestalt IT Rundown: September 12, 2018 - September 12, 2018
- How a Storage Company Approaches Containers - September 12, 2018