>> Announcer: Live from Chicago, Illinois, it's theCUBE! Covering VeeamON 2018. Brought to you by Veeam. >> Welcome back to Day Two of VeeamON 2018 in Chicago. My name is Dave Vellante, and I'm here with Stu Miniman. You're watching theCUBE, the leader in live tech coverage. Dante Orsini is here. He's the Senior Vice President of Biz Dev at iland. CUBE alum. Good friend of theCUBE. Great to see you again. >> Great to see ya. >> Thanks for coming on. >> Yeah, thanks for having me. >> What's happening with iland these days, in the world of cloud service providers? >> Well Dave, it's been insane for us. Obviously Veeam's a huge partner of ours. We've been working together for what, seven years now I think. And it's just amazing to see the growth of this company. Right? We've integrated Veeam -- our relationship. We started off basically providing managed backup many, many moons ago. But six years ago we started to build our own platform, on top of Veeam, on top of Cisco, on top of HPE. Customers really wanted to see more control. They wanted greater levels of security. They really wanted a true enterprise cloud. To do that we had to enhance the VMware stack. We had chose to take Veeam and integrate them via their API. Today if somebody deploys anything in the world with iland, it's automatically backed up by Veeam. If you fast forward a bit, as you see what Veeam's done to innovate with cloud and multi cloud, they've really helped build our business. >> Dante, if you go and look back before the whole cloud wave, the typical service provider. They would have one of everything. You'd walk down the aisles and there'd be whatever it was. An EMC box. A digital box. Whatever it was. Did virtualization change that? Were you able to consolidate? Create a platform. Create a simpler environment to manage. Or is there still a lot of bespoke infrastructure lying around? >> Yeah, that's a great question. For us, I'd love to tell you we hit it right the first time twelve years ago. But no. Just like you said. There's all sorts of different technologies right? But I think what we've done is we quickly standardized. We leverage Cisco UCS from a compute perspective. We leverage some of their storage platforms for the things that we do with Veeam Cloud Connect Backup. We actually help them drive the validation of that product before it came to market. We operate at scale with them. Same thing with Veeam. We're their the largest cloud provider in the world right now. As far as leveraging Veeam technologies. In addition to that on the storage front, we also because of the demands of the environment, we really want to deliver a secure cloud service. Encryption is table stakes, and has been for years. HPE Nimble plays a critical role for us there. That's really our stack. Cisco from a network and a compute perspective, VMware with the hypervisor, and HPE from a storage perspective. >> It's sounds like you've taken some very cost effective platforms. Nimble, Veeam, etc. And then architected an enterprise class solution. You guys are adding value around that as an integrator and obviously a service provider. >> Yup, correct. And I think the market is demanding more and more from a cloud provider. People want true transparency. They want control over the infrastructure. For us it's like, how can we develop an API? So we can make this platform extensible. And then still work with the customers that are struggling with the promise of cloud. And Stu, you see this all the time, right? >> Yeah, and Dante, one of the things we're discussing here is it's a very hybrid world. As Veeam said, customers are doing lots of SAAS. They're using service providers. They have their own data centers. They're using a few public clouds. One of the things I've been watching real closely is companies like iland and the other cloud service providers Amazon and Microsoft aren't the enemy anymore. It's, well we actually have to partner with them on some services. We do some things locally. Maybe give us your viewpoint on how that's changed in the last couple of years. >> Yeah, great question. I would tell you that we're not quite there yet, Stu. From my perspective. You guys know, we're known best for providing disaster recovery as a service. That's where we've made a name in the space. But the irony is we've really focused on building this cloud infrastructure. So an I as platform. And ironically that's the majority of our revenue. When we look at public, clearly it is a hybrid world. Where we spend a lot of time, is investing in how can we highly automate the integration? Because we know that people are going to have workloads everywhere. The idea is, think about it from a recovery perspective. If I'm protecting your traditional workloads. And you've got a dev team that's using various different services that are proprietary to a public cloud, that stuff's got to talk to each other in a true resiliency capacity. We wanted to make sure that people could actually highly automate and orchestrate a failover to us, a test to us. But also integrate the connectivity portion of that. Right? Making sure that all these things can talk together is important. You understand as well as I do, as these cloud architectures change, become more modern, and they're more service driven. The traditional, I'm going to move from point A to point B is no longer in play. It's how can I have more diversity amongst my vendor base? If I'm using containers. You've got a globally distributed architecture. If I can deploy some of that with iland, and some of that maybe using Kubernetes, that gives me diversity for recovery. >> Dante, you've hit one of the key things we've been as an industry struggling with. That pace of change is just so rapid. How do you internally deal with that pace of change? As to I architected something today, and tomorrow there's something new. Tell us what you're hearing from your customers as to how they make their decisions and sort through this constantly changing Rubrik? >> Well it's definitely insane. We see all sorts of various different use cases, depending on the industry. And that pressure to innovate at the speed of light is, really people struggle with it. I think from our perspective, there's a couple things that we're doing. One, we actually wrote our own assessment application. We call it iland Catalyst. This was really designed to help both our customers as well as our partners. Cause we go to market through a lot of partners as well, to help streamline this pre-sales process for a customer. Again, we focus squarely on the VMware infrastructure stack. Being able to pull an inventory of what somebody has in their environment. And then go through and select resource pools and VM's, for whatever the purpose. Whether they're looking to work and shift workloads. Or whether they're looking to protect them from a backup or DR perspective, we're able to mitigate all the challenges associated with that. To your point. As people are looking at cloud, it's like okay. Is this cloud thing real? And how's it apply to my business? What can I really do with this? And by the way, I got to deal with my budget also. What's this stuff cost? We've got some really smart people. But you can't scale our smartest people globally. We wanted to really drive that into an application. It's really helped get people to outcomes much quicker. So do it right first. >> Dante, if you reverse back a few years ago, VMware was calling Amazon a book seller. Amazon was calling guys like VMware the old guard. The old way. They kissed and hugged last year. You must've loved that first of all. Because it was like, great, VMware specialist. We'll just drive truck through that opportunity, because we get service provision, cloud, VMware stack, boom. Now fast forward. They've got this little kumbaya thing going on. How do you now differentiate from that? >> Yeah, that's a great question. First of all, VMware, obviously a very strategic partner. I think they've got a long road ahead of them. On some of the things that they're doing. I think the promise of where they're going is great. But I still think there's a lot of folks that struggle with the idea. Think about co-mingling my traditional workloads. And then trying to integrate cloud native services on top of it. I think it's a tall order. We'll see where it goes. We're keeping a close eye on it. But in the interim for us, we continue to see folks that are saying, look I want to get out of the data center business. I've built my data center on VMware. I need to have much greater levels of control and visibility. And you need to make this easy on me. From that perspective, we've been able to do really, really well. We work with a lot of service providers that are looking for that level of a consultative approach. But also want to realize the benefits of a cloud. The point being is, I want a great cloud but it needs to be enterprise class. And I also need to know that I might need help architecting that migration. >> Well that's the key, right? You're not going to get that from an Amazon. They're not going to come into your shop. They're not going to hold your hand through it. They're not going to help you build the architecture route. And help you manage it on an ongoing basis. >> Dante, it's May 2018, so I'd be remiss if I didn't ask about GDPR. >> Hey Stu, I love you man! This is great. You guys know we operate globally, and have for over a decade. GDPR we were way out in front of this. I'm not sure if you follow, The BSI just came out with a new standard. 10012, I believe. I think our Compliance and DPO Officer would be pretty proud of me for remembering that one. >> Dave: I'm proud of ya. >> It's tailor made for GDPR. We've been pre-certified, one of four companies that did it. We do a ton in the security side and the compliance side. And I know they go hand in hand. We went through a global audit last year. On the back of some of the ISO work we do with the CSA, the Cloud Security Alliance. And actually came out with a gold star certification. Sounds juvenile, right? A gold star, woo hoo! But it's a big deal. Only iland and Microsoft have actually achieved that level of certification. Yeah. On the compliance side we're way out in front of GDPR. We're doing a lot from a thought leadership perspective in educating both the partners and the marketplace. I think it's going to see what happens with Brexit also. I think you'll see the rest of the world kind of find their way to their own type of regulation. >> What do all those acronyms mean for your customers in terms of GDPR compliance? How does that turn into value for them, and make their life easier? Can you explain? >> I think right now the whole market's been in my opinion has been ill prepared for this. You see a lot of people scrambling. Being able to identify what data is going to fall under that regulation. How you treat the data. How you're able to account for the data. And also destroy the data. And validate that. Is frankly I see some of the biggest sweeping change in marketing. I see marketing people really scrambling. Because they have to make sure that they double-opt in. Cause the fines for breaching this are unbelievable. I think you're going to see the regulators make an example out of certain people. >> No doubt. >> Quickly. >> There's going to be some examples. They're going to go after the guys with deep pockets first. But the fines are... What are the fines? Four, is it 10% of the turnover? No, 4% of turnover. >> 4% of your previous year's turnover. >> Which is insane. >> Yep, yep. >> That's going to hurt. >> Or something like 20 million pounds, something like that. >> Which ever is greater. >> Which ever is greater. Yes! Yes, exactly. Yup. >> It's pretty onerous. Dante, VeeamON 2018, we'll give you closing thoughts. >> Fantastic event, right. Just super appreciative for our relationship with Veeam. They've been behind us. They've been behind this whole cloud provider community. I mean guys, you know this. Raat Mere and team had the ability to go take this stuff to a public cloud many moons ago. They chose to enable a managed cloud provider market first. We are very grateful for that. >> Awesome. Hey thanks so much for coming on theCUBE. Great to see you. >> My pleasure. >> As always. >> Yup, go Yankees! >> Oh whoa, time out. >> Go Yankees. >> While we're on the topic. Listen, you can't beat the Red Sox in April. Okay, you know that, right? >> Yeah, here we go. >> So it's going to be interesting to see. I mean I have predicted the Yankees take the east, and they go to the World Series. But you got to be excited as a Yankees fan. >> Could be a good year. >> I've always liked Brian Cashman. I think he's one of the best GM's in the business. Watch his moves at the trading deadline. He's going to beef up the bullpen. I hope the Sox can hang tough with him because anything can happen. >> It's true, anything can happen. >> Hey, great to see ya. >> Great to see you guys, thank you. >> Go Sox. >> Dig it. >> Keep it right there everybody. We'll be back with our next guest right after this short break.

