so uh moving on talking about you know different ways to get your cloud journey started i think that really segues really nicely into the next discussion here which is really about disaster recovery as a service and what can be done with disaster recovery as a service to mitigate some of the risk from this really hot button item that we've been hearing about so much lately in particular around ransomware and other forms of cyber threats and joining us for this conversation is ben miller i've had the distinct pleasure of working with ben for nearly a decade
now and i've got to say with full confidence there is no one better out there to be talking specifically about resiliency disaster recovery backup as a service uh ben has designed these solutions and you know they've been recognized throughout the industry by folks like gartner and and forrester um as a leading solution and i know you know ben is is above all that he's one of the nicest folks you'd ever hope to meet so really excited to have him on the call today and ben i'll let you get things going thank you chris uh and
there is no better hype man than chris so i appreciate the setup big shoes to fill um no that's a great we've got a uh just a small piece of time here so i want to make it most valuable to you all listening um as chris mentioned the the big theme here about my section is to talk about disaster recovery but uh ransomware is very top of mind this poll you you you've told us in the community if you look at the tiered risks over here on the right you'll see ransomware is number one on
a lot of people's minds and no doubt because it is a new and very insidious okay maybe not so new but it is an insidious form of disaster that comes into our environment previously previous generations of i.t uh was used to designing around high availability in disaster recovery for infrastructure natural disaster human error type of problems not a targeted necessarily ransom holding type of attack so this is something that's top of mind for a lot of people and just to be clear at innervision we talk about ransomware as a type of disaster this is uh
it is a disaster i ask anybody who's seen it but it takes a different kind of recovery and we put this under our umbrella of disaster recovery as a service because we design for this scenario now i also want to be fairly clear that the recovery aspect is just one small part of the portfolio of solutions that should be thought about in protecting from ransomware you need protective detection remediation response there are a lot of layers to making sure the best of of possible that your organization's not impacted by ransomware i'm going to talk specifically
about the recovery aspects of things so if and when this occurs within your organization what is it that disaster recovery can do disaster recovery to the cloud can do that can uh you know mitigate this disaster so to do that i'm going to talk about a story and we've been talking about outcome based what does it feel like to be a customer of inner vision what is the result for your business well i figured a great way to do this would be to tell a story and this story is one of our customers we'll call
her janet one saturday night about eight o'clock when all was well on the weekend she received a call from her team and alerts were going off things were down servers were down they were offline and the news was bleak ransomware was in their environment this was live this was happening this was the worst case scenario so she began to work with the team set up the incident uh line start the procedures for response uh however before she was able to dial into that incident line she actually got a call from intervision saying we notice there's
something wrong in your environment that you're replicating to us and we wanted to see if you need any help this was from our end we saw something was falling off the rails and reached out to her and she said no wait uh give me a minute to get my assessment going but stand by and that kind of gave us the ready five flag to get the get the troops in order and get ready to respond uh to a situation so she got on the call and found the damage was pretty thorough and devastating there were
about 40 terabytes of data throughout their critical file shares and application servers that were all encrypted and offline they were getting the ransomware screen things have been deleted things had been infected and the calls were starting to come in from the end users saying hey what's going on um and she knew that would continue because even though it was eight o'clock on a saturday night there were people that worked seven days a week around the clock in this organization now the good news was they were able to isolate and identify the active malware get it
stopped and identify what specific servers were infected but they needed to be able to hold on to all of that data and all that environment long enough to get the forensics that they would need to turn into their insurance as well as any kind of law enforcement or other type of involvement so they needed to keep a lot of that infected data in their infrastructure they were still down at this point so she called back in her vision and said okay here's a situation she described the scenario and talking back and forth with the with
the recovery team they said okay yeah i think your best solution is let's get this recovered and they pulled the trigger on getting their environment recovered into cloud now the recovery team brought the entire infrastructure back online in an isolated bubble in 10 minutes all of the servers all of the data everything that was affected was in a bubble at a point in time right before the ransomware balloon and they were able to go into that bubble and determine by running the appropriate tools those were clean servers those were not infected they were ready to
go and so they committed and said go and so that rearranged the routes and the dns components so that end users were now connecting to the dr center in less than an hour that entire company was back online and working 40 terabytes of data all the critical applications the user and end user routing and communication anybody who connected in after nine o'clock that night they had no idea anything was going on now working with innervision janet and her i.t team essentially ran in a hybrid state for the next couple weeks they were able to identify
servers that they wanted to bring back that they wanted to leave running in cloud make sure things were cleaned up be able to delete the capacity you know delete the infected components from their side so there was capacity to bring workloads back and after two weeks they committed a a planned uh planned maintenance window to roll the environment back to their production data center and they flipped the switch and they were back online 14 days later as if nothing had happened now that's a pretty happy ending to that story and the business owners told janet
they've been paying for this service for three years and every penny was worth it because they essentially had one hour of downtime from a ransomware event from an event that has taken businesses like theirs out completely that they didn't return to business from that activity and they had one hour and that's an outcome based that's what we designed this for that's what we build this for that's our passion about the disaster recovery experience when you're working with innervision so let me talk a little bit about the components of why this was successful they had protected
their data and it was off-site so all their eggs were not in their basket and this is where the whole conversation of cloud where's a great place to put it off-site uh proactive monitoring and detection they had detection in their environment so they were able to detect this while they were dealing with it they had a familiar recovery team they've been working with innervision over the last three years they've been practicing this they knew the team and they could have a conversation say hey is this a quick thing is this you know they could talk
a little bit about what the scenarios looked like they had an up-to-date playbook because they've been testing their playbook at worst case would have been six months old uh in this case it was only a couple months old they knew they had a playbook and i call it a playbook because it covered infrastructure routers outages ransomware outages human error type of scenario so it's more than just one run so they had a playbook that was up to date and it was ready to go they had practiced it and this to me is that one of
the biggest things they didn't have to dust off a binder and say hey is this going to work they were able to go hey you know hey we're calling play x and we practiced that you know a couple months ago we're all familiar with it and let's go they had a team to run recovery this this is a message that you have heard a number of times on the summit already about focusing your internal resources on the strategic and letting somebody else take care of the keep the lights on projects this is one of those
examples where they were able to focus their uh internal i.t on taking care of their end users and taking care of other aspects of it while the intervision team ran the recovery the invision team brought that infrastructure running up in cloud and they didn't have to take those resources off talking to their end users or or working through other issues that they were facing the cleanup and they were running in a production quality target where they had elasticity to grow and shrink and and and all the resources of availability so they weren't urged you know
they weren't in a a press to get out of uh the dr they could do that at their uh you know at their leisure and they had a fail back plan again going back to that playbook rather than a run book one of the plays is how do we get back home so they had all that laid out and that's why this was a successful thing now that sounds like a lot of work that sounds like a lot of stuff but that's where i really push a fully managed service for the disaster recovery because having
a target in the cloud is fantastic there are great software tools there's great technology out there to put your data someplace else to replicate it but what that doesn't replace is all of the know-how the effort the practice uh the the people hours to make this a living and executable situation so that's why this was a successful play and that's why i i really encourage people to leverage a partner to do that managed recovery now how does this strategy start with and another message that you've heard on this on this today is about this is
a business problem not a technology problem focusing on the outcomes of the business so that's our you know the number one place to start here is is business uh support and guidance starting at the top finding out what is critical to the business to have online it has a lot of great ideas about that and probably intuitively understands based on who screams the loudest when something goes down what is most critical of the organization but getting that guidance about what is critical also establishes what the business is willing to invest in mitigating risk against that
and how fast that needs to be up uh you know those are critically important everybody wants it up all the time 100 percent of the time that's just not a reality in our world we can get really great you know nines in terms of uptime but you know there are no perfect guarantees that's why there's disaster recovery in existence so once you have that business guidance and definition getting into the rpo and rto defined we actually work with our customers to go through what we call our recovery assurance approach to continue the design and build
and execution of this disaster recovery and i encourage you to think about this even internally whether you're doing a managed service or not these steps are excellent for making sure that you are you know are set in a good situation and so i'm going to talk about these we've already talked about getting your business goals we've talked about your project scope and design or we're going to talk about that that's the next step architecting to how that solution fits what the business is told is the criticality and that's understanding the uptime requirements etc then moving
into that playbook development that playbook development is that uh creating those scenarios designing how that comes up who's involved orchestrating etc all based on those requirements it's not just a boot log it is a living document that is executed and practiced and then testing i've talked about that i'm going down the bottom of the circle here recovery testing we encourage at least twice a year some people do it quarterly some people do it annually whatever again aligns with what the business is and then the health and operations of that just like your production environment or
your most critical applications are living and breathing so is the dr plan to accommodate them so making sure that this is being monitored it was this monitoring that caught the situation that janet was faced with and then the same with the operations making sure that it's not sitting on three-year-old hardware somewhere that's been deprecated or end of life etc that this is a a clean a solid a secure environment that you can recover in and that it's that it's operated well and finally managing the event if and when it happens we're looking at the orange
circle on the right being able to have that actual failover have it execute their run have people to support you in operating in that situation if you're going to the cloud your team may not be very familiar with the cloud infrastructure cloud ecosystem if that's not where your production lives so having a partner like intervision who can help maintain and manage and run your environment while you're there is is critical as well and the final and most forgotten arrow is the bottom orange arrow when you come back having that plan having the expertise and the
design to make sure that you can fail back to your environment i'll talk a little bit more about deeper about this in a moment but there are as we got into that bottom left circle about architecting it there are three things that we kind of ring the bell over and over again about making sure our part of the design so that you can have a successful recovery in the face of ransomware ransomware that likes to hijack credentials that likes to encrypt data that likes to actually seek out and delete backups and dr data actively to
hold you hostage to pay the money so what we talk about is making sure that architecture has multi-factor authentication built in uh credentials that have mfa that require something off of your you know a number off your phone or a dongle or something are going to be stopped from hijacking credentials and and deleting or messing with your systems having an air gap built in so that your data or your cr or your authentication for your management are air gapped in such a fashion that if your production environment is compromised that there is not a way
that it can roll over and easily delete your backups you know the uh one way to look at that is if you think the the old style of shipping tapes off to some place that was a literal air gap there was air between production and your backed up data in modern world that could be perhaps sending it to a different cloud with or a different account or something where there's a control plane or a means that nothing in production literally can touch or delete the data that's being protected and then finally immutability using that last
example if you send off to the cloud you know ticking that immutable bit having a write once read mini copy of the data such that literally there is no way that the data can be deleted until it is expired uh even if you're on the phone with somebody at the cloud provider saying no please delete that data you have to wait it out and that's that way for a reason so that the data can't be hunted down and deleted as part of ransomware infection so we hit on those three pillars as part of that architecting
and design moving on to the next slide i'm going to talk a little bit about the way we address some of these in the in the tiers and essentially we help customers break up their applications based on those business requirements into different tiers we know this is a way for a lot of customers where there's workloads that need to be running as part of production to help with failover those could be vpn it could be active directory they could be database clusters etc and we categorize those as a d-res run but we also because we
know that they're in a credential plane with production we also know that things need to be backed up or snapshot or protected behind the scenes so that they can't be compromised from a ransomware attack in production draz ready is for those workloads that can have boot time recovery that can have a very short window of lost data and a very quick recovery and back online and we leverage long logs retention logs so you can recover to any point in time within the last week or so to bring something online prior to an infection or an
attack and then the dras restorer uses part of your backups for the purpose of recovery using a 24-hour rpo or rto from your backups to be able to restore things that are important they're just not as urgent and using immutable data repositories for these so they can't be backed up now it could be misleading on the same slide but having baz a backup as a service for your archival data can be part of your recovery plan for all of the rest of your data that may or may not be needed especially if you're running in
dr for an extended period of time so we help create this spectrum to help break out and assess the criticality of your data and put them in the right place because as you can imagine the dollar signs from the left are much bigger than the dollar signs on the right and you need to find the right match with that business alignment that we talked about to start with all right so that's a whole real quick flyby i could talk for an hour about that or more chris has heard it all but i just want to
point out that this is about what the experience is for the end user the ability to have absolute confidence that if something goes wrong when something goes wrong that they can recover and you can talk to our customers you've heard a number of them on the on the summit today talk about their experience with us in g2 crowd and pure insights kind of uh yelp for it if you will we have five star reviews you can go check those out yourself you can see what our customers are saying about why and how they value what
we do for them in that disaster recovery as a service you can also see the note here from royal technologies that goes back to some of the conversations that people have brought up about that first step into that journey to the cloud if you're not in the cloud already the ability for them to be able to say we are shifting that direction you you heard about land of lincoln as well they were looking at shifting the direction of leveraging the cloud in a powerful way and one great way to break that isis with a disaster
recovery implementation with a partner who can provide managed disaster recovery and transition that into what you've heard with omron that fully managed experience as you as you do that journey so even if you're just dipping the toe to start with a disaster recovery or you're going at full length leveraging the cloud for this is is very very powerful in leveraging a partner and essentially you know to close it out why using innervision dr to the cloud cloud is elastic it's it's huge and it's a excellent use case for our proven guaranteed tested and documented disaster
recovery as a service that gives you that outcome of 100 confidence that you are going to be able to recover when you need it awesome thank you so much ben and yeah i think um you know a big takeaway from me and i've heard this from several clients is that disaster recovery does really represent an excellent first step use case you know it's so often that we we know the capability of cloud and what could be done but it's like where do you even start and of course you know there's you've got to keep your
day-to-day operations rolling as well and dras and dr in general backups in general represent a great use case we we hear that from our partners as aws as well as that's one of their leading use cases so thank you so much ben for that conversation and definitely appreciate your expertise thank you