In this episode, Nathan Sirois from Balsam Technologies explains what disaster recovery means for businesses facing fires, floods, ransomware, outages, or failed systems. He covers critical system prioritization, recovery time objectives, backup limitations, and how to test a recovery plan before an emergency happens.

John Maher: Hi, I’m Maher and I’m here today with Nathan Sirois, Support Engineer at Balsam Technologies, a managed IT service company in Gloucester, Massachusetts, offering cybersecurity, IT infrastructure, network support, cloud migrations, data backup, and more. Today we’re talking about Disaster Recovery 101: Could your Business Survive a Fire or Hack? Welcome, Nathan.

Nathan Sirois: Hey, John. Thanks for having me.

What Disaster Recovery Really Means

John: Absolutely. Nathan, when business owners hear disaster recovery, what are some of the types of events that they should be preparing for?

Nathan: Well, basically, if we’re talking about a disaster recovery situation, we’re talking about systems down. So an immediate level one, this is a top priority, needs-to-get-fixed sort of scenario for your organization. We face these all the time, stuff happens, things break, and you need to be able to recover from that or have another solution in place for your organization when there is a disaster.

And one of the main things I was going to focus on in discussing this topic is just how does your organization protect against a disaster situation, especially when it comes to redundancy and having either alternative solutions in place, alternative ways of dealing with your normal day-to-day tasks when a system goes down, or just having something to turn to to make a change, if the way you’ve been using something isn’t working anymore.

Fires, Floods, Ransomware, and System Outages

John: So these events could be kind of a natural disaster type of scenario, like a fire or a flood or something like that, but it could also involve a major cybersecurity attack, something that takes down your whole system, right?

Nathan: Yeah, it can involve quite a few things. Your disaster, it could be a hacker fully ransoming your organization, and you might not think of that as a disaster recovery scenario because your systems are still operational, but now any additional data you add into your systems or changes you make, either the hacker, they’ve got complete control of that or they can directly maliciously affect the work that you’re doing. So even in scenarios like that, it is really important to see that recovering from a disaster can mean a number of things. It’s not just your server goes down, your backups fail, what do we do? It can be a large number of things and your organization needs to be prepared for any and all of them.

Identifying Critical Systems to Restore First

John: So what are some of the business systems and information that a company should identify as most critical to restore first after an outage or a security incident?

Nathan: That all depends largely on your specific organization. So when you think about it, which systems when they go down are really going to negatively impact us? Is it some big database that we have? Say you’re an engineering firm and you’ve got your specific projects that you’re working on and if you can’t access them, then you can’t do any work versus maybe you’re some sort of CPA or accounting firm and you have a bunch of different web applications that you need access to for the different accounting stuff that you’re doing. And if those systems go down, do we have a backup? Do we have another way to do the work that we need to be doing?

So, it all depends on your organization, and it really takes some careful thought to think about what systems do affect me the most on a day-to-day and, if I’m having issues with them, what am I going to do to then be able to continue working or to recover and get those systems back up and running as quick as possible if I can’t do my work other than using those systems?

Why Backups Are Not a Full Disaster Recovery Plan

John: Why is having data backed up not necessarily the same as having a full complete disaster recovery plan?

Nathan: So the difference between just having data backed up versus a full disaster recovery plan largely has to do with having an actual RTO, which is a Recovery Time Objective. So I could have a backup solution in place on my server that I’m paying 10 bucks a month for, and I could have terabytes of data, huge amounts of data, on this server that then…say my server goes down and I say, “Okay, I’ve got this other workstation or server that I can put the backup on” or “I can get my server rebooted and run the backup.”

It sounds well and good until you realize that that product you’ve been paying 10 bucks a month for takes a week to restore your backup. So really realizing where you need to be able to recover quickly and how to purchase the necessary hardware and software to meet those time objectives is essential to a backup plan that is an actual foolproof disaster recovery plan.

And that goes beyond just data, any sort of cybersecurity hack that you undergo or natural disaster to your office, anything like that, really addressing where you need to be able to recover within a specific time period and how you’re going to be able to do that is essential and it’s worth both the financial and time investment to figure that out.

