1
00:00:07,040 --> 00:00:09,390
- All right, so now let's review a demo

2
00:00:09,390 --> 00:00:12,293
of creating a snapshot of an EBS volume.

3
00:00:13,690 --> 00:00:16,950
From the EC2 dashboards,
before we take a look

4
00:00:16,950 --> 00:00:20,250
at our volumes, we can
notice here in the summary

5
00:00:20,250 --> 00:00:22,760
that, of course, we have five volumes.

6
00:00:22,760 --> 00:00:26,270
We know that some of
those are root volumes

7
00:00:26,270 --> 00:00:29,850
and two of those are volumes
that we created for data,

8
00:00:29,850 --> 00:00:33,080
and we currently have no snapshots.

9
00:00:33,080 --> 00:00:35,986
So, let's go to our volumes and again,

10
00:00:35,986 --> 00:00:40,230
here's the 400 gig volume that
we added to our Linux machine

11
00:00:40,230 --> 00:00:44,720
and the 100 gig volume that we
added to our Windows machine

12
00:00:44,720 --> 00:00:48,180
and so, taking a snapshot
is really just a matter of

13
00:00:48,180 --> 00:00:50,470
going here and saying create snapshot.

14
00:00:50,470 --> 00:00:54,180
Now, it is a good idea
to quiesce that disk

15
00:00:54,180 --> 00:00:56,760
from the operating system point of view.

16
00:00:56,760 --> 00:00:59,630
So, if you had a database

17
00:00:59,630 --> 00:01:01,590
or some type of an application running

18
00:01:01,590 --> 00:01:03,270
that was performing writes,

19
00:01:03,270 --> 00:01:06,490
then you would probably
want to pause those writes,

20
00:01:06,490 --> 00:01:08,310
initiate the snapshot

21
00:01:08,310 --> 00:01:11,660
and then you could
continue with your writes.

22
00:01:11,660 --> 00:01:16,010
And so we'll go ahead
and say create snapshot

23
00:01:16,010 --> 00:01:19,320
and then we'll call
this one, we could use,

24
00:01:19,320 --> 00:01:23,650
we could say data-backup, whatever,

25
00:01:23,650 --> 00:01:25,760
some kind of a description
that helps you understand

26
00:01:25,760 --> 00:01:28,650
and of course the date and
time that it was created

27
00:01:28,650 --> 00:01:30,740
will already be recorded for you.

28
00:01:30,740 --> 00:01:33,138
You don't necessarily
need that in the name.

29
00:01:33,138 --> 00:01:38,113
Again, tags, right, environment,
those kinds of things.

30
00:01:39,930 --> 00:01:43,780
And what kind, you might want to add tags

31
00:01:43,780 --> 00:01:48,780
that describe the data
that is on here, right.

32
00:01:49,430 --> 00:01:51,440
Does it belong to a particular database

33
00:01:51,440 --> 00:01:53,230
or a particular application,

34
00:01:53,230 --> 00:01:56,380
for a particular team or project or so on?

35
00:01:56,380 --> 00:01:58,910
And then we'll go ahead
and say create snapshot

36
00:01:58,910 --> 00:02:02,410
and then of course, whatever
data was on that device

37
00:02:02,410 --> 00:02:04,690
at the time we clicked that button,

38
00:02:04,690 --> 00:02:07,520
that's what will be a
part of the snapshot.

39
00:02:07,520 --> 00:02:10,210
So if we go back here to that,

40
00:02:10,210 --> 00:02:12,703
now if we go over to snapshots,

41
00:02:14,330 --> 00:02:17,130
you'll see that it's currently pending

42
00:02:17,130 --> 00:02:22,130
and any data that is being
written to that volume now

43
00:02:22,930 --> 00:02:24,970
will not be a part of the snapshot.

44
00:02:24,970 --> 00:02:26,510
Only data that was written

45
00:02:27,460 --> 00:02:30,530
at the time we initiate the snapshot

46
00:02:30,530 --> 00:02:34,520
will be included in the snapshot, right.

47
00:02:34,520 --> 00:02:36,640
And of course, there
really is no data here,

48
00:02:36,640 --> 00:02:38,540
so it really shouldn't take that long.

49
00:02:40,245 --> 00:02:42,880
And so you can see here the progress

50
00:02:42,880 --> 00:02:46,000
and you can keep an eye
out on the status up here

51
00:02:46,000 --> 00:02:47,350
and you can always hit this little button.

52
00:02:47,350 --> 00:02:49,280
You don't need to necessarily refresh

53
00:02:49,280 --> 00:02:52,610
the entire browser window.

54
00:02:52,610 --> 00:02:55,900
Most AWS consoles give you
this little refresh button

55
00:02:55,900 --> 00:03:00,900
up here that does a better
job of refreshing the console.

56
00:03:01,560 --> 00:03:05,733
So, there you go, the
snapshot is now completed.

57
00:03:06,670 --> 00:03:10,230
Progress 100% and, of course,

58
00:03:10,230 --> 00:03:11,970
we hadn't written any data to it,

59
00:03:11,970 --> 00:03:14,190
but if in a real world scenario,

60
00:03:14,190 --> 00:03:18,310
if we had written data
to that, then from here,

61
00:03:18,310 --> 00:03:21,780
we could say, well, let's create a volume,

62
00:03:21,780 --> 00:03:26,780
and by creating a volume in
this way, from the snapshots,

63
00:03:26,830 --> 00:03:30,320
then that will create a
volume from that snapshot.

64
00:03:30,320 --> 00:03:34,460
All of the data on that
snapshot will then be available

65
00:03:34,460 --> 00:03:37,583
on the EBS volume that
was created from it.

66
00:03:38,540 --> 00:03:41,550
And again, just as a
reminder, this snapshot now,

67
00:03:41,550 --> 00:03:44,710
whatever data is a part of this snapshot,

68
00:03:44,710 --> 00:03:48,220
we know is stored in S3.

69
00:03:48,220 --> 00:03:50,560
We don't necessarily have access directly

70
00:03:50,560 --> 00:03:55,160
to that area of S3 storage,
but we do know that the data,

71
00:03:55,160 --> 00:03:57,840
all of the data that was a part
of this particular snapshot

72
00:03:57,840 --> 00:04:01,210
is stored in S3, so we
gain a much higher degree

73
00:04:01,210 --> 00:04:03,200
of durability in that data.

74
00:04:03,200 --> 00:04:05,890
And so, pretty simple, right?

75
00:04:05,890 --> 00:04:08,370
Not a whole lot to do other
than select your volume

76
00:04:08,370 --> 00:04:09,883
and create a snapshot.