[Music]
hi I'm Destin a cloud support engineer
at the Dallas AWS office customers
sometimes ask me about data protection
and recovery with Storage Gateway cached
volumes I told them that can leverage
EBS snapshots to take point in time
copies of their volumes and then use
those snapshots to recover that data at
a later time before we dig into EBS
snapshots let's go over cash flow lines
of Storage Gateway cached volumes are
ice cozy attached block storage volumes
that store data durably in a special
portion of Amazon s3 that is dedicated
to the storage gateway service cached
volume gateways also provide a fully
managed cache of hot data kept locally
on disk attached the Storage Gateway
appliance you can protect those cached
volumes by using two different features
of the AWS Storage Gateway Amazon EBS
snapshots which are stored on Amazon s3
and clones for cached volume a new
feature we added in May 2017 in this
video I'll explain when you may want to
use each of the features for data
protection and recovery I'll also go
through the steps to create snapshots of
your volumes and show how to recover
volumes based on EBS snapshots
I'll also step you through how to make
clones and perform recoveries with them
let's start with when to use EBS
snapshots of your cached volumes and
what they do
EBS snapshots provide point-in-time
copies of your volumes that will be
stored in s3 the primary reasons to use
EBS snapshots are to have specific
recovery points and also have the
flexibility to recover applications to
Amazon ec2 these snapshots can be taken
on a schedule or on-demand they can be
used for recovery or migration both
on-premises via the Gateway or in the
cloud as full EBS volumes attach to host
applications in Amazon ec2 let's get
started using these features first let's
create an EBS snapshot and use it to
create a volume let's assign it to the
AWS management console I've already done
this on land so let's go ahead and go to
the services and then storage gateway
from here let's go to volumes and let's
select the vine we'd like to make a
snapshot off I only have one so let's
just select this one I'm here we're
going to go to actions I were to create
an ABS snapshot
I'm gonna go ahead and get a description
from here we're gonna create after the
snapshot is triggered and does assigned
an ID and it becomes visible on the
console and AWS command-line interface
immediately however it initially has a
pending status when all data written to
the volume prior to the snapshot request
has been uploaded from the Gateway and
into ApS the status changes to available
naturally the time this takes varies
with the size of the volume after the
snapshot status is available you can use
the snapshot as the base for a new
gateway or EBS volume a common question
customers have is how do I know what
data is in my snapshot the answer is
that a snapshot represents a point in
time copy of the volume at the time the
snapshot is requested the snapshot
contains all of the information needed
to restore your data to a new volume
from the time you requested the snapshot
to be taken data that was written to the
volume by your application prior to
taking a snapshot is included in the
snapshot even if that data has not been
uploaded to AWS if you want to keep
snapshots on a regular basis you can use
a snapshot schedule to do this you
select the volume that you would like to
use you go to actions and then you go to
edit snapshot schedule from here you'll
choose the start time I'm gonna leave
this default and you can also choose the
recurrence time I'm going to set this to
every 24 hours I'm gonna go ahead and
save it from here snapshots will be
taken every 24 hours on this schedule if
for example the application using the
volume had an error and went down or a
network problem took the Gateway offline
you could recover by using one of these
point in time snapshots or if you want
to create a new volume based on a
snapshot say for application testing let
me show you how to do that to create a
new volume from a snapshot for access
via the Storage Gateway first you have
to get the snapshot ID to get the
snapshot ID go to the volume select the
volume and then look under EBS snapshots
select that snapshot this will take you
to the ec2 dashboard where the snapshots
are listed let's go ahead and copy down
a snapshot ID for the snapshot we want
to restore I'm gonna go ahead and
highlight this one since this is the
only one we have now let's go ahead and
create a volume based on that snapshot
let's go back to the Storage Gateway tab
that we have open
from here we're going to select volumes
and then we're gonna go to create volume
choose the Gateway that you'd like to
create the new volume on you can recover
it to an existing gateway or you could
recover to a different or new gateway if
for example your original gateway is
unavailable or offline in this case I'm
going to select my Blaine Gateway go
ahead and enter the capacity for the new
volume the capacity for the new volume
can't be smaller than the size of the
snapshot from which you are recovering
because of that I'm going to go ahead
and select 120 because I'd actually like
to make it a little bit larger the
original volume was 100 G IB next in the
volume contents select based on EBS
snapshot then we'll enter that snapshot
we copied earlier into the snapshot ID
field from here we'll need to give the
volume a unique name my original name
was volume 1 so I'm going to call this
volume 2 from here we're going to go
ahead and create volume I don't need to
chap configuration so I'll go ahead and
skip this for now the surface will now
restore that EBS snapshot to a live
gateway cached volume after this process
is completed your new volume is
available on your specified gateway and
you can then attach or mount it to your
host application now let's move on to
creating a volume on EBS from a snapshot
for recovery to recover a volume on
Amazon EBS you mount the specific EBS
snapshot as a full EBS volume let's walk
through doing this from the console from
here let's go ahead and go to the ec2
console so we're going to go to services
and then ec2
we'll need to make sure that we have the
correct region selected at the top right
we did create the the snapshot no hon so
that's good if you need to restore the
snapshot to a volume in a different
region you can copy your snapshot to the
new region and then restore it to a
volume in that region for now we're just
going to create a volume in this region
so let's go ahead and select volumes now
let's go to create volume in the create
volume dialog box for volume type choose
either general purpose SSD provisioned
IAP sess SD or magnetic in my case I'm
going to choose gp2 for snapshot let's
go ahead and select the snapshot we made
previously in my case I'm just gonna
type volume one because I included that
in the description of the snapshot from
here when I go ahead and select my
snapshot it's gonna fill in the snapshot
ID for me for size enter a new size for
the volume in gigabytes or verify that
the default size of the snapshot is
adequate in my case I want to make it a
little bit larger so I'm going to choose
120 if you specify both a volume size
and a snapshot ID the size must be equal
to or greater than the snapshot size for
io1 volumes in the high-ups field you
also enter the maximum number of
input/output operations per second that
the volume can support and the
availability zone list select the
availability zone in which to create the
volume EBS volumes can only be attached
to ec2 instances within the same
availability zone in my case I used
availability zone a so I don't need to
change any details here but I could need
to change it if my instance was in a
different zone okay from here we're
going to go ahead and create the volume
an important note if you restored a
snapshot to a larger volume size than
the default for that snapshot you need
to extend the filesystem on the volume
to take advantage of that extra space
after you've restored a volume from a
snapshot you can attach it to an
instance to begin using it now let's
look at how you can make a clone of a
volume from the most recent recovery
point a volume recovery point is the
most recent point in time when all the
volume data is consistent there are two
primary reasons you would recover
not a new volume using a volume clone
first using clones does not require the
prior creation and storage of EBS
snapshots second for recovery purposes
it is often faster to create and access
the clone because the Storage Gateway
service presents the new volume
instantly and then copies the data from
the initial volume in the background it
is important to note though that for
maintaining specific prior points in
time for recoveries or to recover
directly to an EBS volume EBS snapshots
are the best approach
alright so to make a clone of a volume
let's first go to services and then
Storage Gateway we're gonna go back to
the screen where we created the volume
instead of choosing based on EBS
snapshot choose clone from latest
recovery point then on the source volume
tab choose the volume you want to clone
I'm going to select the first one here
give it a nice fuzzy name this name
needs to be unique I'm gonna call it
volume 3 since I already have volume 1
and volume 2 let's also select the
capacity here I don't need it to be too
much larger but I'm gonna go and just
make it 150 so let's go ahead and create
a volume
I don't need Champs I'm gonna skip this
for now but this would let me
authenticate against that volume from
here let's take a peek at the volumes on
the left we can see that that new volume
is available and ready to be used
thanks for watching and happy cloud
computing from all of us here at AWS
[Music]
you
[Music]