Skip to main content

 VMware Fault Tolerance (FT) is a feature 

 

 Key Features of VMware FT:

 

 1. Continuous Availability: FT provides continuous availability for VMs by creating a live shadow copy of the VM.

 2. Zero Downtime: FT ensures zero downtime for VMs by automatically failing over to the shadow copy in case of a failure.

 3. Live Shadow Copy: FT creates a live shadow copy of the VM that is identical to the primary VM.

 4. Synchronous Replication: FT uses synchronous replication to ensure that the shadow copy is always up-to-date.

 5. Automatic Failover: FT automatically fails over to the shadow copy in case of a failure.

 

 Benefits of VMware FT:

 

 1. High Availability: FT provides high availability for VMs by ensuring continuous availability.

 2. Zero Data Loss: FT ensures zero data loss by creating a live shadow copy of the VM.

 3. Reduced Downtime: FT reduces downtime by automatically failing over to the shadow copy in case of a failure.

 4. Simplified Disaster Recovery: FT simplifies disaster recovery by providing a live shadow copy of the VM.

 

 Requirements for VMware FT:

 

 1. vSphere 6.0 or later: FT requires vSphere 6.0 or later to be installed and configured.

 2. vCenter Server: FT requires vCenter Server to be installed and configured.

 3. FT-compatible hardware: FT requires FT-compatible hardware, such as servers and storage devices.

 4. VMware Tools: FT requires VMware Tools to be installed on the VM


Comments

Post a Comment

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 πŸ”Ή Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more