Skip to main content

How IT Should Prepare for COVID-19 … or Any Disaster

Dan Timko
J2 Global

It's still unclear whether COVID-19 will become a full-blown global pandemic, but there are few instances in which a business gets a significant amount of advanced warning to prepare for a potential disaster. And even if novel coronavirus doesn't cause massive illness and widespread quarantines, preparing and planning for the worst case scenario won't be a waste of time.

Protect Your People

The prospect of a pandemic, as unsettling as it is, can serve as a forcing issue that ensures your IT operation be ready to deal with almost anything, from a natural disaster to severe weather or a local outbreak of flu or norovirus.

Your first priority must be to protect your people. Talk with HR and work to give as much flexibility as you can with paid sick days and allowing people to work from home. You don't want anyone feeling like they must come in to work even if they feel ill. In the long run, your people and your business will be better off if employees don't spread the virus to one another.

Next, make sure everyone understands who to contact if they can't come into work. People need to know who to speak to when they have questions. Also, promote proper hygiene — frequent handwashing, no handshakes — and insist that anyone who starts showing symptoms must go home immediately.

Protect Your Business

Once you've taken measures to protect employees, it's time to think about protecting the business. Begin by considering how a pandemic will affect operations. For instance, if your IT group supports a healthcare organization, you'll need to prep for a surge. On the other hand, if you support brick-and-mortar retail, you can probably assume there will be a decline.

Talk with business managers to make sure you understand exactly which IT services are most critical for day-to-day operations. Can you provide these services remotely and do you have sufficient capacity to cover everyone who might need to work at home? If there are gaps, prioritize filling them.

Then look at your IT operations. Determine which skills are most critical to keeping the IT shop running, and make sure you have multiple people cross-trained on vital functions. That way, as long as some of your people are healthy and able to come into work, you'll most likely be covered. However, if we have a pandemic that goes on for an extended period of time, you'll need to know which assets are most at risk if no one can come in to maintain them. If some of these vital services can be run from the cloud, it's a good idea to at least prepare to do so.

Look into third-party services such as remote network monitoring centers (NOC) and help desks that could fill in if necessary. And, if you do rely on an outside provider, make sure to do your due diligence. Ask them how they plan to continue providing services if the worst case scenario comes to pass. If you're depending on another organization to fill in the gaps, make sure they are well prepared.

Finally, review your backup and disaster recovery (DR) plan. Can you restore services remotely? After all, a backup tape in a closet isn't going to do you much good if everyone is stuck at home. Ideally, you can replicate vital systems and applications to the cloud so if you need to fail over, it will be ready to go, enabling your people to access the services they need from essentially anywhere. Make sure you build in time to test the DR and backup systems thoroughly so you'll know they will work as expected when needed.

This was a brief overview of how to plan for COVID-19, but if you want a more detailed checklist, here's a useful document from the Centers for Disease Control (CDC).

Remember, as you undergo preparations, don't get too hung up on COVID-19. Preparations are by no means a waste if a pandemic doesn't emerge. Because, while the threat of a pandemic may be the issue that finally convinces executives to give IT the green light to prepare for a worst-case scenario, having a plan to deal with disasters will serve you well long after this crisis has passed. Every organization should have a disaster plan in place. After all, an earthquake or a tornado won't give you several weeks notice to prepare.

Dan Timko is Chief Strategy Officer for Cloud Backup at J2 Global

Hot Topics

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

How IT Should Prepare for COVID-19 … or Any Disaster

Dan Timko
J2 Global

It's still unclear whether COVID-19 will become a full-blown global pandemic, but there are few instances in which a business gets a significant amount of advanced warning to prepare for a potential disaster. And even if novel coronavirus doesn't cause massive illness and widespread quarantines, preparing and planning for the worst case scenario won't be a waste of time.

Protect Your People

The prospect of a pandemic, as unsettling as it is, can serve as a forcing issue that ensures your IT operation be ready to deal with almost anything, from a natural disaster to severe weather or a local outbreak of flu or norovirus.

Your first priority must be to protect your people. Talk with HR and work to give as much flexibility as you can with paid sick days and allowing people to work from home. You don't want anyone feeling like they must come in to work even if they feel ill. In the long run, your people and your business will be better off if employees don't spread the virus to one another.

Next, make sure everyone understands who to contact if they can't come into work. People need to know who to speak to when they have questions. Also, promote proper hygiene — frequent handwashing, no handshakes — and insist that anyone who starts showing symptoms must go home immediately.

Protect Your Business

Once you've taken measures to protect employees, it's time to think about protecting the business. Begin by considering how a pandemic will affect operations. For instance, if your IT group supports a healthcare organization, you'll need to prep for a surge. On the other hand, if you support brick-and-mortar retail, you can probably assume there will be a decline.

Talk with business managers to make sure you understand exactly which IT services are most critical for day-to-day operations. Can you provide these services remotely and do you have sufficient capacity to cover everyone who might need to work at home? If there are gaps, prioritize filling them.

Then look at your IT operations. Determine which skills are most critical to keeping the IT shop running, and make sure you have multiple people cross-trained on vital functions. That way, as long as some of your people are healthy and able to come into work, you'll most likely be covered. However, if we have a pandemic that goes on for an extended period of time, you'll need to know which assets are most at risk if no one can come in to maintain them. If some of these vital services can be run from the cloud, it's a good idea to at least prepare to do so.

Look into third-party services such as remote network monitoring centers (NOC) and help desks that could fill in if necessary. And, if you do rely on an outside provider, make sure to do your due diligence. Ask them how they plan to continue providing services if the worst case scenario comes to pass. If you're depending on another organization to fill in the gaps, make sure they are well prepared.

Finally, review your backup and disaster recovery (DR) plan. Can you restore services remotely? After all, a backup tape in a closet isn't going to do you much good if everyone is stuck at home. Ideally, you can replicate vital systems and applications to the cloud so if you need to fail over, it will be ready to go, enabling your people to access the services they need from essentially anywhere. Make sure you build in time to test the DR and backup systems thoroughly so you'll know they will work as expected when needed.

This was a brief overview of how to plan for COVID-19, but if you want a more detailed checklist, here's a useful document from the Centers for Disease Control (CDC).

Remember, as you undergo preparations, don't get too hung up on COVID-19. Preparations are by no means a waste if a pandemic doesn't emerge. Because, while the threat of a pandemic may be the issue that finally convinces executives to give IT the green light to prepare for a worst-case scenario, having a plan to deal with disasters will serve you well long after this crisis has passed. Every organization should have a disaster plan in place. After all, an earthquake or a tornado won't give you several weeks notice to prepare.

Dan Timko is Chief Strategy Officer for Cloud Backup at J2 Global

Hot Topics

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...