1. EMC RECOVERPOINT FOR VMWARE ENVIRONMENTS
Note to Presenter: This customer presentation includes EMC protection for VMware, using RecoverPoint to protect virtualized environments, RecoverPoint functionality, a customer example for VMware replication, and RecoverPoint integration with VMware vCenter Site Recovery Manager for automated disaster recovery failover and failback.
Integrated data protection for VMware virtual infrastructure

2. Agenda EMC protection for VMware
Using RecoverPoint to protect virtualized environments
RecoverPoint functionality
Customer example for VMware ESX Server replication
RecoverPoint integration with VMware vCenter Site Recovery Manager (SRM)
The presentation will start with an introduction of EMC and VMware Infrastructure for business continuity and disaster recovery, followed by the benefits of RecoverPoint with VMware. An overview of RecoverPoint functionality, and how RecoverPoint is used in virtualized infrastructures will be provided. An example of a current customer deployment that incorporates RecoverPoint and VMware will be reviewed. The last section will address RecoverPoint’s integration with VMware vCenter Site Recovery Manager.
Note to Presenter: Optional slides in the addendum are four technically detailed use cases, and a summary table of splitter configurations.

3. Why EMC for VMware? One report is interesting Two reports is a trend
Consistent market leadership
One report is interesting
2007 SERVER VIRTUALIZATION SURVEY RESULTS – IDC
43%
12% 8% 7% 4%
26%
EMC HP
IBM
Dell
Sun
Other
2008 GOLDMAN SACHS IT SPENDING SURVEY “STORAGE OF CHOICE FOR VIRTUALIZED ENVIRONMENTS”
Two reports is a trend 7%
13%
Hewlett-Packard
25%
22%
IBM
40%
42%
EMC 8% 6%
NetApp 9%
Dell
Hitachi 1% —
Compellent 3%
Sun Microsystems 4% 2%
EqualLogic/Dell
Jun-08
Aug-08
2009 FORRESTER STORAGE CHOICES FOR VIRTUAL SERVER ENVIRONMENTS
Multiple reports, over multiple years and multiple analysts, is a legacy
“Which vendor(s) supplied the networked (SAN or NAS) storage used for your virtual server environment?”
(multiple responses accepted)
Base: 124 global IT decision-makers currently using x86 server virtualization technology
Source: September 2008 Global Virtual Server Environments Online Survey
Dell/EqualLogic
Hitachi Data Sys
IBM HP
NetApp
EMC
Note to Presenter: This slide presents the core messages on customer spending. Review bullet points.
This information is based on an IDC, Goldman Sachs and Forrester surveys shows the results for networked storage connected to virtualized servers (primarily VMware).
It is important to note that three reports over three years show that customers feel that EMC is the lead choice for a Virtualized environment.
Source: Goldman Sachs IT Spending Survey

4. Why EMC is the Leader Shared storage Backup and recovery Replication
All EMC platforms (Fibre Channel, iSCSI, NAS)
Virtual Provisioning, Quality of Service, Virtual LUNs, security, and ease of use
Backup and recovery
Avamar with VMware guest- and image-level backup, and Avamar Virtual Edition for VMware
NetWorker integration with VCB
Replication
VMware vCenter Site Recovery Manager integration for application- consistent disaster recovery
Support for virtual machine business continuity and disaster recovery
RecoverPoint support for discovery of protection of virtual machines
Replication Manager for application consistency
Resource management
EMC Ionix support for virtual machine discovery and management
EMC has the breadth of products, knowledge, and experience to help you make the most of your VMware virtualized infrastructure, including…
Shared storage options to provide multi-protocol storage to meet the most demanding performance, scalability, availability, and recoverability requirements,
Backup and recovery solutions for VMware environments such as Avamar with VMware guest- and image-level backup, and Avamar Virtual Edition for VMware, as well as integrated NetWorker for the management of new and legacy backup solutions,
Replication for business continuity and disaster recovery
Integrated with VMware vCenter Site Recovery Manager to automate disaster recovery of the virtualized infrastructure,
Automatic discovery of the protection status of Virtual Machine resources
Integration with Replication Manager for application-level protection and recovery gives assured application consistency; and
Resource management with EMC Ionix for Storage Resource Management for virtual machine discovery and EMC Ionix for IT Operations Intelligence support

