Have any questions soon about Fault Tolerance yet? If not you will soon… as I’ve noticed an uptick in technical inquiries since it now supports 4 vCPU VMs and 64 Gb of RAM per VM.
So what’s the difference between High Availability and Fault Tolerance. The key difference between FT and HA is interruption to a virtual machine operation in the event of an host failure. Fault tolerant systems instantly transition to a new host, however, high availability systems will need to see the VMs fail within a host before restarting on another host. Now we would obviously love to have FT across all our virtual machines but there are some limits to consider such as:
- You can only protect 4 VMs with FT per physical host -or- 8 FT protected vCPUs (whichever limit is reached first)
- You can protect vCenter server with FT but to my understanding this will not be supported (more to come on this).
- You will probably need to have a 10Gbps network as in the past a single FT protected VM required a 1Gbps network card (more to come on this).
Some additional features include placing the VM and FT machine on a different datastores protecting you from both a host and storage failure (in version 5 both resided in the same datastore). Plus you can also now use backup software to backup your FT protected VMs if it supports the latest vSphere 6 and VADP (vStorage APIs for Data Protection)!
The following checklist contains cluster, host, and virtual machine requirements that you need to be aware of before using vSphere Fault Tolerance.
Fault Tolerance Checklist
This blockbuster release contains the following new features and enhancements, many of which are industry-first features. So what new features have arrived with VMware vSphere 6.0?
vMotion Improvements: You can now perform non-disruptive live migration of workloads across distributed switches and vCenter Servers and over distances of up to 100ms RTT. The astonishing 10x increase in RTT offered in long-distance vMotion now makes it possible for data centers physically located in New York and London for example to migrate live workloads between one another!
Cross vCenter vMotion: Copy and move virtual machines between hosts on different vCenter Servers in a single action! In vSphere 5, migrating VMs between different instances of vCenter was not possible.
Long Distance vMotion: This allows the migration of applications from one datacenter to another datacenter located across the country.
Virtual Volumes (VVols): VVOL technology has finally arrived from VMware with several supported storage vendors. Virtual volumes or VVOLs provide storage for VMware virtual machines that currently need a LUN or other storage abstractions requiring a dedicated storage administrator. To summarize this feature storage arrays publish their services to ESXi using VASA (VMware APIs for Storage Awareness) 2.0 APIs and VMs request a selected service from the service availability list.
Increased Scalability: VMware increased configuration maximums and virtual machines can now support up to 128 virtual CPUs (vCPUs) and 4TB virtual RAM (vRAM). Plus hosts can now support up to 480 CPU and 12TB of RAM, 2,048 virtual machines per host, and 64 nodes per cluster!
Fault Tolerance (up to 4-vCPUs): Support for 64GB RAM and 4 vCPUs will be covered under with fault tolerance
Amazing Graphics: The new NVIDIA GRID vGPU is now integrated to deliver full benefits of NVIDIA hardware-accelerated graphics to virtualized solutions.
Technical White Papers:
What’s New in the VMware vSphere 6.0 Platform
NVIDIA GRID vGPU Enterprise Graphics
vRealize Operations Manager 6.0
- New resilient architecture
- Unified user interface
- Smart Alerts
- Enhanced reporting
- Flexible capacity models
- Custom policies
- Unified storage visibility
vRealize Automation 6.2
- Supportability enhancements
- Integration with vRealize Operations Manager
- API Improvement and new CLI Tool
- Endpoint Support Enhancements
- Advanced Service Designer Enhancements
- Application Services Enhancements
- vRealize Orchestrator Enhancements
- Branding Change to vRealize
vRealize Configuration Manager 5.7.3
- Rebranded vCenter Configuration Manager to vRealize Configuration Manager.
- VCM Collector installation on Windows Server 2012 or Server 2012 R2 operating systems, and support for Microsoft SQL Server 2012 SP2.
- VCM Windows Agent and VCM Linux Agent are now Federal Information Processing Standards (FIPS) 140-2 Compliant.
- Additional Managed Machines Platform Support : RHEL 7,OEL 7,Cent OS 7 and SLES 11 SP3.
- Support of new Software Content Repository (SCR) Tool 6.1 on RHEL 7 Server (64-bit).
- Option to hide SID and event lookup jobs from Running Jobs Window.
- Upgraded JRE to 1.7u65
vRealize Business Standard 6.0.0
- Integration – Integration with vRealize Automation 6.2 and EMC Storage Resource Management (SRM)
- Cost Analysis – Enhancements to pricing, Improved consumption analysis, Support for budgeting and new currencies, and more.
- Cloud comparison -Support for data center comparison
- Public Cloud – Enhancements to AWS support, vCloud Air cloud usage visibility
- Report Enhancements
vRealize Business Adv/Ent 8.2.0
- Pprovides fast time to value with more automation and focused information and business cases, by focusing on the following areas:
- Service planning and optimization
- Usability improvements
- Installation and Deployment enhancements
vRealize Hyperic 5.8.4
- Hyperic 5.8.4 is a maintenance release with major and minor bug fixes.
- In addition to general issue fixing, the following changes have been made in vCenter Hyperic 5.8.4.
- Non-English languages are supported for Windows operating systems.
- JRE version 7u71 is supported.
- Several updates have been made to some of the plug-ins
vRealize Orchestrator vRA plugin 6.2.0
vRealize Orchestrator Plug-In works with vRealize Automation 6.2 and vRealize Orchestrator 6.0.0 and introduces the following new functionalities:
- TheResquestsHelper.setFormValues method and theResquestsHelper.setLiteralMapValues method are no longer restricted to primitive types for entry values.
- New Create an Approval Policy and Add an approval level workflows for creating vRealize Automation approval policies.
- New workflows for content management allow you to validate and share Advanced Service Designer content between tenants or between vRealize Automation hosts.
VMware vRealize Log Insight 2.5.0
– Event Trends Analyzer
– Role-Based Access Control
– Integration with vRealize Operations Manager 6.0
– Log Insight Forwarder
– Integrated Load Balancer
– Built-In Content Packs
– New vRealize Log Insight Linux Agent
– Contextual Log Browsing for Events
– Several Usability, Performance and Security Improvements