All language subtitles for 014 vSphere storage

af Afrikaans
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese Download
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,512 --> 00:00:05,888 Fisher currently has seven options for where we can place virtual machines and other necessary files 2 00:00:06,400 --> 00:00:12,544 The first four options are referred to as Block Level meaning that the esxi host has direct access to 3 00:00:12,800 --> 00:00:16,896 Either the device or the one and then it's formatted with a VMS file system 4 00:00:17,408 --> 00:00:22,272 The first option direct-attached storage is the distant exist inside of the esxi host 5 00:00:22,528 --> 00:00:28,672 Next two options fibre Channel and fibre Channel over ethernet mean that we have an array on a fiber channel say 6 00:00:28,928 --> 00:00:35,072 And then we're either connected to it directly through an HPA in the case of fiber channel or we're connected to 7 00:00:35,328 --> 00:00:39,168 Which through an ethernet switch in the case of fiber channel over ethernet 8 00:00:39,424 --> 00:00:45,568 1/4 Block Level option is ice Guzzi ice cuz he uses our IP network and our IP interface 9 00:00:45,824 --> 00:00:48,384 To communicate with the storage array 10 00:00:48,896 --> 00:00:55,040 The next option NFS is slightly different than our Block Level options in that the underlying operating system tutor 11 00:00:55,296 --> 00:00:57,600 Herman's the format of the file system 12 00:00:57,856 --> 00:01:04,000 McKay's of Windows it'll typically be NTFS in the case of Lennox it will usually be either ext4 or ZF 13 00:01:05,024 --> 00:01:11,168 Our final two options vsan in Virtual volumes are relatively new and they're what's referred to as software-defined storage 14 00:01:11,680 --> 00:01:17,824 Meaning that we have more control inside of vcenter server as far as how we utilize our storage 15 00:01:18,080 --> 00:01:21,920 In this lab environment we're going to be using vsan and NFS 16 00:01:22,944 --> 00:01:29,088 Recent stories takes the discs that exist on our esxi host pulls them together and uses them to create a shared. 17 00:01:30,624 --> 00:01:35,488 They're two different types of discs that need to exist on at least three of the esxi host in our cluster 18 00:01:36,256 --> 00:01:40,608 The first is a capacity disc and will typically have more than one capacity disc 19 00:01:40,864 --> 00:01:47,008 This is used for the storing of the virtual machine can either be hard drives or SS 20 00:01:47,264 --> 00:01:47,776 Besties 21 00:01:48,032 --> 00:01:51,616 The second disc is used for cashing in this always has to be in SSD 22 00:01:52,384 --> 00:01:55,456 Knox take a look at our storage configuration inside of the web client 23 00:01:56,736 --> 00:02:02,880 Our first screen under storage configuration is our storage adapters this will show our local ad 24 00:02:03,136 --> 00:02:08,000 Raptors as well as any fiber channel or Hardware iSCSI adapters that we have 25 00:02:08,512 --> 00:02:14,656 I can also creates a Sakurai scuzzy adapter or a software fiber channel over ethernet adapter by clicking on the Green 26 00:02:14,912 --> 00:02:15,424 Plus 27 00:02:15,680 --> 00:02:21,568 For more information on creating a soft rice cuz he adopt from the lab environment see my up and running on Bistro six course 28 00:02:22,848 --> 00:02:25,408 Our second screen is our storage devices 29 00:02:25,664 --> 00:02:30,528 Initials all of the devices in lawns that are currently visible to this esxi host 30 00:02:30,784 --> 00:02:34,368 We have our local disk where esxi is installed 31 00:02:34,880 --> 00:02:36,416 We have our CD-ROM drive 32 00:02:36,672 --> 00:02:42,560 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 33 00:02:43,328 --> 00:02:49,472 Arthur screen is data stores and this is going to show any data source that this esxi host currently has access to 34 00:02:49,984 --> 00:02:54,336 The moment we have the vsan datastore that was created as part of our scripted installation 35 00:02:54,848 --> 00:03:00,480 For more information about vsphere storage CR configuring and administering Advanced feature storage course 36 00:03:01,504 --> 00:03:04,576 Now let's take a look into our vsan configuration 37 00:03:06,112 --> 00:03:08,928 The recent configuration is done at the cluster level 38 00:03:09,184 --> 00:03:10,720 Select select are 39 00:03:11,488 --> 00:03:12,768 Vsan cluster 40 00:03:13,280 --> 00:03:15,328 And then we'll go to the general screen 41 00:03:16,352 --> 00:03:18,912 This shows that I have vsan turn on 42 00:03:25,312 --> 00:03:31,456 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 43 00:03:31,712 --> 00:03:32,224 Have created 44 00:03:32,736 --> 00:03:36,576 Select one of these discs groups I'll see that there's two discs inside of it 45 00:03:37,088 --> 00:03:39,136 There is my 20 gauge capacity disc 46 00:03:39,392 --> 00:03:41,952 As well as my 4gig cash disc 47 00:03:42,208 --> 00:03:45,024 I can see the same thing for each esxi host 48 00:03:45,280 --> 00:03:49,888 All of that is pulled together to create the storage where I can place virtual machine 49 00:03:50,400 --> 00:03:56,544 As I mentioned software-defined storage gives us finer grind control over how we consumer storage 50 00:03:56,800 --> 00:03:58,592 And that's done through storage policies 51 00:03:58,848 --> 00:04:01,408 The next thing that I need to do is create a storage policy 52 00:04:02,176 --> 00:04:03,712 To do this I go to home 53 00:04:04,224 --> 00:04:05,504 Policies and profiles 54 00:04:06,272 --> 00:04:08,064 MBM storage policies 55 00:04:08,576 --> 00:04:14,720 Now we have one vsan storage policy already created this is the default so it's take a look at this one first 56 00:04:16,256 --> 00:04:17,536 Click on edit settings 57 00:04:17,791 --> 00:04:19,583 Wednesday the name and description 58 00:04:19,839 --> 00:04:21,119 And then the ruleset 59 00:04:21,631 --> 00:04:26,239 This ruleset specifies that we can tolerate one host failing 60 00:04:26,495 --> 00:04:27,519 Which means that 61 00:04:27,775 --> 00:04:30,847 The virtual machine needs to be stored on at least two hosts 62 00:04:31,359 --> 00:04:36,991 Notice the consumption model over here on the side says if this virtual disk is consuming a hundred gig 63 00:04:37,247 --> 00:04:39,807 The actual storage space is going to be 200 gig 64 00:04:43,391 --> 00:04:49,535 The second line in here is the number of districts per object I could set this higher meaning that this virtue 65 00:04:49,791 --> 00:04:51,839 The machine would be stored on more than one disc 66 00:04:52,095 --> 00:04:53,887 Her esxi host 67 00:04:54,399 --> 00:04:58,751 In a striped fashion meaning it doesn't consume any more capacity 68 00:04:59,007 --> 00:05:02,591 But we're going to get higher speed because it's coming from two separate discs 69 00:05:02,847 --> 00:05:06,687 It does require however that I have more than one disc in my environment I don't 70 00:05:07,455 --> 00:05:10,527 The third option under the rule set is force provisioning 71 00:05:10,783 --> 00:05:16,927 This means that will provision the virtual machine even if the storage can't meet our requirements that set to know meaning Venom 72 00:05:17,183 --> 00:05:20,767 Muscle storage can meet our requirements are not going to provision a virtual machine 73 00:05:21,279 --> 00:05:23,839 Next option here is object space reservation 74 00:05:24,095 --> 00:05:30,239 And this is going to be roughly equivalent to thin vs. thick if I set it at zero we're not going to 75 00:05:30,495 --> 00:05:34,079 Reserve any of the space up front that would be the equivalent of sin 76 00:05:34,591 --> 00:05:36,639 If I were to set this to 100% 77 00:05:36,895 --> 00:05:39,711 We would reserve the entire capacity for the disc 78 00:05:39,967 --> 00:05:46,111 And that would be the equivalent of thick provisioning notice I can also go anywhere in the middle and I can reserve 79 00:05:46,367 --> 00:05:48,415 The capacity for the desktop front if I wanted 80 00:05:49,183 --> 00:05:55,327 The final option here is Flash read cash reservation indicating how much of the recast that I want to reserve 81 00:05:55,583 --> 00:05:57,119 For this particular virtual machine 82 00:05:57,887 --> 00:05:59,935 There are additional rules that I can add 83 00:06:00,191 --> 00:06:03,775 About fault-tolerance method Ops limits an object checksums 84 00:06:04,799 --> 00:06:06,591 Smells create our own rule set 85 00:06:07,871 --> 00:06:09,663 Go to create VM storage policy 86 00:06:10,687 --> 00:06:12,735 And I'm going to call this one host 87 00:06:13,759 --> 00:06:14,783 Storage policy 88 00:06:15,807 --> 00:06:16,831 Click on next 89 00:06:17,599 --> 00:06:20,159 The first thing that I can specifier, rules 90 00:06:20,415 --> 00:06:23,231 These are going to apply no matter where we're storing the disc 91 00:06:24,767 --> 00:06:29,375 And you can see that my options here I can specify encryption or storage IO control 92 00:06:29,887 --> 00:06:32,191 I'm not going to use either of those for this policy 93 00:06:33,215 --> 00:06:35,263 Next I can select ruleset one 94 00:06:36,031 --> 00:06:37,567 And here also like vsan 95 00:06:37,823 --> 00:06:41,919 So this applies anytime that I'm starting to reach machine on a vsan datastore 96 00:06:42,687 --> 00:06:43,711 Can add a rule 97 00:06:44,223 --> 00:06:46,271 Have the number of failures to tolerate 98 00:06:46,783 --> 00:06:48,575 And I'm going to set it to zero 99 00:06:49,855 --> 00:06:55,231 This means that I'm only going to store this works machine on a single esxi host and if that goes down 100 00:06:55,487 --> 00:06:57,279 I lose access to the virtual machine 101 00:06:57,535 --> 00:07:00,863 Shouldn't do that in production but it's fine for a loud environment 102 00:07:01,375 --> 00:07:04,959 Add additional rules here number of Stripes I'll leave that is one 103 00:07:06,239 --> 00:07:08,799 Flash read reservation I'll leave that a 0 104 00:07:09,055 --> 00:07:09,823 And 105 00:07:10,591 --> 00:07:13,407 Object space reservation also leave that at zero 106 00:07:13,663 --> 00:07:15,711 I want to add another rule set 107 00:07:16,735 --> 00:07:18,783 And I'm going to use Tag base placement 108 00:07:20,831 --> 00:07:26,975 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 109 00:07:27,743 --> 00:07:29,535 So go ahead and minimize this 110 00:07:30,815 --> 00:07:32,607 Now showing up into work in progress 111 00:07:33,375 --> 00:07:35,167 And let's go back to 112 00:07:35,679 --> 00:07:36,959 My esxi host 113 00:07:38,495 --> 00:07:41,055 I want to select my physical esxi host 114 00:07:43,615 --> 00:07:44,895 And it's datastore 115 00:07:46,175 --> 00:07:48,991 And here under summary is where I can assign a tag 116 00:07:50,015 --> 00:07:53,343 And I need to create a tag cuz I don't have any available yet 117 00:07:54,367 --> 00:07:55,903 So I'm going to name this 118 00:07:57,183 --> 00:07:57,695 Local 119 00:08:00,767 --> 00:08:02,303 I need to create a new category 120 00:08:02,559 --> 00:08:04,095 We're going to call this category 121 00:08:06,399 --> 00:08:07,423 Storage type 122 00:08:12,799 --> 00:08:15,871 Now I've tagged this as local storage type 123 00:08:16,639 --> 00:08:19,711 Let's go back to my create new VM storage 124 00:08:22,271 --> 00:08:24,831 And for my second rule I wanted to tag Bass Place 125 00:08:25,855 --> 00:08:26,879 From category 126 00:08:27,135 --> 00:08:28,159 Storage type 127 00:08:28,927 --> 00:08:29,695 Tigres 128 00:08:30,719 --> 00:08:31,743 Local storage 129 00:08:34,303 --> 00:08:37,119 About the Only Rule that I can apply for type base placement 130 00:08:37,631 --> 00:08:43,775 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 131 00:08:44,799 --> 00:08:49,151 Now I can click next and it's going to show me which day to stores are compatible with this ruleset 132 00:08:49,663 --> 00:08:52,735 And notice that we have to the vsan datastore 133 00:08:52,991 --> 00:08:54,527 As well as the local data store 134 00:08:55,039 --> 00:09:01,183 Had I not done the second rule set only the vsan datastore would be compatible with this storage policy 135 00:09:02,207 --> 00:09:03,743 Now I click on finish 136 00:09:04,255 --> 00:09:08,351 And later on when I creativerse machine I can use that storage policy to specify 137 00:09:08,607 --> 00:09:11,423 I only wanted to be stored on a single esxi host 138 00:09:11,679 --> 00:09:13,471 Now take a look at our NFS storage 139 00:09:15,263 --> 00:09:21,407 Right amount of NFS datastore I need to make a couple of changes to the NFS server on the control center VM 140 00:09:22,687 --> 00:09:28,831 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 141 00:09:29,855 --> 00:09:33,183 I want I want yast to configure the VM 142 00:09:33,695 --> 00:09:35,999 And go down to networking services 143 00:09:36,767 --> 00:09:38,303 And NFS server 144 00:09:40,351 --> 00:09:43,167 Noticed that my NFS server is started 145 00:09:43,423 --> 00:09:44,959 Ports are open on the firewall 146 00:09:45,215 --> 00:09:47,775 And it is enabled for NFS version 4 147 00:09:48,287 --> 00:09:52,639 As of esxi 6.0 NFS version 4 is Now supported 148 00:09:54,175 --> 00:09:58,527 Click on next and I can see that I'm sharing out a home NFS directory 149 00:09:58,783 --> 00:10:04,927 Notice the options currently for that directory however are read-only and root squash those two need to be 150 00:10:05,183 --> 00:10:09,023 You changed in order for me to be able to store virtual machines on that datastore 151 00:10:09,791 --> 00:10:11,839 So I'll die to edit those 152 00:10:13,119 --> 00:10:14,143 I've down 153 00:10:15,935 --> 00:10:19,519 And I want to change this one to no root squash 154 00:10:20,287 --> 00:10:21,823 And read right 155 00:10:23,359 --> 00:10:24,639 Click on okay 156 00:10:24,895 --> 00:10:26,687 And then I'll have to finish 157 00:10:30,271 --> 00:10:36,415 Now anytime you make changes to the NFS server it takes about 90 seconds for that change to take effect so I don't 158 00:10:36,671 --> 00:10:41,535 Don't want to immediately try to mount that NFS datastore I need to give it a moment's 159 00:10:44,607 --> 00:10:47,679 Let's go back to our esxi host 160 00:10:50,239 --> 00:10:52,799 It's like one of the hosts inside of the vsan cluster 161 00:10:54,079 --> 00:10:57,663 Once it's been at least 90 seconds then you should be able to add today to store 162 00:10:58,943 --> 00:11:00,735 So will click on new datastore 163 00:11:02,783 --> 00:11:03,807 NFS 164 00:11:05,599 --> 00:11:11,743 NFS version for it is very important that you don't combine in FS version 3 in in 165 00:11:11,999 --> 00:11:15,839 NFS version 4 connections to the same data store 166 00:11:16,351 --> 00:11:22,495 If 1 houses using an efest version for than they all need to be using NFS version for the two different version 167 00:11:22,751 --> 00:11:27,615 Use dif locking mechanism so you will get data corruption if you mix and match them 168 00:11:29,663 --> 00:11:30,687 Can you call this 169 00:11:31,455 --> 00:11:32,991 NFS datastore 170 00:11:33,759 --> 00:11:34,783 Specify that 171 00:11:35,039 --> 00:11:35,551 Boulder 172 00:11:36,063 --> 00:11:37,087 Manifest 173 00:11:37,599 --> 00:11:40,415 And then our control center IP address 174 00:11:42,719 --> 00:11:43,999 Click on the plus 175 00:11:46,047 --> 00:11:52,191 We're not using Kerberos pre-authentication that's why we had to specify no root squash if we did have active directory setup 176 00:11:52,447 --> 00:11:57,567 We could add all of the esxi host to active directory and then we could use Kerberos based Authentication 177 00:12:00,127 --> 00:12:01,151 Icon finish 178 00:12:01,407 --> 00:12:03,455 We should now see a new datastore 179 00:12:03,967 --> 00:12:06,015 Now I go to that datastore will see that 180 00:12:08,063 --> 00:12:11,135 Currently only mounted on a single esxi host 181 00:12:20,095 --> 00:12:21,375 I can right click on it 182 00:12:25,727 --> 00:12:30,335 And I can slice the other house of my Visa and cluster as well as the physical cluster post 183 00:12:32,895 --> 00:12:34,431 Now if I go to that datastore 184 00:12:38,783 --> 00:12:42,879 Now that we have multiple options for where we can place a virtual machine Let's Go create some 22047

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.