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
- A simple command allows the CIA to commandeer 318 models of Cisco switches - March 23, 2017
- FreeNAS Corral Notes & First Impressions - March 23, 2017
- Elastifile: How Bizur - March 23, 2017
- StarWind Gives You a Gateway to the Cloud - March 21, 2017
- Tech Field Day Gets Containerized at DockerCon and Cloud Field Day - March 20, 2017
- Intel Optane Enters the Market - March 20, 2017
- From Windows to Azure – A Change in Focus - March 17, 2017
- AppliedMicro’s X-Gene 3 SoC Begins Sampling: A Step in ARM’s 2017 Server Ambitions - March 17, 2017
- Hardware vs. Software Innovation - March 17, 2017
- Epoch Rollover: NTP in 2036 - March 17, 2017