Original subtitles

Fisher currently has seven options for where we can place virtual machines and other necessary files

The first four options are referred to as Block Level meaning that the esxi host has direct access to

Either the device or the one and then it's formatted with a VMS file system

The first option direct-attached storage is the distant exist inside of the esxi host

Next two options fibre Channel and fibre Channel over ethernet mean that we have an array on a fiber channel say

And then we're either connected to it directly through an HPA in the case of fiber channel or we're connected to

Which through an ethernet switch in the case of fiber channel over ethernet

1/4 Block Level option is ice Guzzi ice cuz he uses our IP network and our IP interface

To communicate with the storage array

The next option NFS is slightly different than our Block Level options in that the underlying operating system tutor

Herman's the format of the file system

McKay's of Windows it'll typically be NTFS in the case of Lennox it will usually be either ext4 or ZF

Our final two options vsan in Virtual volumes are relatively new and they're what's referred to as software-defined storage

Meaning that we have more control inside of vcenter server as far as how we utilize our storage

In this lab environment we're going to be using vsan and NFS

Recent stories takes the discs that exist on our esxi host pulls them together and uses them to create a shared.

They're two different types of discs that need to exist on at least three of the esxi host in our cluster

The first is a capacity disc and will typically have more than one capacity disc

This is used for the storing of the virtual machine can either be hard drives or SS

Besties

The second disc is used for cashing in this always has to be in SSD

Knox take a look at our storage configuration inside of the web client

Our first screen under storage configuration is our storage adapters this will show our local ad

Raptors as well as any fiber channel or Hardware iSCSI adapters that we have

I can also creates a Sakurai scuzzy adapter or a software fiber channel over ethernet adapter by clicking on the Green

Plus

For more information on creating a soft rice cuz he adopt from the lab environment see my up and running on Bistro six course

Our second screen is our storage devices

Initials all of the devices in lawns that are currently visible to this esxi host

We have our local disk where esxi is installed

We have our CD-ROM drive

And then we have a 20 gig disc and a 4 gig disc these are the ones that are used to create RV sand datastore

Arthur screen is data stores and this is going to show any data source that this esxi host currently has access to

The moment we have the vsan datastore that was created as part of our scripted installation

For more information about vsphere storage CR configuring and administering Advanced feature storage course

Now let's take a look into our vsan configuration

The recent configuration is done at the cluster level

Select select are

Vsan cluster

And then we'll go to the general screen

This shows that I have vsan turn on

Under the next screen I can go to Disk Management and this shows all of the esxi host in the cluster and the disc group that they have

Have created

Select one of these discs groups I'll see that there's two discs inside of it

There is my 20 gauge capacity disc

As well as my 4gig cash disc

I can see the same thing for each esxi host

All of that is pulled together to create the storage where I can place virtual machine

As I mentioned software-defined storage gives us finer grind control over how we consumer storage

And that's done through storage policies

The next thing that I need to do is create a storage policy

To do this I go to home

Policies and profiles

MBM storage policies

Now we have one vsan storage policy already created this is the default so it's take a look at this one first

Click on edit settings

Wednesday the name and description

And then the ruleset

This ruleset specifies that we can tolerate one host failing

Which means that

The virtual machine needs to be stored on at least two hosts

Notice the consumption model over here on the side says if this virtual disk is consuming a hundred gig

The actual storage space is going to be 200 gig

The second line in here is the number of districts per object I could set this higher meaning that this virtue

The machine would be stored on more than one disc

Her esxi host

In a striped fashion meaning it doesn't consume any more capacity

But we're going to get higher speed because it's coming from two separate discs

It does require however that I have more than one disc in my environment I don't

The third option under the rule set is force provisioning

This means that will provision the virtual machine even if the storage can't meet our requirements that set to know meaning Venom

Muscle storage can meet our requirements are not going to provision a virtual machine

Next option here is object space reservation

And this is going to be roughly equivalent to thin vs. thick if I set it at zero we're not going to

Reserve any of the space up front that would be the equivalent of sin

If I were to set this to 100%

We would reserve the entire capacity for the disc

