Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Getting Started with VMware Virtual SAN

You're reading from   Getting Started with VMware Virtual SAN Build optimal, high-performance, and resilient software-defined storage on VSAN for your vSphere infrastructure

Arrow left icon
Product type Paperback
Published in May 2015
Publisher
ISBN-13 9781784399252
Length 162 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Cedric Rajendran Cedric Rajendran
Author Profile Icon Cedric Rajendran
Cedric Rajendran
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. An Introduction to Software-defined Storage and VSAN FREE CHAPTER 2. Understanding Virtual SAN 3. Workload Profiling and Sizing 4. Getting Started with VSAN – Installation and Configuration 5. Truly Software-defined, Policy-based Management 6. Architecture Overview 7. Design Considerations and Guidelines 8. Troubleshooting and Monitoring Utilities for Virtual SAN 9. What's New in VSAN 6.0? Index

VSAN and high availability


A very crucial aspect of any product or solution is how it is able to sustain failure. With a VSAN infrastructure, this becomes all the more critical, since failure with its components may lead to data unavailability or data loss.

VSAN and high availability (HA) are interoperable thus far with vSphere, high availability was concerned with virtual machine availability. With the introduction of VSAN into the equation things are slightly different. In short, vSphere HA with VSAN is object centric. Here, we will assess the key components that make up VSAN, their failure scenarios, and how availability is ensured.

Primary components that attribute to availability are as follows:

  • Magnetic disks

  • Flash devices

  • Host/network related failures

The key thing to remember is that all of the component failures are directly related to the Number of failures to tolerate setting. As long as the actual number of failures is lower than the configured failure threshold, there is no data loss...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image