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
- Novelty MacBook Pro Touch Bar Apps – RANKED - January 20, 2017
- World of StorageCraft- Company Acquires Exablox - January 19, 2017
- The Devil’s in the DRAM with Diablo Technologies - January 18, 2017
- In Search of an Acronym: Zadara’s Storage as a Service - January 17, 2017
- Quorum’s Latest Release, AMD’s Lost Decade, and HCI in Gestalt Server News 17.2 - January 16, 2017
- Getting started with TMUX - January 16, 2017
- Raspberry Pi Foundation Launches New Compute Module - January 16, 2017
- The 802.11ac 1 Gbps Uplink Myth - January 16, 2017
- AMD: The Last Decade - January 16, 2017
- ThousandEyes, Network Shaming, and Google Fiber in this week’s Gestalt Networking News 17.1 - January 13, 2017