which of the following vSphere features?

Raw Device Mapping using Physical Compatibility mode is required for which of the following vSphere features? (Choose two)

Raw Device Mapping using Physical Compatibility mode is required for which of the following vSphere features? (Choose two)

A.
Array-based Snapshots.

B.
N-Port ID Virtualization

C.
SAN management Agent

D.
MSCS Clustering across ESX/ESXi hosts.

Show Hint

Leave a Reply 4

Your email address will not be published. Required fields are marked *

Daniel

Daniel

Pre 5 Question.

MSCS Guide Page 9, Table2.
Virtual AND physical RDM’s can be used for MSCS clusters across boxes.

Reply

Anitha

Anitha

Correct answer is A & C

Physical
Allows the guest operating system to access the hardware directly. Physical compatibility is useful if you are using SAN-aware applications on the virtual machine. However, a virtual machine with a physical compatibility RDM cannot be cloned, made into a template, or migrated if the migration involves copying the disk.

If you use an array-based solution, physical compatibility RDMs are often used for the storage of virtual machines. If you do not intend to use RDMs, check the storage vendor documentation to see if operations on LUNs with VMFS volumes are supported. If you use array operations on VMFS LUNs, carefully read the section on resignaturing.

Virtual
Allows the RDM to behave as if it were a virtual disk, so you can use such features as taking snapshots, cloning, and so on. When you clone the disk or make a template out of it, the contents of the LUN are copied into a .vmdk virtual disk file. When you migrate a virtual compatibility mode RDM, you can migrate the mapping file or copy the contents of the LUN into a virtual disk.

NPIV is used with virtual mode

Reply

Anitha

Anitha

Correct answer is A & C

NPIV can be used only with virtual and MSCS clustering can be used both with phycial or virtual mode .

RDM Virtual and Physical Compatibility Modes
You can use RDMs in virtual compatibility or physical compatibility modes. Virtual mode specifies full virtualization of the mapped device. Physical mode specifies minimal SCSI virtualization of the mapped device, allowing the greatest flexibility for SAN management software.

In virtual mode, the VMkernel sends only READ and WRITE to the mapped device. The mapped device appears to the guest operating system exactly the same as a virtual disk file in a VMFS volume. The real hardware characteristics are hidden. If you are using a raw disk in virtual mode, you can realize the benefits of VMFS such as advanced file locking for data protection and snapshots for streamlining development processes. Virtual mode is also more portable across storage hardware than physical mode, presenting the same behavior as a virtual disk file.

In physical mode, the VMkernel passes all SCSI commands to the device, with one exception: the REPORT LUNs command is virtualized so that the VMkernel can isolate the LUN to the owning virtual machine. Otherwise, all physical characteristics of the underlying hardware are exposed. Physical mode is useful to run SAN management agents or other SCSI target-based software in the virtual machine. Physical mode also allows virtual-to-physical clustering for cost-effective high availability.

Reply