5. Why RecoverPoint for VMware?
#1 in replication for virtualization
SQL Server
Oracle
Exchange
VMware
SAN
Protect VMFS and RDM/P volumes
Replicate physical, virtual, and physical-to-virtual
Restore individual or multiple virtual machines (VMs)
VM failover and failback support
Monitor VM protection status
Application reference architectures
Supports heterogeneous storage
RecoverPoint provides many critical capabilities for VMware environments.
Highlights include:
The ability to restore individual-level virtual machines impacted by logical corruption
Supports heterogeneous storage arrays, between EMC CLARiiON and Symmetrix and between EMC and non-EMC
Integration with VMware vCenter Site Recovery Manager (SRM) for failover
Includes a vCenter Server plug-in for failback from a SRM failover
Consistency groups for physical and virtual environments; since many applications work with each other, it is important that information types are at a consistent point in time to recover.
A single solution for remote and local replication, with a single point of integration with Site Recovery Manager
Compression functionality that reduces networking costs
More economical disaster recovery testing than is possible with alternative approaches
Integration with VMware vCenter Server to discover and show which virtual machines are protected by RecoverPoint, and for those that are not protected, show which LUNs in specific data stores are not protected by RecoverPoint
Integration with key applications and documented in solution guides and reference architecture papers
Support for iSCSI- and Fibre Channel-attached VMware ESX clusters

6. RecoverPoint Concurrent Local and Remote (CLR) Data Protection
Write-order fidelity across servers and VMs
Block-level local protection for SAN,VMFS, RDM, SCSI/iSCSI (on CLARiiON CX3/CX4 volumes)
Logical or physical access to replicated data
Supports EMC and third-party storage
Utilizes host, fabric, or array write splitting
Local replication with any point-in-time recovery
Remote replication with point-in-time recovery
Local and remote write journals enable roll-back to a consistent point-in-time image
LOCAL SITE
REMOTE SITE
WAN
RecoverPoint
Local Journals
SAN
VMware ESX Server
SAN Storage
Remote
Journal
Third-
party
RecoverPoint is an out-of-band, block-level local and remote replication product that incorporates continuous data protection (CDP) to provide point-in-time recovery. RecoverPoint supports local and remote replication across physical and virtual servers, EMC and third-party storage arrays and different operating system environments.
The CDP technology for local replication supports rollback of replica copies to any point in time, with a granularity of a single block write.
The CDP technology for remote replication supports rollback of replica copies to significant points in time, with granularity controlled by recovery point objective policies established by the user.
RecoverPoint employs an out-of-band architecture, that leverages the host, SAN, and intelligent arrays and fabrics to provide increased availability and performance. Being out of band, RecoverPoint only processes write traffic of protected volumes and uses write-splitting technology leveraging host, CLARiiON, and fabric-based splitters.
In a VMware environment, RecoverPoint provides both local and remote replication, supporting many of the configurations encountered at customer sites. These configurations include replication between a physical server configuration and a virtualized infrastructure, also called physical to virtual (P2V) as well as replication between two virtualized infrastructures, also called virtual to virtual (V2V).

7. VMware ESX Replication— Host-Based Splitter
Leverages host-based splitter for replication of any data on a SAN LUN used by ESX Server
Protect VMs in an individual ESX Server, or in groups of ESX Servers
Simplifies failover and recovery for virtual machines (LUN level)
VM1-0.VMDK
VM2-0.VMDK
VM2-1.VMDK
VM3-0.VMDK
V Disk 0
Virtual Machine 1
VM1-0
VM2-0
Virtual Machine 2
V Disk 1
V Disk 0
Note to Presenter: This and the next slide include descriptions of host, network and array splitter functionality. A summary chart is available in the addendum for those customers that want further detail.
The simplest configuration is the host-splitter configuration. For this replication, the RecoverPoint host splitter (called a KDriver) 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 physical RDM volume. The RDM volumes are shown in the picture where the VMDK acts as a reference to the physical volume. The boot volumes are not replicated; and finally, a maximum of 128 volumes per VMware ESX Server can be supported for replication.
VM2-1
V Disk 0
Virtual Machine 3
VM3-0
VMware ESX Server
= Write Splitting
For a Windows-based guest operating system, the RecoverPoint splitter driver will be installed on the guest operating system

