Term
| T/F: Fault tolerance will make VMs continuously available in the event of OS Failure |
|
Definition
|
|
Term
| T/F: Fault tolerance will make VMs continuously available in the event of a host failure |
|
Definition
|
|
Term
| What is the name of the underlying technology that keeps the states of the primary and secondary VM identical |
|
Definition
|
|
Term
| T/F: FT will function even if vCenter is not available |
|
Definition
| True - the switch over to the secondary VM will still happen even in the event vCenter Server is unreachable |
|
|
Term
| T/F: a secondary VM is always present with FT |
|
Definition
| True: when the primary host fails, the secondary VM becomes the primary and a new secondary is created, so there is always protection |
|
|
Term
| List the Cluster requirements for Fault tolerence |
|
Definition
* Host Certificate checking must be enabled
* At least 2 FT-certified hosts running the same FT version or host build number
* Hosts need access to the same storage
* FT logging and vMotion Networking need to be configured
* HA must be enabled on the cluster. If it is not, oyu will not be able to power on an FT machine or adda host running a FT machine to the cluster
Source: blog.mwpreston.net |
|
|
Term
| List the Host Requirements for Fault Tolerence |
|
Definition
* Must contain processors from the FT-compatible processor group. Highly recommended that CPUs are also compatible with one another
* Must be licensed for FT (enterprise or ent + in 5.0, Std in 5.1)
* Must be certified for FT (HCL)
* Bios must have Hardware Virtualization (HV) enabled |
|
|
Term
| List the VM Requirements for fault tolerence |
|
Definition
* Virtual disks must be in virtual RDM mode or VMDK files (NO physical RDM!)
* The disk must be thick = no thin provisioning!
* Cannot have more than one vCPU
* Must be running a supported OS (Windows 7, Windows Server 2008, Vista, 2003, XP, 2000, NT 4, All Linux supported by ESX, Netware, solaris 10, and FreeBSD ( there are some limitations on processors though, so check them out).) |
|
|
Term
| List the vSphere features not supported with FT |
|
Definition
* Snapsots
* Storage vMotion
* Linked Clones
* Backup using Storage API for Data Protection
* Cannot use a floppy or cdrom backed by physical or remote device
* USB and sound devices
* NPIV
* NIC passthrough
* vlance networking drives
* Hot pluggable features
* EPT/RVI
* Serial or parallel ports
* IPv6
* 3D enabled video drivers |
|
|
Term
| What physical perquisites are there for networking for Fault Tolerance? |
|
Definition
| Multiple Gigabit NICs. Need at least one for FT logging and one for vMotion per host |
|
|
Term
| What kind of port would you need to crate for FT logging? |
|
Definition
|
|
Term
|
Definition
| No! so secure this network and probably best to have a private network |
|
|
Term
| What will your hosts summary tab display if you have correctly configured the vmkernel port for FT logging? |
|
Definition
|
|
Term
| How do you enable Fault Tolerance? |
|
Definition
| Right click the VM and select 'Fault Tolerance' -> 'Enable Fault Tolerance' |
|
|
Term
| What reasons might the option to enable FT be greyed out? |
|
Definition
*The VM is registered on a host that is not licensed for FT
*The VM is on a host that is in maintenance or standby
*The VM is disconnected or orphaned
*The user doesn't have permission to do this |
|
|
Term
| What happens to limits and reservations when you enable FT on a VM? |
|
Definition
| Any limits and reservations are discarded and new reservations are set to whatever the configured memory size of the VM. These options cannot be changed whilst FT is enabled for that VM |
|
|
Term
| What happens to limit, reservation, or shares when you disable FT? |
|
Definition
| They remain as their FT values. I.e. they are not reverted back to their values before FT |
|
|
Term
| Identify the two FT configuration tests that can be performed and their impact on the primary and secondary machines. |
|
Definition
1. Testing FT Failover: the secondary machine becomes the new primary and the old primary is removed. A new secondary machine will spawn up and sync with the new primary.
2. Testing restart secondary: The current secondary will be destroyed and another started. The primary is unaffected |
|
|
Term
| Use cases for FT on a VM - name 4 |
|
Definition
* Applications that need to be highly available and protected against a HW failure (with 1 vCPU only)
* Custom built applications that have no form of clustering available
* Simple way to provide HA to apps
* Protect a particluar VM during a critical time |
|
|
