Transcript
Happy Friday and welcome to Episode 213 of the Weekly Recap. It seems like lately we are up for a bunch of specials. As you can see, I have two special guests today. Rick is on the road, I'm on the road in Brazil, and we couldn't align our schedules. Luckily, it almost always works. But if not, we always have some great community members, my colleagues from Product Strategy that are jumping in to help me out with the recap. Great to have you both of you here, Johan, Julia. Let's start with Julia because I think this is her first time in the Weekly Recap. Would you like to introduce yourself, Julia? Yes. Hi, everyone. It's a pleasure to be here. My name is Julia and I'm Global Technologist in the Product Strategy team at Veeam. I handle most of the Cloud products, so Veeam Backup for AWS, testing, now also Veeam Backup for Enter ID. I love to be part of this community. Thank you, Julia. Johan, would you like to give an introduction of yourself? I'm sure the community knows you already. You've been in the recap before, but for the ones that don't know, let them know who you are. Hey, everybody. Thanks to Maddy for inviting me once again. It's actually my second time in the Weekly Recap. I did a Veeam 100 show, so I was on air, let's say a couple of times, but it's always a pleasure to be with you and to jump in if Rick doesn't have time or if your schedules don't align. Yeah. I think maybe because next week I'm going to be on vacation, so who knows, you might be up again for another episode. Let's see how that goes. Yeah, you never know. It's a surprise indeed. But yeah, that's good stuff. Thank you guys for helping out today, for jumping in. I would say because we have so much great content to share, a lot of things happened in the previous weeks. Last week, we were not able to really record, but we did a recording at VeeamON with the community as well, so we have a lot to cover today. I would say, let's just jump in with the first article that comes from Marcus. He's all the time in our recaps now. Great job, Marcus. We like that you are engaging in here. This time, he's writing about how to increase data domain capacity on a retention lock compliance system. He put together a step-by-step guide on how to expand the capacity on a Dell data domain with retention lock compliance mode enabled. Now, I want to ask Jochen, what does he think about this topic and about this article? First of all, it's always a pleasure to read an article of a fellow German Veeam Vanguard, so congrats to Marcus on this one. Actually, it's very interesting because retention lock on a data domain, of course, due to all the ransomware attacks in the last few years, it was a great feature that Veeam supported the retention lock feature of the data domain. To be able to get another piece of protection against those attacks. But of course, most of the time, the security comes with a price and the price is mostly paid in data storage capacity. It's always nice if we see someone who gives a little bit of insight how to get around that, and how to get most out of your systems. Marcus does a great job here explaining how this is done, either via the GUI, which seems to have some problems. It's basically around changing out a license file, which then unlocks a little bit of more capacity. But as he wrote a little bit down in the article, when you come to the error message, so there will be a problem when you try to do this via the graphical user interface. He does then give a great explanation on how to do this via the CLI, because I think most of the customers who would try it via the graphical interface first, they would come to the error messages and then be forced to open a ticket with Dell and see who can help them. This is always the power of the Veeam community when they then provide you with an answer on how to get around the issue without having to go through all the hassle of uploading logs and explaining the problem and so on. He then goes on to really nice explanation on how to insert this via the command line and then also to unlock the additional space on the system. In that case, it doesn't seem like much, like from 50.9 terabytes to 58.2 terabytes, a little bit more down. But of course, the data domain is a deduplicating system, so inline deduplication system, so eight terabytes are not eight terabytes. Eight terabytes will get you a long way on a deduplication system if you count the real number. I think he does it a little bit down in the article. You can see again, file system capacity, it will be expanded by 7.28 terabytes. It even shows it in the GUI, then he uses Veeam to rescan the repository, then it also shows up there. Then in the last sentences, he says around 40 terabytes are occupied on the state domain with over one petabyte actually written and accessed. You can imagine if 40 terabytes refer to one petabyte in real-life data, this is a lot of space saving and seven terabytes will get you a long way. But also, the last sentence should not be overlooked. I think it's very important and I completely agree with Mark on this one. The data domain, let's not just limit it to this specific brand. But inline deduplication systems, in my opinion, and also in a lot of other fellow Vanguard opinions, should not be used as a first choice as a primary target in Veeam. Because as nice as they are for the space savings, and this is also what he says, use them as a secondary target, use them for long-time retention, use it for data which you don't need to access frequently. Because of course, if anything gets deduplicated and you need to read it again, you need to rehydrate all the data and this just takes time. It's in the nature of the system, there's nobody to blame there, it is what it is. That's why a lot of times, it's a problem when you use something like virtual labs and instant recoveries and so on and so on. It's just the VMs get deployed pretty quickly, but actually to work with them and to be able to boot them up and so on and so on, it's just not a good match of random IO versus the inline deduplication systems. There is, that's the nice thing about Veeam, there is a place for every system out there, there is a use case for everything. You just need to be aware of where and how you should use the different systems. It's a great article from Marcus on how to show the community and how to show the world, how to get even more out of your system. Great article. Congrats to Marcus. I agree and you already answered my question because I actually wanted to ask you if you agreed with if data domain should or should not be the first choice when it comes to a primary backup target and on a long-term retention, but you already did answer that question. I'm going to just move to Julia and ask her on her thoughts about this article. Yeah, I really liked the article. You can see there is a lot of engagement, so a lot of people also liked the article. Very helpful because clearly you can tell that he faced a challenge and then he documented it and shared with the community and things like this, you don't see on the documentation, Dell's documentation and this is invaluable because people are going to Google or the error they faced and then they're going to go to the community hub and see that other people have faced the same thing. So I find it is very helpful and very short, simple, straight article. So great, great job. Yeah, I totally agree. And Marcus, don't worry, I can see you are starting. It's a bit older article. Don't worry. I think this type of subjects are going to be useful anytime and actual and people can still use the information. So good job. Thank you for sharing with us, Marcus. Keep on doing what you're doing because it's a great job. Moving forward to another guy that we see very often in our community and posting a lot of stuff. That's Jeff. He's a funny guy as well. Good to see you as well as Marcus at VeeamON a few weeks ago. This time he's talking about don't believe the hype and what he means by that. You know, he is talking about AI here and he says AI is being implemented too fast, too soon and being given too much control. Let's see now. That's a very controversial, interesting topic, I think, and everyone has an opinion. And what I agree with is like AI has been dominating the conversation at every single conference that I attended in the past couple of years. I think the discussion started like to be big at every conference, maybe 2022, the end of 2022, 2023. And I'm sure you guys have had the same experience. But yeah, every company, you know, regardless of industry, seems eager to join this hype, implement AI in their products. And it almost feels like there is a collective FOMO. I don't know if you agree on that or not. Like, you know, the fear that if you don't jump in now, you either fall behind or just miss out on future profits. That's just my opinion on this conversation about AI. And I feel like it's exciting. It's all exciting, of course, and it can be very useful from many points of view, but also raises questions about security and safety. And I think this is what Jeff is talking about in here. And he put together an article. There is a link right there with an article that is pretty good. So if you want to read more, you can just go and open that link. And one thing that I like is like in the comments, you have Chris Hermosel and he says, you know, that right now the European Union created the framework around this. And I think having legal frameworks can actually help mitigate some of the risks when it comes to AI. So hopefully that's going to happen. I don't know if it happened in the US as well or in other parts of the world. Of course, it's still a new topic. But I want to pick up your brain as well, Jochen, Julia, on this subject. What do you think? Sure, I mostly agree with you. I mean, it's always the issue always arises when some sort of new technology comes up on the horizon and there's big money involved. As soon as there's big money involved, as you said, Maddy, it's just if you don't have some form of AI in your product, you're like 1980. Nobody wants to or at least you have the perception of nobody wants to look at your product because you're not AI enabled. And it's actually I mean, everybody of us, especially when you're working with IT, has used some form of AI to to like automate some boring tasks or to to look for something. And I think it's now also at the point where we have to be careful that we actually double check what the AI actually answers us. Because at the moment, I think, OK, I'm going to ask, let's say, chat, GPT, whatever, because it's the most commonly known one. And you take everything for granted, which comes out of there. And this is, yeah, it can be scary. And also, I mean, the text based AI we now got used to, everybody knows it, everybody uses it. But I think yesterday or two days ago, I actually saw a video of an automated like when you make a hotel reception, you call the hotel and you say, I want to make a reception, not a reception, sorry, a reservation for a room. And my name is this and that. I want to stay from here and there. And the hotel agent was completely AI. They even like added little and so little pauses, which a human always does. And it was really I mean, you always I needed one or two minutes to actually hear that it's AI because the little pauses were just they were too automated. They were not like completely perfect. And right now, when you see an AI generated video, especially of humans, you can still see it. There's little hints, especially with the hands and so on. They sometimes look weird, but it's going to get better and better and better. And yeah, although the fake stuff you can create it and the people who believe it without a doubt, it is a scary technology, but it's also a very, very helpful technology. And to your point, Maddy, with the regulations, yes, I think there will be regulations. But I mean, we all know the Internet, right? The Internet has little to zero boundaries. So if one one country or the European Union releases some form of regulation which prohibits the use of XYZ, then you just VPN to another country and so on and so on. There will always be ways around it when it comes to the digital world. So, yeah, it's it's one of the most exciting technologies, but also it can be. It's with every technology, it can be used for the good, it can be used for the bad. And this is something we really need to watch out in the next few years. Yeah, and I think we learned it, as you said, like it can be used for good or bad. We learned it with social media. We learned it with the Internet. Right. So that's true. We'll see what's going to happen with the AI as well. Yeah. Good, good points. Totally agree. Julia, any thoughts on this? Yeah. So I agree with what you both said. And at the beginning, when AI came up, I think we were using it mostly for, you know, productivity tests or, you know, simpler things. But now the problem is that they are integrating AI into core systems. And that's where the danger lies. You need humans looking at it. Because, for instance, you know, if you want to reduce friction in a customer journey, AI might decide to downgrade certain security prompts. Or if the goal is to improve the system efficiency, you may start shutting down processes that it deems unnecessary without telling you. So those are the dangers that I think Jeff was mentioning in the article, that AI is going to start making decisions because we've asked them to do something. They're going to start making decisions without asking us that are important things that, you know, like governance, safety, control, that we need to keep an eye out. So I think every time we need human oversight, independently of whatever AI does, to make sure that everything is in place. Otherwise, we can be creating single points of failure or, you know, automating mistakes at scale. So the good thing of AI is there, but there is a lot of danger. So I think it's good that we have regulations coming. I'm sure, you know, we have in Europe now, I'm sure in the U.S. will have as well in the whole world because AI is pervasive. We're talking about AI everywhere. All the conferences I go to is AI, AI, AI, AI, AI all the time. Yeah, yeah, totally. We actually we were at Web Summit. We're going to discuss a little bit later in this conversation. But it was so much about AI. They had a stage, AI stage, right? And we both saw the Desi, the humanoid robot. I actually, I was part of that session. It was fun, engaging, but it was also a little bit like, you know, scary in a way because she was answering people who were asking questions and were asking questions about, you know, self-awareness and ethical and all that. And the questions seem to be almost like coming from a human. And where is all that going to lead? So, yeah, that's that's a conversation probably we could have for hours and hours. But, yeah, we should also move on to our next article. Thank you, Jeff, for sharing that with us. Really great thoughts in there. And I'm sure we're going to talk more in this show and other shows about AI. So let's go further to Mary. Once again, she's posting on the Veeam app for Splunk. Really, really good. She's a huge fan of Splunk. So, I mean, I get it why. It's a really great tool that, you know, allows Veeam data platform advanced and premium customer to monitor the health, the security status of your Veeam backup infrastructure. And I think it really gives great value because you have like a lot of features in it, built in reports, alerts, you know, like multiple data source location support, app configuration backup, so many things that comes with this app. But this is a great article again, Mary, and thank you for putting it together. I know you like to customize it depending on what you need. We actually discussed it at VeeamON. We had a discussion around this. So very interesting. I want to ask Jochen, what's his takeaway on this article and on the Veeam app for Splunk? It seems to be a trend that every time I come to the community recap, I hit an article about Splunk and I always like, damn, I don't know Splunk a lot. Every time I hit one, but it's actually, and please forgive me if I say anything, which is not correct in the context of Splunk. I just did my disclaimer. I'm not a Splunk expert. But the article is really nice because you don't have to be a Splunk expert to know what she's talking about, what the benefit is. There's actually a dedicated Veeam Splunk app, which you can incorporate into your dashboards and so on. This app is capable of interpreting the messages more granularly or better than other apps. She's actually showing a way how to use the data, which the Veeam app can extract from the data stream or from the events, how you can use this data or this enrichment, as she nicely calls it, from the Veeam app into other apps, which are on your Splunk for whatever reason you need it. This is actually another great article, I think, for the community because it just shows how you can get it done and how you can use the data which Veeam shares with Splunk. Again, please excuse me if I'm saying anything stupid in this context. But how to make more out of the data which Veeam can provide using the logic or the requests or whatever you call it, which the Veeam app for Splunk has built in. So, yeah, it's a great, great article and also very short to the point. If anyone has to forgive us for saying something stupid in here, it's Mary because she's the huge fan and the expert in here. So, Mary, please forgive us if we say anything that is not right. But thank you very much for sharing this with us. Julia, any thoughts on it? Just the first thought is I love when women create content on the community hub and engage with the community hub. Mary, keep going and keep writing more articles. This one is great and it just shows the value of the Veeam app for Splunk that you can use in the environment with multiple Splunk apps and teams and also it reflects how flexible our platform is. So, really great job and technical, again, short to the point, helpful to everyone that uses Splunk and also Veeam app for Splunk. Yeah, and I'm sure there's going to be more coming from Mary because she's working on this and she loves it. And it's not going to be only Mary because we are putting together something, but we are not announcing it yet. So, we're going to have more women in the community. Yeah, yeah. That's still a secret for now. OK, moving forward now to another section, the Vanguard Blog Spotlight. This time we have Petr, I hope I'm pronouncing his name right, from Czech Republic. He's one of the new vanguards in our program. So, first of all, congratulations of being in the program, Petr, because I didn't have the opportunity to say it so far. I think this is the first time we are actually mentioning Petr as well. And this article is pretty straightforward and, you know, like for any person that just begins now learning about Microsoft EnterID backup and recovery options, he covers, you know, the two types of backup tasks, EnterID tenant and EnterID logs. He goes over recovery options, solutions, architecture, required permission in EnterID, licensing, and then he even shows us how to configure the backup for Microsoft EnterID. But now I'm going to start with you, Julia, because I know you've been working quite heavily on this EnterID subject lately. Yeah, yeah. So, why don't you- So, I love this article. Yeah, sorry. Why don't you comment on it? I love the article. He dove really deep into Veeam Backup for EnterID in VDP. So, right now at VeeamON, we also release the Veeam Backup for EnterID in VDC, which is our SaaS offering. But this is a great article because not only he talked about, you know, what we can backup and the licensing, but also he covered the potential issues like when your PostSQL database is not set up correctly, which can disrupt adding, you know, the EnterID tenant. So, he went over some challenges that people might face when they are starting out implementing the solution. And I love it also because it's really important to backup your EnterID objects. People often think that if they're using the cloud or if their, you know, environments are in the cloud, they are protected. But again, we talk so much about shared responsibility model. You have to protect your identity, management, everything. And for instance, if you're using M365, you have EnterID objects, you have EnterID tenants. So, you have to back them up. And Petra did a great job, very, very detailed. And I'm going to talk to him. I'm going to connect with him to maybe create some content about EnterID because it looks like he knows a lot about that. Yeah, that's great. And Johan, what's your takeaway on this article, but in general on the EnterID? What do you think, like from your experience? I totally agree with Julia. It seems like we have the M365 discussion from a few years ago. We have that now over and over with EnterID because when M365 got big, everybody was like, ah, Microsoft is going to take care of it. I don't have to back it up and so on and so on. Now, we have the next workload, the EnterID backup, and we basically start from scratch. So, what I really like about the article is that it's one of the newest workloads that Beam can back up. So, there's not a heap of information out there until now. So, and it's always nice when there's a new article coming out, which really, as Julia said, does a deep dive on the issue. And really, also, he talks about what permissions do you need, what components is used and so on. It's a really deep dive until the troubleshooting at the end. And so, it's always nice because basically, now, everybody or I think most of the people know how to back up and restore VMs. This workload has been around for decades, and there's tons and tons and tons of articles around it. You can find everything. Actually, it's oftentimes you spend too much time looking for the right answer because there's too much content around that until you find the right one. So, it's always nice to have an article about a new workload, which not a lot of people have looked at in detail and so on. But from my perspective, I think the Entra ID backup will be more present in the VDC world than in the VDP world. I mean, it depends if a customer has… It's nice to have the option to have both, although I do not agree with the licensing terms in the VDP world, but that's another story. But I think when a customer has already some VDC workloads going, M365, Vault, Azure, whatever, he will just add the Entra ID backup and be done with it. But it's nice for customers who do not want or have another solution for their M365 backup that they can also use their on-premise Veeam system to back up the Entra ID. And they just have to talk to their sales representative if they can get a better quote. Okay. That's an interesting point of view. Yeah. Thank you. Thank you both for that. And thank you, Petr, for putting this together. Great to have you in the recap. Hopefully, we're going to have you more often. And yeah, wait on Julia. She seems like she's going to contact you and work with you. Good. Yeah. Good stuff. So let's move to our next section, which is the special department news. And the first stop, blog of the month, April 2025 winner. Congratulations, Marcel. I think this is really the first time when you are posting at the community hub. He's also German, Johan. You'd be happy to. Oh, no, he's not. He's Slovakian. He's Slovakian. He's not German. Okay. Still cool. Okay. He's Slovakian. But yeah, first time he's posting, I think, at the community hub. And look at him. He got most of the votes in there, 13 votes. So he got a badge, blogger of the month. So hopefully, we'll see you more often. It seems like the community appreciates values, what you are doing, what you are talking about. So good job. Moving forward, we have a lot of great Veeam user group in-person events happening this month as well, virtual. We are now recording on a Tuesday. But yeah, today, there was one in Turkey as well. Really good attendance. That was a virtual one. And next, and today, I think we have a bunch as well. One of them, Julia and myself are going to attend in Brazil. We are here in Sao Paolo. So we're going to attend. We're going to let you know how that is turning out. But next week, we have VUG Italy meetup. Thank you, Antonio and Marco for putting this together and the Veeam team in there. So that's going to be in Bologna. And yeah, you still have time to register if you haven't done so. The next one, VUG Finland is also going to be an in-person event. That's going to be in Tampere. I think Edwin, our colleague, is going to be there. He's going to have a session as well. And thank you, Mikko and Dil for putting this together. You guys are rocking it. So fantastic. Also, you have time to register May 15. All these three that we are presenting today are going to be on May 15. VUG USA, Shane in Kansas, he's also putting together one. So thank you for that. So if you are in Kansas, you want to attend the Veeam user group. You know where to go to the community hub page and register in there. There's still time for you as well. And yeah, as we said, today we're going to attend the VUG Brazil one in Sao Paolo. So we'll let you know how that goes. Maybe I'm going to share some pictures as well in the next recaps. Not next week, because Johan might replace me, but the week after. So great stuff, really great stuff. Last but not least, Julia, we were at the Web Summit in Rio last week. And we had a good time in there. There was the good, the bad, the ugly, and everything in between. It was a good event, a bit overwhelming. But I'll let you talk a little bit about experience. What I'm going to do, I'm going to talk a little bit about my favorite session. So yeah, so yeah, overwhelming. And I would say the exact word is intense. It was very intense. There were more than 44,000 people, 45,000, I think. Yeah, it was, I think, the biggest. I'm not sure how many people go to reInvent, but probably, you know, similar. But it was just overwhelming as well, because there were several topics discussed there. So they were talking about, obviously, AI, crypto, Web3, about marketing, content creation, about fintech. There were a lot of startups presenting there. There were also investor sessions. There were masterclasses. There were the talks at the main stage. And there were, I think, like six other stages. So it was really hard the first day. I didn't know what to do, because I went without expectations. I didn't know where to go, who to talk to, why I wanted to learn. And I needed to, I even, I stayed, I think, in the bathroom for 20 minutes, because I needed to breathe a little bit. It was too much. And I think next time, if I end up going again, I will go with, like, intent. I will plan ahead. Oh, these are the things I want to learn. These are the sessions I want to go to. Otherwise, I would say it's overwhelming, for sure. Yeah. Well, I totally agree with what you are saying. We were there, actually, for the women in tech component. And I feel like it's a missed opportunity, because that is not that developed as we thought. Also, the community stage or area was also, like, I didn't see that many people gathering there. And not too many talks, you know, like on the women in tech, diversity, equity, you know, these type of topics. There were some, but the ones that I wanted to attend, they said initially they're going to be in English. That's how they put it in the agenda. But they end up to be in Portuguese. So, I did not attend those. But one thing I actually put together, the second part of this is, yeah, is about my favorite session. So, I picked, like, I think, five sessions from different stages, because there was an AI stage. There was a fintech stage. There was a marketing stage. There was a media stage. So many stages, as you said, pretty overwhelming. And the main stage, I only attended one at the main stage, and where you had Iveci Sangalo, who's a Brazilian famous singer in here. We had Aloe Black, who's the singer of I Need a Dollar and Wake Me Up. So, he did, like, some singing as well. Which was, yeah, it was pretty good, that session. It was around AI as well. But it ended up to be very engaging. But my favorite stage, I must say, it was the fintech, because I like cryptocurrency and blockchain topics. So, I put together here on, it's the second, but it's actually my favorite session. It was a panel called Cryptopia, and it was four people, Marcelo, Reinaldo, Kathleen, and there was the moderator as well. And they were discussing about the adoption of blockchain and cryptocurrencies in Latin America. And they were talking about how the pro-administration in the U.S. is going to influence the adoption on a global level. But one of my favorite, really my favorite point was from Marcelo Sampaio. And he says, you know, you should view crypto as a phenomenon and not something to take too seriously just yet, you know, just something to observe and to explore and understand. And to, you know, to just look at the potential utility that could have for you in the future. And I couldn't agree more with that, because this can, you know, this can transform in such a big way. Think about the internet from when it started to where it, you know, where we are today with the internet. Same, he was saying that in 2001, he was working for Microsoft and they were already talking about AI. And it was just like, imagine a conversation about AI in 2001 and where we are today with the AI. So I think this was definitely my favorite conversation. There were so many good points in it. And one of the points that I made, as you can see there in green, is should Veeam explore the world of cryptocurrency and blockchain? And probably when it comes to data trust, immutability, compliance, I think there is a lot of potential in there. I don't know if you guys have any thoughts on that. Johan, any thoughts? How much are you into this world, interested in this world of blockchain, cryptocurrencies? What do you think? Would Veeam have a place in this world or not? His face said everything. I'm completely annoyed that I didn't go into it a few years back. I mean, I'm a couple of years old. I would have had the chance for it, but no, I didn't. And I still could kick myself for that. I'm not so deep into the topic, but what I don't like about it is that now I'm not talking about blockchain technology itself, but about cryptocurrency, that it got such a bad taste because there were so many, the small pump and dumps, the meme coins and so on. So, so many people got ripped off during this hype of the cryptocurrency because it was always the same thing. We have the next big thing and you're going to be earning tens of thousands of percent of your money back and so on and so on. We all know the scams and they work just way too often. And this is why I think it has a bit of a bitter taste in my mouth, but there's definitely room for blockchain and there's definitely technical possibilities when it comes to blockchain technology. I actually never thought about if Veeam could benefit from implementing blockchain at what point. I don't think I'm qualified to answer on your thought. Maybe a question to think of, you know, maybe something to think of. Yeah. But to your point, I agree with what you're saying. A lot of people lost a lot of money, but a good point in this session was, you know, crypto should be viewed less as a vehicle of price speculation, but more like a driver for technological innovation. So I put that line in there and I think this is very powerful and people should look at it more from that respect. And to your point, you are saying like, you should have done more in this respect a few years ago. To Marcelo's point, it's just in infancy. There is still so much opportunity in there. So, and I agree with that. I totally agree. But yeah, I could talk hours and hours about these subjects because I really like it, but I think we should probably close because we are, I think already 50 minutes. But that's great. It means that the conversation was really good. And yes, you put together an article. I put together two articles as well. So if people are interested in reading more about it, they want to, you know, in the future attend, see what's the value, see what are the topics, see if it's worth attending it. But yeah, overall it was a really good event for us and I'm glad we attended. Would I go again? I don't know. But yeah, good pictures for sure. I was standing there. So yeah, I just want to thank you both for taking the time to be part of the show today. Do you have any final thoughts to close this show with? I'm just happy that on Julia's article, you didn't scroll down to the picture of Desmodona or the robot. This picture is scary. It is, it is. She is scary. Well, she, I don't know if we can call the robot. Yeah, but yeah, it's scary. It's creepy. And yeah, no, just ending thoughts were, thank you for the opportunity. This was a lot of fun. Yeah, it's always fun. It's always fun. The recap is always fun. It was my first time, yeah. Well, hopefully it's not going to be the last. So yeah, I hope that everyone that watched us today enjoyed it as much as we enjoyed it to record. And as I said, next week I will be on vacation. Most probably Johan is going to replace me. He's going to do another recap with Rick. But wait for the surprise. We don't know yet. And yeah, have an awesome weekend community and see you next time. See you.
