►
From YouTube: KBE Insider Amsterdam - Gaurav Rishi, Kasten by Veeam
Description
In this interview from KubeCon Europe, Gaurav Rishi, VP of Product & Cloud Native Partnerships at Kasten by Veeam, discusses the data protection challenges that customers face as databases on Kubernetes-based applications grow exponentially in variety and complexity. Effective backup/recovery, disaster recovery, and mobility become mission-critical for applications.
Learn how Kasten ensures simplicity, flexibility, and scalability through a platform approach to meet customers' diverse and evolving data protection needs.
A
B
B
A
B
Know
so
this
is
super
exciting
for
me
because
living
inside
the
cloud
native
ecosystem,
what
first
of
all
we
as
a
company
casting
by
veeam
do
is
three
key
use
cases.
One
is
we
do
kubernetes
application,
backup
and
Recovery?
We
do
disaster
recovery
and
we
do
application
Mobility
I.
Can
you
know,
explain.
A
B
B
You
need
to
make
sure
that
you're
working
with
all
of
the
kubernetes
distributions,
so
that
people
have
their
freedom
of
choice,
whether
it's
to
manage
services
or
whether
it's
on-premises
self-managed,
like
openshift
right
as
well
as
you
need
to
work
in
the
context
of
security,
because
backup
turns
out
to
be
your
last
line
of
defense,
and
so
that's
super
critical
too.
So
that's
that's!
B
Really
going
ahead
and
making
sure
we
can
make
all
of
these
technology
pieces
come
to
life
in
a
way
that
makes
it
super
simple
for
people
and
getting
all
the
companies
to
work
together.
So
that's
really
a
part
of
my
job.
While
you
know
we
helped
Define
the
product
and
build
it
which
obviously
the
smart
engineers
at
cast
and
do
right.
A
Right
yeah
I
mean
you
know,
I,
think
kind
of
the
Crux
of
cloud
native
I
mean
it's
kind
of
true
in
more
traditional
application
environments
as
well,
but
a
cloud
native
is
all
about.
You
know
it's
kind
of
service,
oriented
architecture
right,
it's
all
about
connecting
all
the
pieces
together
to
actually
get
to
where
your
application
is
going
and
I.
B
You
know
it's
a
it's
interesting
to
say
that,
because
I
actually
remember
blogging
about
this
up
front
when
I
joined
Caston
and
the
cloud
native
Community,
which
was
Simplicity
and
freedom
of
choice
and
I
know
it
gets
a
little
philosophical.
But
the
point
is
on
one
hand
you
can
argue
that
hey
look.
If
you
have
a
lot
of
choice,
Things
become
complex,
it's
hard
to
choose.
How
do
you
get
things
to
work,
and
sometimes
people
can
confuse
that
by
saying:
let's
go,
restrict
the
choice,
so
that
becomes
sort
of
simple
but
I.
B
B
We
want
people
to
be
able
to
choose
the
best
storage
infrastructure
choose
the
best
deployment
model,
whether
it's
out
to
the
edges
in
the
cloud
hybrid
Etc,
but
at
the
same
time
make
sure
the
data
has
the
freedom
and
can
sort
of
move
around,
because
that's
very
much
how
I
think
most
of
the
deployments
today
are
and
are
ramping
up.
So
right.
So
that's
that's
yeah,
that's
philosophical,
but
also
very
much
true
to
what
we
are
seeing
today.
A
I'm,
a
big
fan
of
the
opinionated
kind
of
solution
that
allows
for
change
right
because
you
know
not
every
it
doesn't
always
fit,
but
at
the
same
time
getting
it
kind
of
up
and
running
in.
You
know
the
way
that
we
know
kind
of
works.
The
best
starts,
you
know,
is
a
lot
easier
starting
point
than
you
know,
having
to
figure
out
all
the
tools
all
the
way
along
so
yeah
I'm
I'm,
a.
B
Fan
yeah,
no
I,
think
I,
think
Simplicity
is
needed
and
especially
in
this
environment,
I
mean
I,
think
I
I
know
you
probably
know
the
stats,
but
it
amazes
me
every
time
we
come
for
the
kubernetes
event.
Majority
of
the
people
are
attending
kubernetes
for
the
very
first
time,
which
means
that
they
are
actually
new
relatively
to
the
ecosystem
right,
and
so
you
cannot
expect
them
to
be
black
belts
on
day,
one
and
so
I
think
as
organizations
sort
of
scale
up
their
workloads.
A
Approach
it
well,
I
mean
even
even
if
you're
in
the
space,
all
the
time
like
keeping
track
of
you
know,
the
plethora
of
projects
is,
is
really
tough
right.
You
know
in
like
I
was
one
of
the
other
people.
I
interviewing
is
actually
working
on
the
like
Cloud
native
glossary,
as
well
as
like
trying
to
put
together
there's
another
cncf
kind
of
project
summary
map.
B
A
B
A
Quite
that
far
all
right,
okay,
fine
I-
was
pushing.
It
was
exciting
being
out
here,
although
they're
excited
yes
yeah,
so
yeah
I
totally
hear
you,
but
you
do.
Your
organization
does
do
a
fair
amount
of
Open,
Source
kind
of
contribution
and
the
project
you
were
talking
about.
Specifically,
the
thought
was
really
interesting
was
navigate.
B
You
know
big
sponsors
of
not
only
the
kubecon
type
events,
but
also
our
active
contributors
to
a
variety
of
Open
Source
projects,
so
so
I
can
probably
and
depending
on
where
customers
and
the
community
members
are
in
their
journey
to
adopting
kubernetes
there's
something
that
you
know
we
see
as
a
fit
for
them.
So
so,
specifically
around
navigate,
which
is
Navi
G
with
a
letter
or
a
number
eight
behind
it
is,
is
an
exciting
one
and
I.
Think
the
you
know
the
thesis
behind
it
really
started
was
on
one
hand.
Helm
is
amazing.
B
B
There
are
a
lot
more
configuration
parameters
that
you
need
to
go
ahead
and
set
right
and
it
it
is
very
easy
to
lose
yourself
into
these
yaml
files,
authoring
them
and
different
charts
and
different
aspects
of
those
yaml
files
might
not
appeal
to
the
same
domain
owners.
So
your
developers
might
care
about
some
configuration
parameters.
Your
operations
teams
might
care
about
a
different
set
of
parameters
and,
and
things
can
get
out
of
whack
and
complex
to
manage
really
quickly
right.
A
B
And
we
noticed
that
when
we
were
dealing
with
our
customers,
and
so
Caston
K10,
which
is
our
product
also
is
a
cloud
native
application,
and
you
know
we
started
seeing
some
of
those
complexities
ourselves
too.
So
navigate
was
born
from
that
problem
and
to
see,
if
there's
a
way
to
solve
that,
and
so
what
it
allows
you
to
do
is
essentially
gives
you
a
simple.
A
A
A
B
You
to
sort
of
very
easily
be
able
to
go
ahead
and
get
a
list
of
think
of
it
as
values
and
parameters,
and
so
you
can
go
ahead
and
get
your
applications
configured
in
a
way
where
you
know
what
might
be
the
parameters,
what
the
value
for
that
is
set
it
up
and
it
in
turn
will
go
ahead
and
generate
the
chart
for
you
right
and
I.
Think
that,
and
that
turns
out
to
be
something.
B
That's
super
useful,
because
once
you
get
your
perfect
chart,
you've
got
this
it's
easy
to
understand,
but
then
it
can
be
reused
too
right
and
you
can
apply
it
across
a
variety
of
templates.
So
that's
in
fact
how?
If
you
want
to
go
to
install
at
caston.io,
for
example,
that's
what
we
use
under
the
covers
to
go
ahead
and
make
it
easy
to.
A
B
So
yeah,
that's
something
that
we
are
excited
about.
We
are
definitely
seeing
you
know
the
community
sort
of
saying:
okay,
that's
that's
interesting,
and
so
I
think
events
like
this,
where
we've
got
everybody
from
various
Industries
come
in
and
talk
about
it
can
help
sort
of
contribute
to
it
and
take
it
to
the
next
level
yeah
and
there's
so
much
more.
You
can
do
right,
whether
it's
about
parameter
validation
or
things
of
that
nature.
I
think
those
are
all
very
much
a
part
of
it.
B
A
I
mean
you
know
what
you
know.
What
do
you
think
is
the
you
know
the
the
interesting
you
know
things
like
canister
or
whatever
you
know,
you're
doing
a
lot
of
contributions
to
you
know
these
open
source
projects
and
it
sounds
like
you're
contributing
to
them,
like
you're,
you're
kind
of
creating
them
and
contributing
to
them.
Because
of
of
the
need
that
you
have
that
you
think
others
might
share
so
yeah
I
mean
I.
Think
that's
yeah.
B
A
B
Maybe
maybe
the
stops
to
that
is
so
I
like
to
joke.
That
kubernetes
is
a
you
know,
eight
or
nine
year
young
system.
Right
now
the
ecosystem
is
still
developing.
The
Technologies
are
in
production,
but
there's
so
much
Innovation
still
going
on.
So
if
I
really
had
to
rewind
the
initial
years
of
kubernetes,
you
had
this
whole
Paradigm
around
hey
pets
and
cattle.
You
know
stateless
systems
right
and-
and
you
know,
as
a
as
a
vegetarian
that
was
not
very
appealing.
The
whole
analog
around.
A
B
Right,
very
cool,
I,
good
job,
Steve
I
think
that
that
would
have
been
a
much
better
way
to
term
it.
But
for
whatever
reason
that
stuck-
and
that
was
a
good
way
to
start
the
system,
you
had
very
simple
applications
which
didn't
have
state
but
think
about
any
application.
Whether
it's
your
banking
applications
shopping
ad
application,
you
need
to
have
state,
you
need
to
have
data
which
is
generated
as
a
result
of
you
shopping
or
as
a
result
of
you,
hopefully
earning
money
or
spending
money
and
right.
B
You
need
to
store
that
somewhere
and
and
so
state
is
going
to
exist,
and
you
have
the
other
thing
which
sort
of
went
in
came
alive
in
the
cloud
native
development
pattern,
which
was
what
we
call
polyglot
persistence,
which
was
essentially
just
a
fancy
way
of
saying.
A
simple
application
under
the
covers
uses
a
variety
of
data
services,
whether
it's
SQL
nosql
messaging
queue,
streaming
databases.
The
point
is
you
have
not
a
single
relational
database,
which
used
to
be
in
the
monolith
non-cloud
native
world.
B
You
now
have
moved
to
a
cloud
native
application
with
microservices
and
multiple
data
services
under
the
covers.
So
if
I
kind
of
now
fast
forward,
10
years
into
the
journey,
we
actually
have
databases
as
the
most
popular
workload
running
on
kubernetes
right.
So
if
you
kind
of
go,
look
at
your
data
dog
report,
which
is
not
a
survey
but
actually
going
and
looking
into
what's
running
in
these
containers
across
you
know
billion
plus
of
them.
It
turns
out
that
it's
usually
things
like
postgresql
and
you
know,
and
things
of
that
nature.
B
So
so
that's
what's
happened
for
of
all
you've
had
a
huge
amount
of
State
come
in
and
as
soon
as
you
have
state,
you
need
to
make
sure
that
you're
actually
able
to
protect
yourself
in
case
there
are
failures,
and
that
could
be.
You
know,
attacks
from
things
like
ransomware
or
there
could
be
mistakes
that
people
made
by
misconfiguring
Etc,
and
so
you
need
to
be
able
to
go
ahead
and
recover
and
that's
what
brings
up
data
protection
as
a
Here
and
Now
issue.
A
The
control
on
either
side
yeah,
so
I
actually
think
this
is
part
of
my
route.
I,
just
I
wasn't
actually
sure
where
the
next
turn
was
okay,
so
that's
why
I
was
checking
it
out,
so
so
one
of
the
things
that
I
actually
think
has
also
been
really
interesting
kind
of
the
cloud
native
world,
even
even
in
more
traditional
apps
that
are
not
actually
doing
kind
of
the
real
Cloud
native
of
thing.
The
number
of
types
of
databases
that
is
in
every
application
is
like
ridiculous.
A
An
application
used
to
be
just
a
relational
database
behind
it,
but
now
it's
got,
you
know
a
you
know
some
sort
of
name
value
pattern,
no
SQL
database
right.
It
also
has
like
a
you
know:
a
document
store
no
SQL
database.
It
also
has
a
relational
database,
and
maybe
some
others,
yeah
and
I.
Think
that's
been
also
really
interesting.
A
B
B
Be
your
last
time
line
of
defense,
but
in
addition
to
that,
the
makeup
of
your
applications
under
the
covers
have
a
lot
of
this
polyglot
persistence.
Point
that
we
were
making.
But
you
know
when
you
actually
look
at
the
techniques
of
doing
data
protection
or
things
like
being
able
to
take
backups.
You
can
you
know,
as
software
developers
or
former
software
developers
I
mean
I,
think
we
all
love
our
stack
diagrams
and
layers
of.
B
Right,
but
you
know
you
can
you,
can
you
can
work
at
the
storage
layer
right?
So
you
can
do
snapshots,
so
you
can
work
with
block
file
or
object,
stores
and
say
look
I
need
to
go,
take
a
quick
snapshot
of
that
and
that
that
works
fine
in
some
cases,
but
you
also
might
need
to
go
ahead
and
work
at
a
layer
above
which
is
at
the
database
level,
which
we
call
logical,
backups
and
the
reason
you
might
want
to
do.
That
is
for
some
applications.
B
B
For
example,
or
mongodb,
Atlas,
and
so
on
and
and
both
are
good
right
depending
on
the
needs,
you
might
decide,
option
A
or
B
and
A
and
B
also
in
some
cases,
and
so
you
also
want
your
backup
to
work
across
both
those
cases,
which
is
what
we
do
and
so
how
canister
fits
in,
which
is
again
an
open
source
project.
Is
it
gets
a
little
more
involved
and
I
know
we're
navigating
through
the
streets
here.
A
B
But
but
it's
interesting
because
think
about
going
ahead
and
doing
a
backup,
you
might
have
multiple
replicas
running
what
you
might
want
to
go
ahead
and
do
is
say:
look
I
want
to
have
an
order
of
operations
in
terms
of
making
sure
scale
it
down.
Go
act
on
replica
number,
two
make
sure
you
use
these
tools,
so
you
have
pre-hooks
and
post
Hooks
and
our
terminology
to
be
able
to
create
These
Blueprints
for
certain
types
of
databases
right
and
then
the
time
comes
for
recovery.
B
These
order
of
operations
are
even
more
important
because
it
might
be
that
your
application
requires
microservice
2
to
come
up
only
after
microservice
one
has
been
rehydrated
right.
So
so
what
canister
allows
you
to
do
is
create
These
Blueprints,
which
can
be
extended
or
can
be
authored
up
front
for
your
applications,
which
have
under
the
covers
various
types
of
data
services
and
then
be
able
to
Define
these
order
of
operations.
B
B
A
B
No,
so
it's
a
great
question
so
I
think
the
way
we've
got
canister
right
now
and
the
way
we
envision
it
is
the
same.
Essentially
Council
plays
a
really
important
part
in
doing
what
I
just
defined,
which
is
you
know,
the
blueprint
aspect
of
it,
but
if
you
had
to
go
ahead
and
think
about
backup
and
Disaster
Recovery,
there's
so
many
other
aspects
that
are
needed.
So,
for
example,
you
need
to
go
ahead
and
not
only
discover
all
the
applications
right
first
of
all
are
running
in
your
cluster.
B
Then
you
need
to
go
ahead
and
Define.
What
should
be
the
policies?
How
often
should
they
be
backed
up
right?
Then
you
need
to
go
ahead
and
Define.
Well,
how
long
should
they
be
kept?
Because
you
don't
want
to
keep
increasing
your
storage
bill?
You
need
to
go
and
say
my
retention
policy
is
seven
years
or
whatever
or
30
days
and
after
that
time
go
and
delete
it
or
move
it
from.
You
know
this
Object
Store
to
maybe
a
coal
Glacier
or
things
of
that
nature.
A
B
There
are
all
these
other
attributes,
and
so
that's
where
we
have
custom
K10
as
a
core
product
which
does
a
lot
of
that
work,
but
for
some
of
the
key
critical
tasks
it
uses
canister
to
to
be
able
to
Define
These
Blueprints
right.
So
the
problem
we're
trying
to
solve
with
that
and
strike
this
healthy
balance
is
we
want
our
partners,
both
system
integrators
as
well
as
customers,
to
be
able
to
not
wait
for
a
release
from
us
to
be
able
to
say
hey.
B
My
applications
looks
like
this,
and
my
order
of
operations
need
to
be
ABC
right.
Give
me
a
new
release
for
that.
I
should
be
able
to
go
and
work
at
my
own
pace
and
across
my
own
deployment
model,
and
so
that's
the
way
we
see
canister
evolving
and
we
keep
getting
it
richer
and
it
surprises
us
at
times
the
customers
and
community
members
who've
used
it
and
built
their
own
things,
and
you
know
wrapped
it
with
other
kinds
of
scheduling.
B
A
Right
started
right
there,
so
one
thing
I
want
to
ask
you,
because
you
were
talking
about
the
complexity
of
backup,
and
you
know,
data
protection
or
whatever
is
that
you
know
there's
this
I
wouldn't
say
new,
but
it's
getting
it's
getting
more
prevalent
concept
of,
like
eventual
consistency
and
I'm
curious
to
know
like
do
do
some
of
the
tools
you
described
and
kind
of
help.
Somebody
solve
you
know
when
you,
when
you
have
eventual
consistency,
like
is
the
data
you
know
like
how
do
you?
B
A
B
I
just
gave
a
simple
example
of
saying:
hey
look
when
it
comes
to
postgres,
we
could
go
ahead
and
employ
you
know:
PG
dump
right
but,
for
example,
the
Cassandra.
There
is
also
something
called
Kate
Sandra,
which
is
another
open
source
sort
of
operator
framework
which
we've
integrated
into
that
hides
the
complexity
of
being
able
to
go
ahead
and
work
in
such
environments,
and
that's
a
pattern
that
we
are
seeing
come
up
with.
B
A
A
You
know,
creators
like
developers
whatever
like
they
know,
for
example
like
the
best
way
for
their
application
to
scale
and
and
kind
of
containerization
of
those
was
often
not
a
great
idea
because
you,
you
were
like,
like
kind
of
trying
to
know
better
than
the
database
vendor,
and
so
the
database
vendors
are,
are
also
now
going
kind
of
more
containerized
and
I.
Think
they're
doing
you
know
they're
doing
a
good
job
of
that,
and
you
know
this
is
not
a
fault
at
all.
A
A
Know
because,
like
at
the
end
of
the
day,
you
know
Apache,
you
know
or
httpd
right
is
it's
a
pretty
simple
system?
You
know
I
mean
it's
a
really
good
piece
of
code
and
all
that
other
stuff,
but
like
at
the
end
of
the
day.
It
doesn't
you
know
it
kind
of
you
can
kind
of
just
start
it
and
stop
it
right,
whereas
a
database
has
so
many
other
kind
of
moving
parts
and
I
think
that
that's
a
like
your
philosophy
is
a
good
one
where
you're
kind
of
saying,
okay,
we
we
hope.
A
You
know
that
you
as
the
author
of
this
software,
know
the
best
way
to
provide
the
data
and
then
we
can
go
off
and
do
what
we
do
well,
which
is
the
you
know,
the
kind
of
right
back
up
and
restore
and
all
that
jazz.
But
the
the
detail
is
like
you
know
you,
separation
of
concerns,
where
hey
that's
exactly
the
way.
You
folks
know
this
part
well,
and
we
know
this
part
well,
let's
work
it
together.
Instead
of
trying
to
take
over
yeah.
B
And
I
think
there's
another
sort
of
sort
of
bridging
open
source
project,
which
probably
is
worth
mentioning
too,
which
is
copia.
So
you
know
data
movement
once
you've
got
the
backup
process.
Etc
you've
got
some
things
into
your
persistent
volume.
You
need
to
usually
move
them
somewhere
so
that
it's
more
than
just
a
snapshot,
because
that's
a
bad
idea
for
a
backup.
You
know
your
storage
system
can
fail
and
and
so
on,
so
typically
people
would
go
ahead
and
say:
look.
B
Site
so
that
you
can
protect
yourself
and
now
you
need
to
go
ahead
and
do
a
lot
of
work
to
make
sure
you
are
efficiently
and
securely
moving
the
data
out
into
that
place,
which
typically
turns
out
to
be
an
object,
storage,
location
and
at
times
it's.
You
know,
increasingly
in
the
clouds
right,
whether
it's
a
blob
store
and
as
your
side
or
whether
it's
S3
Etc,
and
so
in
that
context,
we've
also
been
contributing
a
lot
in
what
we
call
copia.
A
B
B
Actually-
and
now,
it's
obviously
in
production
with
some
of
the
world's
largest
companies,
using
that
as
a
result
of
using
Caston
and
I,
think
that's
another
interesting
hand
and
glove
project
between
what
we
see
with
canister
and
copia,
as
you
sort
of
evolve
towards
this
data
protection,
Journey
right
so
yeah,
so
yeah
so
I
think
just
to
complete
the
analog
I
mean
you
know,
as
as
you
come
into
kubecon
if
you've
come
in.
For
the
first
time,
we've
got
open
source
sort
of
initiatives
like
Cube
campus,
where
you
can
come
and
learn.
A
B
Strings
attached,
it's
it's
a
way
of
sort
of
giving
to
the
community
making
sure
they're
educated
and
that's
that's
a
that's
a
great
initiative.
The
second
one
is
like,
let's
say,
you've
gone
ahead
and
started,
creating
your
first
few
applications.
You
run
into
some
of
these
practical
problems.
We
were
talking
about
with
things
like
Helm
you've
got
projects
like
navigate
now,
let's
say
you've
gone
ahead
being
able
to
deploy
those
applications.
Things
are
working
fine.
B
What
we've
also
realized
is
people
come
and
say:
hey,
well,
I
need
projects
and
I'll
put
a
plugin
for
another
one
which
is
cubester,
which
is
our
way
of
going
ahead
and
saying
well,
I,
don't
know,
there's
so
many
different
storage
environments
in
mind.
In
my
little
cluster
or
in
my
set
of
clusters
or
hybrid
environments,
can
something
go
ahead
and
figure
out?
What
are
these
different
storage
environments
there?
First
of
all,
just
just
the
auditing
aspect
and
Discovery
aspect.
B
Once
I've
got
that
going,
can
you
go
ahead
and
sort
of
just
make
sure
that
they
are
actually
okay
with
being
able
to
go
ahead
and
do
things
like
backups?
Do
they
even
support
the
snapshot
apis?
You
know
that
some
vendors
don't
support
even
today
the
Legacy
ones,
though,
of
course
that's
quite
corrected
at
this
point
of
time,
or
rather
right,
drivers
installed
and
things
of
that
nature.
B
So
in
that
context
you
also
want
a
tool
which
can
not
only
discover
your
environment
but
can
go
ahead
and
validate
that
you
can
actually
have
all
of
these
pieces
in
and
then
maybe
run
some
performance
tests.
Maybe
it's
an
fio
or
something
right
just
to
just
to
get
that
and
that's
exactly
what
projects
like
cubester
do
for
the
environment
and
then
once
you've
got
that
in
I.
Think
data
protection
comes
in
next
as
a
stop,
so
that
your
have
your
last
line
of
defense
and,
having
said
that
sounds
like
we've
reached.