Skip to main content

After the Hurricane: Expert Advice for Post-Disaster IT Service Recovery

Chris Adams

Hurricane season is in full swing. With the latest incoming cases of mega-storms devastating the Southeastern shoreline, communities are struggling to restore daily normalcy. Accordingly, many voices have weighed in with tips for consumers to get their lives back up and running. People have been stepping up and showing remarkable strength and leadership in helping those affected. However, there is another area that we need to remember in these trying times – and that is businesses continuity.

Today, most (if not all) businesses are heavily dependent on their digital assets and IT functions. This means that if a server is down, a business will not have access to its crucial resources. Even the most basic functions are often tied to these resources. Given the state of flooding and destruction that communities are seeing during storms like Harvey and Irma, business servers are frequently at risk. In 2012 when Sandy hit New York, many data centers fell victim to the storm leaving, several major (and not so major) companies with limited business capabilities in the weeks and months following. Many businesses did not begin moving their assets and focusing on recovery until it was too late.

I want to share tips we advise our clients for keeping your business running during a disaster, or quickly getting back up online after the worst has happened.

Before the Storm, Plan for the Worst

Disaster recovery begins well before the storm strikes.

Disaster recovery begins well before the storm strikes. Have a disaster recovery plan in place. Work with key stakeholders across your company to ensure that measures are in place to address any crisis that may arise. Create a variety of scenarios and plan your responses. Ensure everyone knows and understands their roles and responsibilities. Have a practice run to ensure all parties are working well together.

Additionally, ensure all of your warranties are up-to-date, and if they have expired, consider bringing on a third-party maintenance (TPM) provider. Not only will this save you costs, but TPMs are great support systems in a crisis. When we see a natural disaster, like a hurricane approaching, we work swiftly to contact our clients in that area and have key parts and staff staged and ready to mobilize after the storm has passed.

As the Storm is Approaching ...

As the storm is approaching, notify your OEM or TPM service provider, and let them know ahead of time that there is an incoming storm or a pending disaster that could affect your business. Raising the alert in advance offers your service provider an opportunity to route necessary components to safe staging areas just outside the storm’s reach to expedite recovery once the danger has passed.

After Danger has Passed

After danger has passed and you’ve ensured the safety of your employees, your first goal should be to restore IT servers and bring them back into operation. Turning them on, however, needs be done carefully. As with any water damaged server electrical device, safety comes first. Ensure that there is no standing water with power flowing through it. Before going in, consider switching the breaker for the server room off.

Once the power has been shut down, servers need time to dry. This needs to be done without moving the servers. Any movement may cause otherwise dry critical components, such as circuit boards, to experience additional damage.

After Drying the Servers

After drying the servers, the next step should be assessing the damage. When dealing with post-disaster recovery, there is often damage that is obvious to the naked eye. However, there is also damage that most people would not even think of.

For example, just because the equipment is dry, doesn’t mean its 100% operational. Water can leave corrosive mineral deposits on circuit boards and various other server components. It’s important to be thorough, and follow the manufacturers recommendations for care. If a warranty is still in place, now would be the time to contact the manufacturer.

Alternatively, consider a TPM provider. They have the same expertise as the OEM experts – often they previously worked for an OEM – and can keep your services up and running at 60 percent lower costs.

Monitor the Server Situation Going Forward

Lastly, after addressing the immediate damage and getting back up and running, the final step should always be to monitor the server situation going forward. Sometimes problems resulting from a disaster can appear months later. Keeping on top of server metrics — such as control room temperatures, cooling equipment, and monitoring component failures and other problems — will help alleviate further operation impairment to the business’ IT structure.

Whether addressing disaster recovery yourself, or contacting your warranty service provider, in the end, having a plan is key to effective post-disaster recovery no matter the situation.

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

After the Hurricane: Expert Advice for Post-Disaster IT Service Recovery

Chris Adams

Hurricane season is in full swing. With the latest incoming cases of mega-storms devastating the Southeastern shoreline, communities are struggling to restore daily normalcy. Accordingly, many voices have weighed in with tips for consumers to get their lives back up and running. People have been stepping up and showing remarkable strength and leadership in helping those affected. However, there is another area that we need to remember in these trying times – and that is businesses continuity.

Today, most (if not all) businesses are heavily dependent on their digital assets and IT functions. This means that if a server is down, a business will not have access to its crucial resources. Even the most basic functions are often tied to these resources. Given the state of flooding and destruction that communities are seeing during storms like Harvey and Irma, business servers are frequently at risk. In 2012 when Sandy hit New York, many data centers fell victim to the storm leaving, several major (and not so major) companies with limited business capabilities in the weeks and months following. Many businesses did not begin moving their assets and focusing on recovery until it was too late.

I want to share tips we advise our clients for keeping your business running during a disaster, or quickly getting back up online after the worst has happened.

Before the Storm, Plan for the Worst

Disaster recovery begins well before the storm strikes.

Disaster recovery begins well before the storm strikes. Have a disaster recovery plan in place. Work with key stakeholders across your company to ensure that measures are in place to address any crisis that may arise. Create a variety of scenarios and plan your responses. Ensure everyone knows and understands their roles and responsibilities. Have a practice run to ensure all parties are working well together.

Additionally, ensure all of your warranties are up-to-date, and if they have expired, consider bringing on a third-party maintenance (TPM) provider. Not only will this save you costs, but TPMs are great support systems in a crisis. When we see a natural disaster, like a hurricane approaching, we work swiftly to contact our clients in that area and have key parts and staff staged and ready to mobilize after the storm has passed.

As the Storm is Approaching ...

As the storm is approaching, notify your OEM or TPM service provider, and let them know ahead of time that there is an incoming storm or a pending disaster that could affect your business. Raising the alert in advance offers your service provider an opportunity to route necessary components to safe staging areas just outside the storm’s reach to expedite recovery once the danger has passed.

After Danger has Passed

After danger has passed and you’ve ensured the safety of your employees, your first goal should be to restore IT servers and bring them back into operation. Turning them on, however, needs be done carefully. As with any water damaged server electrical device, safety comes first. Ensure that there is no standing water with power flowing through it. Before going in, consider switching the breaker for the server room off.

Once the power has been shut down, servers need time to dry. This needs to be done without moving the servers. Any movement may cause otherwise dry critical components, such as circuit boards, to experience additional damage.

After Drying the Servers

After drying the servers, the next step should be assessing the damage. When dealing with post-disaster recovery, there is often damage that is obvious to the naked eye. However, there is also damage that most people would not even think of.

For example, just because the equipment is dry, doesn’t mean its 100% operational. Water can leave corrosive mineral deposits on circuit boards and various other server components. It’s important to be thorough, and follow the manufacturers recommendations for care. If a warranty is still in place, now would be the time to contact the manufacturer.

Alternatively, consider a TPM provider. They have the same expertise as the OEM experts – often they previously worked for an OEM – and can keep your services up and running at 60 percent lower costs.

Monitor the Server Situation Going Forward

Lastly, after addressing the immediate damage and getting back up and running, the final step should always be to monitor the server situation going forward. Sometimes problems resulting from a disaster can appear months later. Keeping on top of server metrics — such as control room temperatures, cooling equipment, and monitoring component failures and other problems — will help alleviate further operation impairment to the business’ IT structure.

Whether addressing disaster recovery yourself, or contacting your warranty service provider, in the end, having a plan is key to effective post-disaster recovery no matter the situation.

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...