Transcript
Happy Friday and welcome to Episode 236 of the Weekly Recap. As we promised last episode, we're going to have a special edition, special episode with special guests. I'm having Scott and Charlie with me, both of them Veeam 100 members. Scott, this is not your first time in the Weekly Recap, but it was in a different format. We had you as a guest at VeeamON, special recap. But for Charlie, this is actually the first time in the Weekly Recap. What I'm going to do, I'm going to start by asking you to introduce yourself. I'm going to give it to Charlie because this is his first time in the recap. Why don't you just tell us a few things about yourself, Charlie? Yeah. Hi. I'm Khaled. I'm an infrastructure consultant from Germany, new to the Veeam Legend program from the last intake. I'm dealing with Veeam quite some time. I think the first installation I did was on 4.x, something like that. Yeah. I'm happy to be here. Fantastic. It's great to have you in the program. Thank you for being a guest in this episode as well. Scott, I know you probably introduced yourself last time, but just for the people that are new to the community and they're watching for the first time, or they haven't watched that episode when you were a guest, why don't you just say a few words? Sure. My name's Scott. I'm an information system specialist, which is everything from storage, backups, DR, and anything else they want me to do. I've been a legend for probably two to three years now, and I have a really large Veeam environment, so some of the stuff I have is a little bit more unique with 100 terabyte VMs and stuff like that. Yeah, that's pretty much it. Producing a lot of good content that the community have, so thank you for that. Today, we haven't selected one of your articles, but we usually do because we definitely like it. They're always interesting. Great stuff. Thank you both for introducing, and as I said, for being here with me. As always, our community has shared some great content this week as well, so what better way to recognize them than discussing their articles? Even more today that I have two technical experts with me, I'm sure there's going to be a lot of interesting points of view. What do you think? Should we just jump in? Sounds good. Let's do it. Sounds good. Let's do it. I'm going to share my screen. I'm with one screen, so that's always difficult, but we're going to manage it. We're going to start with one article that I really actually enjoyed from Andre, one of our Vim 100 members as well in Brazil, and VUG leader in Brazil as well. If you remember, I don't know if you two watched two weeks ago, we shared his first article on this topic, and he's basically discussing that most of the times when you consider a repository, you mainly look at the capacity, but this might not be the best approach. He was talking about how to properly design and then configure a DAS repository using internal disk for Vim backup and replication. Then he's getting into details and he shows us some maps and do some calculations, super interesting. This is his second article on the topic. He said he's going to be a series. As you can see, this is part two, and he gives us some updates on the topic. What I want to do is actually ask your points of view on this topic, and on this article, what do you think? I'm going to start with Scott this time. I like this one because I'm a bit of a storage nerd myself. I'm the same way if somebody is building a repository, I usually say, well, what's your requirement for how fast you need to restore your throughput and I or not, how much space do you need? Knowing this really helps you design what you actually need in your Vim infrastructure. I think you actually commented as well something here. I'm not mistaken. We've had a few storage discussions, so yeah, I'm sure we'll be chatting when we get together as well. You're looking forward for Prague in a few weeks to see Andre so you can discuss this topic. We'll nerd out over disks, yes. Fantastic. I like that. I really like that. Tell it, what's your takeaway on this one? Yeah, it's actually, I like that it goes back a little bit back to the basics and stuff. Everybody's talking about Flash nowadays and NVMe and stuff like this, but for backup environments, you usually have spinning disks and it gives you like, think about what you're going to do in case in order to get the performance that you want. That's a good recap. It's good going back to basics and just getting back to the topic. What do you think? Yeah, sorry, go ahead. I was going to add, especially with everything getting so expensive, I didn't even think of that. Yeah, going with disk may make more sense now. That's true. Yeah, totally. What do you think about his little graphs in here and maps that he created? What do you think about those? It could be helpful when you have discussions about architecture and everything, and how do you get to the solution you wanted to just to show the way of thinking and how do you achieve what you want to achieve? For me, for instance, I'm a very visual person, so for me, it's really helpful. I do read through the information, but having a map or a graph or something always gives me more perspective. I think it's a great combination. Thank you, Andre, for this great article, and looking forward for your third one, Part 3. I'm sure it's coming soon. Moving forward, we have Marcus, another Veeam 100 member. It's fantastic to have so many Veeam 100 members mentioned today. I think all articles are actually from Veeam 100 members, discussing it with Veeam 100 members. What can be better? So a really good article in here from Marcus. This is a crucial topic for every business, I believe, disaster recovery, and Marcus is discussing how when a primary system goes down, whether it's power outage or just a major failure, every second of downtime can cost the company thousands. So he's discussing that, and he focuses on using Veeam Recovery Orchestrator to execute the perfect plan system switch, and this method, he says, will help you, you know, that even in an emergency situation, companies can shut down, sync the latest data, and boot up systems on a backup site with minimal loss. So this is kind of very long article, step-by-step guide to achieving the highest level of business continuity. But I'm really interested in hearing from you, because I know you have some interesting point of views. This time, I'm going to start with Charlie. Well, I think, like, the VRO is a little bit of the dark horse in the Veeam software environment, and it's really cool that Marcus puts in so much effort and so much detail to bring it a bit closer to the users, because especially in Germany, it's not the most used tool in the Veeam context. So, yeah, I really liked it. I mean, if you think about, like, I don't think that's necessarily just for Germany, but I think that applies globally. I don't know, maybe Scott is going to have a different opinion now, but what I noticed, you know, when I talked to people, I was in Latin America, for instance, as well, for the VeeamON tours, and I was just chatting with people as they were coming to the booth, and, you know, I was just asking what would be, like, the products that they are using, what, you know, and it's always VBR, some of them VeeamON, but not that many VRO. So that's actually a good point of view. But maybe Scott has a different opinion. I don't know what's the situation in Canada, for instance. Yeah, even myself, we're starting to look at it because we use SRM with storage replication, but with articles like that, I kind of want to hire him to write documentation for my work, because that is fantastic. He went into a lot of detail and just step by step. I don't even think you could mess it up if you were doing that for the first time in a lab. I think that was really well written and lots of detail, really good. And is it, like, used? I mean, yeah, you said your company is now looking into it, but, like, in Canada, what do you think? Is it, like, a product that companies use or not that much? I think it's starting to. I don't think it's used as much. Like VBR, for sure, is the main one that's used here. V1 is getting better and better all the time, too, so I'm seeing a little more of that. I'm really excited to go with V113 just to see the differences in some of the features. But, yeah, I don't know how much Orchestrator is used here. Okay. I understand. Okay, awesome stuff. Thank you, Marcus, for sharing this awesome, long article, very thorough, always great content from you, so looking forward to the next one. And now we got to our third article, and from here it's going to start a bunch of content on VBR V13, V1 V13, so there's going to be a lot of discussions around this topic, as you were mentioning it, Scott, a bit earlier. So this one, the third article comes from Peter, another of our VIM100 members, and it's a really good one, another long article. Seems like he is working on his first larger V13 deployment outside of his lab, and he got some blockers when trying to connect VIM backup and replication and VIM1, he said, after he did the V13 upgrade. And Peter spent a lot of time, he says, figuring out that a simple user account wouldn't work for the connection, and that kind of forced him to learn about specialized roles, like the service account. And I think this is a really good case study on how just a tiny permission is coming on the way and it kind of derailed a critical enterprise deployment. So now that I know you both probably played with some betas, you wrote on it, you tried it, I would really like to pick up on your brain and just get some opinion observations on this article and in general V13. This time I'm going to Scott. I like this one because it's not just a basic how to install, it's some of the issues that I'm sure other people are going to experience. So this will probably be helping people going forward. And yeah, just some of the things he encountered are a little bit, you know, if it's dealing with your firewall, some of that stuff might not be in the actual documentation yet, as he said. And once again, this one was quite detailed too. So if you're having a similar issue, this would be able to help you if you went through it after the fact. I used the beta for V13 and V113. And yeah, it was pretty early. So I had a few issues too, just due to our networking and our stuff's very tricky to get installed. So having documents like this always helps. Yeah, absolutely. And Charlie? Yeah, I haven't played around with V113 yet, but I'm planning to and have some time to do it in the lab at least. Yeah, but it helps because, you know, there are some issues that most of, as Scott said, most of the people will run in. And if you have something to read about it, and then you don't have to look through help articles on anything, everything's like that. It's easier to find it on a community hub or something to just help you to figure out what issue you have. And maybe someone else already had it. There's a way around. Yeah, logically. Yeah, totally. And then we also got here a comment from Jorge, the one and only theme one guy. So he's explaining a few technical stuff in here, I think. So if you have just logged in only once to, let's say, it's Steven with user role in host management, changed your pass, make sure you have been back admin role in VBR and use that in V1 would have worked 100%. Also, you can delete this account from VBR once it's added to Vone, as we do not use that user anymore. Okay. So it looks like it also has a resolution. So, yeah. It's pretty neat that the people that actually work on the product will comment on your post and give you some help too. Yeah, that's fantastic. It's great to see Jorge, you know, just jumping in and just the fact that he's going and reading this kind of stuff, you know, and then takes the time to be like helping the community. That's fantastic. And yeah, then you can see there is like conversation in here. Yeah, that's great. That's really, really great. And thank you, Peter, for sharing this article with us and definitely some good stuff shared that the community have lately. So looking forward to the next one from you as well and looking forward to see you, Marcus, Andre, everyone in Prague as well. So now we are done with the articles, but we are going to the category that we call Vanguard Blog Spotlight. And this week we selected another awesome article from Ben Harmer. And this is on automating V13 appliance deployments. And instead of, he's talking about that, you know, instead really cool image as well, most probably AI. Pretty cool one. And, you know, he's talking about instead of manually configuring complex settings for like hours, you know, he's using, I think that was from his name. Let me, oh my God, why do I forget his name? It's one of our MVPs for sure. Help me in here, guys. Do you remember? He's mentioning it here somewhere. Baptiste, yes. So basically he's using one of the community created automation tool to build a customized installer. And this process allows company to deploy complex data protection systems at scale. And that would obviously save a lot of time and eliminates error in here. And, you know, your system is going to get configured in a better way. And as I said, just avoiding some errors. So it's going to be also secure from the start. So that's fantastic. But what I want is to hear your opinions on this. So this time I'm going to challenge. Yeah, actually I've never thought about in automating the installation of VMVBR. But on the other hand, with the new, these are stick guidelines for the passwords and might come in quite handy so that you don't have to use the console to set the passwords. And then you all have them set and everything and should be a bit smoother. So yeah, I'm happy to try it. Yeah, totally. It's a long article as well, this one with a lot of information. So pretty good, pretty thorough. I'm very curious if anyone gave it a try, Scott, have you? Not yet, but I definitely want to. Yeah, I've never automated a VM install. I think that's super helpful for people who do this frequently, maybe a service provider or something like that. It's going to save you from making any kind of errors and you can just continually deploy it. I'm thinking for a lab environment, you could just do it over and over and over and you could have a whole environment stacked up pretty quick. So I thought this was a great article, very technical, very detailed. I think there's everything in here you need as well, much like the other one that you can just follow it and you're not going to have any issues either. Yeah, I believe so. We have a lot of print screens with a lot of cool stuff shared in here. He's also sharing, as you could see, a bit up. He's sharing as well the GitHub with all the details that Baptiste put together. So you have also that information. And then it's just never ending, as you can see. Okay, wrap up. They paid him by the word. Just kidding, just kidding. Great addition to the existing documented Vim process. Yes, absolutely. Okay, that's a great one. Thank you, Ben Harmer. And great to have you mentioned again in the Vanguard blog spotlight. I think probably from all the Vanguards, I think, if I look back, you probably did the one that got more mentions, the most mentions. So good job. Fantastic stuff. Thank you and keep on doing it. I really enjoy it. And from that, we are going to move to the third category. That's the special department news. And we have one event that is coming next week. That's from VUG Egypt. And we have our VUG Egypt leader, Mohamed Adel, that is putting together this one talking again, Vim VVR V13. This seems to be a hands-on experience. So I'm not really sure what he prepared, because it doesn't look like there's a lot of information in about this event. But what we can tell in here is he's going to have a guest, Mohamed, from Lenovo, technical solution architect. So maybe they're going to do some demos, maybe some conversation. Just keep in mind, this is going to be in Arabic. So for the community, he says in here, Arabic. I think maybe it's translated because this originally is in Arabic. So most probably it's translated just wrong, instead of Vim. That's my guess. But yeah, this is going to be in Arabic. It's going to be next Wednesday, October 22nd. And that's going to be 7 p.m. I think this is the Eastern European Standard Time. I can see 18 people already registered. You still have time. So go ahead for it. Talking about this, Scott, I know you were thinking about having as well a Vim user group experience in Winnipeg. I've already, I still have vendors. I got a few vendors that are wanting to help. I got a few local Vim people that want to help. It's just time was a little tight this summer. And I'm not sure how many people want to come to Canada, where I live, in minus 40 weather. So we may look at spring at this point. I think spring is always a better idea. But yeah, that would be cool. I mean, I'm pretty sure because we don't really have that many events at this point in that area or not at all. So I think the customers and partners that are around, they might just be interested in attending. So I think that would be a cool thing. But yeah, in the meantime, thank you, Mohamed. Thank you, Mohamed. And looking forward to this great event next week. And then talking about events, we also have one event that is in person. This is going to be VUG USA in Los Angeles. We haven't had one in Los Angeles in a while. I can see it's going to be location Topgolf El Segundo. And this is going... Well, this shows my time because it's customized, but it's going to still be Wednesday, October 22nd. And it's going to be a few hours in the evening, as I can see in here. I don't know to translate the time right now, but I think it's going to be sometime evening. A lot of the topics are going to be, again, around VIM V13. So I think this is going to be interesting. Let's see if we go to register. What do we see in here? Okay, so we have basically a registration form. So you can put your details if you are in the area and you want to attend. This is the way to do it. We have data price, object first as sponsor. So thank you both. And I'm sure it's going to be good. We don't really have like a very detailed agenda, but it looks like it's going to be a lot around V13. So that's going to be great. Think, oh, okay. So here we have 4 p.m. 22nd October 2025, 4 p.m. to 7 p.m. local time. Okay, now that makes more sense. Perfect. So thank you, Stephen. Stephen, you for that. He's a new VUG leader, not a new VIM 100 member, but he started this month at the beginning of the month. He had a VUG in New York that was successful. And now he's doing one in LA. All cool stuff. Thank you for that. And now going back to the two of you. Thank you very much for being with me in this episode. It has been great. Any final thoughts on your side? Well, actually it was nice. It was interesting. Yeah. Hopefully not the last time you're going to be my guest. Yeah, hopefully. Yeah. And looking forward to seeing both of you in Prague in a few weeks. Scott, any final thoughts on your side? Oh, just thank you for having me. Looking forward to going to Prague and seeing everyone and meeting everyone in person that's new to the group. That's kind of what the VIM community is all about, is meeting people from all over the world and having similar interests. So, thanks. Thank you very much, both of you. And thank you all for watching us today. And we'll see you next week in episode 237. Okay. Nice.
