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
- Qualcomm’s Pyrrhic Acquisition | Gestalt IT Rundown: February 21, 2018 - February 21, 2018
- White Boxes and Cultural Lock-in - February 20, 2018
- Salon Tries Crypto Mining Monetization - February 20, 2018
- Where AR We? - February 19, 2018
- Flexible Scaleout, Tom Lyon, and Reveal(x) in Gestalt News 18.8 - February 19, 2018
- In Defense of Facebook’s “Protect” - February 15, 2018
- Tom Lyon – IT Origins - February 15, 2018
- Do You Want to Build a Cloud? Gestalt IT Rundown: February 14, 2018 - February 14, 2018
- AI and Machines That Think They Can Think - February 14, 2018
- Docker for Home Automation - February 13, 2018