WEBVTT

00:00.000 --> 00:01.560
>> In our next section,
we're going to

00:01.560 --> 00:03.555
take a look at network storage.

00:03.555 --> 00:06.180
Big reason that we network
is because we have

00:06.180 --> 00:08.700
data and information
that we want to share.

00:08.700 --> 00:11.430
There are lots of different
ways that we share data.

00:11.430 --> 00:14.280
Traditionally, we've had a
file servers on our network.

00:14.280 --> 00:17.040
Those are basic computer
systems that we've had

00:17.040 --> 00:18.240
the sole purpose of storing

00:18.240 --> 00:20.895
files and serving those files.

00:20.895 --> 00:23.235
But now as we move forward,

00:23.235 --> 00:25.080
we find that we have
so much information

00:25.080 --> 00:26.685
that we're managing
today that we've

00:26.685 --> 00:29.190
really outgrown the
typical hard drive

00:29.190 --> 00:31.920
on the file server and
we need something more,

00:31.920 --> 00:34.620
so we have network
attached storage.

00:34.620 --> 00:36.420
This is one method of increasing

00:36.420 --> 00:38.360
your storage space
on the network.

00:38.360 --> 00:41.260
Basically, this is just
a storage of clients.

00:41.260 --> 00:44.135
It's just like a hard drive
on steroids, if you will.

00:44.135 --> 00:47.420
It's going to provide file
level storage and it's

00:47.420 --> 00:50.705
accessible on the network
using some network protocols.

00:50.705 --> 00:53.120
Specifically, things like SMB,

00:53.120 --> 00:55.400
which stands for Server
Messaging Blocks,

00:55.400 --> 00:59.260
and NFS, which is
Network Filing System.

00:59.260 --> 01:01.310
Those are some protocols
that would allow

01:01.310 --> 01:04.550
the access of those
particular files.

01:04.550 --> 01:06.680
An alternative to network

01:06.680 --> 01:10.020
attached storage is to have
a Storage Area Network.

01:10.020 --> 01:14.045
See you've got a NAS
and you've got a SAN.

01:14.045 --> 01:15.590
But with SAN,

01:15.590 --> 01:17.750
you have a specific
network designated to

01:17.750 --> 01:20.840
store data and you're
accessing that data,

01:20.840 --> 01:23.780
usually across a high
speed connection.

01:23.780 --> 01:25.505
You've got the host layer,

01:25.505 --> 01:28.460
which are the individual
systems on your network PCs,

01:28.460 --> 01:30.950
the systems that have
the data to store.

01:30.950 --> 01:33.215
Then you have what's
called the fabric layer,

01:33.215 --> 01:36.595
which is the media across
which the data travels.

01:36.595 --> 01:38.750
Then you have the storage layer,

01:38.750 --> 01:40.550
which is whatever
your storage devices

01:40.550 --> 01:43.050
are in that specific network.

01:43.450 --> 01:46.295
How do we connect to the SAN?

01:46.295 --> 01:47.720
Well, it has to be

01:47.720 --> 01:50.620
high speed connectivity
of some form or fashion.

01:50.620 --> 01:53.805
There's something called a
Fiber Channel over Ethernet.

01:53.805 --> 01:57.155
That ultimately is going to
use fiber channel switches.

01:57.155 --> 01:59.660
That's specifically a
Layer 3 switch that's

01:59.660 --> 02:02.510
compatible within a fiber
channel environment.

02:02.510 --> 02:05.330
Ultimately, what we're
looking at in this section

02:05.330 --> 02:07.205
is a pretty high speed solution

02:07.205 --> 02:09.020
when looking at a fiber channel.

02:09.020 --> 02:11.000
It's about 1,010 gigabits per

02:11.000 --> 02:14.350
second and we're seeing
even more of that today.

02:14.350 --> 02:16.535
You can see some
of these elements

02:16.535 --> 02:18.320
or we've had the
initiator connecting

