This week Trekkies across the globe will be out in droves to see Star Trek Beyond, the third film in the Star Trek reboot series. In the new film, we get to watch the beloved Captain Kirk, Commander Spock, and other USS Enterprise crew members battle with an unexpected attack by an unknown enemy.
Here at CloudEndure, we can’t help but wonder what types of disaster recovery (DR) strategies the USS Enterprise might have had in place — or what DR solutions it should have had in place — in order to protect its systems from unexpected attacks and, even scarier, unexpected outages.
Earlier this year, it was discovered that Star Trek creator Gene Rodenberry had saved story ideas, scripts, and notes on floppy disks. We can therefore assume that if Rodenberry had a DR solution, Captain Kirk and his crew very likely had one too as they boldly traveled “where no man has gone before.”
So if you let your imagination drift, you’ll recognize that the need for disaster recovery in science fiction is not implausible. Consider that space travel is hazardous. And even during peaceful times, asteroid fields, black holes, and other cosmic matter can wreak havoc on the sturdiest of spaceships. Enemy fire from a Klingon vessel is a whole other matter.
Think of the massive amounts of real-time data that Scotty, the Enterprise’s chief engineer, needed in order to constantly measure the ship’s performance and forecast impending repairs. And not a Star Trek episode passed without a time warp or a villain inflicting damage on the Enterprise. The ship’s power was affected many times and its data certainly was put at risk — if not lost.
Although never articulated by Scotty, Kirk, or Spock, disaster recovery must have been an integral function on the Enterprise. The ship simply could not have cruised universes as long as it did without the ability to recover its most recent bit of data. Just think of the critical importance of the energy pattern data needed to return teleported crew members back to the spacecraft. Heck, data was so important to the Enterprise that the name of a major character from Star Trek: The Next Generation was . . . Data.
The only question remaining is what kind of disaster recovery strategy Kirk and his crew would have likely used. Given that the Enterprise’s main objectives were defense, peacekeeping, and diplomacy, an unexpected disaster could have dire consequences for the entire United Federation of Planets. Therefore, we can assume that the Enterprise would have required a DR tool with consistent, block-level, real-time replication that prevents data loss. In the midst of an attack, the Enterprise would have needed to bring up replicated servers as quickly as possible, so near-zero RTO would have definitely been required.
Scotty, who was in charge of fixing disasters, probably would have insisted that the disaster recovery tool enable regular, non-disruptive drills. And the highly logical Spock would likely have required point-in-time recovery, just in case the Romulans decided to hack the Enterprise with their disruptor technology.
In other words, CloudEndure Disaster Recovery would definitely have been a good option for protecting the mission-critical workloads of Rodenberry’s venerated crew. Wouldn’t you agree?
The 2016 Disaster Recovery survey results are finally in. Compare your DR plans to over 243 of your peers with this exclusive report.