Setting a Recovery Time Objective (RTO)

John: So how do you figure out what that RTO should be, that recovery time objective? How can a business determine how long it could realistically operate without access to critical systems like email and files and financial systems or phones or maybe some industry specific software that they’re using?

Nathan: Yeah, it all depends on, again, your industry and just thinking about “what tasks am I doing day to day, what tasks are week to week, what tasks are month to month, and what solutions do I need running to be able to complete them?” So it does take a pretty careful look to have a comprehensive disaster recovery plan into what you’re doing on a day-to-day basis. And the best way to go about doing that is to start from the top down of seniority of these people that are running our organization, what do they need first?

So the CEO, maybe they need access to this one specific platform that only two or three other people in your company need, but if that person doesn’t have access to it, it’s immediate, all flags are up, we need this fixed as soon as possible. And then you’ve got some sort of data storage device that 15 people use, but maybe a lot of the data, it only is needed week to week or the data itself has a backup somewhere else that can be accessed another way.

So it’s really important, in addition to just thinking about the specific usage and how many people need to be using something, who are the people that are using systems? And it could be a disaster situation like what I mentioned before, if the CEO’s access to this system breaks, that could be a disaster that needs to be recovered immediately. The system might still be up, but maybe you had some licensing expire, maybe that person had some sort of change on their machine and now they can’t access whatever.

So it does go beyond just the idea of your entire organization being crippled with one event. There’s a lot of small ways that you need to be able to recover in a lot of large ways, and it’s important that your organization is looking into all of them to make sure that you’re covered, both from the standpoint of being able to serve your customers well, and also your staff and any other people that are relying on your organization.

Testing Your Disaster Recovery Plan

John: What should business owners do to test their recovery plan and make sure that it will actually work before a real emergency occurs?

Nathan: So for the most part, you’re going to have to be manually testing a lot of things or at least running programs that can test system outages and different things for you. And a lot of times systems are playing into other systems that are playing into other systems. So it’s important that you have somebody who can really tell you, “My email’s going to go down. How do I recover from this?” Or “let’s see how long I can survive without my email.” And you might not realize, “Oh, if my email’s down, then the CRM system I have plugged into this is going to break.” And then maybe that affects even my payroll or some sort of time tracking system that I have in place.

And so just really having somebody that’s able to not only work with you and say, “What systems are connected to this,” but also directly being able to technically see, “Hey, this is broken and it’s giving us errors that this other thing isn’t working.” And so actually testing out your disaster recovery plan, you might realize that there are more interconnected systems than you thought, in addition to just realizing the actual time objectives for recovering from certain scenarios.

So it is really important to be testing regularly all your critical systems, just to be seeing how things are interacting and if something does break, how are we going to fix it? And just being prepared for that.

How Interconnected Systems Affect Recovery

John: Some software systems now are utilizing, rather than a password system, you log in with your email and then it sends you a password in your email and then you use that password to get in. So if your email goes down, you might not realize that, “Oh, that means I can’t get my password now in order to get into my software,” and then things start to kind of spiral from there. So like you said, you need to work through those scenarios and have somebody helping you out to try to figure it out. You might say, “Yeah, my email’s down. That’s not a big deal. I can live with that for a little while, but I forgot that affects this, and this and this.”

Nathan: Yeah, exactly. And it does take that manual effort to figure all that out, and it’s important that you do it well. So it’s important to really thoroughly go through your disaster recovery plan and make sure that your organization is protected.

John: All right. Well, that’s really great information, Nathan. Thanks again for speaking with me today.

Nathan: Absolutely, John.

John: And for more information, you can visit the Balsam Technologies website at balsamtechnologies.com or call 978-281-3339.

Get down to business, and leave IT support to us!

Stay in the loop by subscribing to our monthlyTech Tips & Trends newsletter! Just the good stuff!

Error: Contact form not found.

Balsam Technologies Inc., 12 Blackburn Center, Gloucester, MA 01930  •  978-281-3339