Things Gilles Says on Podcasts

…like before running an AI and having a plan in case it is deleted something. Like you move the threat to an actual expectation. Like it's going to happen. And so your only way out is I need to be sure that I can recover when it happens and no longer in case it would happen in the next two years.

…okay, I'm going to install some appliance in my, you know, in my data center. You know, I have lots of different ways to think about lots of different requirements. So, like, what are the ways people can be reasoning about what solutions do we have out there? How should we be thinking about this?

That's what I was just going to say. It seems like, you know, and I'm a big believer in infra-code policy code. I mean, hell, the app that I use for tracking my workshops is work, or not workshops. My workouts for my lifting is a thing called Liftasor. And it's like workouts is code, right? You…

So if you don't work out, you break a CI?

Well, no. See? Yeah, there's a feature request. No, it's just I create like you write in code kind of the like your progressions and everything like that. But anyway, the point is, so yeah, but but but backups, right, not really being thought about that way and trustable and having those…

Yeah, but we have one for Microsoft Active Directory. Active

…and say, like, okay, cement this and you know, tattoo it on the inside of your eyeballs about thinking about your data protection. What's what's the thing that that people should should go? You know, first thing is go check out Plaque R, but you know, for sure. Yeah, of course. Secondly, after you

I feel like that's sort of the key. And so much in the consumerification where that comes in and people think about, and just even at the consumer level, and even us as technologists probably misunderstanding. I mean, I had a conversation with my ex the other day. She's like, I don't understand why…

a false sense of security and a sense of not losing your data. But people who have lost them have been feeling very sorry about this because they write it. They're right. We are not going to back up your data. Share responsibility. You have to do your backups because we can't necessarily restore.…

Fantastic. So everyone, if you head over to arresteddevops.com/slash modern backups, that will have this episode show notes with lots of helpful links. And if you visit arresteddevops.com/slash iTunes, you can leave us a review in the Apple Podcast Store. That helps other people find the podcast. I…

…because backups is not absolutely not a sexy area. No one wants to deal with that. Usually, when you deal with that, it's because you've been tasked to deal with that in a hurry, let's say, and you try to get rid of your task as fast as possible and hope that you never have to look at it again.

…of a, for lack of a better word, user-level problem, right? You know, like we're like, oh man, you know, we did this wrong. We have to, we have to put things back to the way that they were. There's sort of like restoring a system because it went south, and then there's rewind time, you know,

So yeah, it's that threat landscape has changed substantially, right? You know, we think about different things and it seems like almost every day, you know, there's some story about, oh, I accidentally, you know, my AI agent actually dropped this table in production and things like that. And…

I would agree that you do not solve that with backup, but you have to reason about your backups in a different way. Before you would say it's unlikely that I lose data, because it takes like there's very there's statistics about that, yeah, but there's very low statistics, very low odds that you…

So I think we've done a pretty good job of talking about why everything is terrible and everyone should be scared as hell and everything. We're not always here just to tell you that you should just go retire off to a kettle and raise chickens in Montana or something like that. So let's think about…

…that was not even the discussion before. And of course, war, which is an active topic for us, since we've been contacted by people that had data in data centers that were struck by missiles. So not the kind of stuff I would hear about a few decades ago. Not that funny, but interesting. Interesting.

…have it backed up because it was a POC or I never properly operationalized it or anything. And that's all. That is an entirely other topic we can probably talk about on the show, which is how do you get your AI teams to enable teams to think about productionizing apps? But it happens a lot, right?

So I think we've done a pretty good job of talking about why everything is terrible and everyone should be scared as hell and everything. We're not always here just to tell you that you should just go retire off to a kettle and raise chickens in Montana or something like that. So let's think about…

So, I think there's two ways to reason about backups. More than backups, it's data resilience in a sense. The first one is that people usually do not categorize their data sets. So, it's more of a, yeah, I have machines, I will back them up, and they're all backed up with the same kind of level.…

That's what I was just going to say. It seems like, you know, and I'm a big believer in infra-code policy code. I mean, hell, the app that I use for tracking my workshops is work, or not workshops. My workouts for my lifting is a thing called Liftasor. And it's like workouts is code, right? You…