- Paperback: 128 pages
- Publisher: Brio Press (September 1, 2011)
- Language: English
- ISBN-10: 1937061981
- ISBN-13: 978-1937061982
- Product Dimensions: 7 x 0.2 x 9.8 inches
- Shipping Weight: 9.6 ounces (View shipping rates and policies)
- Average Customer Review: 21 customer reviews
- Amazon Best Sellers Rank: #2,003,017 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
Critical VMware Mistakes You Should Avoid Paperback – September 1, 2011
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
About the Author
Larry Loucks is a former VMware Senior Consultant and Instructor. He also serves as a corporate presenter for one of the largest software companies in the world and is a renowned expert on virtualization and disaster recovery.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Larry Loucks and his book "Critical VMWare Mistakes - you should avoid" is such a resources.
If you are implementing your first virtualization or are struggling with performance issues afterward, this book covers the most likely culprits.
In my case, years of experience needed to be updated to understand why some of my "best practices" needed to be reevaluated.
The simple implementation of a single edict with regard to CPU allocation resolved my issue.
This book is easy to read and I suggest that it be read through from cover to cover.
Then go back and read the chapters that were surprising to you.
I am on my third read and ready to tackle a networking strategy that is relevant whether you are virtualizing or not.
which is also a good book, however you can tell that "Critical VMWare Mistakes you should avoid" was written by WORKING people in the field. This book has shined light on issues we have been having in our production environment, and directly addresses some of the questions that were asked of me on an interview "that sadly I didn't get". If I would have read this book before the interview I think I would have gotten the position.
For every one who's trying to take that "next step" in their VMWare career path this is a wonderful book to start you on that direction. I did notice some of the proof reading issues mentioned by other reviewers, but honestly I don't care. It's clear this book was written by a working IT professional, and lets be honest documenting any thing isn't our strong suit.
This is a must read any one looking to get into VMWare virtualization, or seeking to weed out problems in their VMWare deployment. I particularly liked the chapters on SAN/NAS, and CPU configuration.
Wonderful book for the working professional.
This book is targeted towards individuals that are still very new to Virtualization and VMware in particular. I was under the impression that this book would tackle more advanced issues and means of detection such as SAN path-thrashing or virtual machine performance analysis. This book does not go into depth for these types of issues.
That being said, this book does go over a number of common mistakes individuals new to virtualization often make such as over-allocation of resources, confusing space with IOPS, expanding the subnet instead of creating more networks using VLANs/routers/ACLs, placing management in the same network as clients, etc. I did think that Mr. Loucks did a good explanation of CPU RDY time for this target audience. The actual whitepapers on this topic, for example, [...], are extremely deep, much deeper than most individuals in this target audience will need/want to get. Other than storage issues, this is the most common mistake I see by some of the clients I have worked with in my career.
I agree with another reviewer about this book feeling dated. It was not updated for 4.1 or higher for the chapter on memory as there is no mention of memory compression or swap to SSD. The copyright renewal of 2011 appears to have been just a renewal with potentially a few small revisions. Also, Mr. Loucks has a strong opinion on thin-provisioning and separating workloads on different spindles. While I agree to some extent most notably about people who buy their storage solely on capacity without any IOPS analysis - you should always review the best practices of the storage manufacturer. Your storage should be on the VMware HCL for all production workloads. All mainstream manufacturers (NetApp/EMC/Compellent/HP/etc) have dedicated whitepapers on VMware best practices that are specific to the array model and the connectivity in place - iSCSI/FC/NFS. Mr. Loucks beliefs of storage appear that he has a lot of familiar with traditional (legacy) storage designs. Although the book doesn't list names, I was given an impression that he has worked with a lot of EMC gear before the migration to virtualized storage. Leading manufacturers virtualize storage as a way to manage IOPS in the array and to save both capex and opex costs. Automated Storage Tiering (EMC VNX/Compellent) and the Virtual Storage Tier (NetApp) are all valid approaches to dealing with IOPS issues while decreasing the need for large numbers of SSD/15K SAS drives. As a bonus, this simplifies management and reduces operating expenditures. Only the largest clients will have a team of dedicated storage administrators. True, you will create pools for different workload needs. A Tier I application at a Fortune 500 company will not be anywhere near my other applications. In many designs, all virtual machines will run in the same storage and this isn't a design flaw. You still need to size IOPS appropriately. Never build your design around space - nearly all smart arrays will either deduplicate/thin-provision/compress or they will demote cold data to slower storage, allowing you to get more data on your faster spindles.
In summary, I think this book, while dated, is useful to a system administrator who has to wear a lot of caps in his environment - network, application, systems, storage, and virtualization administration. This book will provide less value to vSphere administrators.
Also every argument was analyzed very superficially, without really diving in technical explanations could help reader to better understand them, and to better use them on the field.
Not enough interesting to be a book to be bought.
The idea was good; but whole book need to be rewrote from scratch, with more information, and going more in deep about technically issues and explanations.
Instead, it's the field experiences of a consultant who's been called in to fix lots of broken vmware installations. He knows the mistakes that people tend to make.
These lessons include information on how vmware works; a little understanding really goes a long way to making good design decisions.
The book isn't long, but that's ok. It's concise and readable, and well worth the investment for any vmware admin. I've been doing it for several years in an SMB environment. I am not an expert but I know my way around, and I've built a good-performing environment. I've learned a few things from the book, and if I'd read it when I was starting out with my vmware farm it would have saved me some pain.
Most recent customer reviews
In the introduction to Critical VMware Mistakes You Should Avoid, co-author Larry Loucks notes that this book gives IT personnel the benefit of years...Read more
All material covered in this book, more or less, already exists in the course documentation for a regular VMware vSphere Install &...Read more