8. VMware ESX Server Replication —CLARiiON and Fabric-Based Splitters
SAN
Initiator 1 target read/write
Copy of
primary write
Fabric
Splitter
RecoverPoint
Not in primary
data path
VMware ESX Server
Target
= Write Splitting
The CLARiiON-based RecoverPoint write splitter is the most effective configuration. With a CLARiiON- based splitter, any of the physical RDM or volumes containing VMFS can be replicated. The only restriction on the CLARiiON splitter is that ALL of the volumes must reside on CLARiiON arrays supported by and attached to the RecoverPoint appliance.
The CLARiiON-based splitter is a feature of FLARE 26 and later, and is supported by RecoverPoint V3.0 and later releases. The CLARiiON-based splitter enables RecoverPoint to get a copy of writes to any SCSI or iSCSI volume hosted by a CLARiiON CX4 or CX3 series array once the write is received by the appropriate storage processor in the CLARiiON CX4 or CX3 series array.
Any volumes provisioned from the CLARiiON CX4 or CX3 series array to ESX Servers can be monitored by the CLARiiON splitter and replicated by RecoverPoint. This includes volumes mounted as physical RDM volumes to the ESX Server, volumes used as the ESX Server boot volumes, and volumes that contain VMFS.
RecoverPoint also leverages an intelligent fabric to mirror writes in the SAN. By using partner-based technology to perform VMFS write-splitting, it avoids the need for host-based drivers or software, and enables scaling to many ESX Servers.
Consistency groups can be created within each ESX Server or for groups of ESX Servers. Simplified failover and recovery for virtual machines, at the LUN level, is achieved.
With an intelligent fabric, the volumes can reside anywhere in the SAN. Intelligent-fabric splitting enables the replication of ESX boot volumes; virtual machine boot volumes (either as physical RDM volumes or as a VMFS volume), and virtual machine data volumes (either as physical RDM volumes or as VMFS volumes).
Fabric splitters using the Connectrix AP-7600B switch and the PB-48K-AP4-18 blade in a Connectrix ED-48000B (Brocade), ED-DCX-B, ED-DCX-4S-B or the Connectrix MDS-9000 director (Cisco) are used to intercept and redirect a copy of writes between a given initiator and target. Brocade and Cisco intelligent-fabric services allow RecoverPoint to eliminate the need for a host write splitter installed on each guest operating system.
When a write is issued to VMFS, the switch will capture the write to the backing volume(s) and will send a copy of the write to the RecoverPoint appliance for further processing. The original write is sent to the target without needing to flow though the RecoverPoint appliance, so the ESX Server or guest operating system will not see any delay or interruption in completing the write. When a read is issued to VMFS, the request is passed though the switch without any involvement by the RecoverPoint appliance.
Mirrors each VM’s writes to the RecoverPoint appliance
Supports VMFS and physical RDM, and vCenter Site Recovery Manager
Eliminates need for host agents and simplifies ESX configurations
Allows applications to span groups of VMs or ESX Servers
Simplifies failover and recovery for virtual machines (LUN level)

9. Bank in Southwest U.S. Situation: Solution: Benefits:
CUSTOMER PROFILE
Regional Bank with headquarters in the U.S. Southwest
Two data centers with about 250 miles separation; 180 branches; 35 applications
$3.2B assets, $280M revenue
INDUSTRY
Finance
Situation:
Replicate between twin data centers 250 miles apart, 10 Mb WAN
5-minute recovery point objective, 15-minute recovery time objective
Thirty five applications, each with a unique RPO
No disaster recovery testing
Solution:
RecoverPoint CRR, 2-node clusters at each site
Cisco MDS-9506 with SSM and SSE (MDS-9000 SANTap Service)
VMware Infrastructure 3 (ESX Server, VMware High Availability, VMFS)
Benefits:
Support of multiple RPO and RTO across their various applications
One solution that supports their virtual and physical environment
Full disaster recovery testing without impact to production servers
This is an example of a major bank in the Southwestern United States using RecoverPoint to protect their virtualized infrastructure. This customer has a production and a disaster recovery data center that is more than 250 miles apart. The two sites are connected by private 10 Mb IP network that is not dedicated to data replication. This was a competitive situation where the customer selected RecoverPoint based on features and capabilities that surpassed another vendor’s host-based replication solution. Two capabilities of RecoverPoint lead to the customer choosing this product; the first was the ability for RecoverPoint to support different RPO by application, and the second was the ability for the customer to perform a disaster recovery “fire-drill” (test) without impact to their production servers.

