Absolutely awesome! I watched all 12 videos in one sitting - which was totally *not* what I planned. Useful, practical information, presented in a straight forward, understandable manner. Excellent detail in easily digestible increments. Took copious notes; learned and clarified tons about this technology. Presentation flowed naturally, with each video setting up the foundation for the next. All terms explained in sufficient detail to be able to understand the necessary nuances of more complex concepts. Delivery pulls in the audience. This has been added to my library of "go to" references because it is devoid of marketing/sales spin and vague techno-babble. Every video filled with usable, essential information. Well done, Elver. Well done indeed. Looking forward to more of your videos.
hi , this is phenomenal series, watched all videos in one go, never got the whole idea of stretched clusters till i watch this video. thank you and GOD bless you, prayers and specials thanks to you all the way from islamabad pakistan
thank you so much for this series of vSAN. i learnt a lot. i saw a lot of videos nearly one hour long, did projects for implementation for vsphere and vSAN but still was vague about some concepts. and i got those cleared. again thank you so much this series. WAITING FOR ANY SERIES WHICH EXPLAINS MORE DEEPLY THE CONCEPTS OF vSAN and problems admin face in day to day operations. like object synchronization, re balance, error during maintenance mode , how components get divided and on what size scale. how to maintain health checks and remove inaccessible objects including more details on stretched cluster .
This was a great series to watch, thanks! I did feel a little confused about the block level drive setup though. Kind of wish you'd spent more time talking about physical drives, where they can go, why they aren't using a hardware RAID controller, how to recover from failed drive, etc. I have the resources I need to learn about this on my own but it would have made the video series that much more perfect. :)
Thank you so much for this series of vSAN. Very easy-to-watch series , to the point and very well explained, i will look fwd for more videos from you. thanks again for the vSan 100 Series...
RPO=0 sounds very idealistic as it depends on your network pipe and SAN configured b/w two data centers. Latency and recovery time can vary as we don't live in a perfect world.
so basically, redundant wan links are mandatory between sites, because failure of that wan will mean no ack for writes to the stretched cluster and therefore bring down the whole cluster?
Question: Does the Witness FD3 VM have to be in the third physical location? Can it be a VM in one of the DCs protected by HA or even by F\T? Or can I have 4 Fault Domains 2 of which are VM witnesses each in it's own DC?
RPO=0 agree, but in case corruption or human mi stack in site-1 hosts then the corrupted block will be replicate as well to site-2 then RPO will not chive zero any more, therefor you need the third site to replicate data in Async mode to have a delayed updated copy in the third site.
I don't think a third site would solve the problem you raised. the corruption would propogate to the 3rd one eventually. What you need is a versioned backup of data
![Chlöe - Shake (Feat. Jeremih) [Official Visualizer]](http://i.ytimg.com/vi/aDs_1ufpfv8/mqdefault.jpg)
This was an entertaining and very easy-to-watch series on vSAN which anyone in the field would benefit from. Great work!
Absolutely awesome! I watched all 12 videos in one sitting - which was totally *not* what I planned. Useful, practical information, presented in a straight forward, understandable manner. Excellent detail in easily digestible increments. Took copious notes; learned and clarified tons about this technology. Presentation flowed naturally, with each video setting up the foundation for the next. All terms explained in sufficient detail to be able to understand the necessary nuances of more complex concepts. Delivery pulls in the audience. This has been added to my library of "go to" references because it is devoid of marketing/sales spin and vague techno-babble. Every video filled with usable, essential information. Well done, Elver. Well done indeed. Looking forward to more of your videos.
hi , this is phenomenal series, watched all videos in one go, never got the whole idea of stretched clusters till i watch this video. thank you and GOD bless you, prayers and specials thanks to you all the way from islamabad pakistan
thank you so much for this series of vSAN. i learnt a lot. i saw a lot of videos nearly one hour long, did projects for implementation for vsphere and vSAN but still was vague about some concepts. and i got those cleared. again thank you so much this series. WAITING FOR ANY SERIES WHICH EXPLAINS MORE DEEPLY THE CONCEPTS OF vSAN and problems admin face in day to day operations. like object synchronization, re balance, error during maintenance mode , how components get divided and on what size scale. how to maintain health checks and remove inaccessible objects including more details on stretched cluster .
This was a great series to watch, thanks! I did feel a little confused about the block level drive setup though. Kind of wish you'd spent more time talking about physical drives, where they can go, why they aren't using a hardware RAID controller, how to recover from failed drive, etc. I have the resources I need to learn about this on my own but it would have made the video series that much more perfect. :)
Thank you so much for this series of vSAN. Very easy-to-watch series , to the point and very well explained, i will look fwd for more videos from you. thanks again for the vSan 100 Series...
Watched all these in a row, AMAZING!
You are really Awesome sir ... You have cleared all my VSAN doubts in just 12 small but informational videos...Thank you :-)
Great video! vSAN has me intrigued and loved learning about Stretched clusters and fault domains. Great work!
Thank you man, great videos and great explanations!
Excellent job! Loved this series.
Thank you for this series, quick and informative
Love your videos. Very Informative 🤝🏽
So nice! Magaling!
Really good explanation, Love it :-)
RPO=0 sounds very idealistic as it depends on your network pipe and SAN configured b/w two data centers. Latency and recovery time can vary as we don't live in a perfect world.
Me encanta los videos... gracias hermano!
thank you sir!
so basically, redundant wan links are mandatory between sites, because failure of that wan will mean no ack for writes to the stretched cluster and therefore bring down the whole cluster?
Will there be a video about compression/deduplication?
Question: Does the Witness FD3 VM have to be in the third physical location? Can it be a VM in one of the DCs protected by HA or even by F\T? Or can I have 4 Fault Domains 2 of which are VM witnesses each in it's own DC?
RPO=0 agree, but in case corruption or human mi stack in site-1 hosts then the corrupted block will be replicate as well to site-2 then RPO will not chive zero any more, therefor you need the third site to replicate data in Async mode to have a delayed updated copy in the third site.
I don't think a third site would solve the problem you raised. the corruption would propogate to the 3rd one eventually. What you need is a versioned backup of data
The worst thing about Elver, is that he didn't make more videos across the internet.
software for 2 node 4 socket cluster $50k, not including disks, mem or servers.