ESXi 5.0 存储管理详解：vSphere与vCenter优化

需积分: 7 106 浏览量更新于2024-07-23 收藏 2.46MB PDF 举报

ESXi 5.0 的存储管理是vSphere技术架构中的关键部分，它是VMware vSphere虚拟化平台的核心组件。vSphere 5.0引入了一系列改进和增强，以优化存储性能和效率，支持企业级数据中心的需求。在这个版本中，存储管理被整合在vSphere Storage模块内，与vCenter Server 5.0紧密协作，提供统一的存储管理和监控。 vSphere Storage在 ESXi 5.0中扮演了以下几个重要角色： 1. 统一存储管理：它将不同类型的存储设备（如SAN、NAS、FC SAN、iSCSI等）抽象成统一的视图，简化了存储资源的配置和管理，用户无需关心底层硬件的具体实现，只需关注业务需求。 2. 高级存储特性：包括快照、克隆、虚拟机迁移（Live Migration）、存储I/O控制等，这些功能提升了数据保护和可用性，使得管理员能够更灵活地管理和利用存储资源。 3. 动态资源分配：ESXi 5.0的存储管理可以根据虚拟机的使用情况自动调整存储配额和预留空间，实现动态扩展，提高资源利用率。 4. 与vCenter Server集成：通过vCenter Server，管理员可以集中管理整个数据中心的存储，进行容量规划、性能监控以及故障排除，提升整体运维效率。 5. 在线更新：vSphere 5.0的存储管理组件支持在线更新，这意味着在不影响现有虚拟机运行的情况下，管理员可以安全地对存储系统进行维护和升级。 6. 文档支持和更新：该文档适用于ESXi 5.0及其后续版本，直至被新的版本取代。访问VMware官方网站（http://www.vmware.com/support/）可以获取最新技术支持和产品更新，同时，用户还可以提交反馈至指定邮箱（docfeedback@vmware.com）以改善文档质量。 7. 版权和法律声明：所有VMware产品受美国和国际版权法保护，并可能受到一项或多项专利的保护。在使用时，应确保遵守相关法律法规。 8. 联系信息：VMware总部位于加州帕洛阿尔托，提供了丰富的技术支持和产品资讯，网址为www.vmware.com。 ESXi 5.0的存储管理模块是vSphere平台高效、稳定和可扩展的基础，它不仅增强了虚拟机的性能，还提高了数据中心的运营效率和安全性。对于任何寻求在现代数据中心环境中部署和管理虚拟化的IT专业人员来说，理解和掌握这一技术是至关重要的。

Figure 1-3. iSCSI Storage

iSCSI array

VMFS

virtual

machine

virtual

machine

LAN LAN

iSCSI

HBA

ethernet

NIC

Host

software

adapter

In the left example, the host uses the hardware iSCSI adapter to connect to the iSCSI storage system.

In the right example, the host uses a software iSCSI adapter and an Ethernet NIC to connect to the iSCSI storage.

iSCSI storage devices from the storage system become available to the host. You can access the storage devices

and create VMFS datastores for your storage needs.

For specific information on setting up the iSCSI SAN, see Chapter 8, “Using ESXi with iSCSI SAN,” on

page 63.

Network-attached Storage (NAS)

Stores virtual machine files on remote file servers accessed over a standard TCP/IP network. The NFS client

built into ESXi uses Network File System (NFS) protocol version 3 to communicate with the NAS/NFS servers.

For network connectivity, the host requires a standard network adapter.

NOTE ESXi does not support the delegate user functionality that enables access to NFS volumes using non-

root credentials.

NFS Storage depicts a virtual machine using the NFS volume to store its files. In this configuration, the host

connects to the NFS server, which stores the virtual disk files, through a regular network adapter.

vSphere Storage

16 VMware, Inc.

Targets that are accessed through the network have unique names that are provided by the storage systems.

The iSCSI targets use iSCSI names, while Fibre Channel targets use World Wide Names (WWNs).

NOTE ESXi does not support accessing the same LUN through different transport protocols, such as iSCSI and

Fibre Channel.

A device, or LUN, is identified by its UUID name. If a LUN is shared by multiple hosts, it must be presented

to all host with the same UUID.

Viewing Storage Devices

You can display all storage devices or LUNs available to the host, including all local and networked devices.

If you use third-party multipathing plug-ins, the storage devices available through the plug-ins also appear

on the list.

For each storage adapter, you can display a separate list of storage devices available for this adapter.

Generally, when you review storage devices, you see the following information.

Table 1-2. Storage Device Information

Storage Device Information Description

Name Also called Display Name. It is a name that the ESXi host assigns to the device based on

the storage type and manufacturer. You can change this name to a name of your choice.

Identifier A universally unique identifier that is intrinsic to the device.

Runtime Name The name of the first path to the device.

Operational State Indicates whether the device is mounted or unmounted. For details, see “Detach Storage

Devices,” on page 130.

LUN Logical Unit Number (LUN) within the SCSI target.

Type Type of device, for example, disk or CD-ROM.

Drive Type Information about whether the device is a solid-state drive (SSD) or a regular non-SSD

hard drive. For details, see Chapter 15, “Solid State Disks Enablement,” on page 143.

Transport Transportation protocol your host uses to access the device.

Capacity Total capacity of the storage device.

Owner The plug-in, such as the NMP or a third-party plug-in, that the host uses to manage paths

to the storage device. For details, see “Managing Multiple Paths,” on page 158.

