31. vSphere Fault Tolerance (FT) Explained: Architecture, Fast Checkpointing, & How FT Works!

Sdílet
Vložit
  • čas přidán 22. 03. 2022
  • 31.vSphere 7.x - vCenter Cluster Feature - vSphere Fault Tolerance (FT) | Home Lab
    vSphere Cluster Features
    Session-3 | vSphere Fault Tolerance (FT) | Home Lab
    Agenda
    =======
    Quick Recap - vSphere Clusters Overview
    vSphere Infrastructure - Challenges & Solutions
    vSphere: Protection at Every Level - Conceptual Diagram
    vSphere Fault Tolerance (FT) Architecture
    Enabling a VM
    How does FT Work
    FT Features
    FT Configuration Limits
    FT with HA & DRS
    FT Redundant Vmdk Files
    FT Fast Checkpointing
    FT Shared Files
    vSphere Features - Real-time Scenarios
    vSphere FT Home Lab
    ==================
    Create a Cluster and enable HA & DRS Features
    Add ESXi hosts to the Cluster
    Turn on vSphere Fault Tolerance (FT) for a VM using the vSphere Client
    Test vSphere FT Functionality
    View the vSphere Cluster resource Usage
    #VMware
    #vsphere
    #ServerFundamentals
    #Virtualization
    #VCP-DCV
    #ESXi
    #VM
    #Networking
    #vCenter
    #VCSA
    #VCSA Deployment
    #vCenter
    #Architecture
    #SDDC
    #VAMI
    #NSX-T
    #VSAN
    #VRO
    #VRA
    #Block Storage
    #File Storage
    #Object Storage
    #NFS 3
    #NFS 4.1
    #Veeam
    real-time scenarios
    #ThankYou
    1. IT Infrastructure Evolution & vRealize Automation (vRA) 8.6.2 Architecture Overview
    • 1. IT Infrastructure E...
    Please refer to the following playlist for your review.
    Gnan Cloud Garage Playlists
    www.youtube.com/@gnancloudgar...
    VMware vSphere 7 & VMware vSphere Plus (+) | Data Center Virtualization
    • VMware vSphere |VCP - ...
    vSphere 7.x - Home lab - Quick Bytes | Data Center Virtualization
    • vSphere 7.x - Home lab...
    VMware vSphere 8
    • VMware vSphere 8
    VMware vSAN 8
    • VMware vSAN 8
    VMware NSX 4.x | Network Virtualization
    • VMware NSX 4.0.0.1 | N...
    VMware Cloud Foundation (VCF)+
    • VMware Cloud Foundatio...
    VMware Aria Automation (formerly, vRealize Automation) | Unified Multi-Cloud Management
    • VMware Aria Automation...
    Interview Preparation for Technical Consultants, Systems Engineers & Solution Architects
    • Interview Preparation ...
    VMware Tanzu Portfolio | Application Modernization
    • VMware Tanzu Portfolio...
    Modern Data Protection Solutions
    • Modern Data Protection...
    Storage, Software-Defined Storage (SDS)
    • Storage, Software-Defi...
    Zerto, a Hewlett Packard Enterprise (HPE) Company
    • Zerto, a Hewlett Packa...
    The Era of Multi-Cloud Services|HPE GreenLake Solutions|Solution Architectures|Solution Designs
    • The Era of Multi-Cloud...
    Gnan Cloud Garage (GCG) - FAQs |Tools |Tech Talks
    • Gnan Cloud Garage (GCG...
    VMware Aria Operations (formerly, vROps)
    • VMware Aria Operations...
    PowerShell || VMware PowerCLI
    • PowerShell || VMware P...
    Hewlett Packard Enterprise (HPE) Edge to Cloud Solutions & Services
    • Hewlett Packard Enterp...
    DevOps || DevSecOps
    • DevOps || DevSecOps
    Red Hat Openshift Container Platform (RH OCP)
    • Red Hat Openshift Cont...
    Windows Server 2022 - Concepts
    • Windows Server 2022, 2...
    Red Hat Enterprise Linux (RHEL) 9 - Concepts
    • Red Hat Enterprise Lin...
    Microsoft Azure Stack HCI
    • Microsoft Azure Stack HCI
    NVIDIA AI Enterprise
    • NVIDIA AI Enterprise
    Gratitude | Thank you messages
    • Gratitude | Thank you ...

Komentáře • 33

  • @joginderpal6943
    @joginderpal6943 Před rokem +1

    In Depth Explanation Sir ... Gnan Cloud Garage Rocking

  • @gnancloudgarage5238
    @gnancloudgarage5238  Před 2 lety +2

    31.vSphere 7.x - vCenter Cluster Feature - vSphere Fault Tolerance (FT) | Home Lab
    vSphere Cluster Features
    Session-3 | vSphere Fault Tolerance (FT) | Home Lab
    Agenda
    =======
    Quick Recap - vSphere Clusters Overview
    vSphere Infrastructure - Challenges & Solutions
    vSphere: Protection at Every Level - Conceptual Diagram
    vSphere Fault Tolerance (FT) Architecture
    Enabling on a VM
    How FT Works
    FT Features
    FT Configuration Limits
    FT with HA & DRS
    FT Redundant Vmdk Files
    FT Fast Checkpointing
    FT Shared Files
    vSphere Features - Real-time Scenarios
    vSphere FT Home Lab
    ==================
    Create a Cluster and enable HA & DRS Features
    Add ESXi hosts to the Cluster
    Turn on vSphere Fault Tolerance (FT) for a VM using the vSphere Client
    Test vSphere FT Functionality
    View the vSphere Cluster resource Usage
    #VMware
    #vsphere
    #ServerFundamentals
    #Virtualization
    #VCP-DCV
    #ESXi
    #VM
    #Networking
    #vCenter
    #VCSA
    #VCSA Deployment
    #vCenter
    #Architecture
    #SDDC
    #VAMI
    #NSX-T
    #VSAN
    #VRO
    #VRA
    #Block Storage
    #File Storage
    #Object Storage
    #Storage
    # vSphere Storage
    #FC SAN
    #iSCSI SAN
    #FCoE SAN
    #vSAN
    #vVols
    #Virtual Volumes
    #Virtual SAN
    #Multipathing
    #NFS 3
    #NFS 4.1
    #Veeam
    #real time scenarios
    #ThankYou
    1. IT Infrastructure Evolution & vRealize Automation (vRA) 8.6.2 Architecture Overview
    czcams.com/video/A2MoQ-UdXEA/video.html
    ============================================================
    1. VMware Datacenter Virtualization Basics
    czcams.com/video/cM3NuUxurpk/video.html
    2. Basic Server Fundamentals and Windows Server 2022 ACTIVE Directory AD Configuration
    czcams.com/video/T4JewBlbBwI/video.html
    3. VMware Data Center Virtualization |VCP DCV_ ICM Architectural Differences, Virtual Machines
    czcams.com/video/BhSvDa_62aI/video.html
    4. VMware DCV ICM ESXi Host Build Procedure and Lab
    czcams.com/video/94rZQYAim-0/video.html
    5. VMware DCV ICM ESXi Host Configuration and Management | ESXi Host Components & Log Files
    czcams.com/video/g5fwp9QNkTc/video.html
    6. VMware DCV ICM ESXi Host Networking & Basics of Networking
    czcams.com/video/UsGnF0FFnjM/video.html
    7. VMware DCV ICM ESXi Host Networking & IP Addressing
    czcams.com/video/3YHTEkaizT0/video.html
    8. VMware DCV ICM ESXi Networking & IP Address Classification & Reserved IPs
    czcams.com/video/yt0V0Vb1rR8/video.html
    9. VMware DCV ICM ESXi Host Networking Standard vSwitch
    czcams.com/video/-FmkOUi6cNY/video.html
    10. vSphere 7.x - ESXi Host Networking - vSwitch Policies & Home Lab
    czcams.com/video/rCTICm7sPQw/video.html
    11. vSphere 7.x | vCenter Server 7.0 Architecture & Home Lab
    czcams.com/video/_cr2dHIMPOI/video.html
    12. vSphere 7.x vCenter Server 7.0 Install, Configure, Manage & Home Lab
    czcams.com/video/OR5PlxJxfWY/video.html
    13. vSphere 7.x Architecture ,SDDC ,Inventory Objects Overview & Home Lab
    czcams.com/video/Qo8FqPMNsyw/video.html
    14.vSphere 7.x - vCenter Inventory Objects & Home Lab
    czcams.com/video/nRomjn5VQY4/video.html
    15. vSphere 7.x - vSphere Storage Concepts & Home Lab
    czcams.com/video/H16rvMSnoCM/video.html
    16. vSphere 7.x vSphere Storage - NFS Datastore Configuration | Home Lab
    czcams.com/video/sErpXMXCyfY/video.html
    17. VMware vSphere 7. x Storage - How to Configure NFS Datastore on Windows Server 2022 | Homelab
    czcams.com/video/wRRidfq-XBk/video.html
    18. vSphere 7 Storage - How to Configure iSCSI SAN on ESXi host using Windows Server 2022 | Homelab
    czcams.com/video/yRE3eD5mcUQ/video.html
    19. vSphere 7.x | FC Storage & FCoE Storage Architectures | Home Lab
    czcams.com/video/dRtY70XheJY/video.html
    20. vSphere 7.x | Virtual SAN vSAN Architecture | Home Lab
    czcams.com/video/ajLX_MMzGyQ/video.html
    21. vSphere 7.x Virtual Volumes (vVols) Architecture | Home Lab
    czcams.com/video/Zso7By96JeQ/video.html
    22. vSphere 7. x Virtual Volumes (vVols) Architecture | Real-Time Scenarios | Home Lab
    czcams.com/video/g7CB_OfIj2k/video.html
    23.vSphere 7.x vSAN , vVols, Distributed vSwitch & Home Lab
    czcams.com/video/2G4mCPg-IOA/video.html
    24.vSphere 7.x VMs, Snapshot, Clone, Templates | Home Lab
    czcams.com/video/S7owYwhDhk4/video.html
    25 . VM Snapshot, Clone, Templates | Windows Server OS Upgrade from 2019 to 2022 | Home Lab
    czcams.com/video/NEPpaozsGU4/video.html
    26.vSphere 7. x | VM Migration Methods Cold Migration, Suspended, vMotion, EVC, SvMotion & Home Lab
    czcams.com/video/aeWT6857_hE/video.html
    27.VMware vCenter Converter Standalone - P2V, V2V, Hyper-V VM2V| Home Lab
    czcams.com/video/gCBCrzziI6U/video.html
    28. VMware Converter - Converting from Workstation VM to vSphere VM (V2V) | Home Lab
    czcams.com/video/G71jYzqxPok/video.html
    29. vSphere 7. x - Clusters, DRS, DPM, vCLs, HA, FT and Protecting Data | Home Lab
    czcams.com/video/MPFoqiuX0D0/video.html
    30. vCenter Cluster Feature - High Availability (HA), Protecting Data using Veeam & Home Lab
    czcams.com/video/QBD9IDwxjOU/video.html

  • @harisingh1983
    @harisingh1983 Před 2 lety +1

    superb video !! deep knowledge

  • @user-yb3pk2ns8n
    @user-yb3pk2ns8n Před 8 měsíci +1

    good explanartion

  • @user-cz2sr1hl8f
    @user-cz2sr1hl8f Před 3 měsíci +1

    Nice video and clear understanding of FT. One query ,
    how about the licensing of applications( for example Kepware) ? Whether same license will work once secondary copy is created?

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před 3 měsíci +1

      Thank you for your positive feedback!
      In most cases, software licensing can vary depending on the specific terms and conditions set by the software vendor.
      When implementing fault-tolerant solutions like VMware FT, it's important to consider how software licenses are managed, especially when running redundant instances or creating secondary copies.
      Some software vendors may require separate licensing for each instance or copy of the application, while others may offer special provisions or licensing models for fault-tolerant configurations.
      It's essential to review the software license agreement and consult with the vendor to understand their licensing policies regarding fault tolerance.
      In the case of Kepware or similar applications, it's recommended to reach out to the vendor directly to inquire about their licensing policies for fault-tolerant deployments.
      They can provide you with the most accurate and up-to-date information regarding licensing requirements and considerations in such scenarios.
      Additionally, consider exploring options for license mobility or volume licensing agreements that may offer flexibility and cost savings for deploying redundant instances of the application.

    • @user-cz2sr1hl8f
      @user-cz2sr1hl8f Před 3 měsíci +1

      @@gnancloudgarage5238 Thank you.

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před 3 měsíci +1

      @@user-cz2sr1hl8f Welcome

  • @techsoftgame158
    @techsoftgame158 Před rokem +1

    Sir kindly make VMware Snapshots, DRS,Esxi got hang stae what will do.Deep drive.

  • @uffe3021
    @uffe3021 Před 6 měsíci +1

    but what will happen to the real primary VM when it's up again on another host, because the FT already creates a new secondary vm

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před 6 měsíci +1

      Automatic Handling by VMware FT:
      VMware FT is designed to handle these scenarios.
      If the primary VM is restarted on a different host, and the secondary VM is already running, FT will detect the conflict and initiate a new failover.
      The original secondary VM becomes the primary, and a new secondary VM is created on the host where the original primary VM was restarted.
      It's important to note that FT is designed to provide continuous availability in the event of a host failure.
      If the original primary VM becomes available again, FT ensures that the primary and secondary VMs are properly synchronized to avoid data inconsistencies.

    • @uffe3021
      @uffe3021 Před 6 měsíci

      yes but as i think, there is now 3 vm? 1. original primary vm, 2. the secondary vm (now primary cuz failover) 3. the new secondary vm it's just created, or it will not create a new secondary vm but take the original primary vm as primary again? or disapere the original primary vm? im confused

    • @uffe3021
      @uffe3021 Před 6 měsíci

      so the first primary VM (on ESXI1) will replace the "new secondary" VM (on ESXI3) because you have now second Primary Vm (on ESXI2). earlier primary on ESXI1 and secondary on ESXI2. then the secondary is now the primary on ESXI2 and the Primary from ESXI1 will move to ESXI3 and be the secondary?

  • @tainadesousadias3399
    @tainadesousadias3399 Před rokem +1

    Good afternoon. First, congratulations for the video. Two questions:
    1-If the host where the main VM is allocated fails, the replica VM takes over from the other host. But if the primary VM fails, can the replica VM take over or is this feature just for host incidents?
    2-Can we use Fault Tolerance for VMs with HD above 3 TB?
    Grateful.

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +2

      Hi,
      Very Good Afternoon!
      Thank you for your best wishes😊
      1) Yes, If the Primary VM fails, Secondary VM will take over within a fraction of seconds without interruption not only for Host incidents but also for any VM-related failures.
      2) Answer is we can not use over 3 TB Capacity because Fault Tolerance is not supported with a 2TB+ VMDK , refer to the below official article.
      docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-C1749AD4-70E2-406C-864C-719F54BF1BC1.html

    • @tainadesousadias3399
      @tainadesousadias3399 Před rokem +1

      @@gnancloudgarage5238, thank you.

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +2

      @@tainadesousadias3399 You're welcome

  • @ricardolopez6668
    @ricardolopez6668 Před 2 lety +1

    Hello, i have a question, in the video the FT was not successful right? i mean the vm was not on

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před 2 lety +1

      Hi Ricardo Lopez,
      Yes, There was an error initially because there is no FT-enabled VMkernel Port group.
      Hence, we were created the FT Port group and followed by FT Enabled on “windows10-vm01”
      FT Observation:
      • windows10-vm01 (primary) was powered on
      • Windows10-vm01 (secondary) was in a power-off state
      There were some warnings & errors due to a resources crunch in the home lab :-)
      Thank you

  • @ilovemyride1988
    @ilovemyride1988 Před rokem +1

    Hi,
    I´m searching long time now for a answer, but cant get it ...
    related question:
    The maxvcpusperhost can be set to 0. does that mean if i set it to 0 it is not supported?
    with enterprise plus i can use 8 vcpus per host, what, if i use 2 enterprise plus licenses for 1 host? ..but related to the question above with maxvcpusperhost set to 0?
    and also
    is it possible to assigne explicite cpu cores from the cpu for the ft vm?
    as an example, if I have 2 cpu's in the host, can I explicitly assign 8 cores of cpu2 (socket2) to the ft vm and the other cores to other vm?
    thanks,
    br

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +1

      Hi,
      Good Question!
      Here are the details for your review.
      das.maxftvcpusperhost:
      The maximum number of vCPUs aggregated across all fault-tolerant (FT) VMs on a host.
      The default value is 8. There is no FT vCPU per host maximum, We can use larger numbers if the workload performs well.
      We can deactivate checking by setting the value to 0 (Zero)
      Licensing:
      The number of vCPUs supported by a single fault-tolerant VM is limited by the level of licensing that We have purchased for vSphere.
      Fault Tolerance is supported as follows:
      • vSphere Standard and Enterprise. Allows up to 2 vCPUs
      • vSphere Enterprise Plus. Allows up to 8 vCPUs
      So, We can not assign two Ent+ Licenses for the same host and there is a limit as well, refer to the following FT Configuration Maximums.
      FT Configuration Maximums:
      • FT VMs per host = 4
      • FT vCPUs per host = 8
      • FT vCPUs per VM = 8
      Thank you

    • @ilovemyride1988
      @ilovemyride1988 Před rokem +1

      @@gnancloudgarage5238 Hi, thank you for your answer, but there is a question open:
      is it then supported if i deactivate the check and use 16vCPUS on a single FT VM on a host? because i dont understand why i can deactivate this check? in one thing it says theres a maximum of 8vCPU but on the other hand vmware says i can deactivate it? that makes no sense to me sorry :((
      thanks for your time!
      br, manuel

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +1

      @@ilovemyride1988
      Hi,
      Please refer to the inline response to your questions.
      • Can I increase to 16 vCPUs after deactivating “das.maxftvcpusperhost = 0”?
      “das.maxftvcpusperhost” cannot be increased, because it is limited by license conditions,
      But we might elect to reduce it, to prevent a host from being loaded too much.
      • Why can we deactivate this setting “da s.maxftvcpusperhost = 0”?
      • What VMware has given this option to deactivate (“das.maxftvcpusperhost = 0”) it?
       As we are aware,
       “das.maxftvmsperhost” whose default value is 4,
       “das.maxftvcpusperhost” whose default value is 8
       These above two values can be decreased but an increase is not recommended due to license limitations.
       For example FT VMs Groupings based on Ent+ License such as follows
       8 vCPU limit = 1 VM with 8 vCPUs
       8 vCPU limit = 2 VMs with 4 vCPUs
       8 vCPU limit = 4 VMs with 2 vCPUs
       8 vCPU limit = 1 VM with 4 vCPUs + 2 VMs with 2 vCPUs
       8 vCPU limit = 1 VM with 4 vCPUs + 1 VM with 2 vCPUs + 2 VMs with 1 vCPU
       The reason VMware gave deactivate option, There are scenarios to power on VM or VMotion more FT VMs to one host, and moving one of the existing FT VMs to another host is a challenging situation.
       Hence disable this restriction by setting the value to 0 during that challenging scenario only .
      Thank you

    • @ilovemyride1988
      @ilovemyride1988 Před rokem +1

      @@gnancloudgarage5238
      Hi,
      Thank you for your explanation, the vmware documents just don't make sense to me, because it's somehow ambiguous and it doesn't mention when which scenario is supported! If I understand your answers correctly now, it is not supported to use more than 8vCPUs per HOST for FT, right? and this cannot be changed with a second enterprise plus license for a host either, right?
      you can only disable it but it is not supported and recommended
      So if I want to use 2 vm's with 8vCPU each, I absolutely need 4 hosts with 4 enterprise plus licenses (in my scenario this would be a VSAN cluster, i.e. 4 host + witness, do I understand that correctly?
      I really want to thank you for your time!

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +1

      @@ilovemyride1988
      Hi,
      Yes, It is right.
      Thank you

  • @nagasekhar2689
    @nagasekhar2689 Před rokem +1

    Hi master, in FT shared files two VMs are sharing a datastore. But two FT must have different data stores right. This make me confused. Pls me in understand

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +1

      Hi Naga Sekhar,
      Yes, VMs will use separate datastores only and refer to the vSphere FT architecture ( Video Time 10:30) for better understanding.
      Thank you.

    • @nagasekhar2689
      @nagasekhar2689 Před rokem +1

      @@gnancloudgarage5238 yes sir I agree with you about separate datastore for both primary and secondary machines.
      At 42:28 in the slide it mentioned that two VMs have a shared.vmft

    • @gnancloudgarage5238
      @gnancloudgarage5238  Před rokem +1

      ​@@nagasekhar2689​
      Hi Sir,
      As we are aware vSphere FT Provides fast checkpointing (means continuous copying) to keep primary and secondary VMs synchronized.
      In this process, there are vSphere FT Shared files (shared. vmft) and There should be some purpose when we have share files.
      shared. vmft contains the primary and secondary VMs UUIDs of Primary and secondary VMX paths.
      Hence, It will lead to two active copies of a VM after recovery from a failure.
      For example:
      In general, there is a witness signature for any house registrations :-)

      Similarly, this shared.vmft is a witness (Observer or Evidence) that which UUID belongs to Primary VM and which UUID belongs to Secondary VM.
      So that there will be no conflicts in case of any unexpected issues on one of the VMs.
      That is the reason in our Slide(42:28), We have kept the heading as vSphere FT Shared Files and not secondary VM.
      Reference article: kb.vmware.com/s/article/2116110
      Hope it clarifies for you.
      Please let me know if you have any questions.
      Thank you