3. From the ESX Server console, scan for the new LUNs and then register them with
the appropriate virtual machine.
4. Power up the virtual machine, which will see the point-in-time image data. At this
point RecoverPoint tracks the reads and writes to the image so that they can be
backed out when image access is completed.
After step 2 completes, an array snapshot, such as provided by an EMC TimeFinder
®
BCV or EMC SnapView™ clone, can be created from the replica LUNs, and then
RecoverPoint would be informed that image access is completed. Once RecoverPoint
resumes processing the user would present the snapshot to the ESX server for use by
the virtual machines. Alternatively, these snapshots can be used by VMware
Converter to import the data to existing VMFS volumes.
Virtual-to-virtual replication
In this usage case the customer has fully migrated to a VMware infrastructure for their
production and disaster recovery sites. At the disaster recovery site, they are taking
advantage of the server and storage consolidation capabilities of VMware and
RecoverPoint. The customer has fully deployed a VMware ESX Server environment
using VMFS deployed with either a CLARiiON-based splitter or an intelligent fabric
write splitter. This configuration can also be supported using a Windows-based
KDriver when SAN LUNs are attached as RDM/P volumes.
Figure 14. Virtual-to-virtual replication
If a VMFS is used, then the virtual machines are either configured to use a separate
VMFS volume for each machine or all of the virtual machines use the same VMFS
volumes. In the figure above, each virtual machine is assumed to have its own VMFS;
this allows for an individual virtual machine to be tested and/or failed over to the
disaster recovery site without impacting the remaining virtual machines. When
multiple guest operating systems (OSs) are distributed over a limited set of LUNs,
such as combined into one or more VMFS volumes, a special configuration is
Komentarze do niniejszej Instrukcji