Beruflich Dokumente
Kultur Dokumente
VM Management
Day 4
VMware vSphere:
Install, Configure, Manage
Content
• Virtual Storage
• NFS
• iSCSI
• Clone, Template, Snapshot
• vApp
• Content Library
Virtual Storage
Module Lessons
Storage Concepts
iSCSI Storage
NFS Datastores
VMFS Datastores
Virtual SAN Datastores
Virtual Volumes
Storage Concepts
Learner Objectives
By the end of this lesson, you should be able to meet the following
objectives:
• Describe VMware vSphere® storage technologies and datastores
• Describe the storage device naming convention
Basic Storage Overview
ESXi
Hosts
File
System
Fibre ● ● ● ● ●
Channel
FCoE ● ● ● ● ●
iSCSI ● ● ● ● ●
NFS ● ● ●
DAS ● ●
Virtual
● ● ●
Volumes
Virtual SAN ● ● ●
About Datastores
A datastore is a logical storage unit
that can use disk space on one
physical device or span several
physical devices.
Datastores are used to hold virtual
machine files, templates, and ISO Host Host
images.
Types of datastores:
• VMFS
• NFS
• Virtual SAN
• Virtual Volumes
Datastore
About VMFS5
VMFS5:
• Allows concurrent access to
shared storage.
• Can be dynamically expanded.
• Uses a 1 MB block size, good
Host Host
for storing large virtual disk
files.
• Uses subblock addressing,
good for storing small files: the
subblock size is 8 KB.
• Provides on-disk, block-level
locking.
VMFS Datastore
About NFS
NFS:
• Is storage shared over the
network at the file system
level
• Supports NFS version 3 and
4.1 over TCP/IP Host Host
NFS Datastore
Virtual SAN Overview
Virtual SAN™ is hypervisor-converged, software-defined storage for
virtual environments.
By clustering host-attached hard disks (HDDs) and/or solid state drives
(SSDs), Virtual SAN creates an aggregated datastore shared by virtual
machines.
Virtual SAN
vSphere
3-64
HDD/Flash/SSD
Overview
Virtual Volumes
SAN/NAS: No LUNs or volume management.
.vmdk Raw
.vmdk
-flat.vmdk -rdm.vmdk LUN
iSCSI Target:
192.168.36.101:3260
iSCSI Security: CHAP
iSCSI initiators use
CHAP for authentication
purposes.
By default, CHAP is not
configured.
ESXi supports two types
of CHAP authentication:
• Unidirectional
• Bidirectional
192.168.81.33
192.168.81.72
ESXi Host with
VMkernel Port
NIC Mapped to
Defined on Virtual
Virtual Switch
Switch
Configuring an NFS Datastore
Create a VMkernel port:
• For better performance and security, separate your NFS network from the
iSCSI network.
Provide the following information:
• NFS version: v3 or v4.1
• Datastore name
• NFS server names or IP addresses
• Folder on the NFS server, for example, /templates and /nfs_share
• Select hosts that will mount the datastore
• Whether to mount the NFS file system read-only
• Authentication parameters
NFS v3 and NFS v4.1
NFS v3: NFS v4.1:
• ESXi managed multipathing • Native multipathing and session
• AUTH_SYS (root) authentication trunking
• VMware proprietary file locking • Optional Kerberos authentication
ESXi Host
Enabling Session Trunking and Multipathing
Multiple IP addresses are configured for each NFS v4.1 datastore.
192.168.0.203, 192.168.0.204
Review of Learner Objectives
You should be able to meet the following objectives:
• Describe NFS components
• Describe the differences between NFS v3 and NFS v4.1
• Configure and manage NFS datastores
VMFS Datastores
Learner Objectives
By the end of this lesson, you should be able to meet the following
objectives:
• Create a VMFS datastore
• Increase the size of a VMFS datastore
• Delete a VMFS datastore
Using VMFS Datastores with ESXi Hosts
Use VMFS datastores whenever possible:
• VMFS is optimized for storing and accessing large files.
• A VMFS datastore can have a maximum volume size of 64 TB.
Use RDMs if the following conditions are true of your virtual machine:
• It is taking storage array-level snapshots.
• It is clustered to a physical machine.
• It has large amounts of data that you do not want to convert into a virtual disk.
Creating and Viewing VMFS Datastores
VMFS datastores serve as repositories for virtual machines.
Using the New Datastore wizard, you can create VMFS datastores on
any SCSI-based storage devices that the host discovers, including Fibre
Channel, iSCSI, and local storage devices.
Browsing Datastore Contents
Managing Overcommitted Datastores
A datastore becomes overcommitted when the total provisioned space of
thin-provisioned disks is greater than the size of the datastore.
Actively monitor your datastore capacity:
• Alarms assist through notifications:
– Datastore disk overallocation
– Virtual machine disk usage
Virtual SAN
vSphere
3-64
1 Gb or 10 Gb NIC
Network
Server on
vSphere HCL SAS/SATA: RAID
Controller controller must work in
passthrough or HBA mode.
Capabilities VM
Create policies
presented requirements
that contain VM
from Virtual based on
requirements.
SAN. capabilities.
Objects in Virtual SAN Datastores
In a Virtual SAN datastore, files are grouped into four types of objects:
• Namespaces
• Virtual disks
• Snapshots
• Swap files
VMDK
Snapshot VSWP
Virtual Machine Storage Policies
VM Storage Policy • Virtual machine storage
policies are built before VM
Capacity
Availability
deployment to reflect the
Performance requirements of the
application running in the
virtual machine.
• The policy is based on the
Virtual SAN capabilities.
• Select the appropriate
vSphere
policy for the virtual
Virtual SAN Cluster machine based on its
Virtual SAN Datastore requirements.
• Storage objects for the
… virtual machine are then
created that meet the policy
SSD
Hard disks
SSD Hard disks
SSD
Hard disks
requirements.
Configuring Virtual Machine Storage Policies
Mirroring
Storage
Object
Striping
Viewing a Virtual Machine’s Virtual SAN Datastore
The consumption of Virtual SAN storage is based on the virtual
machine’s storage policy.
The virtual machine’s hard
disk view:
• Summarizes the total storage
size and used storage space
• Displays the virtual machine
storage policy
• Shows the location of disk files
on a Virtual SAN datastore
Disk Management (1)
Disk management in vSphere Web Client:
• Easily map the location of magnetic disks and flash-based devices.
• Mark disks and control disk LEDs.
Disk Management (2)
• Light LED on failures:
– When a solid-state disk (SSD) or a magnetic disk (MD) encounters a permanent
error, Virtual SAN automatically turns the disk LED on.
• Turn disk LED on or off:
– User might need to locate a disk, so Virtual SAN supports manually turning an SSD or
MD LED on or off.
• Marking a disk as SSD:
– Some SSDs might not be recognized as SSDs by ESXi.
– Disks can be tagged or untagged as SSDs for cache.
• Marking a disk as HDD:
– Some SSDs or MDs might not be recognized by ESXi as HDDs.
– Disks can be tagged or untagged as HDDs.
– SSDs must be marked as HDDs in order to be used for capacity.
Adding Disks to a Disk Group
Disk groups can be expanded by adding data disks to a node and adding
these disks to a particular disk group.
The vSphere Web Client shows any unclaimed disk in the disk
maintenance window.
Removing Disks from a Disk Group
Individual disks can be removed from a disk group.
Ensure that data is evacuated before the disk is removed. Alternatively,
you may place the host in maintenance mode.
Virtual SAN Cluster Member Maintenance Mode Options
Before you shut down, reboot, or disconnect a host that is a member of a
Virtual SAN cluster, you must place the host in maintenance mode.
When you place a host in maintenance mode, you can select a specific
evacuation mechanism.
When any member node of a Virtual SAN cluster enters maintenance
mode, the cluster capacity is automatically reduced because the member
node no longer contributes storage to the cluster.
Option Action
Full Data Migration All components are evacuated from the host.
Network/Security
Handle explosive data growth.
Automate service-level
agreements through virtual
machine-centric policies.
Replication Snapshots (Policy-Based Control Plane)
vSphere
Cost of
“We overprovision storage.”
ownership
“Our storage budget keeps going up.”
is too high.
Traditional
Model
VMware vSphere
Virtual volumes
VMDKs and
VMDK Data
Virtual
Operations
Volumes
Offloaded to
Storage Arrays
Replication Snapshots Caching Encryption De-duplication
Storage Array Requirements
Virtual volumes require that the following criteria be met to function
properly:
• A storage array compatible with vSphere API for Storage Awareness 2.0.
• Must implement vSphere API for Storage Awareness to create the storage
provider for virtual volumes:
– Firmware
– Virtual appliance
– Physical appliance
Discover protocol
Register a storage endpoints Create Virtual
provider in Volumes
vCenter Server. (iSCSI, NFS, and datastores.
so on).
Bidirectional Discovery Process
Capacity
SLAs
Virtual Volumes
SAN/NAS
Storage-Based Policy Management (2)
Storage policies represent service levels demanded by virtual machines.
Review of Learner Objectives
You should be able to meet the following objectives:
• Describe the benefits of software-defined storage
• Describe per-virtual machine storage policy management
• Explain how VMDK data operations are offloaded to storage arrays through the
use of VMware vSphere API for Storage Awareness
Key Points
• You use VMFS datastores to hold virtual machine files.
• Shared storage is integral to vSphere features such as vSphere vMotion,
vSphere HA, and vSphere DRS.
• Virtual SAN enables low-end configurations to use vSphere HA, vSphere
vMotion, and vSphere Storage vMotion without requiring external shared
storage.
• Virtual SAN clusters direct-attached server disks to create shared storage
designed for virtual machines.
• Virtual Volumes is a storage management approach that enables
administrators to differentiate virtual machine services per application.
• Key components of the Virtual Volumes functionality include virtual volumes,
VASA providers, storage containers, protocol endpoints, and virtual datastores.
Questions?
Troubleshooting
Storage
Storage Connectivity and
Configuration
Review of vSphere Storage Architecture
If a virtual machine cannot access its virtual disks, the cause of the
problem might be anywhere from the virtual machine to physical storage.
Virtual Disk
Datastore
VSAN VVOL VMFS NFS
Type
Possible Causes
• If the ping command fails, ensure that the IP settings are correct.
Possible Cause: iSCSI HBA Misconfiguration
The iSCSI initiator might be configured incorrectly on the ESXi host.
Use VMware vSphere® Web Client to check the configured components:
• iSCSI initiator name
• iSCSI target address
and port number
• CHAP
Resolve this problem by checking paths between the host and hardware:
• Verify that the iSCSI storage array is configured properly and is active.
• Verify that a firewall is not interfering with iSCSI traffic.
Possible Cause: VMFS Metadata Inconsistency
Verify that your VMware vSphere® VMFS datastore metadata is
consistent:
• Use the vSphere On-disk Metadata Analyzer to check VMFS metadata
consistency:
– voma -m vmfs
-d /vmfs/devices/disks/naa.00000000000000000000000000:1
-s /tmp/analysis.txt
Directory to share
with the ESXi host
NFS Server Name over the network
or IP Address
Mount permission
(Read/Write or
Read-Only) and
ACLs
Data corruption might occur if hosts attempt to access the same NFS
share using different NFS client versions.
Viewing Session Information
You use the esxcli storage nfs41 list command to view the
volume name, IP address, and other information.
Review of Learner Objectives
You should be able to meet the following objectives:
• Discuss vSphere storage architecture
• Identify possible causes of problems in various types of datastores
• Analyze common storage connectivity and configuration problems and discuss
possible causes
• Solve storage connectivity problems, correct misconfigurations, and restore
LUN visibility
Multipathing
Learner Objectives
By the end of this lesson, you should be able to meet the following
objectives:
• Review multipathing
• Identify common causes of missing paths, including PDL and APD conditions
• Solve missing path problems between hosts and storage devices
Review of iSCSI Multipathing
If your ESXi host has iSCSI multipathing issues, check the multipathing
configuration on the ESXi host and, if necessary, the iSCSI hardware
configuration.
Storage Problem 2
Initial checks of LUN paths are performed using the esxcli command:
• Find detailed information regarding multiple paths to the LUNs:
– esxcli storage core path list
• List LUN multipathing information:
– esxcli storage nmp device list
• Check whether a rescan restores visibility to the LUNs:
– esxcli storage core adapter rescan –A vmhba##
• Retrieve SMART data about a specified SSD device:
– esxcli storage core device smart get –d device_name
Identifying Possible Causes
If you see errors in /var/log/vmkernel.log that refer to a permanent
device loss (PDL) or all paths down (APD) condition, then take a bottom-
up approach to troubleshooting.
Possible Causes
To avoid APD problems, the ESXi host has a default APD handling
feature:
• Global setting: Misc.APDHandlingEnable
– By default, set to 1, which enables storage APD handling
• Timeout setting: Misc.APDTimeout
– By default, set to 140, the number of seconds that a device can be in APD before
failing
Possible Cause: NIC Teaming Misconfiguration
Verify that NIC teaming is configured properly.
Possible Cause: Path Selection Policy Misconfiguration
Verify that the path selection policy for a storage device is configured
properly.
Possible Cause: NFSv3 and v4.1 Misconfiguration
Virtual machines on an NFS 4.1 datastore fail after the NFS 4.1 share
recovers from an APD state.
The lock protecting VM.vmdk has been lost error message is displayed.
This issue occurs because NFSv3 and v4.1 are two different protocols
with different behaviors. After the grace period (array vendor-specific),
the NFS server flushes the client state.
This behavior is expected in NFSv4 servers.
Possible Cause: Fault in APD Handling
When an APD event occurs, LUNs connected to ESXi might remain
inaccessible after paths to the LUNs recover.
The 140-second APD timeout expires even though paths to storage are
recovered.
This issue is due to a fault in APD handling:
• When this issue occurs, a LUN has paths available and is online following an
APD event, but the APD timer continues upcounting until the LUN enters APD
Timeout state.
• After the initial APD event, the datastore is inaccessible as long as active
workloads are associated with the datastore in question.
To solve this problem, upgrade ESXi to version 6.0 Update 1. If you are
unable to upgrade, use one of the workaround options:
• Perform the procedure to kill all outstanding I/O to the LUN.
• Reboot all hosts with volumes in the APD Timeout state.
Virtual Machine
Management
Module Lessons
Creating Templates and Clones
Modifying Virtual Machines
Creating Virtual Machine Snapshots
Creating vApps
Working with Content Libraries
Creating Templates and
Clones
Learner Objectives
By the end of this lesson, you should be able to meet the following
objectives:
• Create a template
• Deploy a virtual machine from a template
• Clone a virtual machine
• Enable guest operating system customization by VMware vCenter Server™
Using a Template
A template is a master copy of a virtual machine. It is used to create and
provision new virtual machines.
Creating a Template
Clone the virtual machine to a template:
• The virtual machine can be powered on or powered off.
Convert the virtual machine to a template:
• The virtual machine must be powered off.
Clone a template:
• Used to create a new template based on one that existed previously.
Deploying a Virtual Machine from a Template
To deploy a virtual machine, you must provide such information as the
virtual machine name, inventory location, host, datastore, and guest
operating system customization data.
Updating a Template
Update a template to include new
patches, make system changes,
and install new applications:
1. Convert the template to a virtual
machine.
2. Place the virtual machine on an
isolated network to prevent user
access.
3. Make appropriate changes to the
virtual machine.
4. Convert the virtual machine to a
template.
Cloning a Virtual Machine
Cloning a virtual machine
creates a virtual machine that
is an exact copy of the original:
• Cloning is an alternative to
deploying a virtual machine.
• The virtual machine being
cloned can be powered on or
powered off.
Customizing the Guest Operating System
Use the Guest Operating System Customization wizard to make virtual
machines created from the same template or clone unique.
Customizing a guest operating system enables you to change:
• Computer name
• Network settings
• License settings
• Windows Security Identifier
Dynamically increase a
virtual disk from, for
example, 2 GB to 20 GB.
Inflating a Thin-Provisioned Disk
Thin-provisioned virtual disks can be converted to a thick, eager-zeroed
format.
To inflate a thin-provisioned disk:
• The virtual machine must be powered off.
• Right-click the virtual machine’s .vmdk file and select Inflate.
Or you can use VMware vSphere® Storage vMotion® and select a thick-
provisioned disk as the destination.
Virtual Machine Options
On the VM Options tab, you can set or change virtual machine options
to run VMware Tools™ scripts, control user access to the remote
console, configure startup behavior, and more.
VM Display Name
VM Directory
Guest Operating
System Type
VMware Tools Options
Customize power
button actions.
Schedule VMware
Tools scripts.
Update checks
Boot Options
Retry after
failed boot.
Troubleshooting a Failed VMware Tools Installation on a
Guest Operating System
Problems:
• VMware Tools installation errors before completion.
• VMware Tools installation fails to complete.
• Unable to complete VMware Tools for Windows or Linux installation.
• VMware Tools hangs when installing or reinstalling.
Solutions:
1. Verify that that the guest operating system that you are trying to install is fully
certified by VMware.
2. Verify that the correct operating system is selected.
3. Verify that the ISO image is not corrupted.
4. If installing on a Windows operating system, ensure that you are not
experiencing problems with your Windows registry.
5. If installing on a 64-bit Linux guest operating system, verify that no
dependencies are missing.
Review of Learner Objectives
You should be able to meet the following objectives:
• Describe virtual machine settings and options
• Add a hot-pluggable device
• Dynamically increase the size of a virtual disk
• Add a raw device mapping (RDM) to a virtual machine
Creating Virtual
Machine Snapshots
Learner Objectives
By the end of this lesson, you should be able to meet the following
objectives:
• Take a snapshot of a virtual machine and manage multiple snapshots
• Delete virtual machine snapshots
• Consolidate snapshots
Virtual Machine Snapshots
Snapshots enable you to preserve the state of the virtual machine so that
you can repeatedly return to the same state.
Virtual Machine Snapshot Files
A snapshot consists of a set of files: the memory state file (.vmsn), the
description file (-00000#.vmdk), and the delta file (-00000#-
delta.vmdk).
The snapshot list file (.vmsd) keeps track of the virtual machine’s
snapshots.
Taking a Snapshot
You can take a snapshot while a virtual machine is powered on, powered
off, or suspended.
A snapshot captures the state of the virtual machine: memory state,
settings state, and disk state.
Virtual machine snapshots are not recommended as a virtual machine
backup strategy.
committed to disk
transactions
Pending
.vmdk
Managing Snapshots
The Snapshot Manager enables you
to review all snapshots for the active
virtual machine and act on them
directly.
Actions you can perform:
• Revert to a snapshot.
• Delete one or all snapshots.
Deleting a Virtual Machine Snapshot (1)
If you delete a snapshot one or more levels above You Are Here, the
snapshot state is deleted. The snap01 data is committed into the
previous state (base disk) and the foundation for snap02 is retained.
snap01You are
delta here.
(1GB)
Storage Efficiency
Metadata
Secure Subscription
Types of Content Library
Three types of content library are available: local, published, and
subscribed .
Published
Local Subscribed
Local library that makes
Library of content that Library that syncs with a
content available for
you control published library
subscription
On-Demand
Automatic >>>>
>>>>
Metadata
vCenter Server 6
Content Catalogs in
vCloud Director 5.5
Templates
Other
Password (Optional)
Synchronization and Versioning
Synchronization is used to resolve versioning discrepancies between the
publisher and the subscribing content libraries.
HTTP/NFC