RPVM 4.3_faq | Virtual Machine | Computer Cluster

Please download to get full document.

View again

of 7
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information Report



Views: 10 | Pages: 7

Extension: PDF | Download: 0

Related documents
  RecoverPoint for VMs 4.3.1 FAQ   Page 1  of 7  February 2016   RecoverPoint for VMs 4.3 SP1 Frequently Asked Questions 4.3.1 Release ABSTRACT This document summarizes the frequently asked questions for RecoverPoint for VMs 4.3.1 release. February, 2016 Contents ã   Solution Design  ã   Deployment  ã   Orchestration  ã   License  ã   Upgrade  ã   Advanced   RecoverPoint for VMs 4.3.1 FAQ   Page 2  of 7  February 2016   Solution Design   Question:   How do I know that RecoverPoint for VMs is the right solution for me? Answer:   If you have a virtual workload or a need for VM-level protection, it is likely RecoverPoint for VMs is the right solution for you. Question:   Can I try RecoverPoint for VMs prior to purchasing? Answer:   RecoverPoint for VMs offers a trial version free of charge, with no functional or time limitation. The trial version is for non-production use and without EMC support. Answer:   A RecoverPoint for VMs license for 15 VMs is included as part of HCIA, VNX2 ESSPAK bundle and VNXe3200 base software bundle. Question:   How is RecoverPoint for VMs different from RecoverPoint? Answer:   RecoverPoint for VMs is a hypervisor-based data protection tool that protects virtual machines (VMs) with per- VM granularity. In contrast, RecoverPoint protects storage arrays and replicates data at the storage LUN level. Question:   What are the components of RecoverPoint for VMs? Answer:   There are three components: RecoverPoint for VMs splitter, RecoverPoint virtual appliances (vRPA) for replication, and the RecoverPoint VMware vCenter plugin for management and orchestration. Question:   Which versions of vSphere are supported by RecoverPoint for VMs? Answer:   vSphere versions 5.1 U1, 5.5 and 6.0 and later updates with vCenter Web client are supported. Question:   What storage types are supported by RecoverPoint for VMs? Answer:   RecoverPoint for VMs is storage-agnostic. Any storage supported by VMware (including FC, iSCSI, NAS, DAS and VSAN) is supported by RecoverPoint for VMs. Note: Independent, shared, and non-persistent disks are not replicated. Question:   Does RecoverPoint for VMs support RDM? Answer:    Yes. RecoverPoint for VMs can replicate source RDMs (Raw Device Mappings) to target VMDKs and source VMDKs to target RDMs, making RecoverPoint for VMs an excellent conversion solution for RDM to VMDK and vice versa. The target VMs can be created automatically or manually. When replicating VMDKs to RDMs, the target VM must be created manually so you can define the RDM. Question:   Does RecoverPoint for VMs work with VMware SRM Site Recovery Manager)? Answer:   No. RecoverPoint for VMs provides integrated management and orchestration with VMware vCenter Server at no additional cost. SRM should only be used with RecoverPoint replication for storage arrays. Question:   Is the RecoverPoint for VMs journal virtualized? Answer:    Yes. The RecoverPoint for VMs journal is virtualized (i.e. the journal is a VMDK). Question:   Does RecoverPoint for VMs support Multi-site protection? Answer:    Yes. RecoverPoint for VMs supports up to 4 replica copies for each protected virtual machine, enabling concurrent local and remote replication, or multiple remote copies.  RecoverPoint for VMs 4.3.1 FAQ   Page 3  of 7  February 2016   Deployment   Question:   What’s new in 4.3.1 release deployment flow? Answer:   4.3 SP1 release features an improved deployment flow that is fully guided and monitored. The new deployment flow consists of the following 3 main steps: 1.   Create the virtual RecoverPoint appliances (vRPAs) by deploying the OVA file. 2.   Use the new “RecoverPoint for VMs Deployer” tool to easily create the vRPA cluster. For remote replication, use the Deployer tool to connect the clusters on production and DR sites. 3.   Enter the RecoverPoint for VMs plugin and register all the ESXi clusters on which you wish to run protected VMs and the VMs’ replicas. Question:   Can I automate the RecoverPoint for VMs deployment process? Answer:    Yes, RecoverPoint for VMs provides a full deployment API, enabling deployment flow automation. Question:   Can a vRPA cluster replicate the contents of more than one ESXi cluster? Answer:    Yes. Each vRPA cluster can be connected to up to 4 ESXi clusters. This allows you the flexibility to locate the vRPAs on the same ESXi cluster, or on a separate ESXi cluster than the protected VMs. Question:   How do I connect ESXi clusters to the vRPA cluster? Answer:   Using 4.3.1 release, you can easily register the ESXi cluster under the desired vRPA cluster tab, enabling protection of VMs running on that ESXi cluster. The registration automatically installs the splitters across all the ESXi hosts and verifies iSCSI connectivity is set up properly. Register all ESXi clusters that run protected VMs or the VMs’ replicas and any additional ESXi clusters on which you wish to enable vMotion and provide HA of the protected VMs or the vRPAs. (Note: Replicated VMs and vRPAs cannot be migrated to ESXi hosts without a splitter installed.) Question:   Does RecoverPoint for VMs support automatic provisioning? Answer:    Yes. RecoverPoint for VMs supports automatic provisioning of target VMs as well as journals. In addition, users can also manually select existing VMs as the target VM (VMDK or RDM) or existing data-store pools for the journal virtual disks. Question:   What connectivity interfaces are required for RecoverPoint for VMs? Answer:   RecoverPoint for VMs uses iSCSI for communication between its components (Splitter, vRPA) only. For replication, RecoverPoint for VMs uses IP communication. Question:   How does RecoverPoint for VMs scale? Answer:   RecoverPoint for VMs can either scale up (by including 2 to 8 vRPAs per cluster), or scale out (by adding another vRPA cluster, up to the maximum of 8 vRPA clusters for 4.3.x releases).  RecoverPoint for VMs 4.3.1 FAQ   Page 4  of 7  February 2016   Orchestration  Question:   Can I use RecoverPoint for VMs to failover a single VM? Answer:    Yes. RecoverPoint for VMs works at the consistency-group level. If your consistency group only contains one VM, you can fail over that VM without affecting other workloads. Question:   Can I failover multiple VMs that are logically dependent upon one another, while retaining data consistency? Answer:    Yes. To do so, group all VMs in one consistency group. Question:   Can I use RecoverPoint for VMs to fail over or migrate the entire site? Answer:    Yes, using RecoverPoint for VMs Group Set. Group sets allows you to group together multiple consistency groups up to a full site. You can also test, fail over, and recover production on a group set containing your entire production site in one operation. Question:   Can I pre-define the power-up sequence in case of Failover or Failback?   Answer:    Yes, RecoverPoint for VMs 4.3 provides extensive tools for configuring the power-up sequence. The available tool set Includes: ã   Setting the boot order of virtual machines within the same consistency group ã   Setting the boot order of consistency groups within the same group-set ã   Include external scripts and user prompt messages before/after each VM power-up sequence ã   Network Configuration and Re-IP on failover Question:   Does RecoverPoint for VMs support Microsoft VSS for application-consistent bookmarks? Answer:    Yes, RecoverPoint for VMs 4.3 supports Microsoft VSS for creating application-consistent bookmarks. Question:   What is the relationship between VMs and consistency groups? Answer:   Consistency groups are used to protect VMs. RecoverPoint for VMs consistency group can contain a single VM or multiple VMs. Question:   Does RecoverPoint for VMs support Virtual Volumes VVOLs )? Answer:    Yes, RecoverPoint for VMs is out-of-the-box VVOLs ready. The 4.3.1 release has been tested with VVOLs supporting EMC storage arrays (vVNX & VMAX3) to protect VMs running on top of VVOLs. Note: vRPA datastores and journals should not run on top of VVOLs. Question:   Are target VMs powered off during replication? Answer:    Yes. To save resources, target VMs are not registered. A lightweight shadow VM is created per target VM. The shadow VMs are used as an interface to the target VMs.
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks