Hello, everybody. And welcome to this lecture. We're gonna be talking about disaster recovery here, and there should be a short one, So let's go ahead and dive right into it.
So when we're talking about disaster recovery, what we're talking about is after something bad happens to your organization or server, or maybe somebody stole something ends the office. You want to be able to recover after a disaster,
you wanna be able to get your operations back up and running,
get that computer operational again. Maybe you want to call the cops and be able to recover whatever was stolen, things like that. Bad things tend to happen once in a while, and you want to be able to have a plan in place on how to respond.
And so that's kind of what disaster recovery is. It's just that plan and having an understanding, our dialogue and maybe some documentation that that lays out what everybody's supposed to dio based on their roles are based on who they are as a person
in order to respond to these problems.
And when we're talking about disaster recovery, some things that we need to really keep in mind of at least for the eight plus Anyways, our backup strategies. Now,
um, we're gonna talk about all that right here. But I wanted to take a moment to address system level image ing. And what I'm talking about is, you know, if you if you're dealing with servers or you're dealing with work stations that are valuable there Ah, long standing, You know, maybe you need access them frequently,
and you've been accessing them for many years.
They may hold e mails or certain files or programs that needs to be backed up in its current state. Maybe you vested
20 hours setting up, Ah, workstation. And that work station is gonna be used as some kind of sharing location. Or it's gonna be used to run this very specific application. And instead of having to re invest all that money and time into setting up the system again,
you just want to be able to take a snapshot so that in case something bad would happen to it will say the hard drive crashed.
You had a backup of it, and you could just, uh, spin up a new computer or reinstall or set up a new computer with the with the snapshot or with the backup from the original one. And that's really what hyper visor snapshots are. So
hyper Visor is actually a virtual machine. It's a virtual computer, and when you take a snapshot of what you're doing is you're taking a, uh, a snapshot of its current state's ATT, the entire system, entire virtual system,
the operating system, the programs, the settings and everything. And you're storing in another location in case that hyper visor were to go down and you need to spend it up again
in case that virtual machine were to go down and you would need to, you know, spend it up again in the future.
Um, it gives you the ability to recover the entire system and makes a duplicate of the system and a lousy, restored and other locations that you can always spend up again later.
File level imaging is another way to store on Lee the files, so you're not taking as much information and storing it. You're just duplicating it, um or, you know, storing in another location in case the hard drive where to be wiped out and all the information on it were to be gone.
You could just buy any hard drive and copy all the files from let's say the cloud
and put it back on the hard drive through hard drive that you that you that you need to to operate your local functions. So, you know, this includes simple duplication of files. They're not necessarily used for all system files. That could just be for project folders. Like if you're working on a big in design project, O r
Adobe illustrator Ah, graphic design stuff. Those files can be quite large. Sometimes you want to back them up in kiss
your laptop or to get stolen. And you know you buy a new laptop, you're going to move that the data back over into your new laptop
and then you can go in and pick up and continue working where you where you left off before you had your original laptop stolen.
And you know, part of the file level imaging also includes folders as well, so you could be folders and files and store them all in the cloud. And that could be part of your backup strategy.
Talking a little bit more about hardware specific backup strategies or Ah, at least, uh, data are at least disaster recovery strategies. Ah, ups is really handy because it's an un interruptible power supply
eso whenever you lose power and your organization, maybe you had a streets outed to blackouts or brownouts or power surge.
Uh, you may not want the servers to lose power because they may be processing information. That's if you were to lose power.
You lose all your progress. And that's disastrous because sometimes those you know, this processing can take quite a bit of time.
A UPS is a good backup medium. Usually they can run for 24 to 48 hours, depending on what you get,
and they can run on battery or on gas. There are different types out there. They're kind of like a generator. If you if you've ever been in like some kind of natural disaster situation, and you have to go buy a generator to keep the power on, or at least keep your fridge running. This is the same concept you're keeping your server and your computer's running,
and you're also able to protect those very expensive piece of hardware from power surges
by having the UPS kick on and interrupt any bad power surges that could be going through your local electricals circuits.
So there's different types. You got your standby ups. You got your line interactive and online ups. The last two, you know, they allow you to, ah, have a connection to the Internet, and then your standby ups is more of the standard one that I was talking about, where he just waits
for the power to go out before it kicks on and the battery is activated.
Um, there's probably not give me too much information on this exam regarding ups, but I wanted to make sure to mention is that way you're familiar with its and less been on least cloud storage is another one. That is, uh, it's actually more more standardized these days for disaster recovery.
I allows you to store your programs and your data in the cloud and another part of the world, or maybe another part of your country.
And that way, in case the you know your organization were to be compromised for whatever reason, let's just say,
um, you know, you had a huge fire in your office and all your servers are melted where they all caught on fire, and the date has been gone. You can still have a data stored in another location, and whenever you're able to build your infrastructure backup, get into a new office. You could move that data from the cloud
back over into your local on promise servers. So
that's the topic on disaster recovery. Pretty straightforward. It's really just a plan for when bad things happen and there's a lot more to it. There's a lot more other, you know, other solutions for disaster recovery that are out there. But these are the more popular ones that I wanted to make sure to bring to your attention. If you are interested in it more,
I encourage you to check out my courses on Cloud eight of Us Cloud.
They talk a lot about disaster recovery and the different types of features that are in the cloud for you to incorporate into your on premise. Ah, organization. You're you're processes and and what you're doing in house, all right. And that about wraps up this lecture. I'll see you guys in the next one