(calm music) >> Hi everybody. We're here at VeeamON 2022. This is day two of the CUBE's continuous coverage. I'm Dave Vellante. My co-host is Dave Nicholson. A ton of energy. The keynotes, day two keynotes are all about products at Veeam. Veeam, the color of green, same color as money. And so, and it flows in this ecosystem. I'll tell you right now, Michael Cade is here. He's the senior technologist for product strategy at Veeam. Michael, fresh off the keynotes. >> Yeah, yeah. >> Welcome. Danny Allen's keynote was fantastic. I mean, that story he told blew me away. I can't wait to have him back. Stay tuned for that one. But we're going to talk about protecting containers, Kasten. You guys got announcements of Kasten by Veeam, you call it K10 version five, I think? >> Yeah. So just rolled into 5.0 release this week. Now, it's a bit different to what we see from a VBR release cycle kind of thing, cause we're constantly working on a two week sprint cycle. So as much as 5.0's been launched and announced, we're going to see that trickling out over the next couple of months until we get round to Cube (indistinct) and we do all of this again, right? >> So let's back up. I first bumped into Kasten, gosh, it was several years ago at VeeamON. Like, wow this is a really interesting company. I had deep conversations with them. They had a sheer, sheer cat grin, like something was going on and okay finally you acquire them, but go back a little bit of history. Like why the need for this? Containers used to be ephemeral. You know, you didn't have to persist them. That changed, but you guys are way ahead of that trend. Talk a little bit more about the history there and then we'll get into current day. >> Yeah, I think the need for stateful workloads within Kubernetes is absolutely grown. I think we just saw 1.24 of Kubernetes get released last week or a couple of weeks ago now. And really the focus there, you can see, at least three of the big ticket items in that release are focused around storage and data. So it just encourages that the community is wanting to put these data services within that. But it's also common, right? It's great to think about a stateless... If you've got stateless application but even a web server's got some state, right? There's always going to be some data associated to an application. And if there isn't then like, great but that doesn't really work- >> You're right. Where'd they click, where'd they go? I mean little things like that, right? >> Yeah. Yeah, exactly. So one of the things that we are seeing from that is like obviously the requirement to back up and put in a lot of data services in there, and taking full like exposure of the Kubernetes ecosystem, HA, and very tiny containers versus these large like virtual machines that we've always had the story at Veeam around the portability and being able to move them left, right, here, there, and everywhere. But from a K10 point of view, the ability to not only protect them, but also move those applications or move that data wherever they need to be. >> Okay. So, and Kubernetes of course has evolved. I mean the early days of Kubernetes, they kept it simple, kind of like Veeam actually. Right? >> Yeah. >> And then, you know, even though Mesosphere and even Docker Swarm, they were trying to do more sophisticated cluster management. Kubernetes has now got projects getting much more complicated. So more complicated workloads mean more data, more critical data means more protection. Okay, so you acquire Kasten, we know that's a small part of your business today but it's going to be growing. We know this cause everybody's developing applications. So what's different about protecting containers? Danny talks about modern data protection. Okay, when I first heard that, I'm like, eh, nice tagline, but then he peel the onion. He explains how in virtualization, you went from agents to backing up of VMware instance, a virtual instance. What's different about containers? What constitutes modern data protection for containers? >> Yeah, so I think the story that Danny tells as well, is so when we had our physical agents and virtualization came along and a lot of... And this is really where Veeam was born, right, we went into the virtualization API, the VMware API, and we started leveraging that to be more storage efficient. The admin overhead around those agents weren't there then, we could just back up using the API. Whereas obviously a lot of our competition would use agents still and put that resource overhead on top of that. So that's where Veeam initially got the kickstart in that world. I think it's very similar to when it comes to Kubernetes because K10 is deployed within the Kubernetes cluster and it leverages the Kubernetes API to pull out that data in a more efficient way. You could use image based backups or traditional NAS based backups to protect some of the data, and backup's kind of the... It's only one of the ticks in the boxes, right? You have to be able to restore and know what that data is. >> But wait, your competitors aren't as fat, dumb and happy today as they were back then, right? So it can't... They use the same APIs and- >> Yeah. >> So what makes you guys different? >> So I think that's testament to the Kubernetes and the community behind that and things like the CSI driver, which enables the storage vendors to take that CSI abstraction layer and then integrate their storage components, their snapshot technologies, and other efficiency models in there, and be able to leverage that as part of a universal data protection API. So really that's one tick in the box and you're absolutely right, there's open source tools that can do exactly what we're doing to a degree on that backup and recovery. Where it gets really interesting is the mobility of data and how we're protecting that. Because as much as stateful workloads are seen within the Kubernetes environments now, they're also seen outside. So things like Amazon RDS, but the front end lives in Kubernetes going to that stateless point. But being able to protect the whole application and being very application aware means that we can capture everything and restore wherever we want that to go as well. Like, so the demo that I just did was actually a Postgres database in AWS, and us being able to clone or migrate that out into an EKS cluster as a staple set. So again, we're not leveraging RDS at that point, but it gives us the freedom of movement of that data. >> Yeah, I want to talk about that, what you actually demoed. One of the interesting things, we were talking earlier, I didn't see any CLI when you were going through the integration of K10 V5 and V12. >> Yeah. >> That was very interesting, but I'm more skeptical of this concept, of the single pane of glass and how useful that is. Who is this integration targeting? Are you targeting the sort of traditional Veeam user who is now adding as a responsibility, the management of protecting these Kubernetes environments? Or are you at the same time targeting the current owners of those environments? Cause I know you talk about shift left and- >> Yeah. >> You know, nobody needs Kubernetes if you only have one container and one thing you're doing. So at some point it's all about automation, it's about blueprints, it's about getting those things in early. So you get up, you talk about this integration, who cares about that kind of integration? >> Yeah, so I think it's a bit of both, right? So we're definitely focused around the DevOps focused engineer. Let's just call it that. And under an umbrella, the cloud engineer that's looking after Kubernetes, from an application delivery perspective. But I think more and more as we get further up the mountain, CIS admin, obviously who we speak to the tech decision makers, the solutions architects systems engineers, they're going to inherit and be that platform operator around the Kubernetes clusters. And they're probably going to land with the requirement around data management as well. So the specific VBR centralized management is very much for the backup admin, the infrastructure admin or the cloud based engineer that's looking after the Kubernetes cluster and the data within that. Still we speak to app developers who are conscious of what their database looks like, because that's an external data service. And the biggest question that we have or the biggest conversation we have with them is that the source code, the GitHub or the source repository, that's fine, that will get your... That'll get some of the way back up and running, but when it comes to a Postgres database or some sort of data service, oh, that's out of the CI/CD pipeline. So it's whether they're interested in that or whether that gets farmed out into another pre-operations, the traditional operations team. >> So I want to unpack your press release a little bit. It's full of all the acronyms, so maybe you can help us- >> Sure. >> Cipher. You got security everywhere enhance platform hardening, including KMS. That's key- >> Yeah, key management service, yeah. >> System, okay. With AWS, KMS and HashiCorp vault. Awesome, love to see HashiCorp company. >> Yeah. >> RBAC objects in UI dashboards, ransomware attacks, AWS S3. So anyway, security everywhere. What do you mean by that? >> So I think traditionally at Veeam, and continue that, right? From a security perspective, if you think about the failure scenario and ransomware's, the hot topic, right, when it comes to security, but we can think about security as, if we think about that as the bang, right, the bang is something bad's happen, fire, flood, blood, type stuff. And we tend to be that right hand side of that, we tend to be the remediation. We're definitely the one, the last line of defense to get stuff back when something really bad happens. And I think what we've done from a K10 point of view, is not only enhance that, so with the likes of being able to... We're not going to reinvent the wheel, let's use the services that HashiCorp have done from a HashiCorp vault point of view and integrate from a key management system. But then also things like S3 or ransomware prevention. So I want to know if something bad's happened and Kasten actually did something more generic from a Veeam ONE perspective, but one of the pieces that we've seen since we've then started to send our backups to an immutable object storage, is let's be more of that left as well and start looking at the preventative tasks that we can help with. Now, we're not going to be a security company, but you heard all the way through Danny's like keynote, and probably when he is been on here, is that it's always, we're always mindful of that security focus. >> On that point, what was being looked for? A spike in CPU utilization that would be associated with encryption? >> Yeah, exactly that. >> Is that what was being looked- >> That could be... Yeah, exactly that. So that could be from a virtual machine point of view but from a K10, and it specifically is that we're going to look at the S3 bucket or the object storage, we're going to see if there's a rate of change that's out of the normal. It's an abnormal rate. And then with that, we can say, okay, that doesn't look right, alert us through observability tools, again, around the cloud native ecosystem, Prometheus Grafana. And then we're going to get insight into that before the bang happens, hopefully before the bang. >> So that's an interesting when we talk about adjacencies and moving into this area of security- >> We're talking to Zeus about that too. >> Exactly. That's that sort of creep where you can actually add value. It's interesting. >> So, okay. So we talked about shift left, get that, and then expanded ecosystem, industry leading technologies. By the way, one of them is the Red Hat Marketplace. And I think, I heard Anton's... Anton was amazing. He is the head of product management at Veeam. Is been to every VeeamON. He's got family in Ukraine. He's based in Switzerland. >> Yeah. >> But he chose not to come here because he's obviously supporting, you know, the carnage that's going on in Ukraine. But anyway, I think he said the Red Hat team is actually in Ukraine developing, you know, while the bombs are dropping. That's amazing. But anyway, back to our interview here, expanded ecosystem, Red Hat, SUSE with Rancher, they've got some momentum. vSphere with Tanzu, they're in the game. Talk about that ecosystem and its importance. >> Yeah, and I think, and it goes back to your point around the CLI, right? Is that it feels like the next stage of Kubernetes is going to be very much focused towards the operator or the operations team. The CIS admin of today is going to have to look after that. And at the moment it's all very command line, it's all CLI driven. And I think the marketplace is OpenShift, being our biggest foothold around our customer base, is definitely around OpenShift. But things like, obviously we are a longstanding alliance partner with VMware as well. So their Tanzu operations actually there's support for TKGS, so vSphere Tanzu grid services is another part of the big release of 5.0. But all three of those and the common marketplace gives us a UI, gives us a way of being able to see and visualize that rather than having to go and hunt down the commands and get our information through some- >> Oh, some people are going to be unhappy about that. >> Yeah. >> But I contend the human eye has evolved to see in color for a very good reason. So I want to see things in red, yellow, and green at times. >> There you go, yeah. >> So when we hear a company like Veeam talk about, look we have no platform agenda, we don't care which cloud it's in. We don't care if it's on-prem or Google Azure, AWS. We had Wasabi on, we have... Great, they got an S3 compatible, you know, target, and others as well. When we hear them, companies like you, talk about that consistent experience, single pane of glass that you're skeptical of, maybe cause it's technically challenging, one of the things, we call it super cloud, right, that's come up. Danny and I were riffing on that the other day and we'll do that more this afternoon. But it brings up something that we were talking about with Zeus, Dave, which is the edge, right? And it seems like Kubernetes, and we think about OpenShift. >> Yeah. >> We were there last week at Red Hat Summit. It's like 50% of the conversation, if not more, was the edge. Right, and really true edge, worst cases, use cases. Two weeks ago we were at Dell Tech, there was a lot of edge talk, but it was retail stores, like Lowe's. Okay, that's kind of near edge, but the far edge, we're talking space, right? So seems like Kubernetes fits there and OpenShift, you know, particularly, as well as some of the others that we mentioned. What about edge? How much of what you're doing with container data protection do you see as informing you about the edge opportunity? Are you seeing any patterns there? Nobody's really talking about it in data protection yet. >> So yeah, large scale numbers of these very small clusters that are out there on farms or in wind turbines, and that is definitely something that is being spoken about. There's not much mention actually in this 5.0 release because we actually support things like K3s,(indistinct), that all came in 4.5, but I think, to your first point as well, David, is that, look, we don't really care what that Kubernetes distribution is. So you've got K3s lightweight Kubernetes distribution, we support it, because it uses the same native Kubernetes APIs, and we get deployed inside of that. I think where we've got these large scale and large numbers of edge deployments of Kubernetes and that you require potentially some data management down there, and they might want to send everything into a centralized location or a more centralized location than a farm shed out in the country. I think we're going to see a big number of that. But then we also have our multi cluster dashboard that gives us the ability to centralize all of the control plane. So we don't have to go into each individual K10 deployment to manage those policies. We can have one big centralized management multi cluster dashboard, and we can set global policies there. So if you're running a database and maybe it's the same one across all of your different edge locations, where you could just set one policy to say I want to protect that data on an hourly basis, a daily basis, whatever that needs to be, rather than having to go into each individual one. >> And then send it back to that central repository. So that's the model that you see, you don't see the opportunity, at least at this point in time, of actually persisting it at the edge? >> So I think it depends. I think we see both, but again, that's the footprint. And maybe like you mentioned about up in space having a Kubernetes cluster up there. You don't really want to be sending up a NAS device or a storage device, right, to have to sit alongside it. So it's probably, but then equally, what's the art of the possible to get that back down to our planet, like as part of a consistent copy of data? >> Or even a farm or other remote locations. The question is, I mean, EVs, you know, we believe there's going to be tons of data, we just don't.. You think about Tesla as a use case, they don't persist a ton of their data. Maybe if a deer runs across, you know, the front of the car, oh, persist that, send that back to the cloud. >> I don't want anyone knowing my Tesla data. I'll tell you that right now. (all laughing) >> Well, there you go, that one too. All right, well, that's future discussion, we're still trying to squint through those patterns. I got so many questions for you, Michael, but we got to go. Thanks so much for coming to theCUBE. >> Always. >> Great job on the keynote today and good luck. >> Thank you. Thanks for having me. >> All right, keep it right there. We got a ton of product talk today. As I said, Danny Allan's coming back, we got the ecosystem coming, a bunch of the cloud providers. We have, well, iland was up on stage. They were just recently acquired by 11:11 Systems. They were an example today of a cloud service provider. We're going to unpack it all here on theCUBE at VeeamON 2022 from Las Vegas at the Aria. Keep it right there. (calm music)