10. REMOTE DISASTER RECOVERY SITE
Customer Environment
DATA CENTER
REMOTE DISASTER RECOVERY SITE
VMware ESX Server
VMware ESX Server
Mount target
volume to VM
VMware ESX Server
VMware ESX Server
WAN
This is an summary of the customer configuration described in the previous slide. Note to Presenter: View in Slide Show mode as indicated for animation.
<CLICK> By having the check processing and back-office processing virtual machine data separated into two different consistency groups, <CLICK> the user has the ability to recover and restart the virtual machines that are involved with one of the consistency groups without having to failover and restart the other virtual machines.
RecoverPoint
RecoverPoint
Independently
recover and
test data from
remote site
Check Processing
Back Office Systems
Separate application
managed across unique
consistency groups

11. VMware vCenter Site Recovery Manager
How RecoverPoint supports your recovery plan

12. VMware vSphere 4—Value and Innovations
Data Center Solutions
Enabling a more dynamic, flexible service model, at lower costs
Consolidation
Decrease capital expense
Simplify infrastructure
Delay facility expansion
Management
Decrease operating expense
Manage SLAs, not components
Automate the mundane, simplify the complex
Business Continuity
Ensure high availability at low cost
Recover quickly and efficiently
Guarantee service levels
Note to Presenter: View in Slide Show mode for animation.
Working up from the bottom, this slide shows the three horizontal areas commonly presented by VMware when describing their vSphere 4 architecture. It encompass virtualization platforms for core VMware file services, virtual infrastructure for desktop, cloud and development and test groups, and a management, consolidation and business continuity layer for integrating with storage platforms, desktops, and other elements in the data center.
User access across boundaries
Desktop as a service, without the headache
Increase security and control
Desktop Solutions Enabling desktop as a service
Single way to run, manage and secure applications both internal and via external clouds
Broadest choice of leading cloud service providers
Cloud Services Enabling the bridge to the external cloud
Simplify test set-up and execution
Improve quality
Close the gap between dev and deploy
Dev & Test Solutions Optimizing development to deployment
VMware vSphere™ 4

13. VMware Infrastructure 3.5— Value and Innovations
Management
and
Automation
Infrastructure
Optimization
Business
Continuity
Desktop
Software
Lifecycle 3
Consolidate and contain servers
Optimize your infrastructure
Manage and secure desktops
Maximize continuity and uptime
Automate your virtual labs
Update Manager
vCenter Site Recovery Manager
VDI ACE
Lab Manager
Workstation
Converter +
Virtual
Infrastructure
Resource
Management
Availability
Security
Mobility 2
Note to Presenter: View in Slide Show mode for animation.
Working up from the bottom, this slide shows the three horizontal boxes commonly presented by VMware when describing their architecture. It encompass virtualization platforms for core VMware file services, virtual infrastructure for base VMware functionality, and a management and automation layer for integrating with storage platforms, desktops, and other elements in the data center. The circles represent key areas where VMware currently provides, or plans to provide, value.
<CLICK>
The grey blocks show functionality delivered with ESX Server 3.5, while <CLICK> the blue blocks highlight new capabilities offered with VMware Infrastructure 3, such as Site Recovery Manager.
DPM
High Availability + Consolidated Backup
Storage VMotion
Distributed Resource Scheduler (DRS)
VMotion
vCenter
Virtualization
Platforms
Virtualization Platforms 1
VMware Virtual Machine File System
Virtual SMP
ESX Server 3.5
ESX Server 3i 3.5

14. VMware vCenter Site Recovery Manager Integration
Makes disaster recovery rapid, reliable, manageable, affordable
EMC RecoverPoint
Servers
Heterogeneous Storage
PRODUCTION
VMware Infrastructure
Virtual Machines
RECOVERY
Simplifies and automates disaster recovery workflows
Setup, testing, and failover
Makes disaster recovery a property of the virtual machine
Provides central management of recovery plans from vCenter
Turns manual recovery processes into automated recovery plans
Supports ESX 3.5, ESX 4.0/4.1
VMware Site Recovery Manager simplifies disaster recovery by enabling users to move data from one data center to another based on policies. All virtual machines can be moved, or a subset.
Here are some key points about Site Recovery Manager:
Provides a central point of management for disaster recovery plans
Plug-in to VMware vCenter
Manages recovery plans for virtual machines managed by vCenter
Enables pre-programming of disaster recovery plans
Maps resources between production and recovery sites
Programs steps of recovery process
Automates key disaster recovery workflows
Automates tests of recovery process
Automates failover in disaster scenarios
Simplifies failback to primary data center

