(c)We Want to Hear from You



Essential Virtual SAN

First Edition

Copyright © 2015 VMware, Inc.

ISBN-10: 0-13-385499-X

ISBN-13: 9780-13-385499-2

Warning and Disclaimer

Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an "as is" basis. The author and the publisher shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book or from the use of the CD or programs accompanying it.

When reviewing corrections, always check the print number of your book. Corrections are made to printed books with each subsequent printing.

First Printing: August 2014

Corrections for September 26, 2014

|Pg |Error – First Printing |Correction |

|88 |Chapter 5, Purpose of Write Cache, Second Paragraph, Fourth Sentence |Should read: |

| |Reads: | |

| |Once a write is initiated by the application running inside of the guest OS, the |Once a write is initiated the write is sent to all replicas in parallel. |

| |write is forked to both the local write cache on the owning host, and to the write| |

| |cache on the remote host or hosts. | |

|97 |Chapter 5, Last Paragraph, First Sentence |Should read: |

| |Reads: | |

| |So in this case, if read cache misses were occurring in your VSAN, increasing the |So in this case, if read cache misses were occurring in your VSAN, increasing stripeWidth may |

| |stripe width will improve the performance for I/Os that need to be serviced from |improve the performance for I/Os that need to be serviced from magnetic disk, if a single spindle |

| |magnetic disk, if a single spindle was not enough to handle the requests. |was not enough to handle the requests. |

|166 and |Chapter 7, vCenter Management, First Paragraph, Last Sentence |Should read: |

|167 |Reads: | |

| |If vCenter Server was available, that service would also be temporarily |If vCenter Server was unavailable, that service would also be temporarily unavailable; in the case |

| |unavailable; in the case of vSphere DRS, this meant that no load balancing would |of vSphere DRS, this meant that no load balancing would occur during this time. |

| |occur during this time. | |

|231 |Chapter 10, osls-fs, Heading and First Sentence |Should read: |

| |Reads: | |

| |osls-fs |osfs-ls |

| |osls-fs is more of a troubleshooting command than anything else. |osfs-ls is more of a troubleshooting command than anything else. |

|243 |Chapter 10, , Heading and Second Sentence and Fourth Sentence |Should read: |

| |Reads: | |

| | |disks_info |

|253 |Chapter 10, resync.dashboard, Heading and First Sentence |Should read: |

| |Reads: | |

| |resync.dashboard |resync_dashboard |

Corrections for September 8th, 2014

|Pg |Error – First Printing |Correction |

| |Note * | |

| |vsan.host_stats command has been replaced by two new RVC commands. | |

| |Host_stats references need to be replaced by two new commands, host_info and | |

| |vsan.whatif_host_failures | |

|61 |Chapter 4, Flash Rad Cache Reservation, Second Paragraph, Fourth Sentence |Should read: |

| |Reads: | |

| |If you add this capability to the VM storage policy and set it to a value 0 |If you add this capability to the VM storage policy and set it to a value 0 (zero), however, you |

| |(zero), however, you will not have any read cache assigned to the VM that uses |will not have any read cache reserved to the VM that uses this policy. |

| |this policy. | |

|88 |Chapter 5, Purpose of Write Cache, Second Paragraph, Second Sentence |Should read: |

| |Reads: | |

| |All VMs deployed to VSAN have an availability policy setting that ensures at least|All VMs deployed to VSAN have an availability policy setting that ensures at least one additional |

| |one additional copy of VM data is available. |copy of VM data is available, unless a policy has been selected which explicitly defines the number |

| | |of failures to tolerate as 0. |

|88 |Chapter 5, Anatomy of a VSAN Read, Second Paragraph, Second Sentence |Should read: |

| |Reads: | |

| |If the block is present in read cache on owner, the read is serviced from the SSD |If the block is present in read cache, the read is serviced from the SSD read cache. |

| |read cache. | |

|93 |Chapter 5, Last Paragraph, Fourth Sentence |Should read: |

| |Reads: |But what is this witness component on host 18? |

| |But what is this witness object on host 18? | |

|100 |Chapter 5, Stripe Width Maximum, Third Sentence |Should read: |

| |Reads: | |

| |Remember that when you specify a stripe width and an FTT value, there has to be at|Remember that when you specify a stripe width and an FTT value, there has to be at least stripe |

| |least stripe width (SW) x FTT number of spindles before VSAN is able to satisfy |width (SW) x (FTT+1) number of spindles before VSAN is able to satisfy the policy requirement. |

| |the policy requirement. | |

|105 |Chapter 5, First Bullet Point |Should read: |

| |Reads: | |

| |NumberofFailuresToTolerate for VM Swap is set to 1. This gives us a RAID-1 |hostFailuresToTolerate for VM Swap is set to 1. This gives us a RAID-1 (mirror) configuration for VM|

| |(mirror) configuration for VM Swap. |Swap. |

|110 |Chapter 5, Second Paragraph, Sixth Sentence |Should read: |

| |Reads: | |

| |To have a quorum majority, the two remaining components would require five objects|To have a quorum majority, the remaining hosts would require five components to achieve a majority. |

| |to achieve a majority. | |

|124 |Chapter 6, Figure 6-11 |Replace with: |

| | |[pic] |

|145 |Chapter 7, Number 4 |Should Read: |

| |Reads: | |

| |4. When maintenance mode has completed, right-click the host again and select |4. When maintenance mode has completed, right-click the host again and select Move To to move the |

| |Remove from Inventory under All vCenter Actions. |host outside of the cluster. |

|166 thru |Chapter 7, vCenter Management, Third Sentence |Should read: |

|167 |Reads: | |

| |If vCenter Server was available, that service would also be temporarily |If vCenter Server was unavailable, that service would also be temporarily unavailable; in the case |

| |unavailable; in the case of vSphere DRS, this meant that no load balancing would |of vSphere DRS, this meant that no load balancing would occur during this time. |

| |occur during this time. | |

|194 |Chapter 8, Figure - 15 Caption |Should read: |

| |Reads: | |

| |VSAN and vCloud automation center interoperability |VSAN and vCloud Automation Center interoperability |

|199 |Chapter 9, Failures to Tolerate = 1, Stripe Width = 1, First Paragraph, Second |Should read: |

| |Sentence | |

| |Reads: |If snapshot gets created on that VM, the component count increases by another two per disk, |

| |If snapshot gets created on that VM, the component count increases by another two |resulting in 12 in total (not even including witnesses yet): |

| |per disk, resulting in 12 in total: | |

|200 |Chapter 9, Second Paragraph, |Should read: |

| |Reads: | |

| |We will not run though this exercise for each of the following three scenarios, as|We will not run through this exercise for each of the following three scenarios, as we expect that |

| |we expect that the majority of environments will not come close, but we do believe|the majority of environments will not come close, but we do believe that it is important to |

| |that it is important to understand these constraints. |understand these constraints. |

|213 |Chapter 9, First Sentence after First set of Bullet Points |Should read: |

| |Reads: | |

| |To provide 170GB of flash capacity per host, we need one 200GB flash device per |To provide 170GB of flash capacity per host, we need two 100GB flash device per host. |

| |host. | |

|123 |Chapter 9, Last Bullet Point |Should read: |

| |Reads: | |

| |1 x 200GB SSD SAS (WI) |2 x 100GB SSD SAS (WI) |

|220 |Chapter 9, First Sentence |Should read: |

| |This is what each host configuration will look like for the 20 HPDL350p (25 SFF) |This is what each host configuration will look like for the 20 HPDL380p (25 SFF) hosts consisting of|

| |hosts consisting of the following: |the following: |

|250 |Chapter 10, Heading |Should read: |

| |Reads: | |

| |hosts_stats, disk_stats, and vm_perf_stats |host_info. vsan.whatif_host_failures, disk_stats, and vm_perf_stats |

|250 |Chapter 10, Third Sentence under section hosts_stats, disk_stats, and |Should read: |

| |vm_perf_stats | |

| | | |

| |Reads: |Let’s begin with the whatif_host_failures command. |

| | | |

| |Let’s begin with the host_stats command. | |

|250 |Chapter 10, Sixth Sentence under section hosts_stats, disk_stats, and |Should read: |

| |vm_perf_stats | |

| | |In this example, we navigated to the cluster object in the inventory and ran the |

| |Reads: |vsan.whatif_host_failures command from there, selecting the full cluster as an argument: |

| | | |

| |In this example, we navigated to the cluster object in the inventory and ran the |/mia-cg07-vcsa01/CG07-DC01/computers> vsan.whatif_host_failures 0 |

| |vsan.hosts_stats command from there, selecting the full cluster as an argument: |Simulating 1 host failures: |

| | |+-----------------+-----------------------------+-----------------------------------+ |

| | || Resource | Usage right now | Usage after failure/re-protection | |

| | |+-----------------+-----------------------------+-----------------------------------+ |

| | || HDD capacity | 66% used (3044.69 GB free) | 75% used (1926.94 GB free) | |

| | || Components | 3% used (23376 available) | 3% used (20376 available) | |

| | || RC reservations | 0% used (667.73 GB free) | 0% used (584.27 GB free) | |

| | |+-----------------+-----------------------------+-----------------------------------+ |

| | |/mia-cg07-vcsa01/CG07-DC01/computers> |

|250 thru |Chapter 10 |Replace with: |

|251 |Replace all that Reads: | |

| |vsan.hosts_stats |vsan.whatif_host_failures |

This errata sheet is intended to provide updated technical information. Spelling and grammar misprints are updated during the reprint process, but are not listed on this errata sheet.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download