Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
Now that I have three virtual machines one per esxi host let's take a look at moving them around
Dinar environments
We'll go back to host and clusters
Remember earlier we created our vmotion interfaces so each one of the esxi host
Specified for vmotion and it's on the vmotion TCP IP stack they're all in the same subnet range
And go to migrate actually several different types of migrations that we can do with our running
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
When we move virtual machine that is powered on there are some compatibility checks that have to happen we have
Have to have the same resources available on the other side
In terms of our network storage any other devices it's connected to like a CD-ROM driver flash drive
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
In addition if it's a running virtual machines or trying to do a vmotion the CPUs have to be compatible
The CPA requirements tend to be pretty strict so even if they're in the same family different CPUs might not allow us
2 v motion over to machines we can use EVC to get around that if we need two things like clock speed cash size
Citizen the number of cores don't matter as long as there's enough to support a virtual machine
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
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
Onstage from one esxi host to another
So this one is currently running on 75 and I'll move it over to 76
I can modify the network if I need to but I don't need to in this case always leave it at high priority
Click on finish and then we just monitor our recent tasks
This should go pretty quick what's happening at this point is we're copying the contents of memory from one yes
Text I host to another
Now that it's complete
I click on
76 and I go to Virtual machines I'll see that it has two running virtual machines on it
Not want to move Linux VM to from
The vsan cluster over to the physical cluster
I went ahead and modify the physical cluster I added a
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
I run into another problem
I try to migrate this virtual machine
Migrated to the physical server what's going to give me an error because there is no distributed switch on
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
Cancel out of this
We're going to edit settings on the virtual machine
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
They're both on VLAN zero so it's not going to create any issues for me to migrate its network adapter
Now it's on the VM Network which is also available on the physical host
And also has a VM Network so now when I go to migrate the virtual machine
Select my physical server
And it passes the validation
I need to modify the storage because the vsan datastore is not available and I'm going to start on the local data store
And I'm going to make sure that it is then provisions
Leave it on VM Network
High priority
Click on finish
Now this vmotion is going to take longer because in addition to moving the contents of memory I also have to move the
The storage from the vsan data store to the local data store on the physical esxi host
Once it's completed noticed that Linux VM to is now running on the physical cluster
Let's go ahead in my great that back
I can take a slight shortcut by grabbing the VM and just moving it
Not going to fill in some of the information for me
I need to set it back to my one hose storage policy
Bring it back to the virtual esxi host
Next up going to take a look at snapshots
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.