►
Description
In this demo we will show how to backup an application in one cluster and and restore it in another cluster.
Interested in the open source project Velero?
Check out https://velero.io!
A
A
A
So
I'll
go
ahead
and
publish
that
and
if
I
go
back
to
the
front
page
you'll
see
that
I
have
a
post.
So
now
we'll
go
back
to
my
terminal,
and
the
next
thing
I'd
like
to
do
is
create
a
backup
with
that
WordPress
application,
so
I'll
save
velaro,
backup,
create
and
I'll
call
it
WP
for
WordPress,
and
then
I'd
like
to
include
everything
in
the
default
namespace,
so
I'll
specify
include
namespaces
default
and
then
I'll
also
specify
the
weight
flag,
which
will
just
wait
for
the
backup
to
complete
so
go
ahead
and
run.
A
That
and
velaro
is
now
communicating
with
the
kubernetes
api
and
getting
all
the
resources
running
in
that
default.
Namespace.
And
it's
also
looking
for
any
persistent
volumes
that
are
being
used
by
the
resources
running
in
that
namespace
and
if
it
finds
them,
it
should
take
snapshots
of
the
underlined
cloud
volumes.
So
since
we're
running
on
AWS,
those
persistent
volumes
are
backed
by
EBS
volumes,
and
so
we
should
get
EBS
snapshots
of
those
volumes.
A
So
the
backups
completed
now
so
we'll
go
ahead
and
run
a
Valero
backup
described
command
for
the
WP,
backup
and
I'll
pass.
The
details
5,
which
will
give
me
some
more
detailed
information
about
the
backup
now
there's
a
bunch
of
output
here,
but
I
want
to
just
look
at
what's
on
the
bottom,
and
we
see
that
under
the
persistent
volume
section,
we
have
two
snapshots
that
appear
and
we
have
some
information
about
the
snapshot,
IDs
and
and
other
information
about
the
volumes
that
are
being
backed
up
so
so
far.
This
looks
pretty
good.
A
So
what
I'll
do
now
is
I'll
actually
simulate
a
disaster
by
going
ahead
and
deleting
the
WordPress
application
from
this
cluster,
so
I'm
gonna
say:
cube.
Ctl,
delete
deployment
services
and
persistent
volumes
that
are
labeled
with
app
equals.
Wordpress
I'll
go
ahead
and
run
that
and
I'm
also
gonna.
Stop
my
port
forwarding
command
down
here
on
the
bottom.
A
And
so
these
all
of
these
resources
are
being
deleted
now
and
that's
complete,
and
so,
if
I
switch
back
to
the
browser
and
refresh
you'll
see,
we
no
longer
have
a
connection.
So
the
next
thing
I'd
like
to
do
is
switch
to
my
second
terminal
window
here.
So
I'm
gonna
click
on
that
and
this
terminal
is
connected
to
an
entirely
separate
kubernetes
cluster.
It's
another
cluster
running
in
AWS,
and
so
we'll
call
this
one
cluster
2
and
what
I'd
like
to
show.
You
is
the
backup
locations
that
are
configured
for
Valero
running
in
this
cluster.
A
So
if
I
run
the
lera
backup
location
yet
we'll
see
that
there
are
two
backup
locations
configured
for
this
cluster
and
the
first
one
is
actually
named
cluster
one
and
the
bucket
that
it's
pointed
to
is
called
Valero
backups.
Now
this
is
the
bucket
that
actually
cluster
one
was
pointed,
and
so
the
backup
that
we
took
a
minute
ago
is
actually
stored
in
this
bucket
and
then
additionally,
I
have
a
second
backup
location,
that's
called
default,
and
so
any
new
backups
that
I
take
from
within
cluster
two
will
be
stored
in
this
backup
location.
A
But
the
important
thing
is
that,
since
we
have
a
backup
location
configured
pointing
to
cluster
ones
bucket,
we
should
be
able
to
access
the
backup
that
was
just
taken
from
cluster
one
within
this
new
cluster.
And
so,
if
I
run
a
bolero
backup
get
command
will
see
that
the
WP
backup
which
I
just
took
is
available
in
this
cluster.
For
restore
now
I'll
show
you
that
I
don't
have
any
deployments
services
or
PVCs
running
in
the
default
name
space
apart
from
the
kubernetes
service,
which
is
not
part
of
the
WordPress
application.
A
So
this
restore
should
take
just
a
couple
more
seconds
to
complete
great.
So
our
restore
is
now
complete
and
so
now
I'll
go
ahead
and
look
and
try
to
run
cube.
Ct
I'll
get
deploy
will
see
that
both
of
my
deployments
are
there
and
if
I,
look
at
PVCs,
we'll
see
that
both
of
my
PVCs
that
were
just
created
and
finally
I'll,
look
and
see
if
my
pod
leur
up
and
running
it
and
great.
A
So
we
have
a
wordpress
pod,
that's
now
running
and
that
my
sequel
pod,
that's
running
as
well,
so
I'll
set
up
the
port
forwarding
command
again
so
that
I
can
hopefully
access
the
WordPress
UI
through
my
browser,
all
right,
and
so
now
I'll
switch
back
to
the
browser.
And
if
I
refresh
this
page,
we
get
reconnected
to
skews
awesome
blog,
so
that's
great
and
if
I
scroll
down,
we
have
our
hello
world
post,
so
hello
from
cluster1.
So
this
WordPress
site
is
now
entirely
running
in
cluster
two.
A
We
backed
it
up
in
cluster
1
and
restored
it
in
the
cluster
queue,
so
that
hopefully
gives
you
an
idea
of
how
you
could
either
do
a
disaster
recovery
into
a
new
cluster
running
within
AWS
or
if
you
simply
wanted
to
migrate
a
workload
of
how
you
could
migrate
from
one
cluster
to
another.
So
that
concludes
the
demo
and
thanks
a
lot.