02:18.320 --> 02:19.700
through the switch to the actual

02:19.700 --> 02:22.890
storage area network
on the backend.

02:23.950 --> 02:26.840
There's also an
alternative to connect to

02:26.840 --> 02:30.290
a storage area network
across an iSCSI environment.

02:30.290 --> 02:32.510
Back in the day, we
used to talk a lot

02:32.510 --> 02:34.570
about iSCSI hard drives,

02:34.570 --> 02:36.665
small computer
systems interface.

02:36.665 --> 02:40.350
In our servers, we would
have iSCSI devices

02:40.350 --> 02:43.400
>> because iSCSI provided
faster access and there was

02:43.400 --> 02:46.775
>> a lot more functionality
with the iSCSI system.

02:46.775 --> 02:50.005
Now what we're doing is
taking an extension of that.

02:50.005 --> 02:52.730
The benefit of a iSCSI
environment is you'll

02:52.730 --> 02:55.715
notice I'm not using anything
with a fiber channel.

02:55.715 --> 02:57.605
I'm able to take
advantage and to

02:57.605 --> 03:00.640
leverage my existing
network infrastructure.

03:00.640 --> 03:02.690
Where I'm storing my data is on

03:02.690 --> 03:05.480
the backend on my
iSCSI target area.

03:05.480 --> 03:07.220
We refer to those spaces or

03:07.220 --> 03:10.610
specific storage locations
biological unit number.

03:10.610 --> 03:13.490
Ultimately, that's a
pointer that points

03:13.490 --> 03:16.550
to a specific location
on the SAN network.

03:16.550 --> 03:20.030
We do that to obfuscate
to someone on the outside

03:20.030 --> 03:22.549
>> where specifically the
data is being stored,

03:22.549 --> 03:26.150
>> so that LUN is used to
prevent too much information

03:26.150 --> 03:29.160
>> being disclosed
and being available.

03:29.539 --> 03:32.270
>> Now, InfiniBand is

03:32.270 --> 03:34.790
a relatively new
communication standard.

03:34.790 --> 03:37.460
This is for very high
performance environments

03:37.460 --> 03:39.890
where we want next
to no latency.

03:39.890 --> 03:41.810
Ultimately, this is going to be

03:41.810 --> 03:43.640
in a specific switch network.

03:43.640 --> 03:45.020
This can be connected to

03:45.020 --> 03:47.765
a SAN to provide
even greater speed.

03:47.765 --> 03:51.110
This is just one of
those new technologies.

03:51.110 --> 03:53.795
Also to connect to SAN,

03:53.795 --> 03:56.390
we might be using the
idea of jumbo frames,

03:56.390 --> 03:58.220
which means we have
an environment where

03:58.220 --> 03:59.510
some more information can be

03:59.510 --> 04:01.535
combined into a single frame.

04:01.535 --> 04:03.275
That means we'll get

04:03.275 --> 04:05.840
much better performance
rather than having lots of

04:05.840 --> 04:07.280
little frames and being able to

04:07.280 --> 04:10.710
transmit more information
in a single frame.

04:10.870 --> 04:14.090
Just to wrap up with
network storage,

04:14.090 --> 04:16.280
network attached storage devices

04:16.280 --> 04:18.170
are storage appliances
on the network,

04:18.170 --> 04:21.559
>> whereas a storage
area network is offsite

04:21.559 --> 04:23.420
>> or at least on a
segmented network

04:23.420 --> 04:24.950
that you can access
either through

04:24.950 --> 04:28.945
Fiber Channel over Ethernet
or iSCSI technology.

04:28.945 --> 04:31.610
InfiniBand can also
be a solution for

04:31.610 --> 04:34.190
high-speed access for
storage area networks.

04:34.190 --> 04:35.840
Another means of providing

04:35.840 --> 04:39.540
quick access is through
the use of jumbo frames.