Storm Surge Recovery — What We Found Inside a New Bern Office After a Hurricane

We arrived at the office on a Thursday morning, three days after the storm cleared. The water was gone, but the line on the walls was still visible — about fourteen inches above the floor, running evenly through every room. The carpet was ruined. The baseboards were warped. The furniture that had been touching the floor was swollen and stained. And the server, the workstations, the UPS, the network switch, the surge protector — all of it had been sitting in over a foot of brackish storm surge for an estimated eighteen hours before the water receded.

The business owner was standing in the doorway when we got there. He already knew the furniture and the carpet were gone. What he didn’t know — and what he was afraid to find out — was whether his data was gone too.

This is what storm surge does to a small business’s IT infrastructure, what the recovery process looks like, and what businesses in flood-prone areas of Eastern NC should have in place before the next storm.

What Flood Water Does to Equipment

Storm surge is not clean water. In New Bern, it’s a mixture of river water, sea water, sediment, debris, and whatever else the Neuse and Trent rivers carry during a major weather event. When that water sits in an office for hours, every piece of equipment at floor level is submerged in a corrosive, sediment-laden liquid that penetrates every seam, vent, and opening.

The server. The server was a tower unit sitting on the floor beside the desk. The water line was above the top of the case. Every component was submerged — the motherboard, the power supply, the drives, the RAM, the processor. When we opened the case, sediment had deposited on every surface. The motherboard showed visible corrosion within seventy-two hours of the event. The power supply was waterlogged and would not have been safe to energize even if the server had been dry. The server was a total loss.

The workstations. Three desktop computers, all on the floor or on low shelves. Same story — submerged, sediment-coated, corroded. All three were total losses. The monitors, which were on the desks above the water line, were undamaged.

The UPS. The uninterruptible power supply was under the server desk. UPS units contain sealed lead-acid batteries. When submerged in flood water, these batteries can release gases, leak electrolyte, and become a chemical hazard. We didn’t attempt to power it on. It was disposed of according to the battery recycling requirements.

The network switch and router. Both on the floor. Both submerged. Both losses. The ethernet cables running along the baseboards were contaminated and couldn’t be reused — pulling new cable runs was part of the rebuild.

The printer. A multi-function laser printer on a low table. The water reached the paper tray and the internal feed mechanism. Sediment in the paper path and the fuser assembly made it unrecoverable.

The Data Recovery Conversation

The server contained the business’s primary data — accounting records, client files, project documentation, contracts. The business owner asked the question everyone asks: can you get the data off the drives?

The honest answer in a flood scenario depends on the type of drive and the severity of exposure.

Mechanical hard drives submerged in contaminated water have a chance of recovery, but it requires a professional data recovery lab — a cleanroom facility where the platters can be removed from the contaminated drive assembly and read in a clean environment. This service exists, and it works in many cases, but it’s expensive (typically $1,000 to $3,000 per drive with no guarantee of success), slow (one to three weeks turnaround), and the success rate depends on how long the drive was submerged and what the water contained.

We don’t perform physical data recovery from flood-damaged drives. What we do is assess the situation honestly, recommend whether lab recovery is likely to be productive, and refer to labs we’ve worked with that have a track record. In this case, we sent two drives for recovery — one came back with most of the data intact, one didn’t. The owner got about two-thirds of the files from the server.

If the drives had been solid-state, the situation would have been different. SSDs store data on flash chips without moving parts. Submersion can damage the controller board but the flash chips themselves may survive. Recovery rates from SSDs are generally higher than mechanical drives, though the process is still specialized.

The Rebuild

Once the data situation was resolved — or at least defined — the rebuild began. This is the process of getting the business operational again.

Day one: assessment and ordering. We inventoried everything that was lost and placed orders for replacement equipment. In the aftermath of a major storm, equipment availability can be constrained — everyone is ordering at the same time. We sourced what we could locally and had the rest shipped with expedited delivery.