15. Without Site Recovery Manager
Nine administrator tasks, several GUIs
7. Scan for new disk
8. Register VM
9. Power-up VM
3. Shut down the virtual machine
VMware ESX
VMware ESX
4. Pause replicated image (journal captures)
5. Select most recent snapshot
6. Allow image access to remote VMware ESX
ESX Server
ESX Server (disaster recovery)
The failover process for VMware environments replicated with RecoverPoint can be complex and require that the user interact with both the RecoverPoint console and the VMware console. This is fine for small environments, but as the environments grow larger and more diverse, the user will be required to manually track the failover status of multiple virtual machines.
SAN
SAN
WAN
RecoverPoint
RecoverPoint
VM mapped to LUNs and consistency groups
2. Replicate LUNs

16. With Site Recovery Manager
One task, one GUI
Shut down the virtual machine
Pause replicated image (journal captures)
Select most recent snapshot
Allow image access to remote VMware ESX Server
Scan for new disk
Register VM
Power-up VM
Reverse replication direction
VMware ESX
VMware ESX
ESX Server
ESX Server (disaster recovery)
With VMware Site Recovery Manager, this complex failover process becomes as simple as pressing a single button.
<CLICK>
There is no need for the user to interact with the RecoverPoint console and the VMware console; instead the process is automated by VMware. The user simply has to ensure that the production virtual machines are mapped to LUNs that are replicated to the remote site.
Once the user initiates a failover, VMware works with RecoverPoint to perform all of the necessary tasks, including pausing replication, shutting down the local virtual machines, presenting the replicated data at the remote site, and then restarting the virtual machine at the remote site with full access to the replicated data.
SAN
SAN
WAN
RecoverPoint
RecoverPoint
VM mapped to LUNs
LUNs replicated by RecoverPoint

17. RecoverPoint Integration with VMware Site Recovery Manager
vCenter
SRA
SRM
Non-disruptive
DR testing
Automated VM failover
Heterogeneous
storage
PRODUCTION
Servers
VMware Infrastructure
Protected Virtual Machines
DISASTER RECOVERY
WAN
RecoverPoint
Production LUNs
SAN
DR Replicas
DR Journal
LUN
As you can see by this graphic, RecoverPoint sits below the VMware Infrastructure and is responsible for replicating all changes from the production LUNs to the remote replicate LUNs at the disaster recovery site. The RecoverPoint Storage Replication Adapter is installed on the same servers that run Virtual Center and the Site Recovery Manager service in the production and disaster recovery site. RecoverPoint benefits include replication between differing arrays, such as between a Symmetrix DMX and a CLARiiON CX4 or CX3. Additionally, there is no requirement that the production volumes be attached to the VMware servers in physical RDM mode; instead the data can reside on VMFS file systems that are contained on the production LUNs. Finally, with RecoverPoint the distance between the sites is not a limit since RecoverPoint replicates the data asynchronously, but maintains the write- order consistency at the remote site, ensuring that all replicas remain fully consistent.
Site Recovery Manager is designed as a plug-in to VirtualCenter so that disaster recovery tasks can be executed inside the same management tool as other virtual machine administration tasks such as creation, migration, deletion, etc.
Looking at the graphic:
There are separate VirtualCenter 2.5 instances at each site (managing independent inventory). (Note to Presenter: Point to the Virtual Center blocks at both the production and disaster recovery sites.)
There are separate Site Recovery Manager servers at each site responsible for different Site Recovery Manager components (protection groups, recovery plans, etc.). (Note to Presenter: Point to the SRM blocks and protected virtual machines at both the production and disaster recovery sites.)
The Site Recovery Manager server supports the same platforms and databases as vCenter, and can run on the vCenter host or on a separate host.
Any ESX Server 3.02, ESX Server 3.5 or ESX Server 3i host is supported.
All RecoverPoint benefits discussed in the previous slides apply to RecoverPoint use with Site Recovery Manager. This use includes the CLARiiON array-based write splitter, heterogeneous storage, and policy-based replication. Site Recovery Manager is designed for site-to-site replication. It only works with remote replication as provided by RecoverPoint CRR. If using RecoverPoint concurrent local and remote (CLR) data protection, Site Recovery Manager will only operate with the remote replica copy.