And that would be the equivalent of thick provisioning notice I can also go anywhere in the middle and I can reserve

The capacity for the desktop front if I wanted

The final option here is Flash read cash reservation indicating how much of the recast that I want to reserve

For this particular virtual machine

There are additional rules that I can add

About fault-tolerance method Ops limits an object checksums

Smells create our own rule set

Go to create VM storage policy

And I'm going to call this one host

Storage policy

Click on next

The first thing that I can specifier, rules

These are going to apply no matter where we're storing the disc

And you can see that my options here I can specify encryption or storage IO control

I'm not going to use either of those for this policy

Next I can select ruleset one

And here also like vsan

So this applies anytime that I'm starting to reach machine on a vsan datastore

Can add a rule

Have the number of failures to tolerate

And I'm going to set it to zero

This means that I'm only going to store this works machine on a single esxi host and if that goes down

I lose access to the virtual machine

Shouldn't do that in production but it's fine for a loud environment

Add additional rules here number of Stripes I'll leave that is one

Flash read reservation I'll leave that a 0

And

Object space reservation also leave that at zero

I want to add another rule set

And I'm going to use Tag base placement

Now I haven't yet created any tags so before I can finish this I need to go back and tag one of my datastore

So go ahead and minimize this

Now showing up into work in progress

And let's go back to

My esxi host

I want to select my physical esxi host

And it's datastore

And here under summary is where I can assign a tag

And I need to create a tag cuz I don't have any available yet

So I'm going to name this

Local

I need to create a new category

We're going to call this category

Storage type

Now I've tagged this as local storage type

Let's go back to my create new VM storage

And for my second rule I wanted to tag Bass Place

From category

Storage type

Tigres

Local storage

About the Only Rule that I can apply for type base placement

Because the Tai base placement is used for storage that is not software-defined so it's not going to give us as fine of

Now I can click next and it's going to show me which day to stores are compatible with this ruleset

And notice that we have to the vsan datastore

As well as the local data store

Had I not done the second rule set only the vsan datastore would be compatible with this storage policy

Now I click on finish

And later on when I creativerse machine I can use that storage policy to specify

I only wanted to be stored on a single esxi host

Now take a look at our NFS storage

Right amount of NFS datastore I need to make a couple of changes to the NFS server on the control center VM

I still have the putty session open but if you don't have one just go ahead and reopen a new putty session and log back into the control center via

I want I want yast to configure the VM

And go down to networking services

And NFS server

Noticed that my NFS server is started

Ports are open on the firewall

And it is enabled for NFS version 4

As of esxi 6.0 NFS version 4 is Now supported

Click on next and I can see that I'm sharing out a home NFS directory

Notice the options currently for that directory however are read-only and root squash those two need to be

You changed in order for me to be able to store virtual machines on that datastore

So I'll die to edit those

I've down

And I want to change this one to no root squash

And read right

Click on okay

And then I'll have to finish

Now anytime you make changes to the NFS server it takes about 90 seconds for that change to take effect so I don't

Don't want to immediately try to mount that NFS datastore I need to give it a moment's

Let's go back to our esxi host

It's like one of the hosts inside of the vsan cluster

Once it's been at least 90 seconds then you should be able to add today to store

So will click on new datastore

NFS

NFS version for it is very important that you don't combine in FS version 3 in in

NFS version 4 connections to the same data store

If 1 houses using an efest version for than they all need to be using NFS version for the two different version

Use dif locking mechanism so you will get data corruption if you mix and match them

Can you call this

NFS datastore

Specify that

Boulder

Manifest

And then our control center IP address

Click on the plus

We're not using Kerberos pre-authentication that's why we had to specify no root squash if we did have active directory setup

We could add all of the esxi host to active directory and then we could use Kerberos based Authentication

Icon finish

We should now see a new datastore

Now I go to that datastore will see that

Currently only mounted on a single esxi host

I can right click on it

And I can slice the other house of my Visa and cluster as well as the physical cluster post

Now if I go to that datastore

Now that we have multiple options for where we can place a virtual machine Let's Go create some