Days two through four: infrastructure. New network cabling where the old runs were contaminated. New router and switch installed above desk height — not on the floor. New UPS units, also elevated. New electrical connections checked by an electrician (flood water and electrical systems require professional inspection before power-up).

Days four through six: workstations and server. Three new workstations deployed. A new server configured with the business’s line-of-business software. Data from the successful drive recovery loaded onto the new server. The files that weren’t recovered had to be reconstructed from paper records, client copies, and the business owner’s memory.

Days six through eight: testing and verification. Everything powered on, connected, tested. Software licenses reactivated. Email reconnected. Printers configured. Backup configured and verified — this time with an offsite component.

Total elapsed time from the day we arrived to the day the business was fully operational: eight business days. Total cost including equipment, labor, and data recovery: in the range quoted above.

What the Backup Situation Determines

This is the critical variable in every storm recovery scenario, and it was the difference between an eight-day rebuild and a potentially unrecoverable situation.

This business had no offsite backup. Their backup was an external hard drive connected to the server. The external drive was on the floor next to the server. It was submerged in the same water. The backup was destroyed along with the original data. The recovery depended entirely on whether the data recovery lab could extract files from the flood-damaged server drives.

If they had had an offsite or cloud backup: The data recovery lab would have been unnecessary. The server’s data would have been restored from the offsite copy onto the new hardware. The rebuild timeline would have been shorter — probably four or five days instead of eight — and the cost would have been lower by the amount of the data recovery fee. More importantly, all the data would have been recovered, not just two-thirds of it.

The offsite backup survives the physical event. That’s its entire purpose. A local backup that sits in the same room as the equipment it’s backing up does not survive a flood, a fire, or a theft that affects that room — and, as ransomware victims in Carteret County have found, it won’t survive an encryption attack that targets all locally connected drives either. It protects against drive failure and accidental deletion — both important — but it does not protect against the scenario that just happened.

What Businesses in Flood-Prone ENC Areas Should Have in Place

This guidance applies specifically to businesses in New Bern, James City, Bridgeton, and the low-lying areas of Morehead City, Beaufort, and the rest of Carteret County. Hurricane season is June through November. Storm surge events are not hypothetical in this region.

Offsite backup component. A cloud-based or remote backup that stores a copy of your data in a location physically separate from your office. This runs automatically, is encrypted in transit and at rest, and is verified periodically. If your office is destroyed, your data survives.

Equipment elevation. In areas with flood exposure, keep servers, workstations, UPS units, and network equipment off the floor. Desk height or shelf-mounted is the minimum. Even in years without a major storm, salt air and coastal humidity accelerate hardware failure — equipment sitting on the floor near exterior walls ages faster regardless of flood risk. In a ground-floor office with known flood risk, consider whether critical equipment should be on the second floor if one exists.

Generator or UPS for graceful shutdown. A UPS large enough to keep the server running for twenty minutes allows a graceful shutdown rather than an abrupt power loss. This protects the drives and the data integrity. In areas where extended outages are common during storms, a generator provides extended runtime.

IT evacuation checklist. For businesses that can evacuate ahead of a storm, a checklist of what to take: the server (if it’s small enough), external backup drives, laptops, and the documentation folder. Unhooking a server and putting it in a car takes fifteen minutes. Rebuilding from nothing takes weeks.

Documentation. A record of what equipment you have, what software is installed, what the license keys are, who your ISP is, and how to reach your IT support. This document should exist in a location you can access even if the office is inaccessible — a cloud drive, an email to yourself, a printed copy at home.

If you run a business in a flood-prone area of Eastern NC and you don’t have an offsite backup in place, that’s the single most important conversation to have before hurricane season. We’re at 252-777-2488. We can set up an offsite backup, review your current storm preparedness from an IT perspective, and make sure you’re not starting from zero if the water comes. More at /services/business-backup-recovery.