2,187
edits
Difference between revisions of "VCP4"
Jump to navigation
Jump to search
m
→Enable a Fault Tolerant Virtual Machine: Added "Not Protected" reasons and some deffinitions
m (→Install, Configure and Manage VMware vCenter Update Manager: Added severity levels) |
m (→Enable a Fault Tolerant Virtual Machine: Added "Not Protected" reasons and some deffinitions) |
||
| Line 387: | Line 387: | ||
== Enable a Fault Tolerant Virtual Machine == | == Enable a Fault Tolerant Virtual Machine == | ||
* vLockstep - Keeps Primary and Secondary VM's in sync | * vLockstep - Keeps Primary and Secondary VM's in sync | ||
* vLockstep Interval - Time required for secondary to sync with primary (normally < .5s ec) | |||
* Log Bandwidth - Bandwidth required to keep VM's in sync across FT network | |||
* On-Demand Fault Tolerance - Temporary manually managed FT, configured for a VM during a critical time | * On-Demand Fault Tolerance - Temporary manually managed FT, configured for a VM during a critical time | ||
* Recommenced max of 4 FT VM's per ESX (primary or secondary) | * Recommenced max of 4 FT VM's per ESX (primary or secondary) | ||
| Line 420: | Line 422: | ||
# Create HA Cluster and perform Profile Compliance | # Create HA Cluster and perform Profile Compliance | ||
# Turn on FT for appropriate VM's | # Turn on FT for appropriate VM's | ||
'''Not Protected''' caused by... | |||
* VM's are still starting up | |||
* Secondary VM is not started, possible causes... | |||
** No suitable host on which start secondary | |||
** A fail-over has occurred but FT network link down, so new secondary not started | |||
* Disabled - FT has been disabled by user or VC (because no suitable secondary host can be found) | |||
* Primary VM is not on, so status is ''Not Protected, VM not Running'' | |||
== Create and Configure Resource Pools == | == Create and Configure Resource Pools == | ||