All language subtitles for 017 Perform a vMotion migration

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:06,656 Now that I have three virtual machines one per esxi host let's take a look at moving them around 2 00:00:06,912 --> 00:00:07,936 Dinar environments 3 00:00:09,216 --> 00:00:12,288 We'll go back to host and clusters 4 00:00:12,800 --> 00:00:18,432 Remember earlier we created our vmotion interfaces so each one of the esxi host 5 00:00:24,064 --> 00:00:29,952 Specified for vmotion and it's on the vmotion TCP IP stack they're all in the same subnet range 6 00:00:34,304 --> 00:00:40,448 And go to migrate actually several different types of migrations that we can do with our running 7 00:00:40,704 --> 00:00:46,848 Virtual machine is referred to as a v motion but we can also do a cold migration which is when we move versus machine that's powered off 8 00:00:47,104 --> 00:00:53,248 When we move virtual machine that is powered on there are some compatibility checks that have to happen we have 9 00:00:53,504 --> 00:00:55,808 Have to have the same resources available on the other side 10 00:00:56,064 --> 00:01:02,208 In terms of our network storage any other devices it's connected to like a CD-ROM driver flash drive 11 00:01:02,464 --> 00:01:08,352 Never anything like that it's connected to anything on a piece of physical Hardware we're not going to be able to be motion that virtual machine 12 00:01:08,864 --> 00:01:15,008 In addition if it's a running virtual machines or trying to do a vmotion the CPUs have to be compatible 13 00:01:15,264 --> 00:01:21,408 The CPA requirements tend to be pretty strict so even if they're in the same family different CPUs might not allow us 14 00:01:21,664 --> 00:01:27,808 2 v motion over to machines we can use EVC to get around that if we need two things like clock speed cash size 15 00:01:28,064 --> 00:01:34,208 Citizen the number of cores don't matter as long as there's enough to support a virtual machine 16 00:01:34,464 --> 00:01:40,608 About vmotion this it'll perform all those compatibility checks for us and it'll warn us if there's a problem with the emotional virtual machine 17 00:01:40,864 --> 00:01:47,008 The first one I'm going to change the computer resource only so I'm leaving the VM on the same storage and I'm just moving the Run 18 00:01:47,264 --> 00:01:49,824 Onstage from one esxi host to another 19 00:01:51,616 --> 00:01:56,480 So this one is currently running on 75 and I'll move it over to 76 20 00:01:57,504 --> 00:02:03,136 I can modify the network if I need to but I don't need to in this case always leave it at high priority 21 00:02:04,672 --> 00:02:07,744 Click on finish and then we just monitor our recent tasks 22 00:02:08,000 --> 00:02:14,144 This should go pretty quick what's happening at this point is we're copying the contents of memory from one yes 23 00:02:14,400 --> 00:02:15,680 Text I host to another 24 00:02:16,192 --> 00:02:17,728 Now that it's complete 25 00:02:17,984 --> 00:02:19,008 I click on 26 00:02:19,520 --> 00:02:24,128 76 and I go to Virtual machines I'll see that it has two running virtual machines on it 27 00:02:24,640 --> 00:02:28,224 Not want to move Linux VM to from 28 00:02:28,480 --> 00:02:31,296 The vsan cluster over to the physical cluster 29 00:02:31,808 --> 00:02:35,904 I went ahead and modify the physical cluster I added a 30 00:02:36,416 --> 00:02:42,560 The Infernal adapter to it for vmotion in the same way that we can figure the other ones earlier so that part is correct however I'm going to 31 00:02:42,816 --> 00:02:44,096 I run into another problem 32 00:02:45,888 --> 00:02:47,936 I try to migrate this virtual machine 33 00:02:57,152 --> 00:03:03,296 Migrated to the physical server what's going to give me an error because there is no distributed switch on 34 00:03:03,552 --> 00:03:09,696 On the physical server and I can't add it to the distributed switch because it doesn't have enough uplinks so I need to do something different 35 00:03:09,952 --> 00:03:11,488 Cancel out of this 36 00:03:12,256 --> 00:03:14,560 We're going to edit settings on the virtual machine 37 00:03:15,328 --> 00:03:21,472 Premier I can edit all of the hardware settings on the virtual machine but in this case I just want to change it to BBM Network 38 00:03:21,728 --> 00:03:27,872 They're both on VLAN zero so it's not going to create any issues for me to migrate its network adapter 39 00:03:28,896 --> 00:03:33,504 Now it's on the VM Network which is also available on the physical host 40 00:03:38,112 --> 00:03:42,464 And also has a VM Network so now when I go to migrate the virtual machine 41 00:03:47,584 --> 00:03:49,376 Select my physical server 42 00:03:49,632 --> 00:03:51,424 And it passes the validation 43 00:03:52,960 --> 00:03:59,104 I need to modify the storage because the vsan datastore is not available and I'm going to start on the local data store 44 00:03:59,360 --> 00:04:02,688 And I'm going to make sure that it is then provisions 45 00:04:04,992 --> 00:04:06,528 Leave it on VM Network 46 00:04:08,064 --> 00:04:09,344 High priority 47 00:04:09,856 --> 00:04:10,880 Click on finish 48 00:04:11,904 --> 00:04:18,047 Now this vmotion is going to take longer because in addition to moving the contents of memory I also have to move the 49 00:04:18,303 --> 00:04:24,191 The storage from the vsan data store to the local data store on the physical esxi host 50 00:04:26,751 --> 00:04:31,871 Once it's completed noticed that Linux VM to is now running on the physical cluster 51 00:04:32,383 --> 00:04:34,687 Let's go ahead in my great that back 52 00:04:35,967 --> 00:04:40,575 I can take a slight shortcut by grabbing the VM and just moving it 53 00:04:41,343 --> 00:04:44,159 Not going to fill in some of the information for me 54 00:04:47,487 --> 00:04:51,583 I need to set it back to my one hose storage policy 55 00:04:59,775 --> 00:05:03,103 Bring it back to the virtual esxi host 56 00:05:04,383 --> 00:05:06,687 Next up going to take a look at snapshots 7626

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