18. Storage Replication Adapter
Integrates with VMware Site Recovery Manager
Supports ESX 3.5, ESX 4.0/4.1
Supports RecoverPoint and RecoverPoint/SE, including CRR and CLR configurations
Supports any FC LUN supported by RecoverPoint and iSCSI with CLARiiON-based write splitter
Licensing
No separate RecoverPoint SRM license required
Appropriate VMware Site Recovery Manager licenses
Downloads
Available from the VMware web site
VMware’s list of SRM qualified storage providers
Note to Presenter: View in Slide Show mode for hyperlink to work.
The most interesting piece of the install is the RecoverPoint Storage Replication Adapters. As you know, Site Recovery Manager does not actually do the replication for disaster recovery, only the setup, test, and recovery workflows. Site Recovery Manager relies on storage vendors’ block-based replication, such as provided by RecoverPoint, for the replication. The RecoverPoint Storage Replication Adapter ties together the Site Recovery Manager product and the replication products. The RecoverPoint Storage Replication Adapter was developed and qualified, and is supported, by EMC.
If you are interested in using Site Recovery Manager with RecoverPoint, you can download the RecoverPoint Storage Replication Adapter from the VMware web site.
Note to Presenter: There is no additional RecoverPoint license required to use Site Recovery Manager; however, the customer must ensure that they have the appropriate RecoverPoint license for remote replication (i.e., a RecoverPoint/SE CRR or CLR, RecoverPoint CRR, or a RecoverPoint CRR+CDP license).

19. Automated Failback After SRM Failover
Integrates into vCenter Server
Automates failback by:
Powering down VMs (recovery site)
Failback replicated LUNs and reversing replication (protected to recovery site)
Registering VMs (protected site)
Powering on VMs (protected site)
Provides real-time status
Available in the plug-in
Available in the Recent Tasks area of the vCenter Server
The EMC RecoverPoint failback tool is a plug-in to VMware vCenter Server Virtual Center, just like Site Recovery Manager. Once installed, users have access to the features and steps necessary to automate the failback process after Site Recovery Manager has been used to mitigate a disaster. Similar to Site Recovery Manager, users configure the relationship between the Site B and Site A, <CLICK> identify those LUNs that have been failed over, and simply press the failback button— RecoverPoint handles the rest.
Additional Talking Points
It is important to understand what this tool does not do.
It is not a replacement to SRM, only a compliment;
Unlike SRM, it does not provide users with a mechanism to execute custom scripts or business logic that is specific to their organization;
It does not provide an ordering mechanism for virtual machine dependencies;
It does not reset the IP addresses on each virtual machine;
The tool does not rebuild SRM Protection Groups and SRM DR plans—after running failback, the user still needs to delete the old SRM Protection Groups and DR Plans and to re-define new ones; and
Most importantly, the tool does not support the loss of your RecoverPoint cluster. The tool requires access to the original RecoverPoint cluster to resolve replication configuration and settings as part of automating the failback.

20. Monitoring VMware Virtual Machines
Tree view displays all the VMs belonging to a vCenter Server
Displays VMs and their protection level
Monitors vCenter for creation of and changes to VMs
Updates display and sends alert when a VM’s storage protection changes
RecoverPoint is integrated with VMware vCenter for the discovery of ESX servers and their associated virtual machines and the mapping of virtual machine storage resources to RecoverPoint consistency groups. The RecoverPoint protection status for each discovered virtual machine is displayed on the GUI and will also be available though the command line interface. Additionally, a RecoverPoint alert will be sent when the protection status of a virtual machine changes.
The screen shot—and the call-out—shows that RecoverPoint is monitoring the ESX servers that are registered to a vCenter server at Two ESX servers were discovered by RecoverPoint, one at and the other at The first ESX server has two virtual machines (Exchange at , and LDAP at ). This screen shows that RecoverPoint has discovered that the Exchange virtual machine is partially protected, with only its LUN(vmhba1:1:1), in the ESX Datastore “Exchange DB Datastore” not protected by RecoverPoint. The other machine is called LDAP and RecoverPoint has discovered it has a single LUN (vmhba:1:2:0) that is not protected. The other ESX server has one machine “LDAP (testing)” at , and RecoverPoint has discovered that it has a single LUN(vmhba:1:3:0) in the ESX Datastore “LDAP Datastore (Testing)” and that this LUN is also not protected by RecoverPoint. All of the information shown on the Management Application GUI for each virtual machine can also be queried though the RecoverPoint command line interface.
Any change in this protection status, such as a virtual machine moving from being fully protected by RecoverPoint to being partially protected by RecoverPoint will result in RecoverPoint logging and raising an alert.

