Free tools · Free · 2 minutes
Would your IT survive a cyclone?
In Mauritius, the question is not whether a cyclone will come, but when — and whether your IT will be ready that day. Tick what is genuinely in place in your organisation today: the score and your weak spots are computed in your browser, and nothing is sent without your consent.
UPS units in place, with autonomy actually measured During a cyclone, power cuts last far longer than usual; autonomy that has never been measured reveals its true value at the worst possible moment. Automated clean shutdown of servers when the battery runs out A server that loses power abruptly can corrupt its data; the orderly shutdown must trigger by itself, because nobody will be on site to press the button. Off-site backup, validated by a recent restore If the building is flooded or damaged, only the copy that lives elsewhere still matters — and a backup that has never been restored remains an assumption, not a protection. Fallback site or capacity identified to restart critical services If your premises stay inaccessible or out of service for days, you must know where and on what to restart — that decision is made before the crisis, not during it. Written procedure per cyclone warning class (1, 2, 3): who does what, when Each warning class leaves less time than the one before: deciding in advance what happens at each stage avoids improvising once the wind picks up. Remote work ready: remote access tested in real conditions After the cyclone passes, the office may stay closed while business has to resume; remote access never tested with the whole team gives way on day one. Inventory of exposed equipment (windows, ground floor, roof) Water and flying debris come in through the building's weak points; knowing in advance what to move, raise or unplug saves precious hours when the warning comes. Emergency contacts up to date: suppliers, operators, electrician, insurer During and after the cyclone, everyone calls at the same time; a verified list, available offline, is the difference between waiting your turn and being served first. Full failover test to the standby setup, with a date on it A fallback plan that has never been exercised almost always fails on an unforeseen detail; the date of the last test tells the truth about your actual readiness. Client communication prepared (message templates, alternative channel) Telling your clients before they start worrying protects the relationship; the messages get written calmly, before the season, not in the middle of the storm.
See my result
The companion article: Cyclone season: the 7 IT tests to run before December