>> Announcer: Live from Las Vegas, it's theCUBE! Covering Veritas Vision 2017. Brought to you by Veritas. >> Welcome back to the Aria in Las Vegas, everybody. This is theCUBE, the leader in live tech coverage. We go out to the events and extract the signal from the noise. We're here at Veritas Vision 2017, #VtasVision. Jyothi Swaroop is here. He's the vice president of product and solutions marketing at Veritas. Jyothi, welcome to theCUBE. Good to see you. >> Thanks, Dave. I'm an officially an alum, now? >> A CUBE alum, absolutely! >> Two times! Three more times, we'll give you a little VIP badge, you know, we give you the smoking jacket, all that kind of stuff. >> Five or six times, you'll be doing the interviews. >> I'm going to be following you guys around, then, for the next three events. >> So, good keynote this morning. >> Jyothi: Thank you. >> Meaty. There was a lot going on. Wasn't just high-level concepts, it was a lot of high-level messaging, but then, here's what we've done behind it. >> No, it's actually the opposite. It's a lot of real products that customers are using. The world forgets that Veritas has only been out of Symantec, what, 20 months? Since we got out, we were kind of quiet the first year. That was because we were figuring our strategy out, investing in innovation and engineering, 'cause that's what Carlyle, our board, wants for us to do is invest in innovation and engineering, and build real products. So we took our time, 18 to 20 months to build these products out, and we launched them. And they're catching on like wildfire in the customer base. >> Jyothi, Bill came on and talked about, he made a lot of changes in the company. Focused it on culture, innovation, something he's want. What brought you? You know, a lot of places you could've gone. Why Veritas, why now? >> Well, Bill is one of the reasons, actually. I mean, if you look at his history and what he's done with different companies over the years, and how the journey of IT, as he put it during his keynote, he wants to make that disruption happen again at Veritas. That was one. Two was just the strategy that they had. Veritas has a Switzerland approach to doing business. Look, it's granted that most Fortune 500 or even midmarket customers have some sort of a Cloud project going on. But what intrigued me the most, especially with my background, coming from other larger companies is, Veritas was not looking to tie them down or become a data hoarder, you know what I mean? It's just charge this massive dollar per terabyte and just keep holding them, lock them into a storage or lock them into a cloud technology. But, we were facilitating their journey to whichever cloud they wanted to go. It was refreshing, and I still remember the first interview with Veritas, and they were talking about, "Oh, we want to help move customers' data "into Azure and AWS and Google," and my brain from previous storage vendors is going, "Hang on a minute. "How are you going to make money "if you're just going to move all of this data "to everyone else?" But that's what is right for the customer. >> Okay, so, how are you going to make money? >> Well, it's not just about the destination, right? Cloud's a journey, it's not just a destination. Most customers are asking us, "On average, we adopt three clouds," is what they're telling us. Whether it's public, private, on-prem, on average, they have about three separate clouds. What they say is, "Jyothi, our struggle is to move "an entire virtual business service "from on-prem to the Cloud." And once we've moved it, let's say Cloud A is suddenly expensive or is not working out for them. To get out of that cloud and move it to Cloud B is just so painful. It's going to cost me tons of money, and I lost all of the agility that I was expecting from Cloud A, anyway. If you have products like VRP from Veritas, for example, where we could move an entire cloud business service from Cloud A to Cloud B, and guess what. We can move it back onto on-prem on the fly. That's brilliant for the customers. Complete portability. >> Let's see. The portfolio is large. Help us boil it down. How should we think about it at a high level? We only have 20 minutes, so how do we think about that in 15, 20 minutes? >> I'll focus on three tenets. Our 360 data management wheel, if you saw at the keynote, has six tenets. The three tenets I'll focus on today are visibility, portability, and last, but definitely not the least, storage. You want to store it efficiently and cost-effectively. Visibility, most of our customers that are getting on their cloud journey are already in the Cloud, somewhere. They have zero visibility, almost. Like, "What applications should I move into the Cloud? "If I have moved these applications, "are they giving me the right value? "Because I've invested heavily in the Cloud "to move these applications." They don't know. 52% of our customers have dark data. We've surveyed them. All that dark data has now been moved into some cloud. Look, cloud is awesome. We have partnered up with every cloud vendor out there. But if we're not making it easy for customers to identify what is the right data to move to the Cloud, then they lost half the battle even before they moved to the Cloud. That's one. We're giving complete visibility with the Info Map connectors that we just announced earlier on in the keynote. >> That's matching the workload characteristics with the right sort of platform characteristics, is that right? >> Absolutely. You could be a Vmware user, you're only interested in VM-based data that you want to move, and you want role-based access into that data, and you want to protect only that data and back it up into the Cloud. We give you that granularity. It's one thing to provide visibility. It's quite another to give them the ability to have policy-driven actions on that data. >> Jyothi, just take us inside the customers for that. Who owns this kind of initiative? The problem in IT, it's very heterogeneous, very siloed. You take that multi-cloud environment, most customers we talk to, if they've got a cloud strategy, the ink's still drying. It's usually because, well, that group needed this, and somebody needed this, and it's very tactical. So, how do I focus on the information? Who drives that kind of need for visibility and manages across all of these environments? >> That's a great question, Stu. I mean, we pondered around the same question for about a year, because we were going both top-down and bottoms-up in the customer's organization, and trying to find where's our sweet spot. What we figured is, it's not a one-strategy thing, especially with the portfolio that we have. 80% of the time, we are talking to the CIOs, we are talking to the CXOs, and we're coming down with their digital transformation strategy or their cloud transformation strategy, they may call it whatever they want. We're coming top-down with our products, because when you talk visibility, a backup admin, he may not jump out of his seat the first thing. "Visibility's not what I care about, "the ease of use of this backup job "is what I care about, day one." But if you talk to the CIO, and I tell him, "I'll give you end-to-end visibility "of your entire infrastructure. "I don't care which cloud you're in." He'll be like, "I'm interested in that, "'cause I may not want to move 40% of this data "that I'm moving to Cloud A today. "I want to keep it back, or just delete it." 'Cause GDPR in Europe gives the citizens the right to delete their data. Doesn't matter which company the data's present in. The citizen can go to that company and say, "You have to delete my data." How will you delete the data if you just don't know where the data is? >> It's in 20 places in 15 different databases. Okay, so that's one. You had said there were three areas that you wanted to explore. >> The second one is, again, all about workload data and application portability. Over the years, we had storage lock-ins. I'm not going to name names, but historically, there are lots of storage vendors that tend to lock customers into a particular type of storage, or to the company, and they just get caught up in that stacked refresh every three years, and you just keep doing that over and over again. We're seeing more and more of cloud lock-in start to happen. You start migrating all of this into one cloud service provider, and you get familiar with the tools and widgets that they give you around that data, and then all of a sudden you realize this is not the right fit, or I'm moving too much data into this place and it's costing me a lot more. I want to not do this anymore, I want to move it to another local service provider, for example. It's going to cost you twice as much as it did just to move the data into the Cloud in the first place. With VRP, Veritas Resiliency Platform, we give our customers literally a few mouse clicks, if you watched the demo onstage. Literally, with a few mouse clicks, you identify the data that you want to move, including your virtual machines and your applications, and you move them as a business service, not just as random data. You move it as an entire business service from Cloud A to Cloud B. >> Jyothi, there's still physics involved in this. There's many reasons why with lock-in, you mentioned, kind of familiarity. But if I have a lot of data, moving it takes a lot of time as well as the money. How do we handle that? >> It goes back to the original talk track here about visibility. If you give the customer the right amount of visibility, they know exactly what to move. If the customer has 80 petabytes of data in their infrastructure, they don't have to move all 80 petabytes of it, if we are able to tell them, "These are the 10 petabytes that you need to move, "based on what Information Map is telling you." They'll only move those 10 petabytes, so the workload comes down drastically, because they're able to visualize what they need to move. >> Stu: Third piece of storage? >> Third piece of storage. A lot of people don't know this, but Veritas was the first vendor that launched the software to find storage solution. Back in the VOS days, Veritas, Oracle, and Sun Microsystems, we had the first file system that would be this paper over rocks, if you will, that was just a software layer. It would work with literally SAN/DAS, anything that's out there in the market, it would just be that file system that would work. And we've kept that DNA in our engineering team. Like, for example, Abhijit, who leads up our engineering, he wrote the first cluster file system. We are extending that beyond just a file system. We're going file, block, and object, just as any other storage vendor would. We are certifying on various commodity hardware, so the customers can choose the hardware of their choice. And not just that. The one thing we're doing very differently, though, is embedding intelligence close to the metadata. The reason we can do that is, unlike some of the classic storage vendors, we wrote the storage ground-up. We wrote the code ground-up. We could extract, if you look at an object, it has object data and metadata. So, metadata standard, it's about this long, right? It's got all these characters in it. It's hard to make sense of it unless you buy another tool to read that object and digest it for the customer. But what if you embed intelligence next to the metadata, so storage is not dumb anymore? It's intelligent, so you avoid the number of layers before you actually get to a BI product. I'll just give you a quick example in healthcare. We're all wearing Apple Watches and FitBits. The data is getting streamed into some object store, whether it's in the Cloud or on-prem. Billions of objects are getting stored even right now, with all the Apple Watches and FitBits out there. What if the storage could predictively, using machine learning and intelligence, tell you predictively you might be experiencing a stroke right on your watch, because your heartbeats are X and your pulse is Y? Combining all of the data and your history, based on the last month or last three months, I can tell you, "Jyothi, you should probably go see the doctor "or do something about it." So that's predictive, and it can happen at the storage layer. It doesn't have to be this other superficial intelligence layer that you paid millions of dollars for. >> So that analytic capability is really a feature of your platform, right? I mean, others, Stu, have tried it, and they tried to make it the product, and it really isn't a product, it's a byproduct. And so, is that something I could buy today? Is that something that's sort of roadmap, or, what's the reaction been from customers? >> The reaction has been great, both customers and analysts have just loved where we're going with this. Obviously, we have two products that are on the truck today, which are InfoScale and Access. InfoScale is a block-based product and Access is a file-based product. We also have HyperScale, which was designed specifically for modern workloads, containers, and OpenStack. That has its own roadmap. You know how OpenStack and containers work. We have to think like a developer for those products. Those are the products that are on the truck today. What you'll see announced tomorrow, I hope I'm not giving away too much, because Mike already announced it, is Veritas Cloud Storage. That's going to be announced tomorrow, and we're going to go deep into that. Veritas Cloud Storage will be this on-prem, object-based storage which will eventually become a platform that will also support file and block. It's just one single, software-defined, highly-intelligent storage system for all use cases. Throw whatever data you want at it. >> And the line on Veritas, the billboards, no hardware agenda. Ironic where that came from. Sometimes you'll announce appliances. What is that all about, and when do you decide to do that? >> Great question. You know, it's all about choice. It's the cliched thing to say, I know, but Veritas, most people don't know this, has a heavy channel revenue element to what we do. We love our partners and channel. Now, if you go to the channel that's catering to midmarket customers, or SMBs, they just want the easy button to storage. Their agility, I don't have five people sitting around trying to piece all of this together with your software and Seagate's hardware and whatever else, and piece this together. I just want a box, a pizza box that I can put in my infrastructure, turn it on, and it just works, and I call Veritas if something goes wrong. I don't call three different people. This is for those people. Those customers that just want the easy button to storage or easy button to back up. >> To follow up on the flip side, when you're only selling software, the knock on software of course is, I want it to be fast, I want it to be simple, I need to be agile. How come Veritas can deliver these kinds of solutions and not be behind all the people that have all the hardware and it's all fully baked-in to start with? >> Well, that's because we've written these from the ground up. When you write software code from the ground up, I mean, I'm an engineer, and I know how hard it is to take a piece of legacy code that's baked in for 10, 20 years. It's almost like adding lipstick, right? It just doesn't work, especially in today's cloud-first world, where people are in the DevOps situation, where apps are being delivered in five, 10, 15 minutes. Every day, my app almost gets updated on the phone every day? That just doesn't work. We wrote these systems from the ground up to be able to easily be placed onto any hardware possible. Now, again, I won't mention the vendor, but in my previous lives, there were a lot of hardware boxes and the software was written specifically for those hardware configurations. When they tried to software-define it forcefully, it became a huge challenge, 'cause it was never designed to do that. Whereas at Veritas, we write the software layer first. We test it on multiple hardware systems, and we keep fine-tuning it. Our ideal situation is to sell the software, and if the customer wants the hardware, we'll ship them the box. >> One of the things that struck me in the keynote this morning was what I'll call your compatibility matrix. Whether it was cloud, somebody's data store, that really is your focus, and that is a differentiator, I think. Knocking those down so you can, basically, it's a TAM expansion strategy. >> Oh, yeah, absolutely. I mean, TAM expansion strategy, as well as helping the customer choose what's best for them. We're not limiting their choices. We're literally saying, we go from the box and dropboxes of the world all the way to Dell EMC, even, with Info Map, for example. We'll cover end-to-end spectrum because we don't have a dollar-per-terabyte or dollar-per-petabyte agenda to store this data within our own cloud situation. >> All right, Jyothi, we got to leave it there. Thanks very much for coming back on theCUBE. It's good to see you again. >> Jyothi: No, it's great to be here. >> All right, keep it right there, everybody. We'll be back with our next guest. We're live from Veritas Vision 2017. This is theCUBE. (fast electronic music)