21. Summary #1 in replication for virtualization
Protect all your important systems and applications
Any mix of virtual and physical
EMC Proven solutions
VMware Certified solutions
Decrease downtime
Protect more with less resources
Accelerate recovery
Automate disaster recovery
In summary, EMC believes that RecoverPoint is the ideal product to provide comprehensive protection of information in a physical and virtualized infrastructure.
Highlights include the following:
The VMware certified and EMC proven RecoverPoint Storage Replication Adaptor for VMware Site Recovery Manager
Multiple EMC proven solutions for business applications, such as Exchange Server
Support of both existing SAN volumes in Raw Disk mode, as well as a fully virtualized file system environment using VMFS
Coexistence with VMware VMotion, Storage VMotion, Distributed Resource Scheduler, and High Availability configurations.
With its out-of-band, appliance-based design, RecoverPoint can be added to the environment at any phase of the migration to a virtualized infrastructure, which enables support for physical-to-virtual as well as virtual-to-virtual replication environments.
RecoverPoint offers flexibility in deployment scenarios with options for host, network, and array configurations, and major network protocol support. RecoverPoint also supports EMC and third-party storage arrays, protecting existing technology investment.
Lastly, RecoverPoint offers state-of-the-art replication features and capabilities, including simultaneous local and remote replication at a highly granular level. Of course, this replication of production data takes place without impact to the production application performance.

22. Thank you.

23. Physical to Local Virtual Replication
Replicating physical volumes enables use by a local ESX Server
Consolidates multiple physical servers into a single ESX Server
Imports replicated volumes as R/W without impact to physical servers
Imports array volumes for long-term use
Consistency Groups
Physical
Server A
Fibre Channel
RecoverPoint
Server B
Server C
ESX Server
Virtual
Machine A
Machine B
Machine C
Storage Arrays
CG3
CG2
CG1
SAN
OPTIONAL SLIDE
Note to Presenter: The next four slides provide technically detailed use cases that may be appropriate for some customers.
This is a common configuration for customers that have deployed VMware Infrastructure to provide disaster recovery resources in a remote data center, but who have not migrated their production data center onto a VMware Infrastructure. This configuration is commonly referred to as physical-to-virtual (P2V) replication and is supported by host, CLARiiON, and fabric splitters.
To configure RecoverPoint to support the P2V replication, the customer configures the LUNs into unique consistency groups and defines replication pairs mapping physical server LUNs to virtual machine LUNs. This step enables consolidation of physical servers at local site to single ESX Server at remote disaster recovery site. It also enables consolidation of multiple physical storage arrays at local site to single storage array at remote disaster recovery site.
At the remote site, each replica volume is zoned to the ESX Server(s). When it is necessary to recover an image, the remote replica image is accessed using local image access. It is then mounted to the appropriate virtual machine in the ESX Server as a physical RDM volume.
USE CASE

24. DISASTER RECOVERY SITE
Physical to Local Virtual Replication and Physical to Remote Physical Replication
Replicates production data to use for import and test using local ESX Server
RecoverPoint with VMware enables consolidation to a single ESX Server
CLR enables quick provisioning and testing of ESX disaster recovery environment
CRR enables concurrent support of remote physical disaster recovery environment
Storage Arrays
PRODUCTION SITE
DISASTER RECOVERY SITE
Physical
Server A
Fibre Channel
RecoverPoint
Server B
Server C
ESX Testing Server
Virtual
Machine A
Machine B
Machine C
CG3
CG2
CG1
CONSISTENCY GROUPS
SAN
WAN
OPTIONAL SLIDE
This is a typical configuration for customers looking to migrate from a physical to virtual environment— either for their production data center or for their disaster recovery data center. In this example, the CLR features of RecoverPoint V3.0 are used with local replication to a test VMware ESX Server configuration and remote replication to an existing physical disaster recovery infrastructure.
This configuration is similar to the previous use case, except the virtualized environment is in the same site as the production volumes so local replicas created using RecoverPoint CDP are used instead.
This configuration is supported by host, CLARiiON, and fabric splitters.
To configure RecoverPoint to support the P2V/P2P replication, the customer configures the LUNs into unique consistency groups and defines replication sets mapping physical server LUNs to local virtual machine LUNs, and remote physical disaster recovery machine LUNs. This step enables consolidation of physical servers at local site to single ESX Server while retaining the server-to-server equivalency at the remote disaster recovery site. It also enables consolidation of multiple physical storage arrays at the local site to a single storage array at the remote disaster recovery site.
At the local site, each local replica volume is zoned to the ESX Server(s). When it is necessary to recover an image, the local image is accessed using local image access. It is then mounted to the appropriate virtual machine in the ESX Server as a physical RDM volume.
USE CASE

