Study guide

3.5 RDM, PMem, NVMe, NVMe-oF & iSER Use Cases

VMware Certified Professional - Data Center Virtualization VCP-DCV

Track your progress as you read

Finished sections get a check mark.

1 Introduction: VCP-DCV Exam Overview

About the VCP-DCV Exam (2V0-21.23)

2 Chapter 1: vSphere Architecture & Core Platform Technologies

1.1 vSphere 8.x Architecture and Components Overview 1.2 vCenter Server Appliance (vCSA) Architecture & Deployment 1.3 vSphere Distributed Services Engine (DSE) & DPUs 1.4 vSphere Products, Solutions & Workload Platform 1.5 vCenter Topology: SSO Domains & Enhanced Linked Mode 1.6 vSphere with Tanzu: Supervisor, Namespaces, Zones & Lifecycle 1.7 vSphere in the SDDC: vCenter Converter, vSphere Replication & SRM

3 Chapter 2: Compute Resources & Cluster Management

2.1 vSphere High Availability (HA) Architecture 2.2 Distributed Resource Scheduler (DRS) & Resource Pools 2.3 vMotion & Enhanced vMotion Compatibility 2.4 Virtual Machine Advanced Compute Configuration 2.5 Fault Tolerance, Proactive HA & Advanced Cluster Options 2.6 vSphere Cluster Services (vCLS) & Retreat Mode 2.7 Migration Types: Cold Migration, Storage vMotion & Cross vCenter Export

4 Chapter 3: Storage Technologies & VMFS Datastores

3.1 Storage Access Protocols & Multipathing 3.2 VMFS Datastore Architecture & Management 3.3 Storage Policies (SPBM) & Virtual Volumes (vVols) 3.4 Storage DRS & Storage I/O Control 3.5 RDM, PMem, NVMe, NVMe-oF & iSER Use Cases

5 Chapter 4: VMware vSAN Architecture & Operations

4.1 vSAN Core Architecture & Disk Groups 4.2 vSAN Fault Domains & Stretched Clusters 4.3 vSAN Storage Policies & Data Protection 4.4 vSAN Maintenance, Health Checks & Monitoring

6 Chapter 5: Virtual Networking Architecture & Configuration

5.1 Standard Switches (vSS) vs Distributed Switches (vDS) 5.2 Port Group Policies & NIC Teaming 5.3 VLAN Configuration & Security Policies 5.4 Network I/O Control (NIOC) & TCP/IP Stacks

7 Chapter 6: Security, Identity & Access Control

6.1 vCenter Single Sign-On (SSO) & Identity Sources 6.2 Role-Based Access Control (RBAC) & Global Permissions 6.3 Virtual Machine Encryption & Key Management 6.4 ESXi Host Security & vSphere Trust Authority 6.5 vSphere Certificate Management 6.6 VM Firmware, Secure Boot, vTPM & Virtualization-Based Security

8 Chapter 7: Lifecycle Management & Host Configuration

7.1 vSphere Lifecycle Manager (vLCM) Cluster Images 7.2 Baseline-Based Lifecycle Management 7.3 Host Profiles & Cluster Quickstart 7.4 Content Libraries & Virtual Machine Deployment 7.5 ESXi Host Configuration: Time, Services, Product Locker & Boot Options 7.6 vCenter Lifecycle: Update Planner, VAMI Patching & Upgrades 7.7 Virtual Machine Snapshots & VM Creation Methods

9 Chapter 8: Monitoring, Performance Tuning & Troubleshooting

8.1 Performance Monitoring & Metrics 8.2 Command-Line Diagnostics & esxtop 8.3 Log Analysis & Diagnostic Data Collection 8.4 Troubleshooting Common Infrastructure Scenarios 8.5 Alarms & vCenter Appliance Health Monitoring

3.5 RDM, PMem, NVMe, NVMe-oF & iSER Use Cases

Key Takeaways Explain This Topic AI

A raw device mapping (RDM) is a mapping file on a VMFS datastore that points a VM at a whole LUN; physical compatibility mode passes SCSI commands through and does not allow VM snapshots.

Physical-compatibility RDMs suit SAN-aware applications and Windows Server Failover Clustering across hosts, while vSphere 7.0 and later also offer clustered VMDKs on VMFS-6 for WSFC.

ESXi supports NVMe over Fabrics using Fibre Channel, RDMA (RoCE v2), and TCP transports, and claims NVMe devices with the VMware High-Performance Plug-in (HPP).

iSER (iSCSI Extensions for RDMA) runs iSCSI over RDMA-capable NICs to cut CPU use and latency, and is enabled with esxcli rdma iser add.

vSphere 8 supports Intel Optane PMem as vPMem (a virtual NVDIMM for PMem-aware guests on hardware version 14+) or vPMemDisk; PMem support ends with VMware Cloud Foundation 9.0.

Last updated: September 2026

3.5 RDM, PMem, NVMe, NVMe-oF & iSER Use Cases

Most VMs store their disks as VMDK files on VMFS, NFS, vSAN, or vVols. Objective 1.3.6 covers the special-purpose options you pick when a workload needs direct LUN access, persistent memory, or the lowest-latency transports.

Raw Device Mapping (RDM)

