This configuration requires that the VMware virtual machines utilize RDM/P volumes,
or that VMware Converter is used to convert these volumes to VMFS.
Figure 13. Physical-to-virtual replication
In physical-to-virtual replication, each physical machine is mapped to a RecoverPoint
consistency group. Each of the LUNs accessed by the production machine becomes a
replication set in the consistency group. Separating the physical server replication by
consistency group allows for either a planned failover or for the use of the replicated
image in the ESX machine for purposes such as testing, data mining, and object
recovery. The target virtual machine can be either local, as shown in the previous
figure, and/or remote. With RecoverPoint there is no need to have the replicas reside
in the same array, array family, or volume type as RecoverPoint will manage the
physical replication between dissimilar arrays.
The ESX server is built and configured with virtual machines that match the
application configuration of the physical machines. The virtual machines are not
running during normal operations, and are only powered on to access new data. The
basic flow is as follows:
1. Select the appropriate image using either a point-in-time selection or a bookmark
selection requesting physical image access. This will cause RecoverPoint to roll
back the replica image to the selected point-in-time image.
2. Once the rollback is completed, the selected image LUNs will be unmasked and
will become visible to the ESX server.
Comentarios a estos manuales