Behind the scenes, we run a sizeable infrastructure to deliver the services available to our 12,000 registered users (staff and students, including distance learners). There is a Campus wide network (wired and wireless) connecting around 3,000 workstations, hundreds of phones, printers and an untold number of personal devices. This links to the core University services and also, of course, to the Internet via the national JANET academic network that connects all Universities and Colleges. We have two main server rooms on Campus that house all our servers and storage – we manage over 300 servers and over 40 Terabytes of storage. All this runs 24 hours a day, 7 days a week. This whole environment has to be constantly monitored, backed up and upgraded – old servers replaced, software updated, capacity expanded and new services brought on stream. It’s a bit like changing the engines on a Jumbo Jet one at a time without landing . . .
Most of this is unseen by our users, but it has to be a key part of our strategy to keep our infrastructure up to date, and to plan in advance what capacity we will need over the next few years. Particularly when many of our users use external services (e.g. Apple Cloud, Google, Facebook, YouTube) and these can change quickly – increasing the traffic on our network.
We’re also looking at ways to reduce costs and lower our environmental footprint. We have recently signed up with other regional institutions to create a shared regional datacentre, and we will move half of our servers and storage into this in a year’s time. The new datacentre will be state of the art and highly efficient in its use of power. Our equipment consumes over 100kW of electrical power and it takes more energy on top of this to cool it which is why it is so important to have an efficient datacentre.
We also have to plan for unforeseen events – what happens if we lose a server room through fire, power loss or other incident? What happens if one of our major network links is cut? We run dual systems on our critical services to ensure that they can continue even if we lose one of the server rooms and we have dual links and equipment on the core of our network. It is important to test our disaster recovery measures, and this year we are going to start running regular rehearsals which will include shutting down one of our server rooms to prove that the critical services continue to run as expected.