
Hurricane season runs June 1 through November 30, and NOAA is calling for an above-normal 2025 season. Whether your office is in Fort Myers or on Long Island, the IT playbook is the same: assume you’ll lose power, internet and building access for days — then set things up so the business runs anyway. Here’s the checklist we work through with clients in both regions.
Hurricane risk is not just a Florida problem
Southwest Florida knows the drill — Ian in 2022 left parts of the region without power or connectivity for weeks, and Helene and Milton arrived back-to-back just last fall. But the Northeast gets its share too: Sandy flooded server rooms across lower Manhattan and the Jersey Shore in 2012, and the remnants of Ida drowned basements — and the equipment in them — across New Jersey and New York in 2021.
We support businesses in New York, New Jersey, Connecticut, Pennsylvania and Southwest Florida, so most seasons we’re watching both coasts at once. The pattern never changes: companies that rehearsed recover in days; companies that improvised recover in weeks.
The before-the-storm IT checklist
Work through these in order over the next two weeks — every item is cheap or free right now, and either expensive or impossible once a storm is named and tracking toward you.
- Test a restore, not just a backup. Pick a critical system and actually bring it back. A backup you’ve never restored is a rumor.
- Keep one copy out of the region. Follow 3-2-1: three copies, two media types, one offsite — cloud counts, a USB drive in a desk drawer does not.
- Write down your recovery time objective. How long can you afford to be down, and does your current setup actually meet that number?
- Move what you can to the cloud now. Email, files and phones that live in the cloud don’t care what happens to your building.
- Check UPS batteries and test the generator under load — not just the power light.
- Print the contact tree. Staff, IT, ISP, insurance and key vendors, on paper, because you’ll need it when nothing has power.
- Photograph your server room and equipment for the insurance claim you hope you never file.
- Issue laptops, chargers and hotspots to essential staff before the storm is named, not after.
During and right after the storm
Once the watch becomes a warning, the goal shifts from protection to a clean shutdown and a fast, verified return.
- Shut down on-prem servers gracefully before landfall if flooding or surge is possible — hardware survives a clean shutdown far better than dirty power.
- Move equipment up. Off the floor, away from windows.
- Expect scam season. Fake FEMA notices, insurance “adjusters” and charity appeals spike after every storm — verify before clicking or paying anything.
- Document damage before touching anything, then let IT verify systems before staff reconnect.
Test your disaster recovery plan in July, not in the forecast cone
A plan that’s never been rehearsed is a hope. Run a one-hour tabletop exercise this summer: pick a storm scenario, walk through the first 72 hours, and time an actual restore. You’ll find the gaps on a sunny day, when they’re cheap to fix. Invite whoever runs operations, not just IT — plans fail at the seams between departments, and that’s exactly what a tabletop exposes.
One more lesson from real storms: when cell networks are jammed and every vendor’s support line has a two-hour hold, having a dedicated account manager whose real cell number is taped to your monitor changes everything.
Key takeaways
- Hurricanes are a NY and NJ problem too — Sandy and Ida proved it.
- Verify restores, keep a copy out of the region, and know your recovery time.
- Cloud-hosted email, files and phones make your building optional.
- Prepare for post-storm phishing along with the wind and water.
- Rehearse in July; improvisation is expensive in October.
If your recovery plan is a binder nobody has opened since 2023, our disaster recovery team will test it, fix it, and stand watch with you through the season.
Turn insight into action.
Take a free cybersecurity or AI readiness assessment, or book a call with a NetSys engineer — no obligation, no runaround.



