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

Gnan Cloud Garage

Подписаться 9 тыс.

Просмотров 4,8 тыс.

50% 1

Видео Поделиться Скачать Добавить в

Опубликовано:

22 мар 2022

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 33

@harisingh1983 2 года назад

superb video !! deep knowledge

@gnancloudgarage5238 2 года назад

Thanks a lot

@joginderpal6943 Год назад

In Depth Explanation Sir ... Gnan Cloud Garage Rocking

@gnancloudgarage5238 Год назад

Thank you so much Joginder Sir

@user-yb3pk2ns8n 9 месяцев назад

good explanartion

@gnancloudgarage5238 9 месяцев назад

Thank you

@gnancloudgarage5238 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 ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-A2MoQ-UdXEA.html ============================================================ 1. VMware Datacenter Virtualization Basics ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-cM3NuUxurpk.html 2. Basic Server Fundamentals and Windows Server 2022 ACTIVE Directory AD Configuration ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-T4JewBlbBwI.html 3. VMware Data Center Virtualization |VCP DCV_ ICM Architectural Differences, Virtual Machines ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-BhSvDa_62aI.html 4. VMware DCV ICM ESXi Host Build Procedure and Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-94rZQYAim-0.html 5. VMware DCV ICM ESXi Host Configuration and Management | ESXi Host Components & Log Files ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-g5fwp9QNkTc.html 6. VMware DCV ICM ESXi Host Networking & Basics of Networking ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UsGnF0FFnjM.html 7. VMware DCV ICM ESXi Host Networking & IP Addressing ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-3YHTEkaizT0.html 8. VMware DCV ICM ESXi Networking & IP Address Classification & Reserved IPs ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-yt0V0Vb1rR8.html 9. VMware DCV ICM ESXi Host Networking Standard vSwitch ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE--FmkOUi6cNY.html 10. vSphere 7.x - ESXi Host Networking - vSwitch Policies & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-rCTICm7sPQw.html 11. vSphere 7.x | vCenter Server 7.0 Architecture & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-_cr2dHIMPOI.html 12. vSphere 7.x vCenter Server 7.0 Install, Configure, Manage & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-OR5PlxJxfWY.html 13. vSphere 7.x Architecture ,SDDC ,Inventory Objects Overview & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Qo8FqPMNsyw.html 14.vSphere 7.x - vCenter Inventory Objects & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-nRomjn5VQY4.html 15. vSphere 7.x - vSphere Storage Concepts & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-H16rvMSnoCM.html 16. vSphere 7.x vSphere Storage - NFS Datastore Configuration | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-sErpXMXCyfY.html 17. VMware vSphere 7. x Storage - How to Configure NFS Datastore on Windows Server 2022 | Homelab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-wRRidfq-XBk.html 18. vSphere 7 Storage - How to Configure iSCSI SAN on ESXi host using Windows Server 2022 | Homelab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-yRE3eD5mcUQ.html 19. vSphere 7.x | FC Storage & FCoE Storage Architectures | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-dRtY70XheJY.html 20. vSphere 7.x | Virtual SAN vSAN Architecture | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ajLX_MMzGyQ.html 21. vSphere 7.x Virtual Volumes (vVols) Architecture | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Zso7By96JeQ.html 22. vSphere 7. x Virtual Volumes (vVols) Architecture | Real-Time Scenarios | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-g7CB_OfIj2k.html 23.vSphere 7.x vSAN , vVols, Distributed vSwitch & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-2G4mCPg-IOA.html 24.vSphere 7.x VMs, Snapshot, Clone, Templates | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-S7owYwhDhk4.html 25 . VM Snapshot, Clone, Templates | Windows Server OS Upgrade from 2019 to 2022 | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-NEPpaozsGU4.html 26.vSphere 7. x | VM Migration Methods Cold Migration, Suspended, vMotion, EVC, SvMotion & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-aeWT6857_hE.html 27.VMware vCenter Converter Standalone - P2V, V2V, Hyper-V VM2V| Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-gCBCrzziI6U.html 28. VMware Converter - Converting from Workstation VM to vSphere VM (V2V) | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-G71jYzqxPok.html 29. vSphere 7. x - Clusters, DRS, DPM, vCLs, HA, FT and Protecting Data | Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-MPFoqiuX0D0.html 30. vCenter Cluster Feature - High Availability (HA), Protecting Data using Veeam & Home Lab ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-QBD9IDwxjOU.html

@user-cz2sr1hl8f 3 месяца назад

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 3 месяца назад

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 3 месяца назад

@@gnancloudgarage5238 Thank you.

@gnancloudgarage5238 3 месяца назад

@@user-cz2sr1hl8f Welcome

@techsoftgame158 Год назад

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

@gnancloudgarage5238 Год назад

Hi Sir, Sure will do that. Thanks

@tainadesousadias3399 Год назад

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 Год назад

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 Год назад

@@gnancloudgarage5238, thank you.

@gnancloudgarage5238 Год назад

@@tainadesousadias3399 You're welcome

@ricardolopez6668 2 года назад

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

@gnancloudgarage5238 2 года назад

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 Год назад

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 Год назад

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 Год назад

@@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 Год назад

@@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 Год назад

@@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 Год назад

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

@uffe3021 6 месяцев назад

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 6 месяцев назад

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 6 месяцев назад

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 6 месяцев назад

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?

@nagasekhar2689 2 года назад

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 2 года назад

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 2 года назад

@@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 2 года назад

@@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