Today, we're talking about protecting cloud infrastructure.
Like infrastructure as a service pass and SAS.
We hope you make sense of the differences between these very similar acronyms and
what parts of each need to be backed up.
If you've ever wondered if your pass or SAS product needs to be backed
up, you've come to the right place.
Hi, I'm w Curtis Freston and they've been calling me Mr.
Backup, since I wrote the first book on the topic over 20 years ago.
I've dedicated over 30 years to making sure that people like you
keep your data safe from accidents, disasters, and cyber attacks.
My podcast turns on appreciated backup admins and to cyber recovery heroes.
This is the backup wrap up.
welcome to the show.
I have with me the guy who makes me sweat.
Prasanna Malaiyandi.
How's it going?
Prasanna?
I'm good, Curtis.
How are you doing?
Are you get that?
Sweating is good.
They say it helps release toxins.
it helps you lose weight.
It helps you feel healthy and more alive and
know if I felt alive after our walk this morning.
yeah, for those who don't know, we live 400 miles apart, but we
go on walks together, via this
little device here in my air.
Just like we do
the podcast.
We are not in the same room.
We're not even in the same county.
Walking is good.
And I think the reason that you built up such a sweat today was I was a little,
just a tiny bit delayed in joining
15 minutes delayed, sir?
Sir?
I think it was actually like, yeah, it was, it was 15 minutes
plus you started 10 minutes
early.
And I think you mentioned that you were going to wait till I called you
to turn around and start walking back.
So yeah, so that
added
up.
Yeah, I walked one direction and I wasn't gonna turn around until you called me.
So I did, but I did a good walk, did a good walk today.
so let's stop talking about sweat and start talking about industry news.
We have, I think a very apropos story that comes to us from Denmark, the,
Danish hosting company that lost all of its customers data, or at
least the majority of its customer data after a ransomware attack.
What do you think about that?
It's sad when these things don't shock you anymore, you know, you've sort of been
acclimated to it, which is sad, right?
But I'm not surprised as we've seen, and we've had guests talk
about this in the past, right?
Ransomware isn't dying down, right?
It's just getting worse and worse.
And people are going after these larger targets, if you will, right?
More Centralized, right?
Rather than necessarily going after like mom and pops and all the rest.
And a service provider is like the perfect place to go attack, right?
Because you have all these customers, data, all in a central place, right?
They're offering services, it's probably business critical
data, all the rest of that.
And it's like, why not go after them?
And that way you're negotiating with the service provider if you are trying
to get ransom out of them, right?
Getting them to pay versus dealing with every single end user out
Yeah.
The article mentioned that, this has been an, another new tactic by the ransomware
folks, because by attacking a hosting provider, you create not one victim,
but many victims, any one of which you could potentially go and, get them to,
pay you a ransom in order to recover.
Yeah, it reminds me a bit about the Rackspace attack
that happened last year, right?
Where they did target a very large service provider, right?
Hitting their exchange environment,
right?
And it's the same sort of things.
It feels a bit like Deja Vu, right?
yeah, exactly.
We encourage people that when they're hacked to tell people what happened.
And there is a, what happened section in a page that is in Danish,
but we have translated it via the, wonder of Google translator.
And what happened was they were in the middle of a server move and they, there
was a previously unknown infection.
And during that server move, they were temporarily connected
to, an administrative network.
And that allowed the hackers to gain access and infect the, backup systems.
And then via the backup systems.
They were able to, this is one of the things we talked about many times
that I know in recent episodes where we talked about that you really need
to focus on the security of your backup and recovery system because.
it is the goose that has the golden egg, right?
It has everything.
Or Crown Jewels, whichever way you want to think about it
Yeah.
The crown jewels.
Yeah.
basically it's one place.
It's like they got the golden egg within the golden egg, right?
They had the, this is the backups within the hosting provider that creates
multiple, victims, but basically.
I, I will say this, I have to admire the company because they're saying
they are refusing to pay the ransom, even though this quite possibly will
have significant, negative damage to the company because they don't
have any backups of anybody's data.
the craziest part was where they were suggestions for you to re, to
rebuild your own website that actually pointed people at, the web archive,
which is just the way back machine.
Yeah.
that's just fundamentally wrong.
So just two things to also add to this new story quickly.
I think one is the article I think that you had referred to earlier
was found on Bleeping Computer.
So if listeners, you want to go read more about it, go there.
I think the other thing is it is mentioned that there are two companies that got
hit, but the two companies actually belong to the same parent company.
So there is that aspect as well.
So if you do read that, Hey, there were two Nordic companies that got hit.
They are Owned by the same company.
Gotcha.
and the good news category, we have the fact that Windows 10 is now going
to have a built in backup, the built in backup features it looks like
that were already in Windows 11.
Microsoft was using that as a, has anyone in the history of computing
migrated to a new operating system because it had better backup software?
Of course, Curtis, that's the first reason to migrate.
but that's what Microsoft was thinking, that people would upgrade
to Windows 11 because it had better backup, and it's just not happening.
People are still hovering on Windows 10, and so they decided to add
these and they're saying that most of the functionality was not new.
It was just all put under a single umbrellas to increase ease of use.
And then there was some new functionality.
So that's,
don't know if you've ever tried to use backup in Windows 10, but it is awful.
is this, what is this windows thing that you speak of?
I'm sure you, so I have one Windows, no, actually I have two Windows boxes at home,
but yes, for both, which I rarely use.
And most of the time it is powered off just because of.
Ransomware and other things like that.
But yeah, so yeah, anytime I try to get in and figure things out, I'm like, oh
my God, I just want to shoot myself.
Just make it simple.
Yeah, absolutely.
I think this sort of the earlier story gives us a perfect segue
into what we wanted to talk about.
This is another part of our Backup to Basics series, where we review,
basically stuff from the book, Modern Data Protection by the book,
I mean, my book, from O'Reilly.
And, we're looking at chapter eight, so first we've covered sort of traditional
data sources, sort of servers and VMs and databases and things like that.
Now we're starting to look at data sources that are relatively
new, comparatively speaking.
And, so the first thing we're going to talk about is the public cloud.
is that a thing?
What is a public cloud?
Yeah, what is a public cloud?
Because, honestly, if you take 10 people on the street, right, IT professionals,
they don't have to be on the street because they don't have jobs, but
just you find them somehow, right?
and you talk to them, and you'll ask them, what's a public cloud?
I bet you, you will get a half a dozen answers.
Yeah, I think so.
I still.
Remember the first time I asked someone else, it happened to be Steven Foskett,
I asked him what the, I remember we were having lunch in Manhattan, I still
remember this, the first time I asked that question, what in the world is
this cloud thing they're talking about?
And, there is no such thing as a cloud, just somebody else's computer, right?
that's basically what I always tell people.
And the big thing, when...
When we're talking, the big thing I want to make sure that people
understand is this stuff still needs to be backed up, right?
Everything needs to be backed up.
The question is.
Who is doing that backup?
Cause the answer is not always the same.
and, even if...
You do figure out who is responsible and it's not you, you may still want
to back it up in some fashion to avoid the new story we talked about
Exactly.
So let's first talk, so let's look at the different parts of the public
cloud and just talk about that.
And the first is, the one that I hate the most to say as an acronym, cause
it doesn't, you, I as that doesn't.
Just doesn't, infrastructure as a service.
what would you, how would you define that?
In my mind, that literally is whatever you were running on your physical,
like your applications were running somewhere on, in your own data centers.
It needs to run somewhere in the cloud.
All you're doing is you're hosting those applications on infrastructure
that you are renting, borrowing, whatever you want to call it from
the public cloud provider, right?
So this is, if I look at AWS, these are like EC2 compute instances, right?
So I am borrowing Infrastructure to host my application.
It's probably EBS volumes because data needs to be stored on something
Yeah.
I would say I would include S3 and I would include the networking
that's part of it as well.
Basically storage, compute, and networking that you're renting.
Is that, that seem about right?
And so here's the question.
What?
Did you have something?
which in the past was a great first step for a lot of people trying
to figure out how do I go from my data center to the cloud, right?
Because in.
Your mind, right?
It's just an easy lift and shift.
Whatever I was running on premises, I just rent the infrastructure and
then I just run my applications on it.
It's not a real big, heavy lift for me.
I'm not changing any applications or code or redoing things.
It's just whatever was running here is now running there.
Yeah.
and just so that we're all on the same page, let's, because we use
this term lift and shift quite a bit.
and I often use it pejoratively.
Can I put Lee at the end of pejorative?
I think I can.
I use it in the pejorative sense.
And because I'm not a huge fan of lift and shift, right?
it's a good like toe in the water.
It allows you to start using the public cloud.
It is a lousy way to use the public cloud.
If all you do is take your VMs on prem and move it to VMs in the cloud.
Why do I say that?
Because you get some of the benefits and all of the badness, right?
That basically you get, you basically, it's a really expensive
way to have a data center, right?
and so there's all these people that did this big lift and shift and
they moved everything into cloud and they stopped using VMware and now
they're using EC2 and then they're like, holy crap, this is expensive.
You're like, You went from owning a car to renting a car and you're
still driving it 24, seven, it's going to be expensive to do that way.
The alternative is to do what's called refactor, which is, actually
programming to the hundreds.
Of services that Amazon runs and not just Amazon, but other providers,
other services that they run, things that are, you use on demand and you
pay for them as you use them rather than a server VM that's running 24
seven, regardless of what it's doing.
Anyway, I stepped down off my soapbox.
I like what you talked about people being surprised by the cost aspect.
And one of the things I just wanted to plug is, if you follow
Corey Quinn on Twitter, I think he's part of Duck Bill Group.
He does an amazing job of breaking down public cloud costs and why
you should be careful when you are doing lift and shift to the
Exactly.
It's a good resource.
does this need to be backed up,
Of course.
is The data
important to you?
yes.
I'll give you a clue.
The answer is always yes.
So here's a question.
Let's talk specifically AWS, because you and I have spent a lot of time in AWS.
it's not the only cloud provider, it's just the one I
have the most experience with.
If you have EC2 instances, Are they backed up in any way if you don't do anything?
I do not
I don't think so.
and when you talk about EC2, remember EC2 is just compute.
You need to actually attach a volume, which is an EBS
volume, in order to actually
right.
Really what
Right?
And I
the EBS volume that's behind that.
And yeah, it is my understanding that with EC2, If you have a VM, literally nothing
that anyone would literally nothing like it's not even, there's not even something
that maybe someone consider a backup, but others would not, there's nothing right.
You are 100 percent responsible for that.
Exactly.
Yeah.
Unless you do take advantage of things like EBS snapshots.
to you.
The tools are there.
But my point of making is specifically with, again, this is just speaking of EC2.
I think it's actually the same and other.
like Azure and GCP, that specifically VMs, they're assuming, you're running
this thing, you're in charge, right?
there are two ways to back up a VM in the cloud, right?
You can use the built in tools.
essentially, they call them snapshots.
I don't like to call them snapshots.
They are actually image copies.
It's actually a copy of that drive made to another location.
In the case of AWS, it is, it's in S3, right?
EBS snapshots are stored in S3.
So they're stored as an object and you can do incremental snapshots, right?
then what do you do once you've done that?
So since the EBS snapshot lands in S3, right, you get all the benefits
of S3, right, so it is replicated within three availability zones,
right, the only downside is, Right?
That's just one copy.
You still want to follow the 3 2 1 rule, right?
So you want to make sure that that one copy also makes it into a
different region, a different account.
So using S3 technologies, you can make sure the image copy that's in
S3 in a local spot gets replicated to somewhere else in a different account.
So you get protected as well.
exactly.
Codespace, Codespaces.
That's all I'm going to say, right?
Codespaces.
com, read that story.
That's why.
You've got to put it in a different account and a different region, right?
That, that, that's the way in the cloud.
That's the way you comply with the 3 2 1 rule, right?
Veeam likes to turn it into 0.
I don't like to do that.
I just like to say, listen, just properly follow by the 3 2 1 rule that says
having multiple things on different, the idea of the two is having it on two
different things that have different.
Risk profiles, right?
So put it in a different region.
And also the one, I think the truly one is to have it offsite, not
only to have it in another region, but to have it in another account.
So if you're one main account of Compromised, then it's not going
to, it's not going to be over there.
And maybe for listeners who may not have heard us talk about 3 2 1 rule
before, do you want to explain what the
3 2 1 rule is?
yeah.
if, yeah, thanks.
So 3 2 1 rule is just a rule of thumb that was coined by somebody who we
actually had on the podcast, Peter Krogh.
he's a digital photographer and he just said, you want to have three
copies of every piece of data.
He does see the first, the original is one of those copies.
So then the two of those three, two of those, you want them to have
them on two different risk profiles.
He's talking about maybe two different kinds of media.
and in this case, we're saying put it in two different regions.
some people like to take that to the point of saying, we're going
to put one on disc and one on tape.
I don't have any disagreement with that.
and then the one is, making sure that one of the copies is offsite.
In the cloud, there is no such thing as offsite.
So that's again, why we talk about a different region.
And I think the different account is.
gets added to
mainly today we use the 3 2 1 to show things that aren't backups, right?
We're gonna get to that in a minute Things that definitely are not backups.
Alright, so what's next?
We're talking about PaaS.
What is PaaS Prasanna?
platform as a service, right?
And I think this evolved because, okay, IaaS was the first level,
the base level, if you will.
And then people were like, that's too complicated, right?
It basically doesn't help simplify my management aspects, right?
I'm still managing infrastructure.
I don't want to have to deal with that.
And so PaaS was built on top and it's more platform as a service.
So these are things like.
You'll still be managing and deploying your applications, but you don't
have to deal with all the underlying infrastructure and figuring out
how many EC2 instances you have to spin up and everything else.
So an example of this would be AWS RDS, which is their database
service, which allows you to say.
Provision for MySQL or Oracle, right?
or Postgres, I believe.
And so you can spin up these database instances without having to worry about,
okay, how many individual EC2 nodes do I need and all the rest of that.
Yeah, instead of saying, build a box and then install Oracle on it, right?
They're like, here's an Oracle database, right?
Here's your, here's your admin password and log in and do all the things,
Tell us how big you want it, what tables you want, all those things.
And you're administering it, maybe even not even through the
traditional Oracle interface.
You may have a, Another UI that you're using to create the tables.
you probably in the case of Oracle and MySQL, you probably can also
administer it via the standard tools.
But you may have this additional UI and you just get this, here's this database.
Now, I won't bother asking, should it be backed up?
But here's my question.
Do you know whether or not RDS databases, for example, are automatically backed up?
So I think that they do have a policy that you can create to say,
I want to do automatic backups.
I am not sure if it's default on or not.
I believe that it actually is by default on.
but it's just a very basic, like snapshot replicated S3.
Stays in the same account, stays in the same region, all of that.
I'm pretty
For 30 days only,
for 30 days, yeah.
and then if you want to do more than that, if you want to replicate
to another region, if you want to replicate to another account, which you
should, that's where it's up to you.
but even that, again, that's still, if you're not getting it out of that account.
I don't think of that as a valid backup.
Leave it in the account, yes, for convenience and ease of restore, but get
it out of the account from a security perspective and a risk perspective,
and that other account should be locked down, right?
You don't want anyone and everyone to have access.
if someone gets access to the production account, you don't want
them to necessarily be able to quickly get access to that backup
exactly.
in addition to locking it down and having super crazy MFA and all of those
things, I would configure it so that if, and when somebody does log into
it, it sets off all kinds of alarms.
that go to important
Will Robinson,
Yeah.
some of our listeners might not get that reference, but...
Um, so yeah.
Also needs to be backed up, also needs to be transferred.
with the case of EC2, right?
There's a couple different ways we talked about that, the snapshot
plus replication is the typical way.
There, you can also load an agent on an EC2, thing.
With RDS specifically, and again, we're only talking about RDS
just because this is where you and I have a lot of experience.
There are other tools you need to look into those tools.
In the case of RDS, I'm pretty sure you're stuck with the RDS way of backing up.
You can't put in an agent.
And I know, for example, in the case of Oracle, and I don't know
if they've changed this, but the last time I checked, RMAN backups
work, RMAN restores do not, which
Yep, which is
is really weird, and just wrong, right?
I don't even know how, like, how you would go about restoring.
so what do you think people that are doing, RDS backups, via non
standard, or standard ways, what do you think they should do to
know exactly how that stuff works?
they should try it out, right?
Test your backups, do your test restores, right?
Try these various scenarios and figure out, can I restore a tablespace?
Can I restore an instance, right?
Can I restore...
Logs, right?
Roll back in time.
Yeah, roll back in time, right?
Do all those things work?
Because it's better to try it now before you actually need
it, rather than scrambling
Exactly.
and there are all kinds of different PaaS.
Generally, when I think about PaaS, generally, I find myself talking
about a database of some sort.
I was also thinking about things like VMware right?
Which runs in the public cloud, right?
That's probably more of a PaaS.
no, I see that.
I see that as IS.
Yeah.
Because again, you're just managing VMs, right?
now, let's talk about that.
VMware Cloud on AWS is a great thing to talk about.
And that is that It's, it has a completely different backup
and recovery paradigm, right?
You need to use a tool that knows how to backup VMware cloud, on a
w s or on the other places where VMware cloud happens to run.
And, any decent modern backup and recovery tool is going to have that.
but don't assume if you're moving from VMware on prem to VMware cloud on AWS,
don't assume that your backup product.
we'll support it because one big thing, for example, is, like
you, you have to use the APIs.
You can't, there, there's no, place where you can, install stuff to,
to do things like the old way.
you have to use the APIs.
the other thing also, specifically with VMware Cloud, is you have to
also check to see, because I know at least in the past, there was some
functionality which isn't fully available in the VMware Cloud environment just
because of the infrastructure and other complexities that you might
have been able to do on premises.
if you were relying on certain restore functionality specifically,
that may not work in VMware Cloud.
By the way, speaking of VMware cloud, six years ago today, according to
photos in my library, VMware was talking about VMware cloud on AWS
at VMworld that I was attending because it popped up a photo of the.
Of the, the slides I was like, what?
They're kind of run VMware on AWS.
what in the world, who would want to do that?
I said, and once again, the world said us.
Yeah.
All right.
so the next is Server Serverless Services.
that's a mouthful.
That's a handful.
Yeah, I was going to say, say that 10 times fast, Curtis.
Yeah, I'm not gonna do that.
So this is like Lambda and other things.
remember there's always a server behind Serverless Services.
But, I don't, these are typically actions that do things against
other things that I don't think.
is this the one exception to the backup rule?
So I would disagree
Okay.
All
I think you still need to back up because think of serverless
as your writing function.
I think you have to back up the actual
Okay, so the function that you've created, yeah, just this is just
like Kubernetes and Dockers.
You're backing up sort of the configuration, but the thing the
serverless action is doing is going to affect some other piece of storage.
That's the thing that you're going to be backing up.
Yeah, you should already be backing that up
Okay.
so I, as I was saying it, I was probably in back of my brain was
like, what about the configuration?
Yeah.
So yes, you want to back up the configuration of the
thing that you developed that you're running as a function.
and it may be complicated because one of the things like I know We haven't
quite talked about it on this episode, but it's why do you back up right?
It's to be able to restore in the case of different types of failures, right?
And one of it is hey that lambda file or the serverless function that I wrote.
It's not behaving the way I want it I want to be able to go back in time and restore
whatever it was from like a month ago
Yeah.
The whole agile development model.
I'm 17 revisions in and, yeah, exactly.
that is one of the reasons we restore is developers mess up stuff, right?
All right.
So let's talk about our next cloud resource that we may or may not want
to back up a little thing called SaaS.
sa.
Software
so I think first before, so before we get into whether or not we should
back it up, Curtis, I want you to give your definition of what you think S
is and what you think ssas is not, because there's a lot of confusion out
there when people use the word SaaS,
Yeah,
and
there are two things that are often marketed as SaaS.
and there's one really big company that's marketing.
itself is SaaS.
And I'm like, I'm sorry, that is not SaaS.
SaaS is, it's easier to define it.
in terms of to give examples of it, then, An example of SaaS is
Microsoft 365, Salesforce, HubSpot.
It's a service.
It's an application.
Yes.
But it's an application where you don't manage any of the infrastructure.
You just use the thing.
You go to Microsoft 365 and you say, I want to add 7, 000 users and
magic happens underneath the covers.
All of the, all of the infrastructure that does have to
be provisioned to make that happen.
That happens without you, hopefully without you even feeling it.
it may, if you go and you say, I need to provision a hundred thousand users.
Microsoft 365 might say, give me a minute because it's got to go out
and provision a bunch of storage.
But, go ahead.
or even like how we're recording this podcast.
Oh, yeah, this is a SaaS.
We're now using Squadcast, to record this podcast.
And you and I log in, we go to a website, we go, we say record.
It does the magic and then saves the data.
That is another example of a SaaS service.
What is not an example of a SaaS service?
Adobe software.
This is,
Creative Cloud.
yeah, Adobe Creative Cloud is not SaaS.
They keep like the CEO of Adobe say, we want to be a hundred
percent SaaS by 2025 or whatever.
And I'm like, you're not 0 percent SaaS.
What is often called SaaS is subscription based pricing.
They're saying, you're, it's a software as a service, right?
No, it's software as a subscription, right?
Which also by the way is SaaS.
It comes out as SaaS.
so so I think there is one correction though.
I know with Adobe, there is a lot of the tools.
one reason why I know you complain about it is you want to use Photoshop, right?
You subscribe to Creative Cloud, you download Photoshop, you have to
install it, you have to manage the updates, you're doing all of that.
I believe now Adobe is actually pushing towards a true SaaS product for
Photoshop where it is everything done on
When that happens, I will rescind my, thing.
But if I'm downloading something And I'm installing it on my infrastructure.
That is not SaaS.
I can think of, I don't want to pick on them by name, but there's
a backup vendor that sells their stuff now through subscription
based pricing and they call it SaaS.
And I'm like, I'm sorry, that is not SaaS.
Right.
and I don't really care what you call your product.
It's just.
It's just a little confusing when we're trying to talk about, backing up SaaS.
I think that when you say SaaS, it should mean one thing.
And it means like Microsoft 365, a service that I use via, I'll give you one.
if I've got, I don't think anyone does this, but if I
had To, what, you know what?
Zoom.
Zoom is a perfect example.
I have to install a piece of software to use Zoom.
But it's just a UI to the infrastructure that's running in the background, right?
It's not...
I'm not running Zoom on my platform.
That's still
and Yes, and technically, you could also not have to install a
client locally, you could always use a web client and join via that.
yeah, so here's my, we've talked about this plenty of times, but my biggest
problem with SaaS is it's so many people seem to think that because
I'm getting the entire application delivered to me on a silver platter.
Backup is part of that service.
Isn't it, Curtis?
Come on!
Now you're just poking the bear.
yeah, it's not, here's the thing.
There may be a SaaS service out there.
In fact, I may have encountered one where they actually include backups
as part of the infrastructure.
And, it's in the service contract, it's in the documentation, right?
and those backups, by the way, if you actually have backups as part of the
product, all I want to know is how do they conform to the 3 2 1 rule?
How can I make sure that at least one of those copies is being managed?
In a different location and has a different risk profile
than the primary stuff.
My, can you remember what three letter acronym I would throw out to remind
people about what happens when you have the backups managed by the same people?
OVH.
Exactly.
Yeah.
OVH, the largest cloud provider headquartered in France, had a backup
service for the back, the servers that they were backing up, and the data was
stored literally in the same data center.
And when they had this giant fire, it took out both the
production and the backup systems.
And even if I was using a SaaS service that said it had
SaaS, or said it had backup.
I would need a really good reason to use that service.
it would be so much easier for me in terms of to feel better, to back
that up to a different service.
at least that way, again, it's splitting the risk profile, right?
the one other example, I know we don't normally think of it as SaaS,
but I think the Rackspace example with their managed email is actually
Yeah, yeah, I think it might actually be PaaS, because it was hosted
Exchange, but I never, it's somewhere between PaaS and SaaS, right?
because if you're still managing Exchange, Like it's exchange and you're not just,
but if the UI, I never administered, if the UI is basically the same as
365 and you just get the advantages of having all your data in one place,
then it would be, then it would be, that would be SaaS, but, but yeah,
But they were doing their own
they were doing their own backups as well.
And we know how that went.
so
We don't mean to pick on these same companies, but it's
just good learning examples,
for...
right?
And yeah, if you don't want me to name you as an example, uh,
then don't, don't do bad stuff.
Back up your
Bag of your data.
Yeah.
If you don't want to be the next example that I talk about on some
future episode of, this podcast, then, just don't do that stuff.
So summary statement, Prasanna.
All cloud stuff needs to be backed up.
Any problems with that statement?
Okay.
And then what do we want to do?
We want to make sure that we separate.
The backups from the primary as much as possible.
And I talk about a different region and a different account.
and then You brought up a really good point of making sure that backup,
because again, now this is your core.
It's your, you know, it's the, the golden goose and the egg, right?
So make sure that you've locked that down as much as you possibly can.
I was thinking about this.
You know what we should be calling that thing?
You know how they have that seed vault in...
where is it?
Somewhere in, the Arctic region, where they have, like, all these seeds for
yeah, yeah, yeah.
The, um, give me a second.
It's, um, Heirloom, the heirloom seed ball.
Yeah,
Yeah, so that, that's what this should be, right?
This is literally the last copy of all your data for your entire company, right?
You want to preserve it just like that.
exactly.
Exactly.
Yeah.
That's a, people probably don't know about that, but basically, an heirloom
seed is an unmodified original, thing and the somewhere, somebody is
storing seeds for all these things.
just in
It's across the world,
yeah,
a nuclear disaster or something.
this has been a good episode.
hopefully you've, uh, learned a lot about, backing up cloud resources.
The first of, let's see, the first of like three different, um, modern things
that need to be backed up and, um, any final thoughts on that, Prasanna?
I think the final thought would be, just because it runs in the cloud doesn't
mean you don't need to back it up.
Ask the question, how are you protecting your data and where is it going?
Yeah.
Couldn't have said it better.
so anyway, thanks a lot, Prasanna.
Thank you, Curtis.
Always fun, always a
Always fun.
I want to thank you for listening to this episode of the backup wrap-up.
It is an independent podcast.
And any statements made are the opinions of the speaker and
not necessarily their employer.
Be sure to check out our other episodes on backupwrapup.Com.
Our YouTube channel by the same name, or of course, wherever you get your podcasts.