all right. So moving on to our data stores, we see that we've got our various be ems connected to various hosts
or registered to those host. That's probably a more accurate way to say it.
And the hosts are connected to the very storage that we, as we saw here you're the host might have several V EMS. Some might be, Ah, nice cosy, stored somewhat bien NFS. Because there
you need a distributed service's ivy motion or storage. The emotion
so shared storage might be required for certain PM's.
And then you might have other be EMS that are on the direct attach disc.
Maybe if you're running your V Center server appliance,
you could run that on a direct attach storage to give the best possible performance
if you're not planning to have it motioned to another host
so the day store itself can have different types of file systems. It could be an F S B E M f s.
Basically, you're two choices
just depends on what your requirements are and what kind of technology available.
So thinking about B. M. F s follow systems, in particular via Memphis, five is the
highest performance. Newest version. There are older
VM fast versions like Version three, for instance, which you might need to support for legacy reasons.
If you do have a V a Memphis pre file system
and you want to convert it to be a Memphis five to take advantage of some of the other features, you can do that. You could just right click the file system and say, Convert to the NFS five.
not get all of the features enabled. That V. M. F S five supports when you do that,
because the underlying structure is still the NFS three as it's allocated on the physical storage,
that presents some limitations.
So if you do have that situation, the best thing to do
is to create a new V M. F S five partition and simply copy the data from via Memphis, three to the V A Memphis five
partition. Now you'll get full advantage of all these features we see here.
Soviet Memphis five lets you have concurrent access to shared storage. What we see here, two hosts
connecting to be in that place five at the same time,
it uses a one megabyte block size,
which is useful for storing large files because Europe you're basically allocating, stored one megabyte at a time.
However, within that mega boy block,
the file system supports what's known as a sub block.
So eight kilobytes is the default. You can change these parameters, of course. The block size and the sub locks eyes,
but a smaller sub locks eyes means I can store many small.
Or I can allocate many small blocks of data within the larger block to handle
smaller files. If we didn't have this kind of technology, that would mean every time I want to store anything, I would have to allocate a megabyte of storage that will be hugely wasteful.
So the sub locks give us the ability to subdivide the big block into smaller chunks.
The Memphis I'd also supports on disk block level locking.
when a block is in use,
it's locked on the disk itself
until the file system signals that the right or the reed operation Well, we're right. Operation
has been completed, which means that the lock can be lifted from the from the block at that point, and another device or the same device can now access it again without without being locked.
So the Memphis five supported on direct attach discus. I mentioned also in Fibre Channel and I scuzzy.
lets you share your file systems at the file system level, the typical example would be an export from a UNIX or Lennox system or a Windows server.
So any time you attached to a shared drive in a window's environment that's unified. Utilizing the network file system protocol
Version three is supported currently,
and this is over your TCP epi network,
as we can see from our connection here to the manifest to are nasty.
interesting things about be Centre is that you can use storage maps
so I could go to any OF'EM. I can go to any host or a cluster, for instance,
and go the storage maps tab
how my information is connected or how my storage is conducted. I might even have,
depending on what options you pick
might also show your host,
and I can see relationships between the host and its networks, the host on its storage, the host and it's,
relationship to other hosts, for instance,
and when you when you see the storage maps feature, you'll, you'll notice a little area in the upper right corner that gives you a little check boxes that you can select or deselect
to decide what you want to display.
The last name we'll talk about
is the naming conventions for your devices.
the the storage area of your configuration, you can see the stories that you've got attached.
You'll see entries for your direct disc, your fibre channel fibre channel or Ethernet I Scotty, you manifest, for instance,
and depending on what kind of stories you're looking at, it has a different Amy convention, so you can identify. For instance, if it's
a direct attached describes scuzzy
or fibre channel. It all looks like a a scuzzy device to the host,
so your scuzzy ideas some kind of unique hex number. It will be many more digits than this. That's just a example.
The other column that you'll see in that same entry for you know ice cosy, for instance, is the canonical name.
This is a name that's persistent across reboots,
so even if you reboot the system, the economical name should remain the same relative to its ah scuzzy I D.
And we have some different naming conventions here. You've got the t 10 Siri's
or teach an organization has they're naming conventions, so it starts with T 10 and then some numbers or hacks, digits
and then the other convention is the N A A,
has its own stream of unique digits
again persistent across reboots
and in the last item is your runtime name.
It's called one time, because if you, for instance, reboot the system or you, you've moved your connections to your discs around
the canonical name and the and the scuzzy idea might be mapped to a different runtime name.
Because when the controller initialize is, it looks at all the connections that it sees on its
and does the map ings. So you've got your your host basic after h B. A. That's what we see here, right? PMH be a one. You may be a 34
and then it lists the controller
number, the target number and the blood so controlled. Zero target 013
And as you reboot your system, those things may change, but you can still access the storage
in the same fashion if if it was already mounted.
All right, So to recap, lesson one we've talked about
are different storage protocols and what capabilities they have.
We know what our storage device naming convention looks like.
And we also looked at
with a little bit of information. About what V. N. F. S five and manifest supports.
All right, that concludes Lesson one. Thank you.