1
00:00:06,830 --> 00:00:08,278
- Now let's review a demo

2
00:00:08,278 --> 00:00:12,396
of creating a snapshot within Amazon EBS.

3
00:00:12,396 --> 00:00:15,684
From the AWS console dashboard,

4
00:00:15,684 --> 00:00:17,767
I'm gonna go back to EC2.

5
00:00:19,492 --> 00:00:23,311
I'm gonna go back to my list of volumes.

6
00:00:23,311 --> 00:00:26,811
Can see we have several data volumes here.

7
00:00:30,003 --> 00:00:33,682
So from this volume, it
could be a 100 gig volume,

8
00:00:33,682 --> 00:00:37,384
but perhaps we only have
10 gigs of storage on it.

9
00:00:37,384 --> 00:00:39,099
Doesn't really matter.

10
00:00:39,099 --> 00:00:40,913
One thing that we should keep in mind

11
00:00:40,913 --> 00:00:44,503
is that if we are making regular snapshots

12
00:00:44,503 --> 00:00:47,357
of our volumes for the sake of durability,

13
00:00:47,357 --> 00:00:49,610
for the sake of backing up that data,

14
00:00:49,610 --> 00:00:52,587
we should take these snapshots

15
00:00:52,587 --> 00:00:55,464
with no more than 20 gigs of dirty data,

16
00:00:55,464 --> 00:00:57,772
meaning that if we wait too long

17
00:00:57,772 --> 00:01:01,465
and enough data has changed
so that the snapshot

18
00:01:01,465 --> 00:01:05,101
causes 20 gigs of data to be backed up,

19
00:01:05,101 --> 00:01:08,125
then we can see a performance hit

20
00:01:08,125 --> 00:01:10,538
while the snapshot is in place.

21
00:01:10,538 --> 00:01:14,163
So creating a snapshot is really easy.

22
00:01:14,163 --> 00:01:17,738
We just highlight the volume
that we want to snapshot.

23
00:01:17,738 --> 00:01:21,340
Go to Actions, and Create Snapshot.

24
00:01:21,340 --> 00:01:24,173
From here, I might put the date or

25
00:01:25,145 --> 00:01:27,812
I'm just gonna call this one AWS

26
00:01:29,129 --> 00:01:30,046
livelessons

27
00:01:31,898 --> 00:01:32,731
backup.

28
00:01:35,626 --> 00:01:36,901
And we also need a description.

29
00:01:36,901 --> 00:01:39,429
A lot of times, I just
use the name over again.

30
00:01:39,429 --> 00:01:42,008
And then once we have the
name in the description,

31
00:01:42,008 --> 00:01:46,175
we can hit Create, and the
snapshot creation has started.

32
00:01:47,263 --> 00:01:49,845
So that means that this volume

33
00:01:49,845 --> 00:01:53,689
is in the process of creating a snapshot.

34
00:01:53,689 --> 00:01:56,680
So if we go over here to the snapshots,

35
00:01:56,680 --> 00:02:00,014
we can see that this one
has already completed.

36
00:02:00,014 --> 00:02:01,284
That's because we don't really have

37
00:02:01,284 --> 00:02:03,846
a whole lot of data on
there, didn't take very long.

38
00:02:03,846 --> 00:02:07,980
But if we had this volume with
upwards of 20 gigs or more

39
00:02:07,980 --> 00:02:10,449
worth of data, then it
would've taken a bit longer

40
00:02:10,449 --> 00:02:13,064
for that snapshot to complete.

41
00:02:13,064 --> 00:02:15,743
So this is just one way
to create a snapshot

42
00:02:15,743 --> 00:02:17,826
here through the console.

43
00:02:18,724 --> 00:02:21,827
The other ways would be to
leverage the command line tools

44
00:02:21,827 --> 00:02:25,494
or the Amazon SDK and
do it programatically.

45
00:02:26,769 --> 00:02:28,403
So it's a very common practice

46
00:02:28,403 --> 00:02:31,463
to write scripts that leverage those tools

47
00:02:31,463 --> 00:02:33,736
that automatically do these backups

48
00:02:33,736 --> 00:02:36,319
at a prescribed period of time.

49
00:02:37,176 --> 00:02:39,926
So now that we have our snapshot,

50
00:02:40,863 --> 00:02:43,238
from here we could do a number of things.

51
00:02:43,238 --> 00:02:45,095
We could Copy that snapshot

52
00:02:45,095 --> 00:02:47,350
to another region if we wanted to.

53
00:02:47,350 --> 00:02:49,039
You can see here it's in Ohio,

54
00:02:49,039 --> 00:02:51,926
but we might want to copy
that to some other region,

55
00:02:51,926 --> 00:02:54,347
any other region around the globe

56
00:02:54,347 --> 00:02:57,775
and give some geographical
diversity to our data

57
00:02:57,775 --> 00:02:59,638
if we wanted to.

58
00:02:59,638 --> 00:03:02,138
We could also create a volume.

59
00:03:04,025 --> 00:03:05,195
You can see here,

60
00:03:05,195 --> 00:03:09,017
we can recreate another EBS
volume from that snapshot

61
00:03:09,017 --> 00:03:13,100
and put that volume in
another availability zone.

62
00:03:15,121 --> 00:03:16,861
Or the same availability zone.

63
00:03:16,861 --> 00:03:18,848
That's up to us depending
on whatever it is

64
00:03:18,848 --> 00:03:22,002
that we're trying to achieve.

65
00:03:22,002 --> 00:03:25,107
So that is creating snapshots

66
00:03:25,107 --> 00:03:27,053
from existing EBS volumes

67
00:03:27,053 --> 00:03:28,303
in Amazon EC2.