Book Image

VMware vSphere 6.5 Cookbook - Third Edition

By : Abhilash G B, Cedric Rajendran
Book Image

VMware vSphere 6.5 Cookbook - Third Edition

By: Abhilash G B, Cedric Rajendran

Overview of this book

VMware vSphere is a complete and robust virtualization product suite that helps transform data centers into simplified on-premises cloud infrastructures, providing for the automation and orchestration of workload deployment and life cycle management of the infrastructure. This book focuses on the latest release of VMware vSphere and follows a recipe-based approach, giving you hands-on instructions required to deploy and manage a vSphere environment. The book starts with the procedures involved in upgrading your existing vSphere infrastructure to vSphere 6.5, followed by deploying a new vSphere 6.5 environment. Then the book delves further into the procedures involved in managing storage and network access to the ESXi hosts and the virtual machines running on them. Moving on, the book covers high availability and fair distribution/utilization of clustered compute and storage resources. Finally, the book covers patching and upgrading the vSphere infrastructure using VUM, certificate management using VMCA, and finishes with a chapter covering the tools that can be used to monitor the performance of a vSphere infrastructure.
Table of Contents (18 chapters)

Managing VMFS volumes detected as snapshots

Some environments maintain copies of the production LUNs as a backup, by replicating them. These replicas are exact copies of the LUNs that were already presented to the ESXi hosts. If for any reason a replicated LUN is presented to an ESXi host, then the host will not mount the VMFS volume on the LUN. This is a precaution to prevent data corruption.

ESXi identifies each VMFS volume using its signature denoted by a UUID (Universally Unique Identifier). The UUID is generated when the volume is first created or resignatured and is stored in the LVM header of the VMFS volume.

When an ESXi host scans for new LUN; devices and VMFS volumes on it, it compares the physical device ID (NAA ID) of the LUN with the device ID (NAA ID) value stored in the VMFS volumes LVM header. If it finds a mismatch, then it flags the volume as a snapshot volume...