Disaster Recovery is essentially a backup plan, something to say "if things go horribly wrong, this is what we will do to recover from that incident". This could be a range of things, from storing file backups, storing money in case you need it when the going gets tough, or having a solid plan to get you back on track if things don't go to plan. Eveything to do with disaster recovery has one key thing in common: you hope you never need to use this plan, but if you do have to use it - it should get you back in the game quickly and with minimal disruption.
Almost every company has a disaster recovery plan - if you don't have one, you're practically treading on ice hoping for the best outcome, when it could all go wrong in the matter of seconds.
IT is the biggest sector in the industry by far, almost everything you do requires some sort of interaction with a computer.
The good news is that backups are possible - what does this mean? Not only does it mean that you are protecting yourself from data loss, it also means that you can recover computer systems - even if they completely break down.
The "Disaster Recovery" project is all about exploring ways in which disaster recovery is possible, one of the main areas of disaster recovery Access Remote focused in on was OS recovery over WAN - the type of recovery for your computer, to restore your files, applications and operating system back to how it was before a disaster even occured. For those who don't know, WAN stands for Wide Area Network, what most people refer to as "the internet".
Birmingham City University provided us with Cisco routers and switches, ethernet cables, 2 desktop computers and of course, a place to work in the lab environment.
Microsoft Azure for Education provided us with the Operating Systems Windows Server 2016 Standard and Windows 10 Pro.
Finally, a team consisting of Reece McCaskill, Adam Jones and Zara Sheikh attempted to put the peices together to complete the experiment.
Our goal was to create a disaster recovery environment over a Wide Area Network, so a business could recover from an Operating System failure.
Scroll down for more information on this project!
Overall, this was a fun experiment which lasted over 5 days (including the setup of the routers, server, dummy PC and working on a schedule around lecture timeslots). We didn't accomplish our goals, but that's not to say we won't try again in the future!