FT is nothing but an active passive failover setup...If both the VMs goes down, there is nothing much can be done..(You can look for three tier clustering with Microsoft HPC 2008 I believe which obviously requires three machines). which is still not in place with VMware...
Below is the lifecycle of FT...if that helps...
Lifecycle of a fault-tolerant virtual machine
Turning on and enabling VMware FT for a virtual machine affects the virtual machine’s lifecycle, but it is entirely transparent to the end-user client and does not disrupt client connections or the client’s workload. The following steps outline the lifecycle of a VMware FT virtual machine:
1. Administrator selects a virtual machine in either the powered-on or off state and turns on VMware FT.
2. The virtual machine becomes the Primary VM and a Secondary VM is automatically created and assigned of an ESX host, sharing the same disk as the ESX host running the Primary VM.
3. If the Primary VM is already powered-on when VMware FT is turned on, its active state is immediately migrated using a special form of VMotion to the Secondary VM on an automatically chosen ESX host. If the Primary VM is powered-off then the migration of its active state to the Secondary VM occurs right
after the Primary VM is powered on.
4. The Secondary VM stays synchronized with the Primary VM through VMware vLockstep technology.
5. If the ESX host running the Primary VM goes down, the Secondary VM will immediately “go live” and become the Primary VM.
6. VMware HA automatically starts a new Secondary VM on another available host to restore protection.
7. The Secondary VM is powered off when the Primary VM powers off or when VMware FT is disabled. The secondary VM is removed altogether when VMware FT is turned off.
Thanks,,
Ramesh. Geddam,
VCP 3&4, MCTS(Hyper-V), SNIA SCP.
Please award points, if helpful
http://communities.vmware.com/blogs/rameshgeddam
Thanks,,
Ramesh. Geddam,