An RDM is a mapping file (a small .vmdk pointer) on a VMFS datastore that gives a VM direct access to a whole LUN . The VM's I/O goes to the LUN, while the mapping file lets vCenter manage it like a disk.

  • Virtual Compatibility Mode (vRDM) Physical Compatibility Mode (pRDM)
  • SCSI commands Virtualized like a VMDK Passed through to the device (except REPORT LUNs)
  • VM snapshots Supported Not supported
  • Can be converted to VMDK with Storage vMotion Yes No (only the mapping file moves)
  • Typical use Features of a VMDK plus a dedicated LUN SAN-aware applications and clustering

Use cases for RDMs:

Windows Server Failover Clustering (WSFC) across hosts with shared disks that use SCSI-3 persistent reservations (pRDM).

SAN management or array-aware software in the guest that must send commands directly to the LUN, such as array snapshot agents.

Physical-to-virtual flexibility , where a LUN may need to be presented to a physical server again later.

Since vSphere 7.0 , clustered VMDKs on VMFS-6 datastores (with eager-zeroed thick disks) are an alternative to pRDMs for WSFC, which simplifies management. NPIV , which gives a VM its own Fibre Channel WWPNs on an RDM, is being retired: the vSphere 8.0 release notes announce its deprecation in a future release.

NVMe and NVMe over Fabrics

NVMe is a storage protocol designed for flash, with deep parallel queues. vSphere uses it in three places:

Local NVMe devices : PCIe SSDs in the host, often used for vSAN (ESA requires NVMe) or local VMFS.

NVMe over Fabrics (NVMe-oF) : NVMe commands carried over a network to an external array.

Virtual NVMe controller : a VM-side controller type (hardware version 13 and later) that lowers guest I/O overhead. It is independent of the physical transport.

ESXi's NVMe-oF transports:

Transport Adapter Type Notes

NVMe over Fibre Channel (FC-NVMe) Hardware FC HBA that supports NVMe Appears as a Fibre Channel adapter (vmhba) whose protocol is NVMe; no extra adapter configuration

NVMe over RDMA (RoCE v2) Software NVMe over RDMA adapter on an RDMA-capable NIC Needs a lossless or well-tuned RoCE network; add controllers after creating the adapter

NVMe over TCP Software NVMe over TCP adapter on a standard NIC Works on ordinary Ethernet with no special NIC; add controllers after creating the adapter

Key points:

NVMe devices present namespaces rather than LUNs, and you connect to array controllers through discovery.

ESXi claims NVMe devices with the VMware High-Performance Plug-in (HPP) instead of the Native Multipathing Plug-in used for SCSI. HPP has its own path selection schemes, such as load balancing by round robin or by latency.

Use cases: latency-sensitive databases and analytics on all-flash arrays, or moving off FC SCSI to NVMe without changing the fabric (FC-NVMe), or using existing Ethernet (NVMe/TCP).

iSER: iSCSI Extensions for RDMA

iSER keeps the iSCSI model (targets, IQNs, port binding) but moves the data transfer onto RDMA , using RDMA-capable NICs (RoCE). This cuts the host CPU work and latency of software iSCSI.

Enable the adapter from the ESXi shell with esxcli rdma iser add , which creates a VMware iSER adapter (a vmhba).

Bind it to a VMkernel adapter on an RDMA-capable NIC, then configure discovery and targets as with iSCSI.

Use case: an iSCSI array that supports iSER, where you want lower latency and CPU cost without moving to a new protocol.

Persistent Memory (PMem)

PMem (Intel Optane persistent memory) sits between DRAM and flash: byte-addressable like memory, and persistent like storage. vSphere 8 supports it in two ways:

Mode How the VM Sees It Requirements

vPMem A virtual NVDIMM device, bypassing the storage stack Hardware version 14 or later and a PMem-aware guest OS

vPMemDisk A virtual disk stored on the host-local PMem datastore Works with legacy guests that are not PMem-aware

PMem can also run in Memory Mode , where it transparently expands host memory capacity.

Use cases: in-memory databases and applications that need very fast restarts or persistent in-memory structures.

Constraints: PMem is local to each host, so VMs using it need destination hosts with PMem for vMotion, and HA restarts need spare PMem.

Status: Intel discontinued Optane, and Broadcom ends PMem support starting with VMware Cloud Foundation 9.0 . It is still in the vSphere 8 blueprint, so know the modes.

Choosing Among Them

  • Requirement Best Fit
  • Shared-disk WSFC across hosts pRDM, or clustered VMDK on VMFS-6 (vSphere 7.0+)
  • Guest software must issue SCSI commands to the array pRDM
  • Lowest-latency external flash over existing Ethernet NVMe over TCP
  • NVMe on an existing Fibre Channel fabric FC-NVMe
  • Lower CPU cost for an iSCSI array that supports RDMA iSER
  • PMem-aware in-memory database vPMem
  • Exam Traps

pRDM means no VM snapshots. Backup tools that rely on VM snapshots cannot protect a physical-mode RDM, so plan array-level protection.

NVMe devices are not claimed by NMP. If a question asks which plug-in manages NVMe paths, the answer is the High-Performance Plug-in (HPP).

NVMe/TCP needs no special NIC; NVMe/RDMA and iSER do. Match the transport to the hardware in the question.

PMem is host-local. Plan vMotion and HA capacity accordingly, and remember that support ends with VMware Cloud Foundation 9.0.