25. Local Virtual to Remote Virtual Replication
Uses RecoverPoint consistency groups for replication of multiple VMs
Uses vCenter integration to ensure volumes belonging to VMs on all ESX machines are protected
RecoverPoint enables consolidation of ESX Servers at remote disaster recovery site
PRIMARY PRODUCTION SITE
Storage array
DISASTER RECOVERY SITE
Fibre Channel
ESX Server 1
Virtual
Machine A
ESX Server 2
Machine B
Machine C
CG3
CG2
CG1
ESX Server
CLARiiON or fabric-based splitter
RecoverPoint
WAN
SAN
OPTIONAL SLIDE
In this use 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 an ESX Server environment using VMFS deployed with either a CLARiiON splitter or an intelligent-fabric write splitter. This configuration can also be supported using host splitters if the customer utilizes SAN LUNs attached as physical RDM volumes. RecoverPoint’s integration with vCenter lets RecoverPoint users quickly ensure that all volumes attached to virtual machines in each of the ESX servers are being protected by RecoverPoint.
This configuration is supported by host, CLARiiON, and fabric splitters:
Host splitters use guest operating system and RDM to replicate physical LUNs mapped to virtual machines.
The fabric-based or CLARiiON array-based splitters can leverage VMFS to take advantage of a VMware virtual infrastructure.
This configuration also supports replication of virtual machines residing in multiple ESX Servers at the production site to a single ESX Server at remote site.
USE CASE

26. Virtual Machine File System Replication
RecoverPoint replicates VMFS
Enables VMFS replication and protection of entire ESX Server
vCenter integration ensures all VM volumes on all ESX machines are protected
PRIMARY PRODUCTION SITE
DISASTER RECOVERY SITE
Fibre Channel
ESX Server
Virtual
Machine A1 B1 C1 A2 B2 C2
Standby Virtual
VMFS
CG2
CG1
Production ESX Server 1
Production ESX Server 2
CLARiiON or fabric-based splitter
RecoverPoint
WAN
SAN
OPTIONAL SLIDE
This configuration is supported by CLARiiON array-based or intelligent fabric-based splitters only.
This configuration fully supports the ability to replicate virtual machines that use VMFS and takes advantage of the VMware virtual infrastructure.
RecoverPoint’s integration with VMware vCenter 2.5 enables a RecoverPoint administrator to quickly ensure that every VMFS in use by a virtual machine on any of the ESX servers is protected by RecoverPoint.
This configuration also supports VMotion’s moving of a virtual machine between ESX Servers in the same site, since the virtual machine has a relationship to a VMFS and each VMFS belongs to a RecoverPoint consistency group (which is unchanged by any use of VMotion).
USE CASE

27. Splitter Recommendations for VMware ESX
Type Features
Splitter
Windows Host Splitter
CLARiiON Splitter
Brocade/Cisco Fabric Splitter
Physical RDM support
Yes
VMFS support No
VMotion support
VMware DRS support
VMware SRM support
P2V replication support
RDM/P only
V2V replication support
Guest operating system BFS replication
RDM/P and VMFS
ESX BFS replication support
Maximum number of guests supported per ESX Server
128 (VMware limit)
N/A
Maximum number of volumes
255 per guest
255 per guest, 1,024 maximum
Heterogeneous array support
EMC CLARiiON CX series and Symmetrix DMX series only
EMC CLARiiON CX4 or CX3; Celerra NS20, NS40, NS80, NS120, NS480, NS960 over Fibre Channel only
OPTIONAL SLIDE
This table summarizes the VMware features and the restrictions imposed by each of the three write- splitting technologies supported by RecoverPoint
The simplest configuration is the host-splitter configuration. For this replication, the RecoverPoint host splitter (called a KDriver) 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 physical RDM volume. The boot volumes are not replicated; and finally only a maximum of 16 volumes per VMware ESX Server can be supported for replication.
The CLARiiON splitter is the most effective configuration. With a CLARiiON splitter, any of the RDM volumes or volumes containing VMFS can be replicated. The only restriction on the CLARiiON splitter is that ALL of the volumes must reside on CLARiiON arrays that are supported by and attached to the RecoverPoint appliance.
The final configuration uses intelligent SAN APIs provided on some Brocade and Cisco switches. Using Intelligent fabrics, the volumes can reside anywhere in the SAN. Intelligent-fabric splitting enables the replication of ESX boot volumes; virtual machine boot volumes (either as physical RDM volumes or as a VMFS volume), and virtual machine data volumes (either as physical RDM volumes or as VMFS volumes). As you can see by this chart, the CLARiiON splitter provides the best mix of functionality.