WEBVTT
1
[Link].107 --> [Link].030
In this video, we will discuss Block Storage
2
[Link].030 --> [Link].820
and how it compares to File Storage in the Cloud.
3
[Link].820 --> [Link].780
Block storage breaks files
into chunks (or blocks) of data
4
[Link].780 --> [Link].320
and Stores each block separately under a unique address.
5
[Link].325 --> [Link].360
Like direct attached storage and file storage,
block storage also must be attached to a compute
6
[Link].360 --> [Link].890
node before it can be utilized for your workloads.
7
[Link].890 --> [Link].460
Block storage, like file storage, can be mounted
from remote storage appliances, making it
8
[Link].468 --> [Link].880
extremely resilient to failure, and keeping
data far more secure in them, on account of
9
[Link].880 --> [Link].310
encryption in transit, and encryption at rest
services, available on these appliances.
10
[Link].314 --> [Link].980
Block storage is mounted as a volume to compute
nodes using a dedicated network of fibers,
11
[Link].980 --> [Link].580
through which signals move at the speed of
light.
12
[Link].588 --> [Link].660
These fiber optic networks are more expensive
to build than the ethernet ones which deliver
13
[Link].660 --> [Link].880
File Storage, which is one reason why Block
Storage tends to have a higher price-point.
14
[Link].880 --> [Link].400
However, since the traffic is moving faster
and with speed consistency, they are perfect
15
[Link].400 --> [Link].000
for workloads that need low-latency storage
to work effectively.
16
[Link].000 --> [Link].400
In terms of workloads, it is important to
note that unlike File Storage, which can be
17
[Link].400 --> [Link].040
mounted onto 80 compute nodes or more, Block
Storage is normally mounted onto only one
18
[Link].040 --> [Link].300
compute node at a time.
19
[Link].300 --> [Link].640
Since these disks run at a consistent high
speed, they are perfect for workloads that
20
[Link].640 --> [Link].720
need consistently fast storage, such as databases
and mail servers.
21
[Link].720 --> [Link].760
Block storage is not suitable for workloads
where there needs to be some level of disk
22
[Link].760 --> [Link].620
sharing between compute nodes.
23
[Link].620 --> [Link].860
For block storage, as it is for file storage,
you need to take the IOPS capacity of the
24
[Link].860 --> [Link].060
storage into account.
25
[Link].060 --> [Link].480
Most cloud providers will allow you to specify
IOPS characteristics when you provision storage
26
[Link].480 --> [Link].360
and, in some cases, adjust the IOPS of your
storage as you need, so if the requirements
27
[Link].360 --> [Link].220
or usage behaviour of an application changes,
you can adjust accordingly.
28
[Link].220 --> [Link].220
So, to summarise the commonalities and differences
between these two storage types:
29
[Link].220 --> [Link].680
Block and File Storage is taken from appliances
which are maintained by the service provider.
30
[Link].680 --> [Link].680
Both are normally highly available and resilient
and will often include data encryption at
31
[Link].680 --> [Link].240
rest and in transit.
32
[Link].240 --> [Link].180
File storage is attached to a compute node
using an ethernet network, so it is sometimes
33
[Link].180 --> [Link].590
called Network attached or NFS Storage.
34
[Link].594 --> [Link].920
File storage is very reliable, but the speed
of the connecting network can vary, based on load.
35
[Link].925 --> [Link].500
Block storage is attached via a high-speed fiber
network, which is very reliable and consistent.
36
[Link].500 --> [Link].520
File storage can be attached to multiple compute
nodes at once.
37
[Link].520 --> [Link].180
Block storage can only be attached to one
node at a time.
38
[Link].180 --> [Link].880
File storage is a good choice where file shares
are required, where workloads do not require
39
[Link].880 --> [Link].560
lightning fast connectivity to storage, or
where cost is a factor.
40
[Link].560 --> [Link].680
Block storage is a good choice when supporting
an application that needs consistent fast
41
[Link].680 --> [Link].450
access to disk, such as databases.
42
[Link].451 --> [Link].280
Remember to consider the IOPS requirements
of the application when provisioning either
43
[Link].280 --> [Link].280
file or block storage.
44
[Link].285 --> [Link].180
Hey guys, my name is Amy Blea.
45
[Link].180 --> [Link].060
I'm on the offering team here with IBM cloud and today
46
[Link].060 --> [Link].850
I want to talk to you about some traditional
types of storage: file and block storage.
47
[Link].851 --> [Link].380
Kind of give you an overview of what they are
48
[Link].380 --> [Link].350
and then give you some tips on how to decide
when to use one over the other.
49
[Link].350 --> [Link].020
So, let's get started with block storage.
50
[Link].028 --> [Link].040
Block storage is storage where data is
written in raw blocks on the storage and it's
51
[Link].040 --> [Link].910
accessed by the servers that you
have through a storage area network.
52
[Link].914 --> [Link].240
So, you have all of your servers, they can
either be on the same network with each other or
53
[Link].240 --> [Link].390
a different network but they all connect through
the storage, through this storage area network.
54
[Link].390 --> [Link].810
Now, some of the advantages of using
block storage is that block storage
55
[Link].810 --> [Link].000
provides the lowest possible
latency for your applications,
56
[Link].000 --> [Link].770
and you can also use it for those applications
that require high performance or lots of IOPS.
57
[Link].770 --> [Link].730
Another thing you'll find with block storage
is that, in general, it is highly redundant.
58
[Link].731 --> [Link].840
Most block storage services provide
a capability that's built-in,
59
[Link].840 --> [Link].550
where your data is redundant across the volume, so that if,
60
[Link].558 --> [Link].280
so there should be
either a volume should go down
61
[Link].280 --> [Link].730
or a disk should go away and
you can recover your data
62
[Link].730 --> [Link].120
from another place without having any
kind of impact to your application.
63
[Link].820 --> [Link].180
Now, file storage is connected to your service
a little differently than block storage is.
64
[Link].180 --> [Link].290
Everything is connected on the same network so you
have all of your files or your file share here.
65
[Link].620 --> [Link].100
Those are all the files and they
can all be accessed on the same network
66
[Link].108 --> [Link].200
by any of the servers on that network.
67
[Link].200 --> [Link].620
So, it's network attached storage.
68
[Link].622 --> [Link].350
File storage is highly scalable so you can have
multiple file shares on your network
69
[Link].350 --> [Link].300
and have all of
your servers attached to that at one time.
70
[Link].308 --> [Link].140
It's accessible to multiple runtimes.
71
[Link].140 --> [Link].250
So, here in this illustration,
we have a single file share that
72
[Link].251 --> [Link].600
has multiple servers accessing it all at once,
73
[Link].600 --> [Link].500
and you can also have multiple simultaneous
reads and writes going to your file share all
74
[Link].500 --> [Link].870
at one time without having to worry
about your data being overwritten.
75
[Link].180 --> [Link].830
So, how do you know when is the
right time to choose
76
[Link].830 --> [Link].770
either block storage or file storage
for your application?
77
[Link].770 --> [Link].140
Well, first of all, you need to
think about what you're using it for.
78
[Link].148 --> [Link].660
So, for example, let's say you have
a VMware configuration where you have
79
[Link].660 --> [Link].420
multiple virtual servers with VMware
on them and you need boot volumes.
80
[Link].420 --> [Link].750
Well, in that case, you would use block storage.
81
[Link].080 --> [Link].380
If you have workloads such as transactional
databases or relational databases that require
82
[Link].380 --> [Link].620
very low latency and high performance,
you would choose block storage
83
[Link].200 --> [Link].400
In situations where you have a mix of
the structured and unstructured data,
84
[Link].405 --> [Link].410
for example, a web hosting server
where you have both, you know,
85
[Link].410 --> [Link].110
text files as well as media files,
then you would choose file storage.
86
[Link].800 --> [Link].610
And then, if you have a collaborative
space where you need to have multiple
87
[Link].611 --> [Link].400
users accessing it all at one time,
working together, doing, you know,
88
[Link].400 --> [Link].150
reads and writes all at the same
time, you would choose file storage.
89
[Link].860 --> [Link].180
So, like I mentioned in the beginning,
90
[Link].180 --> [Link].560
block and file storage are very
traditional types of storage.
91
[Link].560 --> [Link].330
They're not as flashy and shiny and
exciting as some of the new
92
[Link].330 --> [Link].380
storage services that have entered the market,
93
[Link].388 --> [Link].840
but they are still very relevant and useful
94
[Link].840 --> [Link].450
for the different types of workloads that you
have, whether it's on premise or in the cloud.
95
[Link].450 --> [Link].010
Thanks for checking out this video on the differences
between file and block storage with me today.
96
[Link].010 --> [Link].960
If you have any questions or comments or ideas
for other videos, just put something in the
97
[Link].960 --> [Link].610
comments below and then if you'd like to see
more videos like this in the future subscribe.
98
[Link].610 --> [Link].500
In the next video, we'll start
to look at Object Storage.
