Figure 5. VMware Raw Device Mapping
Introduced with VMware ESX Server 2.5, Raw Device Mapping allows a special file in
the VMFS volumes to act as a proxy for a raw device. An RDM/P can be thought of as a
symbolic link from a VMFS volume to a raw LUN. The mapping makes LUNs appear as
files in a VMFS volume. The mapping file, not the raw LUN, is referenced in the virtual
machine configuration. When a LUN is opened for access, the mapping file is read to
obtain the reference to the raw LUN. Thereafter, reads and writes go directly to the raw
LUN rather than going through the mapping file.
Using RDM/P in physical mode allows SAN-aware layered applications, such as a
RecoverPoint host splitter, to run inside the virtual machine. If RDM/P is not feasible,
then a SAN-agnostic solution, such as the CLARiiON array-based splitter or a SAN-
aware solution, such as intelligent-fabric splitters from Brocade or Cisco, must be
used.
How to choose the appropriate RecoverPoint splitter
Table 1 summarizes the VMware features and limits for each of the three write-
splitting technologies supported by RecoverPoint.
The simplest configuration is the host-splitter configuration. For this configuration,
the RecoverPoint host splitter is installed on each virtual machine that has data that
needs to be replicated. There are a few limitations on the host driver. First, it only
supports the 32-bit and 64-bit Windows platforms; second, only the virtual machines’
data can be replicated, and it must be attached as a RDM/P volume, and the boot
Commentaires sur ces manuels