Term
| Identify host requirements for vMotion and Storage vMotion |
|
Definition
* Each host must be licensed (standard and up for storage vMotion)
* Each host mus meet the shared storage requirements for vMotion (not in 5.1)
* Each host must meet the nw requirements: must have a vmkernel port that has been assigned to vMotion, on the same subnet on all hosts, must be named identically. Also, the networks that the VMs are attached to must also reside on both hosts and be named the same. |
|
|
Term
| What type of port is created for vMotion traffic? |
|
Definition
| vmkernel port, there must be a dedicated one for vmotion on all participating hosts! |
|
|
Term
| Identify VM requirements for vMotion |
|
Definition
* Must not have RDMs for clustering purposes
* Cannot vMotion a VM that is backended by a device that isn't accessible to the target host. e.g. a CDROM connected to local storage. These devices must be disconnected first. USB is supported if the device is enabled for vMotion
* VM must not have a virtual device backed by a device on a client computer |
|
|
Term
| What are the requirements for vMotion with Snapshots |
|
Definition
| Both vMotion and Storage vMotion are available to virtual machines with snapshots |
|
|
Term
| Outline the steps to perform a storage vMotion |
|
Definition
1. Right click VM and select 'Migrate'
2. Select migration option (change host, change datastore, change both - only through web client 5.1)
3. Select a disk format
4. Select datstore location |
|
|
Term
| What options are available for disk formats when performing a storage vMotion? |
|
Definition
1. Same as source - uses the same format as the original disk (RDMs with virtual compatibility mode will be converted to VMDK, RDMs in physical compatibility mode will only have mapping files migrated)
2. Thin Provisioned - can be converted to a thin disk even if it wasn't before. Cannot use with physical compatibility RDM, can with virtual compatibility RDM
3. Thick - will be converted to thick if it wasn't before. RDM compatibility same guidelines as for Thin option |
|
|
Term
| What options are available for datastore location when you perform a storage vMotion? |
|
Definition
1. Store all VM files on the same datastore
2. Store all VM files in the same SDRS cluster
3. Store the VM configuration files and disk in separate locations |
|
|
Term
| Outline the steps to perform a vMotion (host vmotion) |
|
Definition
1. Right click VM and select 'Migrate'
2. Select Change Host.
3. Select the destination resource pool & host or cluster
4. Select migration priority |
|
|
Term
| When is the VM swap file created? |
|
Definition
| The vmkernel will create a swap file for each VM when it is powered on |
|
|
Term
| What is the function of the VM swap file? |
|
Definition
| This is used as a backing store for the VMs RAM contents. |
|
|
Term
| Where is the swap file stored by default? |
|
Definition
| At the same location as the VMs configuration file |
|
|
Term
| How can you change the location of the VMs swap file on a cluster level? |
|
Definition
| Specify a datastore, accessed in the software section of the host's configuration tab. There is a 'Cluster Settings' option which contains a 'Swap File Location' link |
|
|
Term
| How can you change the location of a VMs swap file on a host level? |
|
Definition
| Go to software section of the host's 'configuration' tab. There is a 'Virtual Machine SwapFile Location' link. Specify the datastore. |
|
|
Term
| How can you change the swap file location on a VM level? |
|
Definition
| Specify Default location, Store with the VM, or store in the host's swapfile datastore. There is a SwapFile location section of the options tab of VM's 'Settings' where you can configure this |
|
|
Term
| How do you migrate a powered-off or suspended VM? |
|
Definition
| Same as for powered on: Right click and select 'migrate'. You must choose the destination location, datastore location, target disk format. |
|
|
