(upbeat music) >> We're back at VeamON 2022, at the Aria in Las Vegas. You're watching The Cube. My name is Dave Vellante, and I'm here with my co-host, David Nicholson. Danny Allan here is the Chief Technical Officer at Veeam. And he's joined by Ope Bakare who's the Chief Technical Officer at HBC Dave. One of the few companies that's older than my home. >> Unbelievable. >> Ope. >> That's right. >> Danny, great to see you. Thanks for coming on. It's true by the way. 1670, we're going to learn more about HBC. But I wonder, Danny, if you could set it up. The kind of topic of this discussion here is hybrid cloud, we've got a pretty interesting use case, give us the high level, what should we be focused on here? >> So lots of customers today focused on digital transformation and moving into the cloud, everyone talks about that, I can take my workload and move into the cloud. And one of the interesting things that we saw originally was, you know, I'll just lift it and move it over there. That's not necessarily the best model for the cloud. So you see people doing that. What I actually think is really interesting, and I know Ope has been very focused on is actually transforming the application so that works most effectively in the cloud model. >> So Ope, maybe give us the background on HBC, for folks who aren't familiar with the company and your role there. >> Sure, so HBC is 350, somewhat years old. It's the oldest corporation that's continually existed in North America. I have the privilege to serve as the chief technology officer there. And, you know, HBC is a company that has innovation kind of baked into its core DNA. We have to keep reinventing ourselves, otherwise, we get stagnant and we get left behind. Clearly, we're still around so--. >> So far so good. >> We must be doing something right. But kind of pivoting to what you were saying earlier, you know, our journey to the cloud was multifaceted. Some of it was to improve the pace of innovation, some of it was to improve on quality. So you know, we have typical data center technologies, and, you know, we had some of the typical issues you would have, right, so some older equipment, you know, failures, etc, etc. When you're in the cloud, a lot of that is just managed for you. Again, it's about what I talked about this morning, it's about moving your team up the value chain, towards creating value, right? So you start with the managing of core basic infrastructure, and you start consuming them as services. The interesting thing is, as you mentioned, for the vast majority of people, your first foray into the cloud, is pick up all those virtual machines that you had on-prem, and put them in the cloud. And that's great, you get, immediately you get a better, possibly a better or more available under a cloud platform there. But you're just barely scratching the surface. You don't really get into cloud until you start consuming cloud native services, until you go serverless, you go stateless with containers in Kubernetes, you can use platforms like, you know, Kafka for streaming your data, as opposed to, you know, constructing cumbersome, easy to break data pipelines and all that. So it's a very interesting pivot. And I think a lot of people sometimes struggle with going past that first step, they have the VMs, it's familiar to what they're used to. But for us, we had a digital transformation in the works. We were replatforming from a legacy platform, some of you may know, Blue Martini. But we were moving to a more modern, more flexible platform that was really suited to accelerate our omni channel strategy. Thank goodness we did because the pandemic came around and proved it exactly correct. >> Good timing. >> Yeah, so that's really what happened for us, that actually forced us forward in the cloud journey. >> So Alan Nance, who was at the time, he was like a CIO slash CTO at Philips. And he said to me, if you just lift and shift to the cloud, this is early days of cloud, he said, he's not going to change your operational model. The company, if you want to save billions, you got to change that operational model. But listening to what Ope just said, Danny, what does that mean, from your perspective, I mean, cloud native, and what does that do for your business? >> Well, cloud native,. The benefit of the cloud, of course, makes completely portable, and it's elastic, you can scale almost infinitely, and you don't have to build it. However, the hard part is not the technology. I always say the hard part is the process, you actually have to rewrite your applications to take advantage of all the things in the cloud. And that is not an easy thing. So what we're seeing a lot in the industry across our customer base, is when they have a greenfield opportunity, a new project, they always start in the cloud. We're not seeing a lot of, hey, am going to completely modernize my applications, because that's expensive. It's already built. And so customers will sometimes pick that up and move it to the cloud. And sometimes they'll actually move it back on premises, because the cost model isn't there. But I do think in the long term, if you're looking at four or five years, all the new applications will be designed for a cloud native experience. What that means is written in containers, with container orchestration, you know, seamlessly orchestrating the entire portfolio and data lifecycle. >> So Ope. >> Spot on. >> Translate that into what actually happened at HBC. So as Danny said, we're not going to just going to move everything into the cloud, we've got a hybrid setup, maybe some of the new stuff. What did you do? You have the, your back end systems, your database kind of protected that? How did you go about this omni channel journey? >> So, you know, for us, you know, by the way, that was completely spot on. You know, it's not a fallacy to really examine some cost, because we all have to, we'll have to live in the real world, right? We understand that there are budgets, and there are limits to what we can accomplish within a fiscal year. So you look at an application that's already built, that's already fulfilling the business purpose for which for which it was built. What's the value in immediately going and taking it all apart and containerizing it? If there is a small or easy lift, sure, it might be worth it. But if it's a major system that you have to rewrite, the ROI is just not there, right? So a lift and shift model in that scenario, kind of makes sense. But what you said earlier is exactly what we did. When we had an opportunity again, with the omni channel strategy, we're looking to strengthen our digital arm. And so we were moving from our legacy platform to this new one. And that required us to do a bunch of work. So we had to modernize some of our services, we had to change some of our data, our data process, how we stream data into and out of the e-commerce platform. And all of that actually provided sort of almost a groundswell of support for all of this transformative works. Apologies, for all this transformative work we had to do. So it totally made sense in that case, we actually were able to kill two birds with one stone, really transform and go cloud native, at the same time as deprecating a bunch of legacy technologies that to be perfectly frank didn't really have much of a place in the cloud. >> So many questions. I hope, go. >> Yeah, so it's interesting, because when you talk about that sort of journey to cloud that you're on, sometimes people will ask the question, well, how long before everything is in the cloud? And often the answer is, if you look at what's called the vanishing point, where the two sides of the highway come together, off in the distance, it's like, that's, that's when it'll happen. But as you get closer to that point, it gets further away. So if you had to categorize it in terms of a percentage of where you are now, and then an aspiration over time, how would you categorize that? >> So I have the pleasure of telling you that we are probably at about, I'd say 90% in the cloud? >> Oh, wow, okay. >> We were very aggressive about it. And frankly, I think, you know, first of all, I have the privilege to lead an amazing team. And they did everything possible to make this real. We had a goal, and it was focusing on our customers, being customer obsessed, really. And for us, data centers just didn't make sense in that world. So all we did was work towards how do we deprecate these legacy technologies? How do we consolidate and then move them to the cloud as quickly as possible? So for us 90%, and we're going even even further. Is that last 10% worth it, to go for that? I mean, you know, what's the, you know, you get to that marginal return? >> I really think the next 5% will be worth it, the last five we're not going to pursue and here's why. So think about, you know, we talked about really low latency things that need to be physically in the building. So we have a bunch of, we have a whole lot of fulfillment and distribution centers, right? Those, in some cases, we have automation equipment that really requires low latency connectivity to physical equipment. Moving that to the cloud, is not really a high value proposition. If you think about, you know, large corporate presences, there are some pieces of technology that you could move to the cloud. But again, latency in the customer, the users experience might be compromised as a result. If there's no value, really, to moving that into the cloud, why would you do it? >> And wouldn't you have to freeze the application in order to move it into the cloud or not for these 10% or 5%, or not necessarily? >> Not necessarily. In many cases, we have applications that are built in a distributed fashion so that you can take, you know, some percentage of it, move it to the cloud, validate it over there, and then move the rest of it-- >> You could build some kind of abstraction layer, okay. So the million dollar question is, what does Veeam have to do with all this? >> Well, so Veeam has been for quite some time now, our data protection engine. You know, when I talk about moving people up the value stack, I don't take that lightly. For me, you know, having engineers do things like and please forgive me for a second here, but do things like backups, to me that's, it's a hard requirement, but it's not really high value for me. So if I can get a platform that can use policies, can use tags can operate natively in the cloud. And once you have it running, you can set it and forget it, other than your periodic, you know, business continuity to DR Tests. You know, that's the dream scenario. And we've achieved that largely. We still have some legacy systems that are not on vignette. But that's something that's going to change over the next, let's call it 18 or so months. >> So did you evolve as Veeam evolved? How long have you been in this role? I apologize-- >> I've been with HBC for three years now. >> Okay, so now, Veeam goes, well, I remember I first saw Veeam at a VMUG. I'm like VMware, I was just brilliant, right? Of course, we all say that. Now, but you saw Veeam's ascendancy through virtualization, and then it took a while, but then all of a sudden, bare metal, the first in SAS, great cloud strategy. Now the first in I don't know if I can say that. Scratch that. We will talk to you about that tomorrow. Someone will come here. >> Someone else will come here. At VeeamON. So, from what you know, about HBC, did you kind of follow that Veeam strategy, they were just sort of there as you migrate it to the cloud, SAS, you know, Microsoft 365, etc? >> Yeah, so we actually started using Veeam in a very limited capacity quite some time ago, mostly to protect on-prem virtualized workloads. And that was, you know, that was really the limit. And, you know, my team had been used Veeam, in my previous role when I worked for a large healthcare provider, health care company in the states. So I was pretty familiar with Veeam as a platform, I was very familiar with the journey. I think that you know, more than many other, most of their competition, they've made the transition into the cloud first world, far more successfully. If you think about the policy engine, the automatic tearing, by age, as well as some of the cloud tagging, and the full integration with the native capabilities in AWS and Azure, it's been a dream scenario for us. >> You and I have talked about this Danny, and a lot of your competitors, especially early on the cloud, they wrap their stack in, you know, to container, or Kubernetes, it's shoved it in the cloud, which is really hosted on prem app. You guys didn't do that. I mean, I pushed you on this a number of times. What did you do? >> Every time there's a modern infrastructure, we say, how can we actually apply data protection, modern data protection to that infrastructure, specifically. We don't try and take what already exists. And Veeam started at this. If you think back when we first started, everyone was doing agents. And if you took an agent, put it on a hypervisor, and you'd 100 of them running at the same time, you would kill your production system. So we said, we'll take a snapshot at the hypervisor level. And then when storage arrays came up with snapshots, let's take advantage of that. When we went to the cloud, we said let's take advantage of the API's rather than trying to put an agent in there. And so every time we encounter a new infrastructure, we say, how do we take advantage of what that infrastructure is bringing? >> We're going to dig into more of this tomorrow. But I don't want to steal from the HBC story. Let me ask you about, you talked about, we talk a lot about digital transformation and modernization. And, of course, COVID was like a force march to digital, we all sort of realize this. What do you see Ope, that's now permanent? Whether it's, you know, security, data protection, and how you're thinking about modernization? What are those practices that are now best practices that will become permanent? >> Well, the obvious one that kind of hits up hits us all in the face is remote work. For the past, let's call it two ish years, my team has been almost completely remote. And as a result, you know, we've been able to show that, for us, it worked just fine. There were some teething pains as we all did >> It was like Y2K. Wasn't it? Hey, the world didn't end. >> It became a non factor very quickly, why? Because for most technology organizations were too used to working outside of normal hours. So it wasn't a stretch really to extend a logic to just working, you know, working remotely permanently. That said, you know, one of the things that for us, and I'm going to deviate away from the technology side for a second, one of the things that is really critical for us is we're trying to make sure that we respect people's work-life balance. As we have colleagues who work from home, you know, today, it's very easy to roll out of bed in the morning, you know, put your zoom suit on, and you know, where you're wearing your shorts, and all that and just work the whole day and then around like five to 7 P.M. or whatever, you sign off and you just realized, I just spent way more time working than I probably would have if I were going to the office. That's you know, it's a great productivity-- >> With no breaks. >> With no breaks, right? And there's no button, no water cooler moments or whatever. But, you know, we're trying to, we're trying to come up with various ways to respect people's, you know, work-life balance. Interestingly enough, we actually have a law that is going to effect in early June, in Ontario, where there will be a right to disconnect. So outside of normal working hours, you will be required to disconnect from your employees unless it is an operational issue, or some other pertinent emergency that requires them to engage. So, I think that's going to become the new norm as we go forward. Coming back to technology, I think just looking at the last two years, I don't know if you've noticed the same thing, but the pace of innovation seems to have picked up a tick. And I think that is going to become the new normal. You're going to see a lot of people challenging status quo a lot of sacred, a lot of sacred cows are going to get, you know, get, you know put out to pasture. And I think that's a good thing for our industry, it's going to quicken the pace of innovation. And it's also going to make people more thoughtful about where they place their bets, I think. You know, the other thing, this is the last one, dollars and cents. If you think about the pandemic, when it first started, we all had to take a breath, because instantly, a whole lot of industries just paused, right? And when that happened, you know, you had no revenue coming in. You had, it was whoa, what are we doing here? And I think that also sharpened our focus, when it came to making some some decisions. You know, we all had to deal with, you know, in some cases, furloughs and some cases reductions. Thankfully, we're all back to back to normal now. But where you place your bets financially, it's going to drive a lot of technology decision in investing, right? So I think that's going to be a larger part of our kind of landscape going forward. >> So that last point about innovation, Danny, it's got to be music to your ears, because your, the premise, you're saying, behind Veeam, is you look at the next trend and then modernize, you put meaning behind modern data protection. It's not just a tagline. You gave a couple of good examples. But talk a little bit more about, you know, what Ope just said and what that means to you guys? >> Well, at a technology level, I always talk about three things being part of modern data protection. One is, around the security, everyone working from home, there's intellectual property going into the home on the endpoint in Microsoft Teams, in all the collaboration tools, that needs to be protected. And actually, we're seeing because of the rise in ransomware, cyber insurance is actually requiring data protection for that. So a big part of modern data protection is all about the security of the environment. The second is cloud acceleration. We want customers to move to the cloud. I love sitting here quietly listening to him tell the story of what they're doing, because it's perfect. That is the story that we want from our customers moving to the cloud. And we don't want to stop that in any way. In fact, all of our licensing models go to market, support set cloud acceleration. And then the last thing is, of course, data protection. If they're going to do that, you own that data, you need to protect it on any cloud and on every cloud. And so our focus around modern data protection is those three things. Ransomware protection, cloud acceleration and modern data protection >> In an environment that is not bespoke, I presume, we're going to talk about Supercloud tomorrow. But right, but this idea that instead of going to, I don't know, if you run on Google, AWS, Azure, whatever, but instead of going there and doing your thing, and going over here and doing your on-prem, but you want a consistent experience across all your estates, whether it's on-prem and the cloud, eventually out to the edge, we're going to talk about that tomorrow, too. Is that a fair premise? >> It is. I mean, operational consistency is absolutely crucial for my team to succeed. I mean, think about running multiple different tools for data protection, it just creates a whole lot of interaction, let's call it that has friction. And ultimately, with anything and technology, wherever there's friction, you're going to have problems eventually, and you're going to have varying levels of skill in the team. Suppose you have part of your data protection team, you lose one or two people to COVID for a week, right? And you have a DR test. And it's so happens that these are the experts at FUBAR software, that is your data protection platform. The people that you may have on-prem, available may not have the right skills. I mean, unifying that stuff and actually running them out of the same ethos, really. I think that creates operational consistency that is so valuable for us to be successful. There was one thing I wanted to bring up, just hearing what you said earlier. Zero trust, I think is going to become part of our industry baseline as well. Zero trust approaches to network connectivity to tooling so that you stop dealing with traditional VPN. >> Tho nication >> Tho nication It just, that's where we're going as well. So apologies but-- >> No, not at all, it was a buzzword before the pandemic. >> It was but it's actually-- >> Now, it's a mandate. >> It's kind of, it's come back and become actually useful. >> If people are trying to, okay, what does this really mean? What does this mean to our organization? Exciting times, you know, the thing is, there's a lot of unknowns, right? And we certainly saw that with COVID. So how do you as a technologist deal with, you know, it used to be we would automate the known. This industry is built on that, right? How are you approaching what you don't know, from a technology, infrastructure and process standpoint? >> So I'm going to, everyone watching, everyone turn their videos off, when it's, I'm going to give them a secret, it's the people. The people are the secret sauce. If you surround yourself with amazing people, curious people, you can solve any problem. I again, like I said, I have the privilege of leading this team. And we have some amazing thinkers and problem solvers. If you set them to task and give them the right support as a leader, they will accomplish anything. And so for me, having a robust and just really diversely skilled team allows us to attack any problem, I have zero, I have zero worries about the future of state of technology, I have absolute confidence, we'll be able to engage, master and exploit whatever technologies come our way or any other challenges that actually happened to you know, be in our path as well. >> We hear this a lot in The Cube people process technology. Technology, figure itself out and get the good people you can get the right process and win. >> Absolutely. >> Ope, Danny, thanks so much for coming on The Cube. Danny, we'll see you tomorrow. Tomorrow afternoon Danny's coming back and we're going to dig into a lot of this stuff and double click on it. Appreciate your time. >> Absolutely. >> Thank you. >> This is Dave Vellante, for David Nicholson. You're watching The Cube's coverage VeamON 2022. From the Aria, in Las Vegas. This is day one. Keep it right there. (enchanting music)