(digital pulsing music) >> We're back at VeeamON 2022. My name is Dave Vellante. I'm here with my co-host David Nicholson. I've got another mass boy coming on. Patrick Osborne is the vice president of the storage business unit at HPE. Good to see you again, my friend. It's been a long time. >> It's been way too long, thank you very much for having me. >> I can't even remember the last time we saw each other. It might have been in our studios in the East Coast. Well, it's good to be here with you. Lots have been going on, of course, we've been following from afar, but give us the update, what's new with HPE? We've done some stuff on GreenLake, we've covered that pretty extensively and looks like you got some momentum there. >> Quite a bit of momentum, both on the technology front and certainly the customer acquisition front. The message is certainly resonating with our customers. GreenLake is, that's the transformation that's fueling the future of Hewlett Packard Enterprise. So the momentum is great on the technology side. We're at well over 50 services that we're providing on the GreenLake platform. Everything from solutions and workloads to compute, networking and storage. So it's been really fantastic to see the platform and being able to really delight the customers and then the momentum on the sales and the customer acquisition side, the customers are voting with their dollars, so they're very happy with the platform, certainly from an operational perspective and a financial consumption perspective and so our target goal, which we've said a bunch of times is we want to be the hyperscaler on on-prem. We want to provide that customer experience to the folks that are investing in the platform. It's going really well. >> I'll ask you a question, as a former analyst, it could be obnoxious and so forth, so I'll be obnoxious for a minute. I wrote a piece in 2010 called At Your Storage Service, saying the future of storage and infrastructure as a service, blah, blah, blah. Now, of course, you don't want to over-rotate when there's no market, there was no market for GreenLake in 2010. Do you feel like your timing was right on, a little bit late, little bit early? Looking back now, how do you feel about that? >> Well, it's funny you say that. On the timing side, we've seen iterations of this stops and start forever. >> That's true. Financial gimmicks. >> I started my career at Sun Microsystems. We talked about the big freaking Web-tone switch and a lot of the network is the computer. You saw storage networks, you've seen a lot, a ton of iterations in this category, and so, I think the timing's right right now. Obviously, the folks in the hyperscaler class have proved out that this is something that's working. I think for us, the big thing that's really resonating with the customers is they want the operational model and they want the consumption model that they're getting from that as a service experience, but they still are going to run a number of their workloads on-prem and that's the best place to do it for them economically and we've proved that out. So I think the time is here to have that bifurcated experience from operational and financial perspective and in the past, the technology wasn't there and the ability to deliver that for the customers in a manner that was useful wasn't there. So I think the timing's perfect right now to provide them. >> As you know, theCUBE has had a presence at HPE Discover. Previous, even HP Discover and same with Veeam. But we got a long history with HP/HPE. When Hewlett Packard split into two companies, we made the observation, Wow, this opens up a whole new ecosystem opportunity for HPE generally, in storage business specifically, especially in data protection and backup, and the Veeam relationship, the ink wasn't dry and all of a sudden you guys were partnering, throwing joint activities, and so talk about how that relationship has evolved. >> From my perspective, we've always been a big partnering company, both on the route to market side, so our distributors and partners, and we work with them in big channel business. And then on the software partnership side, that's always evolving and growing. We're a very open ecosystem and we like to provide choice for our customers and I think, at the end of the day, we've got a lot of things that we work on jointly, so we have a great value prop. First phase of that relationship was partnering, we've got a full boat of product integrations that we do for customers. The second was a lot of special sauce that we do for our customers for co-integration and co-development. We had a huge session today with Rick Vanover and Frederico on our team here to talk about ransomware. We have big customers suffering from this plague right now and we've done a lot together on the engineering side to provide a very, very well-engineered, well thought out process to help avoid some of these things. And so that wave, too, of how do we do a ton of co-innovation together to really delight our customers and help them run their businesses, and I think the evolution of where we're going now, we have a lot of things that are very similar, strategically, in terms of, we all talk about data services and outcomes for our customers. So at the end of the day, when we think about GreenLake, like our virtual machine backup as a service or disaster recovery, it's all about what workloads are you running, what are the most important ones, where do you need help protecting that data? And essentially, how can we provide that outcome to you and you pay it as an outcome. And so we have a lot of things that we're working on together in that space. >> Let's take a little bit of a closer look at that. First of all, I'm from California, so I'm having a really hard time understanding what either of you were saying. Your accents are so thick. >> We could talk in Boston. >> Your accents are so thick. (Dave laughing) I could barely, but I know I heard you say something about Veaam at one point. Take a closer look at that. What does that look like from a ransomware perspective in terms of this concept of air gaping or immutable, immutable volumes and just as an aside, it seems like Veeam is a perfect partnership for you since customers obviously are going to be in hybrid mode for a long time and Veeam overlays that nicely. But what does it look like specifically? Immutable, air gap, some of the things we've been hearing a lot about. >> I'm exec sponsor for a number of big HPE customers and I'll give you an example. One of our customers, they have their own cloud service for time management and essentially they're exploited and they're not able to provide their service. It has huge ripple effect, if you think about, on inability to do their service and then how that affects their customers and their customers' employees and all that. It's a disaster, no pun intended. And the thing is, we learn from that and we can put together a really good architectures and best practices. So we're talking today about 3-2-1-1, so having three copies of your data, two different types of media, having an offline copy, an offsite copy and an offline copy. And now we're thinking about all the things you need to do to mitigate against all the different ways that people are going to exploit you. We've seen it all. You have keys that are erased, primary storage that is compromised and encrypted, people that come in and delete your backup catalog, they delete your backups, they delete your snapshots. So they get it down to essentially, "I'm either going to have one set of data, it's encrypted, I'm going to make you pay for it," and 40 percent of the time they pay and they get the data back, 60 percent of the time they pay and they get maybe some of the data back. But for the most part, you're not getting your data back. The best thing that we can do for our customers that come with a very prescriptive set of T-shirt configuration sizes, standardization, best practices on how they can take this entire ecosystem together and make it really easy for the customers to implement. But I wouldn't say, it's never bulletproof, but essentially, do as much as you can to avoid having to pay that ransomware. >> So 3-2-1-1, three copies, meaning local. >> Patrick: Yeah. >> So you can do fast recovery if you need to. Two different types of media, so tape fits in here? Not necessarily flashing and spinning disks. Could it be tape? >> A lot of times we have customers that have almost four different types. So they are running their production on flash. We have Alletras with HPE networking and servers running specific workloads, high performance. We have secondary storage on-prem for fast recovery and then we have some form of offsite and offline. Offsite could be object storage in the cloud and then offline would be an actual tape backup. The tape is out of the tape library in a vault so no one can actually access it through the network and so it's a physical copy that's offline. So you always have something to restore. >> Patrick, where's the momentum today, specifically, we're at VeeamON, but with regard to the Veeam partnership, is it security and ransomware, which is a new thing for this world. The last two years, it's really come to the top. Is it cloud migration? Is it data services and data management? Where's the momentum, all of the above, but maybe you could help us parse that. >> What we're seeing here at Hewlett Packard Enterprise, especially through GreenLake, is just an overall focus on data services. So what we're doing is we've got great platforms, we always had. HPE is known as an engineering company. We have fantastic products and solutions that customers love. What we're doing right now is taking, essentially, a lot of the beauty of those products and elevating them into an operational experience in the cloud, so you have a set of platforms that you want to run, you have machine critical platform, business critical, secondary storage, archival, data analytics and I want to be able to manage those from the cloud. So fleet management, HCI management, protocol management, block service, what have you, and then I want a set of abstracted data services that are on top of it and that's essentially things like disaster recovery, backup, data immutability, data vision, understanding what kind of data you have, and so we'll be able to provide those services that are essentially abstracted from the platforms themselves that run across multiple types of platforms. We can charge them on outcome based. They're based on consumption, so you think about something like DR, you have a small set of VMs that you want to protect with a very tight RPO, you can pay for those 100 VMs that are the most important that you have. So for us driving that operational experience and then the cloud data service experience into GreenLake gives customers a really, gives them a cloud experience. >> So have you heard the term super cloud? >> Patrick: Yeah. (chuckles) >> Have you? >> Patrick: Absolutely. >> It's term that we kind of coined, but I want to ask you about it specifically, in terms of how it fits into your strategy. So the idea is, and you kind of just described it, I think, whether your data is on-prem, it's in the cloud, multiple clouds, we'll talk about the edge later, but you're hiding the underlying complexities of the cloud's APIs and primitives, you're taking care of that for your customers, irrespective of physical location. It's the common experience across all those platforms. Is that a reasonable vision, maybe, even from a technical standpoint, is it part of HPE strategy and what does it take to actually do that, 'cause it sounds nice, but it's probably pretty intense? >> So the proof's in the pudding for us. We have a number of platforms that are providing, whether it's compute or networking or storage, running those workloads that they plum up into the cloud, they have an operational experience in the cloud and now they have data services that are running in the cloud for us in GreenLake. So it's a reality. We have a number of platforms that support that. We're going to have a set of big announcements coming up at HPE Discover. So we led with Alletra and we have a block service, we have VM backup as a service and DR On top of that. That's something that we're providing today. GreenLake has over, I think, it's actually over 60 services right now that we're providing in the GreenLake platform itself. Everything from security, single sign on, customer IDs, everything, so it's real. We have the proof point for it. >> So, GreenLake is essentially, I've said it, it's the HPE cloud. Is that a fair statement? >> A hundred percent. >> You're redefining cloud. And one of the hallmarks of cloud is ecosystem. Roughly, and I want to talk more about you got to grow that ecosystem to be successful in cloud, no question about it. And HPE's got the chops to do that. What percent of those services are HPE versus ecosystem partners and how do you see that evolving over time? >> We have a good number of services that are based on HPE, our tried and true intellectual property. >> You got good tech. >> Absolutely, so a number of that. And then we have partners in GreenLake today. We have a pretty big ecosystem and it's evolving, too. So we have customers and partners that are focused, our customers want our focus on data services. We have a number of opportunities and partnerships around data analytics. As you know, that's a really dynamic space. A lot of folks providing support on open source, analytics and that's a fast moving ecosystem, so we want to support that. We've seen a lot of interest in security. Being able to bring in security companies that are focused on data security. Data analytics to understand what's in your data from a customer perspective, how to secure that. So we have a pretty big ecosystem there. Just like our path at HPE, we've always had a really strong partnership with tons of software companies and we're going to continue to do that with GreenLake. >> You guys have been partner-friendly, I'll give you that. I'm going to ask Antonio this at Discover in a couple of weeks, but I want to ask you, when you think about, again, to go back to AWS as the prototypical cloud, you look at a Snowflake and a Redshift. The Redshift guys probably hate Snowflake, but the EC2 guys love them, sell a lot of compute. Now you as a business unit manager, do you ever see the day where you're side by side with one of your competitors? I'm guessing Antonio would say absolutely. Culturally, how does that play inside of HPE? I'm testing your partner-friendliness. How would you- >> Who will you- >> How do you think about that? >> At the end of the day, for us, the opportunity for us is to delight our customers. So we've always talked about customer choice and how to provide that best outcome. I think the big thing for us is that, from a cost perspective, we've seen a lot of customers coming back to HPE repatriation, from a repatriation perspective for a certain class of workloads. From my perspective, we're providing the best infrastructure and the best operational services at the best price at scale for these costumers. >> Really? It definitely, culturally, HPE has to, I think you would agree, it has to open up. You might not, you're going to go compete, based on the merit- >> Absolutely. >> of your product and technology. The repatriation thing is interesting. 'Cause I've always been a repatriation skeptic. Are you actually starting to see that in a meaningful way? Do you think you'll see it in the macro numbers? I mean, cloud doesn't seem to be slowing down, the public cloud growth, I mean, the 35, 40 percent a year. >> We're seeing it in our numbers. We're seeing it in the new logo and existing customer acquisition within GreenLake. So it's real for us. >> And they're telling you? Pure cost? >> Cost. >> So it's that's simple. >> Cost. >> So, they get the cloud bill, you do, too. I'd get the email from my CFO, "Why the cloud bill so high this month?" Part of that is it's consumption-based and it's not predictable. >> And also, too, one of the things that you said around unlocking a lot of the customer's ability from a resourcing perspective, so if we can take care of all the stuff underneath, the under cloud for the customer, the platform, so the stores, the serving, the networking, the automation, the provisioning, the health. As you guys know, we have hundreds of thousands of customers on the Aruba platform. We've got hundreds of thousands of customers calling home through InfoSight. So we can provide a very rich set of analytics, automated environment, automated health checking, and a very good experience that's going to help them move away from managing boxes to doing operational services with GreenLake. >> We talk about repatriation often. There was a time when I think a lot of us would've agreed that no one who was born in the cloud will ever do anything other than grow in the cloud. Are you seeing organizations that were born in the cloud realizing, "Hey, we know what our 80 percent steady state is and we've modeled this. Why rent it when we can own it? Or why rent it here when we can have it as operational cost there?" Are you seeing those? >> We're seeing some of that. We're certainly seeing folks that have a big part of their native or their digital business. It's a cost factor and so I think, one of the other areas, too, that we're seeing is there's a big transformation going on for our partners as well, too, on the sell-through side. So you're starting to see more niche SaaS offerings. You're starting to see more vertically focused offerings from our service provider partners or MSPs. So it's not just in either-or type of situation. You're starting to see now some really, really specific things going on in either verticals, customer segmentation, specific SaaS or data services and for us, it's a really good ecosystem, because we work with our SP partners, our MSP partners, they use our tech, they use our services, they provide services to our joint customers. For example, I know you guys have talked to iland here in the past. It's a great example for us for customers that are looking for DR as a service, backup as a service hosting, so it's a nice triangle for us to be able to please those customers. >> They're coming on to tomorrow. They're on 11/11. I think you're right on. The one, I think, obvious place where this repatriation could happen, it's the Sarah Wong and Martin Casano scenario where a SaaS companies cost a good sold become dominated by cloud costs. And they say, "Okay, well, maybe, I'm not going to build my own data centers. That's probably not going to happen, but I can go to Equinix and do a colo and I'm going to save a ton of dough, managing my own infrastructure with automation or outsourcing it." So Patrick, got to go. I could talk with you forever. Thank you so much for coming back in theCUBE. >> Always a pleasure. >> Go, Celts. How you feeling about the, we always talk sports here in VeeamON. How are you feeling about the Celts today? >> My original call today was Celtics in six, but we'll see what happens. >> Stephen, you like Celtics? Celtics six. >> Stephen: Celtics six. >> Even though tonight, they got a little- >> Stephen: Still believe, you got to believe. >> All right, I believe. >> It'd be better than the Miami's Mickey Mouse run there, in the bubble, a lot of astronauts attached to that. (Dave laughing) >> I love it. You got to believe here on theCUBE. All right, keep it right- >> I don't care. >> Keep it right there. You don't care, 'cause you're not from a sports town. Where are you in California? >> We have no sports. >> All right, keep it right there. This is theCUBE's coverage of VeeamON 2022. Dave Vellante for Dave Nicholson. We'll be right back. (digital music)

