(light orchestral music)
>> Hello, everyone, and welcome to the Cube Conversation
here at the Palo Alto studios for theCUBE.
I'm John Furrier, the co-founder of SiliconANGLE Media.
We're here for some news analysis
with Peter Smails, the CMO of Datos.IO
D-a-t-o-s dot I-O.
Hot new start up with some news.
Peter was just here for a thought leader segment
with Chris Cummings talking about the industry breakdown.
But the news is hot,
prior to re:Invent which you will be at?
>> Absolutely.
>> RecoverX is the product.
2.5, it's a release.
So, you've got a point release on your core product.
>> Correct.
>> Welcome to this conversation.
>> Thanks for having me.
Yeah, we're excited to share the news.
Big day for us.
>> All right, so let's get into the hard news.
You guys are announcing a point release
of the latest product which is your core flagship, RecoverX.
>> Correct.
>> Love the name.
Love the branding of the X in there.
It reminds me of the iPhone, so makes me want to buy one.
But you know ...
>> We can make that happen, John.
>> You guys are the X Factor.
So, we've been pretty bullish on what you guys are doing.
Obviously, like the positioning.
It's cloud.
You're taking advantage of the growth in the cloud.
What is this new product release?
Why?
What's the big deal?
What's in it for the customer?
>> So, I'll start with the news,
and then we'll take a small step back
and sort of talk about why exactly
we're doing what we're doing.
So, RecoverX 2.5 is the latest in
our flagship RecoverX line.
It's a cloud data management platform.
And the market that we're going after
and the market we're disrupting
is the traditional data management space.
The proliferation of modern applications--
>> John: Which includes which companies?
>> So, the Veritas' of the world,
the Commvault's of the world,
the Dell EMC's of the world.
Anybody that was in the traditional--
>> 20-year-old architected
data backup and recovery software.
>> You stole my fun fact. (laughs)
But very fair point which is that the average age
approximately of the leading backup
and recovery software products
is approximately 20 years.
So, a lot's changed in the last 20 years,
not the least of which has been this proliferation
of modern applications, okay?
Which are geo-distributed microservices oriented
and the rapid proliferation of multicloud.
That disrupts that traditional notion of data management
specifically backup and recovery.
That's what we're going after with RecoverX.
RecoverX 2.5 is the most recent version.
News on three fronts.
One is on our advanced recovery,
and we can double-click into those.
But it's essentially all about giving you
more data awareness,
more granularity to what data you want to recover
and where you want to put it,
which becomes very important in the multicloud world.
Number two is what we call data center aware
backup and recovery.
That's all about supporting geo-distributed
application environments,
which again, is the new normal in the cloud.
And then number three is around enterprise hardening,
specifically around security.
So, it's all about us increased flexibility
and new capabilities for the multicloud environment
and continue to enterprise-harden the product.
>> Okay, so you guys say significant upgrade.
>> Peter: Yep. >> I want to just look at that.
I'm also pretty critical,
and you know how I feel on this so don't take it personal,
multicloud is not a real deal yet.
It's in statement of value that customers are saying--
It's coming!
But cloud is here today, regular cloud.
So, multicloud ...
Well, what is multicloud actually mean?
I mean, I can have multiple clouds
but I'm not actually moving workloads across clouds, yet.
>> I disagree. >> Okay.
>> I actually disagree.
We have multiple customers. >> All right, debunk that.
>> I will debunk that.
Number one use case for RecoverX
is backup and recovery.
But with a twist of the fact that
it's for these modern applications
running these geo-distributed environments.
Which means it's not about backing up my data center,
it's about, I need to make a copy of my data
but I want to back it up in the cloud.
I'm running my application natively in the cloud,
so I want a backup in the cloud.
I'm running my application in the cloud
but I actually want to backup from the cloud
back to my private cloud.
So, that in lies a backup and recovery,
and operation recovery use case that involves multicloud.
That's number one.
Number two use case for RecoverX
is what we talk about on data mobility.
>> So, you have a different definition of multicloud.
>> Sorry, what was your--
Our definition of multicloud is fundamentally
a customer using multiple clouds,
whether it be a private on-prem GCP, AWS, Oracle,
any mix and match.
>> I buy that.
I buy that.
Where I was getting critical of was a workload.
>> Okay.
>> I have a workload and I'm running it on Amazon.
It's been architected for Amazon.
Then I also want to run that same workload
on Azure and Google.
>> Okay.
>> Or Oracle or somewhere else.
>> Yep.
>> I have to re-engineer it (laughs)
to move, and I can't share the data.
So, to me what multicloud means,
I can run it anywhere.
My app anywhere.
Backup is a little bit different.
You're saying the cloud environments
can be multiple environments for your solution.
>> That is correct. >> So, you're looking at it
from the other perspective.
>> Correct.
The way we define ourselves
is application-centric data management.
And what that essentially means is we don't care
what the underlying infrastructure is.
So, if you look at traditional backup and recovery products
they're LUN-based.
So, I'm going to backup my storage LUN.
Or they're VM-based.
And a lot of big companies made a lot of money doing that.
The problem is they are no LUN's and VM's
in hybrid cloud or multicloud environment.
The only thing that's consistent across application,
across cloud-environments is the data and the applications
that are running.
Where we focus is we're 100% application-centric.
So, we integrate at the database level.
The database is the foundation
of any application you create.
We integrate there, which makes us agnostic
to the underlying infrastructure.
We run, just as examples, we have customers running
next generation applications on-prem.
We have customers running next generation applications
on AWS in GCP.
Any permutation of the above,
and to your point about back to the multicloud
we've got organizations doing backup with us
but then we also have organizations using us
to take copies of their backup data
and put them on whatever clouds they want
for things like test and refresh.
Or performance testing or business analytics.
Whatever you might want to do.
>> So, you're pretty flexible.
I like that.
So, we talked before on other segments,
and certainly even this morning about
modern stacks.
>> Yeah.
>> Modern applications.
This is the big to-do item for all CXOs and CIOs.
I need a modern infrastructure.
I need modern applications.
I need modern developers.
I need modern everything.
Hyper, micro, ultra.
>> Whatever buzz word you use.
>> But you guys in this announcement have a couple key things
I want to just get more explanation on.
One, advanced recovery, backup anywhere, recover anywhere,
and you said enterprise-grade security is the third thing.
>> Yep.
>> So, let's just break them down one at a time.
Advanced recovery for Datos 2.5,
RecoverX 2.5. >> Yep.
>> What is advanced recovery?
>> It's very specifically about providing
high levels of granularity for recovering your data,
on two fronts.
So, the use case is, again, backup.
I need to recover data.
But I don't want to necessarily recover everything.
I want to get smarter about the data I want to recover.
Or it could be for non-operational use cases,
which is I want to spin up a copy of data
to run test dev or to do performance testing on.
What advanced recovery specifically means is
number one, we've introduced the notion
of queryble recovery.
And what that means is that I can say things like
star dot John star.
And the results returning from that,
because we're application-centric,
and we integrated the database,
we give you visibility to that.
I want to see everything star dot John star.
Or I want to recover data from a very specific row,
in a very specific column.
Or I want to mask data that I do not want to be recovered
and I don't want people to see.
The implications of that are think about that
from a performance standpoint.
Now, I only recover the data I need.
So, I'm very, very high levels of granularity
based upon a query.
So, I'm fast from an RTO standpoint.
The second part of it is for non-operational requirements
I only move the data that is select to that data set.
And number three is it helps you with things like
GDPR compliance and PII compliance
because you can mask data.
So, that's query-based recovery.
That's number one.
The second piece of advanced recovery
is what we call incremental recovery.
That is granular recovery based upon a time stamp.
So, you can get within individual points in time.
So, you can get to a very high level of granularity
based upon time.
So, it's all about visibility.
It's your data and getting very granular in a smart way
to what you want to recover.
So, if I kind of hear what you're saying,
what you're saying is essentially
you built in the operational effectiveness
of being effective operationally.
You know, time to backup recovery, all that good RTO stuff.
Restoring stuff operationally >> Peter: Very quickly.
>> very fast. >> Peter: In a smart way.
>> So, there's a speed game there which is table stakes.
But you're real value here is
all these compliance nightmares
that are coming down the pike, GDPR and others.
There's going to be more.
>> Peter: Absolutely.
I mean, it could be HIPPA, it could be GDPR,
anything that involves-- >> Policy.
>> Policies.
Anything that requires, we're completely policy-driven.
And you can create a policy to mask certain data
based upon the criteria you want to put in.
So, it's all about--
>> So you're the best of performance,
and you got some tunability.
>> And it's all about being data aware.
It's all about being data aware.
So, that's what advanced recovery is.
>> Okay, backup anywhere, recover anywhere.
What does that mean?
>> So, what that means is the old world of backup
and recovery was I had a database running in my data center.
And I would say database please take a snapshot of yourself
so I can make a copy.
The new world of cloud is that these microservices-based
modern applications typically run,
they're by definition distributed,
And in many cases they run distributed across
they're geo-distributed.
So, what data center aware backup and recovery is,
use a perfect example.
We have a customer.
They're running their eCommerce.
So, leading online restaurant reservations company.
They're running their eCommerce application on-prem,
interestingly enough,
but it's based on Cassandra distributed database.
Excuse me, MongoDB.
Sorry.
They're running geo-distributed, sharded MongoDB clusters.
Anybody in the traditional backup and recovery
their head would explode when you say that.
In the modern application world,
that's a completely normal use case.
They have a data center in the U.S.
They have a data center in the U.K.
What they want is they want to be able to do
local backup and recovery while maintaining
complete global consistency of their data.
So again, it's about recovery time ultimately
but it's also being data aware
and focusing only on the data that you need
to backup and recovery.
So, it's about performance
but then it's also about compliance.
It's about governance.
That's what data center aware backup is.
>> And that's a global phenomenon
people are having with the GO.
>> Absolutely.
Yeah, you could be within country.
It could be any number of different things that drive that.
We can do it because we're data aware--
>> And that creates complexity for the customer.
You guys can take that complexity away
>> Correct. >> From the whole global,
regional where the data can sit.
>> Correct.
I'd say two things actually.
To give the customers credit,
the customers building these apps or actually getting
a lot smarter about what they're data is
and where they're data is. >> So they expect this feature?
>> Oh, absolutely.
Absolutely.
I wouldn't call it table stakes
cause we're the only kids on the block that can do it.
But this is in direct response to our customers
that are building these new apps.
I want to get into some of the environmental
and customer drivers in a second.
I want to nail the last segment down.
Cause I want to unpack the whole why is this trend happening?
What's the gestation period?
What's the main enabler for you?
But okay, final point on the significant announcements.
My favorite topic enterprise-grade security.
What the hell does that mean?
First of all, from your standpoint
the industry's trying to solve the same thing.
Enterprise-grade security,
what are you guys providing in this?
>> Number one, it's basically security protocol.
So, TLS and SSL.
This is weed stuff.
TLS, SSL, so secure protocol support.
It's integration with LDAP.
So, if organizations are running,
primarily if they're running on-prem
and they're running in an LDAP environment,
we're support there.
And then we've got Kerberos support
for Kerberos authentication.
So, it's all about just checking the boxes around
the different security
>> So, this is like in between >> and transport protocol.
>> the toes, the details around compliance,
identity management.
>> Peter: Bingo.
>> I mean we just had Centrify's CyberConnect conference,
and you're seeing a lot of focus on identity.
>> Absolutely.
And the reason that that's sort of from a market standpoint
the reason that these are very important now
is because the applications that we're supporting
these are not science experiments.
These are eCommerce applications.
These are core business applications
that mainstream enterprises are running,
and they need to be protected and they're bringing
the true, classic enterprise security, authentication,
authorization requirements to the table.
>> Are you guys aligning with those features?
Or is there anything significant in that section?
>> From an enterprise security standpoint?
It's primarily about we provide the support,
so we integrate with all of those environments
and we can check the boxes.
Oh, absolutely TLS.
Absolutely, we've got that box checked because--
>> So, you're not competing with other cybersecurity?
>> No, this is purely we need to do this.
This is part of our enterprise--
>> This is where you partner.
>> Peter: Well, no.
For these things it's literally just us
providing the protocol support.
So, LDAP's a good example.
We support LDAP.
So, we show up and if somebody's using my data management--
>> But you look at the other security solutions
as a way to integrate with?
>> Yeah. >> Not so much--
>> Absolutely, no.
This has nothing to do with the competition.
It's just supporting ...
I mean Google has their own protocol,
you know, security protocols, so we support those.
So, does Amazon.
>> I really don't want to go into the customer benefits.
We'll let the folks go to the Datos website,
d-a-t-o-s dot i-o is the website,
if you want to check out all their customer references.
I don't want to kind of drill on that.
I kind of want to really end this segment
on the real core issue for me is reading the tea leaves.
You guys are different.
You're now kind of seeing some traction and some growth.
You're a new kind of animal in the zoo,
if you will. (Peter laughs)
You've got a relevant product.
Why is it happening now?
And I'm trying to get to understanding
Cloud Oss is enabling a lot of stuff.
You guys are an effect of that,
a data point of what the cloud is enabled as a venture.
Everything that you're doing,
the value you create is the function of the cloud.
>> Yes. >> And how data is moving.
Where's this coming from?
Is it
just recently?
Is it a gestation period of a few years?
Where did this come from?
You mentioned some comparisons like Oracle.
>> So, I'll answer that in sort of,
we like to use history as our guide.
So, I'll answer that both in macro terms,
and then I'll answer it in micro terms.
From a macro term standpoint,
this is being driven by the proliferation
of new data sources.
It's the easiest way to look at it.
So, if you let history be your guide.
There was about a seven to eight year proliferation
or gap between proliferation of Oracle
as the primary traditional relational database data source
and the advent of Veritas who really defined themselves
as the defacto standard for traditional on-prem
data center relational data management.
You look at that same model,
you'll look at the proliferation of VMware.
In the late 90s, about a seven to eight year gestation
with the rapid adoption of Veeam.
You know the early days a lot of folks laughed at Veeam,
like, "Who's going to backup VMs?
People aren't going to use VMs in the enterprise.
Now, you looked at Veeam, great company.
They've done some really tremendous things
carving out much more than a niche
providing backup and recovery and availability
in a VM-based environment.
The exact same thing is happening now.
If you go back six to seven years from now,
you had the early adoption of the MongoDBs,
the Cassandras, the Couches.
More recently you've got a much faster acceleration
around the DynamoDBs and the cloud databases.
We're riding that same wave to support that.
>> This is a side effect of the enabling
of the growth of cloud.
>> Yes. >> So, similar to what you did
in VMware with VMs and database for Oracle
you guys are taking it to the next level.
>> These new data sources are completely driven by the fact
that the cloud is enabling this completely distributed,
far more agile, far more dynamic, far less expensive
application deployment model,
and a new way of providing data management is required.
That's what we do.
>> Yeah, I mean it's a function of maturity, one.
As Jeff Rickard, General Manager of theCube, always says,
when the industry moves to it's next point of failure,
in this case failure is problem and you solve.
So, the headaches that come from
the awesomeness of the growth.
>> Absolutely.
And to answer that micro-wise briefly.
So, that was the macro.
The micro is the proliferation of,
the movement from monolithic apps
to microservices-based app, it's happening.
And the cloud is what's enabling them.
The move from traditional on-prem to hybrid cloud
is absolutely happening.
That's by definition the cloud.
The third piece which is cloud-centric
is the world's moving from a scale up world
to an elastic-compute, elastic storage model.
We call that the modern IT stack.
Traditional backup and recovery,
traditional data management doesn't work
in the new modern IT stack.
That's the market we're planning.
That's the market we're disrupting
is all that traditional stuff moving to the modern IT stack.
>> Okay, Datos IO announcing a 2.5 release of RecoverX,
their flagship product,
their start up growing out of Los Gatos.
Peter Smails here, the CMO.
Where ya going to be next?
What's going on--
I know we're going to see you re:Invent in a week in a half.
>> Absolutely.
So, we've got two stops.
Well, actually the next stop on the tour is re:Invent.
So, absolutely looking forward to being back on theCUBE
at re:Invent.
>> And the company feels good about those things are good.
You've got good money in the bank.
You're growing.
>> We feel fantastic.
It's fascinating to watch as things develop.
The conversations we have now
versus even six months ago.
It's sort of the tipping point of people get it.
You sort of explain,
"Oh, yeah it's data management from modern applications.
Are you deploying modern applications?"
Absolutely.
>> Share one example to end this segment
on what you hear over and over again
from customers that illuminates what you guys are about
as a company, the DNA, the value preposition,
and their impact on results and value for customers.
>> So, I'll use a case study as an example.
You know, we're the world's largest
home improvement retailers.
Old way, was they ran their multi-billion dollar
eCommerce infrastructure.
Running on IBM Db2 database.
Running in their on-prem data center.
They've moved their world.
They're now running,
they've re-architected their application.
It's now completely microservices-based
running on Cassandra,
deployed 100% in Google cloud platform.
And they did that because they wanted to be more agile.
They wanted to be more flexible.
It's a far more cost effective deployment model.
They are all in on the cloud.
And they needed a next generation backup and recovery
data protection, data management solution
which is exactly what we do.
So, that's the value.
Backup's not a new problem.
People need to protect data
and they need to be able to take
better advantage of the data. >> All right, so here's the
final, final question.
I'm a customer watching this video.
Bottom line maybe, I'm kind of hearing all this stuff.
When do I call you?
What are the signals?
What are the little smoke signals
I see in my organization burning?
When do I need to call you guys, Datos?
>> You should call Datos IO anytime,
if you're doing anything with
development of modern applications, number one.
If you're doing anything with hybrid cloud
you should call us.
Because you're going to need to reevaluate
your overall data management strategy
it's that simple.
>> All right, Peter Smails, the CMO of Datos,
one of the hot companies here in Silicon Valley,
out of Los Gatos, California.
Of course, we're in Palo Alto at theCube Studios.
I'm John Furrier.
This is theCUBE conversation.
Thanks for watching.
(upbeat techno music)