It’s 2:13 p.m. and two of your PDUs just went down. The ones supporting 900 business-critical servers.
2:13 p.m. You get a text alert from iTRACS telling you that two PDUs just went down.
2:14 p.m. You log into iTRACS to find out the precise location of the PDUs and assess the scale of the outage.
2:15 p.m. Using interactive 3D visualization, you instantly locate the PDUs that have gone down and confirm it’s due to mechanical failure. Within seconds, you’re executing a Failure Simulation to find out which assets are impacted by the loss of these PDUs. You need to determine how and where to deploy your resources.
What you learn is scary – the PDUs support high-density rows with a total of 900 servers sustaining your business-critical applications.
2:16 p.m. You send an alert notifying key personnel that two critical PDUs have gone down and outline the scope of the problem.
2:17 p.m. You send out a tech team to begin repairing and/or replacing the two PDUs. Since iTRACS visually shows you exactly where the two PDUs are, you can quickly dispatch repair teams armed with detailed graphics and operational data. No more guesswork about where the units are or what they’re connected to. It’s all right there in iTRACS. The units are on the first floor by the rear stairway and you know exactly what they’re connected to.
2:18 p.m. You send out a second team to reboot the affected servers. Again, iTRACS visually shows you exactly which servers are affected, so can you can dispatch repair teams armed with detailed operational data. They begin work immediately.
2:19 p.m. You contact the server owners to notify them of the outage. You assure them teams are already on location and in repair mode – in less than 5 minutes from the beginning of the event.
2:20 p.m. You contact other personnel so they’re prepared to do any necessary reconfiguration of the servers once they have been rebooted.
4:10 p.m. The teams report that the crisis is over – power has been restored and the affected servers have been rebooted and are back on line. There’s been minimal disruption to the business.
In a normal disaster recovery scenario, this event might require a full day’s recovery time with significant impact on the business. Thanks to iTRACS, it took less than two hours. It all started by being able to identify the source of the problem – and every server affected – within mere minutes. The rest was up to your staff. Fortunately, you have a great team.