Hardware Acceleration Information about whether the storage device assists the host with virtual machine

management operations. The status can be Supported, Not Supported, or Unknown. For

details, see Chapter 18, “Storage Hardware Acceleration,” on page 173.

Location A path to the storage device in the /vmfs/devices/ directory.

Partition Format A partition scheme used by the storage device. It could be of a master boot record (MBR)

or GUID partition table (GPT) format. The GPT devices can support datastores greater

than 2TB. For more information, see “VMFS Datastores and Storage Disk Formats,” on

page 115.

Partitions Primary and logical partitions, including a VMFS datastore, if configured.

vSphere Storage

18 VMware, Inc.

Understanding Storage Device Naming

Each storage device, or LUN, is identified by several names.

Device Identifiers

Depending on the type of storage, the ESXi host uses different algorithms and conventions to generate an

identifier for each storage device.

SCSI INQUIRY

identifiers.

The host uses the SCSI INQUIRY command to query a storage device and uses

the resulting data, in particular the Page 83 information, to generate a unique

identifier. Device identifiers that are based on Page 83 are unique across all

hosts, persistent, and have one of the following formats:

naa.number

t10.number

eui.number

These formats follow the T10 committee standards. See the SCSI-3

documentation on the T10 committee Web site.

Path-based identifier.

When the device does not provide the Page 83 information, the host generates

an mpx.path name, where path represents the path to the device, for example,

mpx.vmhba1:C0:T1:L3. This identifier can be used in the same way as the SCSI

INQUIRY identifies.

The mpx. identifier is created for local devices on the assumption that their path

names are unique. However, this identifier is neither unique nor persistent and

could change after every boot.

Legacy Identifier

In addition to the SCSI INQUIRY or mpx. identifiers, for each device, ESXi generates an alternative legacy

name. The identifier has the following format:

vml.number

The legacy identifier includes a series of digits that are unique to the device and can be derived in part from

the Page 83 information, if it is available. For nonlocal devices that do not support Page 83 information, the

vml. name is used as the only available unique identifier.

Example: Displaying Device Names in the vSphere CLI

You can use the esxcli --server=

server_name

storage core device list command to display all device

names in the vSphere CLI. The output is similar to the following example:

# esxcli --server=

server_name

storage core device list

naa.

number

Display Name: DGC Fibre Channel Disk(naa.

number

)

...

Other UIDs:vml.

number

Runtime Name

In the vSphere Client, you can see the device identifier and a runtime name. The runtime name is generated

by the host and represents the name of the first path to the device. It is not a reliable identifier for the device,

and is not persistent.

Typically, the path to the device has the following format:

Chapter 1 Introduction to Storage

VMware, Inc. 19

vmhbaAdapter:CChannel:TTarget:LLUN

vmhbaAdapter is the name of the storage adapter. The name refers to the physical adapter on the host, not

to the SCSI controller used by the virtual machines.

CChannel is the storage channel number.

Software iSCSI adapters and dependent hardware adapters use the channel number to show multiple

paths to the same target.

TTarget is the target number. Target numbering is determined by the host and might change if the

mappings of targets visible to the host change. Targets that are shared by different hosts might not have

the same target number.

LLUN is the LUN number that shows the position of the LUN within the target. The LUN number is

provided by the storage system. If a target has only one LUN, the LUN number is always zero (0).

For example, vmhba1:C0:T3:L1 represents LUN1 on target 3 accessed through the storage adapter vmhba1 and

channel 0.

Display Storage Devices for a Host

Use the vSphere Client to display all storage devices or LUNs available to a host. If you use any third-party

multipathing plug-ins, the storage devices available through the plug-ins also appear on the list.

Procedure

1 In Inventory, select Hosts and Clusters.

2 Select a host and click the Configuration tab.

3 In Hardware, select Storage.

4 Click Devices.

5 To view additional details about a specific device, select the device from the list.

Display Storage Devices for an Adapter

Use the vSphere Client to display a list of storage devices accessible to a specific storage adapter on the host.

Procedure

1 In Inventory, select Hosts and Clusters.

2 Select a host and click the Configuration tab.

3 In Hardware, select Storage Adapters.

4 Select the adapter from the Storage Adapters list.

5 Click Devices.

Copy Storage Device Identifiers to the Clipboard

A storage device identifier is a universally unique ID assigned to a storage device or LUN. Depending on the

type of storage, different algorithms are used to create the identifier and it can be long and complex. You can

copy the storage device identifier directly from the vSphere Client.

Procedure

1 Display a list of storage devices.

2 Right-click a device and select Copy identifier to clipboard.

vSphere Storage

20 VMware, Inc.

剩余221页未读，继续阅读

michael_yzq123

粉丝: 3
资源: 75

ESXi 5.0 存储管理详解：vSphere与vCenter优化

Vmware_Horizon_View搭建过程

VMWARE-ESXI5.0-6.5搭建阵列和电池BBU配置详细文档及资源.rar

vmware6.5 官方中文文档

Vmware ESXI 5.0 安装RHEL5与Oracle 11g RAC详细步骤

Vmware+Sphere+ESXI5.0+使用虚拟文件共享安装RHEL5-x64+Oracle11gR2-x64+RAC

vsphere-esxi-vcenter-server-501-installation-setup-guide

vSphere Resource Management 题库

基于Matlab面板版的卡尔曼小球运动跟踪[Matlab面板版].zip

Day01(1).py

面试-PHP高频面试题整理-面试题合集.zip

最新资源