(fastpaced upbeat music) >> Welcome back to theCubes coverage of the power of N and the collaborations between HPE Aruba and Pensando. Where the two companies are setting out to create a new category in network switching. Joining me now is Simon McCormack, who looks after product management at HPE Aruba. Welcome Simon. Good to see you. >> Good morning. Thanks for having me today. >> You're very welcome. So Simon, we've been talking all day about the Aruba switching fabric that you're bringing to market, embedding the Pensando technology. Can you tell us what's the primary value prop that AFC brings to its customers? >> Sure. Aruba Fabric Composer. This is orchestration and management for the Aruba wide switching platform. Primarily for data centers. It does a lot of things. I'll give you three key ones just to get a feel for it. So in data center networking, there's a lot of complex technologies. I'm afraid to say, lease spines, overlays, underlays, EDP and OSPF BGP. I can throw out loads of acronyms for you. Fabric Composer can really simplify through a bunch of intent based workflows, the deployment and management of these fabrics. We can do it either interactively through a UI or fully API driven, if you want to. So it really takes away a lot of the plexity there makes it dead easy to deploy these and that scale. Number two, in a data center, a lot of compute storage hypervisor technologies that you have to interact with the THEO network products. So in Fabric Composer, we built an integration layer into it that interacts with other orchestrators, vCenter, VMware vcenter is a good example of that. So an operator may make changes to vCenter that affect the network. You don't want to call the network team for it. Fabric Composer can automate that network side configuration on the Aruba switch, making your day to operations, insertion of new services, much more simpler. And then finally, number three, because we've got all these capabilities I've just told you about. We actually have a great typology model that we build from it. And we can use that to visualize this virtual to physical network layer that is really powerful for troubleshooting the environment. >> Great? So three things, actually four right. To simplify or integrate and automate. And it's kind of two and two way, I'm going to to call it. and then the visualization piece for troubleshooting. Awesome. What about security policy? How are you thinking about that in this release? >> Yeah, so that's where in this release, we're extending it with the Pensando PSM technologies embedded into the 10K. Now we can use Aruba Fabric Composer to actually orchestrate the policy in addition to the network. So you think about today, Fabric Composer does network primarily. You bring policy into it. You've got one single pane of glass now that does network and policy. It actually provides a really powerful capabilities for operators of different skill sets to be able to manage and orchestrate this environment. >> What about the sort of operational model as it pertains to the network and security, I'm interested in how flexible that is. For instance, if a customer wants to use their own tooling or operational frameworks. What if they want to leverage multi-vendor fabrics like a third-party spine? How do you deal with all of that? >> Yeah, and I think that's, we built that into essentially the DNA of this technology is that we're, we're expecting to often go into brownfield environments. Where they've already got best practices for security and networking. They've already got networking vendors there. The 10K is a very powerful lease switch on its own. We want those lease switches to go in all of these different environments, not just Greenfield. It's really great for Greenfield. And I'm going to explain this a little bit in a few ways. First of all, the technology we have with Aruba fabric Composer and Pensando PSM, you can do a pure operational split between them SecOps, NetOps. A lot of customers that's how they deal with it. They've got the security operations team, network operations team. If they're split, you can use the two tools and make a fantastic product using that. However, if they're not split, and you've got a single policy for it. You can use Aruba Fabric Composer to do both of them. So you've got the options there and we fully embrace that in the architecture of what we built. This extends to multiple layers for the technology build as well. Again, as I said, the 10K's is a lease switch, it can connect to third-party spines. So you could use Fabric Composer to manage this lease Spitch and the policy you could use Fabric Composer just to manage the least switch and connect and interoperate the lease to the spine, or you can do a full Aruba solution, the full Aruba spine and use that operating model. There's one final thing in this area is fabric Composers are a UI based orchestrator, API driven. Some customers love it. Some customers love their CLIs. We fully embrace the operational model where customers still use their own APIs and their own CLIs. So the customer may be using Ansible to automate through API. They can still use that directly to the switch and they can use it to AFC and mix the two. If you talk directly to a switch and change it, Fabric Composer detects it and basically sinks its configuration together. So we can insert all or any part of this solution into existing or new Netflix. >> Yeah, that's nice. Right? Because I mean, so there's the network hard guys, right they, they want that CLI access. So you you're accommodating that. And then as well, being able to bring those SecOps view and the netOps view together is important because let's say, let's face it. A lot of organizations, especially some of the smaller ones, they don't actually have a full blown SecOps team. That's really the netOps responsibility. And so that's nice flexibility, you can handle both worlds. How about segmentation? What a customer is telling you that they want regarding segmentation and how are you guys approaching that? >> Yeah, I mean, it's, it's actually a key feature of what we're doing in this area. Now the iland segmentation generates it's kind of a wide area with many layers to it and we could talk about it for hours. So let me talk briefly about some of the areas we're going into when it comes to the segmentation. But particularly of a compute and virtual type environment. So when you, when you're typically creating policies in today's world, current policies based on addresses, IP addresses, or Mac addresses. You have lots of rules and big lists of addresses. It's really annoying. Customers generally don't talk in addresses. They talk in machines and names of machines. So if you think about what I've already told you with the Fabric Composer, we've already got these hooks in the compute hypervisor layer. So we didn't know about the virtual machines? So it said obviously, a natural extension now for you to be able to create these policies based on the machines. So there's, there's a scale problem in policy distribution at two levels, at the top and the bottom. The top level is your chronic create the policy. You've got this massive distribution addresses. So Fabric Composer can really help you by allowing you to then create these groups, sensible groups, using the names then you can distribute. The 10K solution with the distributed architecture of the bottom layer, now allows us to distribute these policies and rules across your racks within your data center. So it scales really well, but that's one level I've described. You know, you're creating groups of machines with names, so it's easier to define it, but there's auto and automation angle to this as well. You might not want to even create it interactively. Now a lot of customers with VMware vCenter, For example, are tagging the virtual machines. So the tag tells you a group information. Again, Fabric Composer can already get the tag within its database model. So we can use the tag now either to fully automate or use as a hint to creating these groups. So now I've got a really simple way to basically just categorize my machines into the groups so that now I can push rules down onto them. And there's one, one final thing that I just want to tell you before, before we move on. There's, there's often a zero trust model you want to do in the data center for segmentation. Meaning I've got two virtual machines on the same network on the same host. Normally they can talk to each other, nothing's stopping them, but sometimes you want to isolate even those two. You can do it in products like vCenter with PV land technologies. A bit cumbersome to configure on the vSphere side, you got to match it with what you see on the switch side. It's one of those that's a real headache, unless you've got an orchestrator to do it. So Fabric Composer could basically orchestrate this isolated solution. You're now grouping your machines and you're saying they're isolated. We can do the smarts and both of the vCenter side and the switch side, get them in sync, get it all configured. And now the masses can start to do this kind of segmentation at scale. >> Got it. Thank you Simon. Can the Fabric Composer kind of be used as the primary prism for troubleshooting? How do you handle troubleshooting and this art combined architecture? Who, who do I call when there's a problem? How do you approach that? >> Well, definitely start by calling me or actually call my product first, so fabric Composer. If you're using it, use that as the front tool for what you're going to try and figure out what's going on. There is a global health dashboard. It encompasses networking security policy across the solution, across the fabric. So that's your, tells you what's going on immediately. Down to port stats on what's happening within the physical topology of the network. Down to the end-to-end view, we have in terms of policy connectivity between machines. So Fabric Composer is your first port of call, but we built a solution here that we don't want to hide the pieces underneath it. Any networking guy knows when they're deep troubleshooting networking stuff, they're going to end up with the switch. So you started the orchestrator, but sometimes in the deep troubleshooting, not day-to-day, hopefully. You'll go to the switch and you'll troubleshoot that way. We've got the same technology here with the policy, with the firewall rules, with Pensando PSM. We still fully embrace for deep troubleshooting, go to Pensando PSM. They have really advanced tools in their bag of tricks in the product to give you advanced troubleshooting down to the policy layer. They have a really powerful firewall log capability, where you can search and sort, and see exactly what role is allowing or stopping any traffic going through the environment. And the two orchestrated model, we really like it 'cause it scales really well. It allows Fabric Composer to remain lightweight, PSM focused on the policy orchestration bit. But again, if your that customer that wants to do single pane of glass use Fabric Composer for the standard day-to-day stuff. But you've got the tools there to do the advanced troubleshooting between the different elements that we have within the Pensando and the Aruba tools. >> Yeah, really well thought out. You got the simplification angle nailed, the integration automation we talked about that, the visualization and the topology map, zero trust. And then remediation with deep^ened inspection. Simon, thanks so much for taking us through the announcements. Really appreciate your insights and time today. >> Thank you very much. >> You're welcome. Okay. Keep it right there, this is Dave Vellante for theCube. More content from the HPE Aruba Pensando announcements coming right up. (soothing music)

