Transcript
but not for long. Hey, I'm Rick Vanover, your host. Thanks for joining us here today. And I've got my partner in community crime or community things of good nature. I shouldn't call it crime. Maddalina, how are you doing today, Maddy? Hello, Rick. And hello, community. I'm doing great. I mean, this might be the last episode before my vacation. And mine, so... And yours. Are you going on vacation as well? Yes, that's... I'm sneaking one more in for the summer. Oh, my. You are taking so many vacations, Rick. Yeah. But other than that, a lot of good stuff in the community, as you can see. And today, we're going to talk about a bunch. So really looking forward to the start. Yeah, indeed. And, you know, it's crazy about the vacations, like for... It's always busy, but it's the least crazy, if that makes any sense, in the summer. Okay. So that's why I take a lot of vacations in the summer. And last few years, I've taken, you know, some are shorter, some are longer, but I've taken three vacations through the summer, just to kind of space it out. So I'll do that until... As long as I can, but we'll see. I think... Talk for yourself, because for the community team, summer is actually very busy. Yeah, you're right. You're right. You're right. But all right. So before I get myself in trouble, let's like change the subject here. Let's get into the topics. And by the way, Maddy, you, Sofia, Nikki, and Carolina, you all work so hard on community stuff, as does the actual community. So I don't underappreciate that for sure. But let's start with our first pick here today. And that is Marco Escobar. I like this one. Cool new project he's got in the Veeam GitHub. Yeah, absolutely. And it's good to call his name. We haven't called his name in a while. So good that he's back. I know he's very busy with a lot of stuff going on, expanding in Latin America, which is always fantastic. But yeah, this project is incredibly relevant nowadays, if you think about over, I think, over the past year, we've been seeing more and more organizations that are exploring alternatives to VMware as well, with all the acquisition and stuff that all the community is aware of. And while choosing a new hypervisor is one of the challenges, moving hundreds of workloads is a completely different story and another challenge to deal with when you when you decide to move your workload. So he is talking about an open source project from Veeam Hub that is called Move. And this is exactly what Move is trying to solve to help you move your workloads from, you know, from VMware to another hypervisor. So what is doing Move? Basically, it uses your existing Veeam backup and replication restore points to migrate VMs directly to platforms like Proxmox, Vover, HP, Veeam Essentials, without actually having to reconnect to your VMware environment, which I think is pretty cool. And, you know, the this is designed for large scale migration. So this is pretty cool, because I think we might have seen some similar tools, but not made not made for large scale migration. So this is not just basically moving one VM at a time. Because I think we previously mentioned a few tools if I recall it well in other recaps. So it kind of automates tasks like driver injection and preserves networking and supports both instant and cold migration and then lets you move multiple workloads in parallel, as I mentioned. So yeah, this is great, you know, to see this type of projects at Veeam Hub, you know, they are built for community by community for community. And it's kind of solving real customer challenges. And right now, as I understand from his article movies in beta, so I think this is a great opportunity to have our community members jump in and try it in, you know, their labs, and then provide some feedback, maybe help shape that the project is going, you know, but also, please keep in mind that Veeam Hub community projects are not developed by our Veeam R&D team. And they haven't really been through the official Veeam QA process. So don't use it in production. We always say that, but it's worth mentioning again, use it in your lab and test it. And you know, then once you know that is sure just good to go. You can use it in your production environment as well. But overall, I think this is such a fantastic tool. And thank you, Marco, for sharing it with us. Wow, whoa, whoa, this is amazing, Marco. And I was skimming the GitHub, as you can see for being quote unquote, beta, this is looking pretty good to me. A couple of things here. Number one, you might say, why not Hyper-V or Nutanix? Well, first of all, the orchestrator product already does mass migrations to Hyper-V. We may or may not have a roadmap element for the orchestrator for the other hypervisor. Time can only tell. Wink, wink. I'll also tell everyone that this is super interesting when it comes to things like Proxmox. I can tell you friends, Proxmox is really being adopted. We look at a lot of the telemetry that comes in from what hypervisors people are using. I can tell you the biggest benefactors in this, you know, the little bit of time I've been looking at this in the VMware conditions is really the biggest benefactors have been Hyper-V, Nutanix, and Proxmox. So watch out for that. And that one's pretty serious. So fantastic. Outstanding tool, Marco. And I just thought of something new, Maddy. I'm going to shout out recap every time we feature it when we record. So let's see if that changes any behavior. But outstanding. Outstanding, Marco. Definitely. Next up, Scott, Veeam Legend, talking about the softer side of life, in a way, about the Veeam backup admin quit. Now what? What do we do? I think Scott's broken down a great list here. Yeah, absolutely. And this is kind of taking us back, you know, to the operational resilience conversation. I think we've had a lot of those, a lot of our community members brought topics around operational resilience. And I feel, you know, like, this is a really great topic. And yeah, just bring it on. We love it. And this one is another great one. And yeah, the question is, what if your Veeam backup administrator quits tomorrow? What do you do? And I think it's a scenario that, you know, every organization will face it at some point. And you know, while, yeah, of course, replacing a person is possible. Replacing years of knowledge might not be that easy as we think it could be. So Scott walks us through everything that should happen next, from changing passwords, reviewing privileged access to validating backups, checking, monitoring, alerting, reviewing documentation, even making sure someone else on the team knows how to perform critical recovery tasks. And that is, this article is a great reminder that, you know, backup administration isn't just about running job or jobs. It's about understanding your entire recovery process and the environment behind it. So yeah, we really spend a lot of time talking about protecting data, but we also really need to protect the knowledge that keeps our environment running. So it's a really great article in here. And yeah, as I said, he mentioned good documentation, regular recovery testing, cross training your team. And these are not just best practices, it's something that you must have, you must do, because this is what is going to make your backup strategy sustainable in the long run. So nice one, Scott, really enjoyed it. Yeah, hard to pick a favorite here. But I'd argue number five is one that's kind of important in the sense of know how to do a restore, know how to do a backup, because just net new workloads, that would be a new problem if they're unprotected. But I really like Edwin Morales, aka shout out Rising Star. Edwin's point here about the join, move or leave. I love that. And that aligns well to NIST two directives, you know, so this is really good advice as well. So I think depending on where you are, in your organization, your size, your maturity, your requirements, that mindset of a join, move or leave, and then a specific thing for an app. This is fantastic advice. So thank you, Scott, and a hat tip to Edwin for the insight on the comment. Yeah, totally. All right, next up, Link State, always looking around the corner, bringing to our attention about an upcoming deprecation of the RC4. Maddy, I don't even know what this is. Yeah, basically, it looks like Microsoft is permanently retiring RC4 encryption for Kerberos. And that's July this month, 2026, coming with the security updates. And you know, it says what Link State says in there is like, okay, if your environment is up to date, you won't notice much, most probably. But if you still have like legacy applications, like service accounts, older systems lurking around, this change could actually lead to authentication issues. So you have to be very careful about it. And yeah, what is great about this article is that Luca, aka Link State is giving us a practical checklist to assess our environments. Now, before this, you know, deprecation take place, and you can go over identifying accounts that still rely on RC4 to using Microsoft's PowerShell scripts, event logs to detect potential issues, and so on and so forth. There's a long list in there. And, yeah, these are the kinds of changes that, you know, can be easy to overlook until patch Tuesday arrives. So I think, yeah, just spending a little bit of time on this right now could actually save you a lot of headaches later on. I don't know, in August, maybe. So good job. And thank you for bringing this, you know, into our attention, Luca. Yeah, indeed. And, you know, a couple of points. I'm just reading through here. This is a really good one here to kind of start with. So really good stuff. And I don't know if I'm making, I don't know, more problems or starting something new here. But saying shout out ReCap every single time, or maybe we're blowing the secret. I don't know. Maybe Maggie will talk to me later about that. We'll see. But thank you so much, LinkState. Outstanding information as well. All right, next up, our Vanguard blog spotlight. Haven't called Zane's name in a long time with the West Coast Hipster blog. And he's got a great post about moving to 13.1 part of a series about the proxies, repositories, and the VNR server. Yeah, so this is part two of Zane's series on moving to Vim Backup and Replication v13.1. And this, in this one, he focuses on architecture mainly. And Zane says that, you know, before you migrate, before you actually deploy anything, you need to know what you're actually trying to build. And actually, this concept took me back to last week article from Edwin Moral, because you just mentioned Edwin Moral. But if you remember, we mentioned his article. And yeah, it's kind of the same concept, same rational, I think, behind it. So yeah, he got shout out twice. Edwin, good job, our rising star. So Zane basically takes us through designing a complete backup infrastructure around the new appliance model. And he's covering the backup server, proxy placement, you mentioned as well, repository strategy, sizing, immutability, and object storage. And he also shares the reasoning behind every decision from, you know, keeping the backup server outside the production blast radius, to choosing between hardened repositories and object log, and even why he's running two environments during the transition. So it's a very comprehensive article. And it's, it's not just about, you know, following some best practices. It kind of let us know how to, you know, look at the environment and kind of understand the trade offs and, you know, make informed design decisions. So I think it's very smart how he builds it. Because, you know, many, hopefully not many, but I know some people might just, you know, jump straight into the installation guides, migration checklist, but then the architecture is actually what is going to determine if your environment will still make sense two or three years from now. And so that's why, you know, I kind of associated with what Edwin shared in his article, the article that we mentioned last week. And yeah, I think this is great. And I think it's coming more. And for the ones that are trying, you know, to move to, you know, v13.1, or you just kind of think about redesigning the whole backup infrastructure, I think this series is something that you should go and read and follow. Because it kind of explains a lot, the why behind every decision. It's not just how to do it, but also why to do it. And I think this is very relevant when you, you know, redesign your, your environment. So great stuff. Thank you for this, Zane. And yeah, we are looking forward to your next article. And we are super excited about v13.1 GA, which should come soon. End of the month, if you didn't hear from me, but it's coming up very soon. Yeah, and this is great. And then, you know, the previous segment, you can get into some views ahead of time. So good stuff. Thank you, Zane. One thing I want to highlight is KB4800, which may be a really helpful knowledge base article for those of you who want to do your own migration from the Windows Veeam backup and replication to the Veeam software appliance. This breaks down what is and is not supported for the move right here. And, and Maddy, you might be thinking, that's a good cause to update the Upgrade Center, which I will. So I do plan a big update to the Upgrade Center here today, hopefully, in front of the recording, but only time will tell if I get that done. But no, this is a good one. So thank you, Shane. All right, let's go over to special department news. And we're going to start in Italy on the 28th at, I guess that's going to be about 1500 CET. Antonio and Marco and five expert friends are going to talk about what changes for an IT backup manager with the introduction of AI. And we've got some Veeam folk, we got some other legends and vanguards, really looks like a solid panel of the state of AI and backup manager world. Yeah, definitely. This one looks really good. And it's very mysterious, because they don't give us too much information in the description, they only say Veeam's AI innovation. So I think all you have to do is join this kind of panel, I think it's gonna be. And yeah, I can see a lot of knowledge of people that are going to be part of this show. So if you understand Italian, if you speak Italian, I think you have all the good reasons to be part of this show. Next Tuesday on July 28. And if I'm, if I'm keeping score right here, everyone is one of the Veeam 100 because Danilo I think is MVP. So yeah, this is a great, great expert panel, great perspective here. So thank you all for this and already good turnout pre-reg. So that's looking pretty good. So that'll be on the 28th. That's 9am for me here in New York time, but I think that's 3pm Italy time. All right, next up Automation Desk. Maurice and Jonah, I have a really interesting thing, simplifying Veeam automation with Python, looking at an open source project called Symbora. Now, I've not heard of this, but I'm telling you what these two guys, Maurice and Jonah do on the day to day, will really make it clear. I know Maurice has done a lot with like Chocolaty and Jonah. And in his role, he uses a lot of these types of things. So I think if there's anyone that's really qualified to talk about the secrets of deploying, I think it's these two. So this one looks really interesting, Maddy. Yeah, and of course, because we like to have all events the same day. It's gonna be again, July 28, just one hour later. But yeah, I think this is gonna be also a good one. And you know, if you are looking to automate your Veeam environment or any environment with Python, I think this is the session that you should attend. Also, there is this Symbora that is new for you. It's new for me as well. So I think it's going to be very interesting. I don't know, let us know if this is new for you or you heard about Symbora before. But I think it's gonna be good. And I think especially maybe for the people that are also participating in the hackathon this year, this might be something that you know, you can learn and apply it in there. So pretty good stuff. Yeah, indeed. So thank you, Jonah. Thank you, Maurice, always bringing the goods here. So I don't know why I just did a dramatic change of scene, but whatever. And now we have a winner. And I love this Oxford style debate series here. So series two has some results who are winners. I mean, there are two winners, as you suggested Rick, one for one against. So we have Yoss and Mateus that are winners this time for Beam Oxford style debate episode two. And this was another great discussion. I could see that, you know, everyone jumped in and enjoy the, you know, the debate, because this is probably one of the most talked and most debated topics in the IT world. Is tape really dead? And what I figured from this debate, actually, I think people struggle to be like, for, right, for because everyone thinks that tape is not dead and is coming back in fashion. So but yeah, we had that we had a few relevant answers. For tape is dead. So it's difficult, you know, to think the question and it kind of gets you confused. But, but yeah, congratulations, the two of you. And I'm really looking forward. I'm coming probably in the next few days with episode three and another interesting topic to be debated. I think we have a typo for tape is not dead. It should be tape is not dead for Yoss, right? Yeah. I just can't let this I'm gonna fix it right now. We can do that here. That's what we do. I'm gonna fix it. Just do it. I'm doing it because you know, it's important, you know, and while I do that, I want to let everybody know that I was a guest on the LTO show, which is a tape podcast. No joke. There is a tape podcast. And I had the opportunity to be a guest on that. And I'm thinking that we'll, we'll put that in. And what do you call it in special department news once once that publishes. So I really was joined in by Pete. So that was a lot of fun. And you know what, that's what we do when we record. Look at that. How about that? Do you approve Maddie? Is that looking more correct? There you go. Yeah, it was very confusing. Very confusing. Goodness. Congratulations, Yoss. Congratulations, Mateus. Fantastic. Whoo, cold chill. What's going on? All right, next up, there's a new contest in town. Maddie, tell me about it. Oh, yeah, I have a fun challenge for everyone in the community. You know, I thought, you know, because this month is a sysadmin day, I think it's July 31 is the last Friday of this month, if I'm not mistaken. So I thought, you know, the incident commander challenge is gonna sound so cool. So basically, what we want is, from our community member, what's one Veeam tip that's always, you know, in your toolbox. So we just need like a 300, 600, just a blog, you know, where you share some tips and tricks, a feature, a script, anything, you know, that uses you to make your life easier as a sysadmin. So yeah, basically, all the details of, you know, the timeline, the winners, how to enter and all that is going to be here in this blog. But yeah, there's going to be three people that are going to win a surprise, surprise, surprise, surprise, surprise, surprise. Okay. But yeah, what we're gonna do is basically, we're gonna take all the blogs, and we're gonna put it in a poll similar to blog of the month. And then we're gonna have all our community vote for it. And the, you know, the three most voted blogs are gonna get a badge, the incident commander, which is a really cool badge, you're gonna see it. And then, yeah, they're gonna get also some some surprise prizes. So I'm really excited about this, because I think everyone can learn a lot. And of course, the idea of all this content is to have fun, but also to learn from each other, you know, from our knowledge and expertise. So I think it's gonna be good and fun. Yeah, and it we going to announce the winners on August 14. So there's plenty of time. And I'm just trying to think how can you cheat? How can you like hack this process, but I really, I think it's somewhat subjective. Because I think if you're talking about scripts and workflows, those are some things that are, you know, community supported versus officially supported. So you've got pretty good set of rules here. So I like it, Maddie, this is fantastic. So good luck, everyone. Bring your A game. All right, next up, fresh from the desk of Sophia, we have plus 105 new members in the Veeam community with Rastrak, Joshua ASF, Scooch and Dafu Duck as our coolest usernames with Alfred's pic being Danish Danny or Danish Danny. I don't know. That's a cool one. Yeah, you know, it's funny, you gotta you gotta like slow down when you read those because they might come off like an expletive if you do it wrong. So good stuff. Welcome, everyone new to the community and more. So other than that, Maddie, nothing's going on. Yeah, well, a lot of good stuff. And I'm happy, you know, it's still it's summer, people are on vacation, people are, you know, on the beach or wherever, doing some hikes, but they still take the time, you know, to contribute to the community hub and to the Veeam community. And that's really excited. And I can always say that I'm very grateful for every community member and for everyone, you know, that, you know, is just there and helping other and, you know, contributing. So that's always fantastic. And yeah, what are we gonna do next week, Rick? You're on vacation. I am on vacation. I forecast a post will be the way. We'll see. We'll see. I don't know. We'll see how Nikki's or Safi and Carolina are feeling. Maybe they can, maybe they could do a takeover. Well, I don't know. We'll have to talk to them about that. But minimum, we'll keep up with the post. It's hard. You know, we allocate a good half hour to do the recording. There's a little bit of production. We have some help with our video teams to get these out. So the video is a nice ad. But you know, sometimes you just don't have enough week to get it done. So big shout out to Jeffrey and Mark for helping us with that. We can also take the week off, right? Never! Never! Come on, we can come the week after, we can come strong and we can break the rule. Maybe January 1st. I'll allow it. But I don't know. We'll see. I promise I'm not a horrible boss, friends. Yeah, it's gonna be a surprise. Just stay tuned. And you'll see it. All right. Who knows what 272 has in store, but you'll have to come back next week to find out. But anyways, thank you, Maddy, for curating a great set of content. Absolutely. All right, everyone. That is it for today. Thanks for watching. We'll see you next time.
