Welcome to the EMC RecoverPoint for Virtual Machines "Ask the Expert" event!
EMC RecoverPoint for Virtual Machines 4.2, a hypervisor-based, software only data protection solution, protects and recovers VMware Virtual Machines (VMs) with VM-level granularity. It is built on the robust engine of EMC RecoverPoint, which has over 250M run hours in the marketplace. RecoverPoint for Virtual Machines empowers vAdmins and enterprise application owners to manage data protection from VMware vCenter, through a plug-in, with orchestration and automation capabilities that make disaster recovery simple and fast.
EMC RecoverPoint for VMs provides local and remote replication for VMs over any distance, sync or async, offering data protection for disaster recovery and operational recovery.
If you are looking to streamline your recovery workflows, meet stringent protection SLAs and eliminate data protection and recovery complexity in your VMware virtualized infrastructure, then ask our experts about EMC RecoverPoint for VMs from August 26th – Sep 5th 2014.
EMC RecoverPoint for VMs experts will be responding to your questions.
Post any questions you might have about EMC RecoverPoint for VMs. We look forward to an informative and exciting exchange of discussions.
Alex Almeida (EMC Elect 2013): Alex's passion for technology started at an early age and has never stopped. Today, he finds himself immersed in backup. In addition to blogging for The Backup Window and participating on the EMC Community Network, Alex is a member of EMC Elect 2013 and active in the New England VMware User Group (NEVMUG) and the Virtualization Technology User Group (VTUG).
Sharon Yen is a Principal Product Marketing Manager at the EMC Data Protection & Availability Division. Sharon has had various responsibilities in the past with different companies, including software development, technical pre-sales support, IT project management, product management and marketing focusing on server consolidation, high availability clustered server solutions, high performance computing, storage virtualization and data center management areas.
Ori Yitzhaki is a Senior Product Manager at the EMC. He is a member of the RecoverPoint product management team, which is part of EMC Data Protection & Availability Division. Ori has had the fortune to experience product management and technology in different fields such as Healthcare, Security and now Data Protection, all of them are very innovative with an impressive footprint in the Israeli tech' industry.
Share this event on Twitter:
>> Join our Ask the Expert, EMC RecoverPoint for VMs: Simple, Efficient, Proven Data Protection for VMware http://bit.ly/1oEglY9 #EMCATE <<
This discussion is now open for questions. We look forward to a lively and informative event.
As you know, RecoverPoint for VMs and RecoverPoint are powered by the same technology but are really two different products, protecting data in two different environments. RecoverPoint for VMs protects VMware VMs and RecoverPoint protects the physical storage array LUNs. One other major differences between the two product (there are many) is that RecoverPoint for VMs has auto-provisioning and DR orchestration capabilities built-in while RecoverPoint leverages VMware Site Recovery Manager (SRM) through product integration to have such capabilities.
Let me just start with the basic question by asking how is DR orchestration done?
It may be beneficial that we use this forum to begin the discussion about the building blocks used to enable the orchestration process such as Consistency Group and CG set.
RecoverPoint for Virtual Machines best practices around journalling are pretty much the same as with the classic RecoverPoint. If possible use a dedicate resource pool for journal. If you need more than 1 journal for a vmdk (across multiple datastores) per copy use CLI to add multiple journals. You can approach sale engineer to get your sizing requirements.
Hope that answer you question.
Consistency Groups (CGs) and Consistency Group Sets (CG Sets) are important components of RecoverPoint for VMs' orchestration feature set. CGs allow for the creation of VM DR policy groups to perform DR, Test Copy, and Fail-back operations. CG Sets allow admins to group together CGs into logical sets and perform DR operations across multiple CGs.
This is particularly valuable where consistent bookmarking is desired (or required) between VM sets hosting components of a mission critical application. For example, a Sales Portal Use Case comprised of VMs hosting a clustered database application, and VMs hosting the corresponding web front end application.
CG sets allow you to be able to create a consistent bookmark of both the Database VMs and the web front end VMs but perform DR operations on each CG individually, or the entire set.
Is this recoverpoint 4.2 version already available or still under a beta program?
RecoverPoint for Virtual Machines, 4.2 release, was not released officially yet. However you can see various blogs mentioning it.
My favourite is the one of Stephen Manley and Beth Phalen on Pulse blog.
In a discussion we had with Zahid, I believe he mentioned that somewhere in the stack, iSCSI was needed... I seem to remember it was for the vRPA communication back to the array, but I've slept since the presentation. Do we need to allocate some RE's for iSCSI? If not, where is iSCSI used in RP4VM? We're really looking forward to testing RP4VM as we are 100% virtualized and RP4VM will offer more granular control over our environment. I would like to +1 the request to have RP4VM be able to snap/replicate in addition to continuous replication. Another option I'd like to see is auto-enrollment of a VM into a protection policy - similar to how the latest version of Avamar can auto-enroll protection of a VM based on it's location in a particular cluster, VM folder, etc. Today, our consumers know that if they want their VM to be part of the DR plan, they select one of the RP protected datastores as the location for the VM. In RP4VM, they would have to deploy the VM to wherever, and then go to the RP4VM tab in the vSphere Web Client to enroll the VM. I can see times where the consumer will forget to do that and believe their VM is protected when it really isn't. Some sort of compliance checking will need to be implemented by us for the initial deployment, but we'd love to see auto-enrollment in a future version. Thanks and kudos to all the RP4VM / DPAP team for making this product a reality!
The iSCSI requirement is between the ESXi host and the vRPA. So the requirement on the ESXi host is to create an iSCSI software adapter and bind a couple of vmkernels to it. Every ESXi host in the HA cluster should have this configured on the basis of a vRPA vMotion to any ESXI host in the cluster.