>> Announcer: Live from New Orleans, it's theCUBE, covering VeeamON 2017. Brought to you by Veeam. >> Welcome, everybody. This is theCUBE's special coverage of Veemon 2017 from New Orleans. theCUBE is the leader in live tech coverage, and this is our second day wall-to-wall coverage. I'm Dave Vellante with Stu Miniman. Danny Allan is here as the Vice President of Cloud and Alliance Strategy at Veeam. Danny, big week for you. >> Very exciting to be here. My first VeeamON, so you can imagine how excited I am. >> Us too. So cloud and Alliance Strategy, what is the strategy there? Sum it up for us. >> So kind of three things. There's to the cloud, from the cloud, within the cloud. So if you break those out, most organizations today, what they're doing, or what they do is they use their backups, they push them up to the cloud. Some of those that are in areas where they care about disaster recovery are using disaster recovery as a service, both of those kind of pushing services up to the cloud. From the cloud would be things like SAS services. You have things like Office 365, pull the data down, protect it because it belongs to you. And then within the cloud, we've seen our customers with cloud-hosted workloads, and they say, "I want to keep my protection but in a different cloud, "in a multi-cloud world." >> Interesting they would say, in the keynote this morning, they would say, "Well, today's going to be cloud day," but yesterday you had some AWS announcements, too. We know today you can't talk about IT without having cloud and kind of the hybrid multi-cloud get dispersed everywhere. Lot of announcements. What I was hoping you could dig into a little bit for us is the Veeam powered network with Azure and maybe give us the quick overview and let's drill down in there a little bit. >> Sure, so one of the capabilities we've had for a while is this ability to do direct restore to Azure. So you have the Veeam, it goes down and you hit a button and it goes up to Azure. Now that's all great, but when that server was in your data center, you could actually just connect to it because it was on your network. One of the challenges is when you put something up in the cloud, how do you get your users to that service? It's a different IP, it's a different subnet, it's a different network. So this is to make it simple. We've always focused on it just works, so this is a model that we can do a very simple model to connect users to the service when we push it up into the cloud. >> Yeah, maybe, I think most people in cloud understand the Amazon VPN service. Could you maybe compare and contrast that with what you've got? >> Very similar. So Amazon does the VPC, and this just takes it down and simplifies it so that it's part of your orchestration strategy. So typically, when you have something running up in the cloud, what happens is you set it up, the connection, and you maintain the connection for the duration of that service. This is a little bit different, because you want the connection, but only when you need it. And so it's orchestrating that connection in a very simple lightweight way that you don't have to maintain an ongoing connection. That enables that service delivery. >> There's a lot of talks at events like this and certainly has been at this event about just migrating workloads and help us square the circle. So you hear a lot of that talk, and then the same time you hear about data explosion, data growth, and then there's the speed of light problem. So how are customers sort of managing that, and how can you help? >> So I don't necessarily believe that organizations are migrating from cloud to cloud on a regular basis. But what does happen is they outgrow the cloud that they happen to be in. We see this in private cloud all the time. I have so much capacity, I don't have any left, I need to jump over to another cloud. So there's kind of three drivers that cause people to go into a multi-cloud air. One is certainly disaster recovery. Second though is cost optimization and business alignment. So it's sometimes you'll have an executive level far above IT says, "Hey, we strategically aligned "with this cloud; we would like to shift workloads "over to another one." And the last is around really the footprint of the cloud provider themselves. So it could be because of geophysical location or compliance certifications. That organizations say, "I need to take this particular "service and move it over here." >> We had some talk about cloud service providers as a channel this week, and what's the discussion like with CSPs in terms of them monetizing services? And how do you help? With whether it's software defines something, or programatic thresholds through APIs. Can you and how do you support that monetization strategy? >> So, a few different things. One is that the cloud service providers are very focused on their specific value add. And if you go talk to them, some of them are heavy in security, some of them are heavy in the managed services, some of them are heavy in the analytics. They all have a specific value add that they have. But one of the things that we do for them is in the platforms that we've announced, like Veeam Availability Console has a full restful API that they can integrate into their environment. Take iland, for example. They have their own portal, they call their APIs, customer never sees anything other than their specific portal, and that's true for all of the products that we've been announcing. Veeam Availability Console, Veeam Backup for Office 365, we enable that integration with our product set. >> One of the other announcements that we were digging into a little bit is to be able to have an archive tier with a lot of the object storage out there. Whether it be as the Amazon Blob, is this some of the AWS offerings, or any kind of S3 or Swift compatible solutions. Is that something that you've been hearing customers asking for for a while? How do you expect that to roll out? >> It is. So there's two kinds of customers. Those that say, "Hey, I would like to leverage "the hyper-scale public clouds 4S3 or Azure. "We have credits with them, we want to use them up." And so this enables them to push off an archive tier to the data up to there. But we also see organizations, especially the large ones that are building their own on premises object storage because of the characteristics of scale up, scale out. And they've been saying, "Hey, we want to leverage that." Now, the performance historically has not been as good as block storage, obviously, but now it's catching up and people are using it more for an archive tier than a primary tier or a secondary tier. >> The other day at the analyst briefing, you talked about there were three things that came out. One was digital transformation and agility, and we want to explore that a little bit. The other was core business continuity, and the third was analytics and visualization. And I wonder if we could stick on that for a minute. That analytics and visualization. Can you explain a little bit further what you guys bring to the table there and how customers are using it? >> So one of the things that Veeam has is an archive of all of your data that is stored. And we've been looking to expose that data to our partners so that they can dig into it and add their value. So we announced a partnership with Data Gravity, for example, that reaches into those VMs. And as regulations like GDPR come out, then there is a higher and higher business need, sorry, General Data Protectionary Regulation, higher and higher business need to understand what is in the data that we're storing and then perform analysis on it. >> Yeah, so GDPR takes affect like basically a year from now, right? >> Danny: Yeah, May. >> May of '18. We've had also a lot of discussion about ransomware, and just creating air gaps and so forth. The reason why I was so interested in analytics and visualization is it seems that it would require more than just an air gap because Bill Philbin said it today. When you make a boo boo, the boo boo gets replicated very quickly. Well, when someone's maliciously encrypting your data, it probably gets maliciously encrypted very quickly, or replicated very quickly. It seems that you are in a unique position to provide analytics on an anomalous behavior on change data. Has that discussion taken place with your partners and clients? >> Yes, absolutely, we're looking at it. In fact, there was a breakout session on this very thing. Basically, when you saw the files being deleted from a particular folder or .docex files being changed to .enc files, when you saw a ransomware attack taking place that you could actually roll back to the latest snapshot, or you could take a snapshot and send an email to someone and say, "Hey, this is happening, you should look at it." I look forward actually out into the future that we can leverage some of the things that we're doing now with continuous data protection that traps the IO traffic. So that is the VCR API for IO filtering. And if you see an attack taking place, you could actually roll back that IO journal say five minutes and say take a snapshot at that point even before it happened. So it has more behavioral-based protections associated with it. So I think we're at a really interesting era in the space where we're going to begin to see new things that have never been done in the past. >> And potentially specific solutions are around ransomware. Maybe they'll talk about it generically, maybe they're out there, I just haven't seen a very specific, I'm sure they are out there. But I haven't seen a specific solution around. It seems like the guy with the backup data would be in a unique position to do that. >> Yeah, data is the lifeblood of the organization, so being able to mine it for data insights, being able to leverage that for data governance, being able to use it for e-discovery, but also to be able to use it in proactive ways for the business. Like determining that a ransomware attack is taking place and perhaps fire off instructions to your perimeter to act differently. Who knows what these things are going to go towards. But the data is the content that actually drives a lot of those behaviors. >> Danny, one of the things I found interesting, Mark Rosinovich's keynote. He was talking about the evolution of application platforms and Veeam started with the VM, and I saw a lot of the show. There's physical endpoints, there's cloud endpoints. When you start going to things like paths an even serverless functions as a service, what impact will that have on availability overall and where does Veeam see that going in your world? >> So our vision is to perform always on availability for any service, so as we go forward into containers and serverless, there's still a requirement to provide protection. So I was listening to him as he was saying, "Hey, there could be an API that resizes the image." You could actually use that exact same API to say, "Hey, is that image important? "Send it over to this repository for retention." So there's still a requirement for availability, and what it means is, if you're looking at paths and container-type model, then maybe we do it underneath the containers to protect them as they're running. But if you're looking at serverless, maybe we actually inject it into the APIs itself to perform that same protection. It's going to be required no matter what the structure of the data happens to be. >> We're out of time, but maybe, Danny, quick summary of the announcements that you guys made this week and some of the things that people are excited about. >> Yeah, so a lot of different announcements, obviously. Veeam Availability Console Release Candidate is out. We announced a whole lot of disaster recovery as a service functions for service providers. Things like continuous data protection, things like VCD integration. We announced Veeam Backup for Office 365. Actually two different versions of it. One is for service providers, multi-tenant, multi-repository, but also adding in SharePoint and OneDrive capabilities. We obviously, our flagship product, Veeam Availability Suite. We talked a lot about the object storage. We talked about continuous data protection. A lot of these capabilities have been announced over the last few days. >> Yeah, so Veeam, you've seen a lot of strategy, they're hitting R and D, turning it into product, turning into customer value and revenue. So you guys have been busy and quite an impressive stream of innovation coming out this week. So Danny, thanks very much for coming on theCUBE and sharing that with us. >> Thank you very much. Appreciate being here. >> Okay, keep it right there, everybody. We'll be right back with our next guest. This is Dave Vellante and Stu Miniman live from VeeamON 2017. Right back.