SRM - HP EVA replication Question

Similar Questions

• SRM vSphere possible replication or SAN?

  Hello

  
  Just curious to know if you can configure the replication SAN with the SRA to who is matched (1 site, Site 1DR) and then also configure Replicator Vmware for SAN systems who don't not have built in replication.

  
  Is it possible to install?  Let me know?

  VMware and vSphere replication port replicator?

  Use vSphere replication, you must deploy the unit of replication vSphere on each site, and you can use the same server of MRS. along the coast with SRA.

  Combined based on the Bay and vSphere replication of the limits of Protection with SRM

  With MRS, you can run groups of protection based on the Bay alongside vSphere protection groups on the same SRM Server replication. However, the total number of protection groups cannot exceed 250. For example, you cannot create 150 groups of protection based on the Bay and then create 250 vSphere replication protection associations, because this creates 400 total protection groups. If you have 150 groups of protection based on the Bay, you can create an additional 100 vSphere protection of the replication groups, for a total of 250 groups of protection.

  VMware KB: Operating for SRM and vSphere replication limits

• Replication question break?

  Hello

  I am an engineer of VMware. We implement SRM with Dell storage. I'm new with replication of dell.

  We have completed the initial replication of volume 5. We made this site (LAN) primary replication only.

  My question is, can I start planning for replication of these volumes (on main site) before to move to the storage back to the site of the DR.?

  We can stop the replication?

  appreciate any suggestion.

  Thanks and greetings

  Tejas

  Yes you can.  Think before put you pause replication when you move the table allow you to finish all replication running.

  Make sure that you can TEST all the interfaces when its on the site of DR, so that the port 3260 is open.  Also, check the routers WAN to apply the ILO do not fragment.   MPLS tends to ignore by default.

• Replicate the VMS with FTP and VM with virtual disk shared by: SRM with vSphre replication

  I have a VM and FT is configured on it. Now I can reproduce the virtual machine with SRM with replication of vSphere. I have not configured array based replication. Similarly, I have two DB VMs cluster, but they share a virtual disk between them. Can I replicate these VMs DB with vSphere replication?

  Your valuable contribution is much appreciated.

  I got the answer, for the virtual machine with FT and shared virtual disk replication, to do SRM with array based replication. vSphere replication cannot replicate virtual machine with FT or shared disk.

• Dell FS7610 replication question

  We currently have a FS7610 NAS and an EqualLogic PS6510E (with ~ 100 TB useful).  Our company just bought another FS7610 and PS6510 for replication purposes (the two new units will reside in another data center) and in the coming months we'll probably buy a bunch more (FS7610 and PS6510s) which will also replicate each other.  At this point, I don't know what to expect, but I am a little concerned about bandwidth Layer 3.  I talked to a couple of sellers of Dell and got two different answers on this... but on a FS7610, replication happens on the front-end or back-end?

  Thank you in advance!

  In the case of the 76xx, replication is performed by the FS, not EQL table nodes, and it uses the subnet of the iSCSI network to perform replication.

  Kind regards

• Replication question

  I have a 300 GB volume which currently holds 20 GB of files of database MSSQL (MDF, NDF, LDF)

  This volume has never been reproduced in the past.  Just now, when I created this volume to replicate to an Equallogic off-site, "pending data transfer" immediately jumped to more than 71 GB.

  Why would it, as this volume has never been implemented for replication in the past so there shouldn't be any incremental change to synchronize, and the volume contains only 20 GB of total data?

  TIA!

  No, the table is a block level device, when a file is deleted by default that the info is not given in the table so that it can cancel the allocation of the blocks.  There is a new standard called UNMAP that will do just that.  But he had been in place from the beginning to UNMAP the blocks.

  Windows Server 2012 and W2K8R2 with HIT kit 4.5 will do it.   Or file system EXT4 linux also supports SCSI UNMAP.

  However, currently UNMAP is NOT supported with replicated volumes.

• Concerns about the replication on the VDR SRM Server

  Dear Experts,
  I have a few questions that I can't know since last week.
  FYI, my current environment has a VDR VM on a cluster of HQ. The VDR Server attachs with 1 system VMDK (8 GB) and 2 physical RDM disks (each disc = 1 TB).
  Now my environment will set up the Site Recovery Manager to replicate 1/3 of the total production of virtual machines on the site of DR, and VDR is one of the SRM protected VM list. In addition, we will build a DR cluster for these protected virtual machines.
  Our lease between HQ & DR line connection speed is around 20Mbps, specifically for the purpose of replication for the SRM storage.
  Questions
  1. Is it recommended to replicate Server HQ for DR using MRS. VDR online? Why?
  2. What is the best practice for backup server VDR (include backup data)?
  3. If we repliacte to Dominican Republic, VDR VDR allows to restore all backup VMs on cluster vCenter DR, since already, it was tied with vCenter cluster HQ?
  4. My total of VMs protected memory size is 148 GB, whereby for DR cluster only have 128 GB of physical memory total (2 ESXi, each has 64 GB). During the execution of failover or real failover Test, will all the VMs protected able to be powered at the same time?
  I'm happy to get any feedback from you guys.
  Thank you.
  VMheaven

  As I said in my previous post doesn't do SRM not replication - it works in conjunction with a product supported SAN to SAN replication - SRM will contact the bays of SAN to identify what LUN replicare and will know what virtual machines are sprinkled on those LUNS - only the changes of the block will be replicated.so that it would be unwise to replicate the vDR machine since there are a large number of block all changes day - it might be prudent to have a vDR VM built on the site of DR and will only be used when there is a failover.

  Yes it works in the same way between 4.0 u3 and 4.03-

• Reconfigured HP Data Replication Group does not present as a group of SRM data store

  Hello

  I configured in two data centers with an EVA4000 on the source site and an EVA4400 on the destination site, countered with Continuous Access EVA of SRM.

  I had replicated two EVA virtual disks (and ESX data warehouses) on the EVA4000 Source called EXCHANGE01 and EXCHANGE02 that have been configured in separate groups, data replication (named EXCHANGE01-GROUP and EXCHANGE02 GROUP) of the HP Command View EVA. These have been picked up properly by SRM as replicated data stores.

  So I decided that it would be preferable to not not two data stores more as a single unit and therefore re-configured continued access by removing the virtual disk EXCHANGE02 of its data replication group and adding as a member of a GROUP named EXCHANGE01. After that, the GROUP named EXCHANGE01 is fail-over for Command View EVA unit and contains EXCHANGE01 to virtual disks and EXCHANGE02. The problem is that when I use the "Rescan replicated storage" option in SRM, you can still see the two Datastores EXCHANGE01 and EXCHANGE02. As it is, I need to create two groups, one by the data store, while in reality a continuous access switch the two as a single unit. The MRS server has been restarted, the berries reread several times, and in fact the EVA4000 has been restarted.

  Two things, I guess. Am I right in thinking that SRM should report to the Group of data replication HP (despite the fact that he refers to it as a\ group data store)? If I am, is there a way I can fix it (preference to short to remove all the replication groups in Command View EVA, a new analysis in the MRS and re - duplicate records?

  I have attached two screenshots - one to SRM showing the list of groups of data store after a new analysis and the other from Command View EVA, showing the Group of data recovery

  AX

  Hi Bob.

  The term SRM data store group is intentionally generic because MRS. support many different providers, and all could use a term "Replication group" as EVA does. If MRS. may correspond to a data store that was created on a LUN that the one being replicated is returned by the adapter, it considers that the store of data as being replicated. It's the storage provider for code adapter for return information LUN appropriate to their table - if you look at the SRM newspapers you will see EVA adapter returns each LUN replicated individually with no information about the relationship of Group of replication at all, so it would be impossible for SRM to have knowledge of this relationship as well.

  Although the LUN in a replication failover as one group power group, they can be taken individually for use during the test of SRM, so maybe it's one of the reasons why HP choice to list each ONE separately.

  In all cases, you have several alternatives: one is to keep your existing environment and configure two groups of protection; on the side of recovery, you can set up a restoration plan unique to switch both of these groups; In addition, you may have configured 2 other recovery plans, one for each protection group, which would be only used for the test, and which would test each LUN and virtual machines on it individually - this could reduce the load on the DR ESX servers during the test rather than to test simultaneously. Of course, you can create a single LUN as well and that of course would make the theoretical discussion - it could be better if your virtual machines must be tested together because the application dependencies.

  You might consider following up with HP if you want more insight as to the relationship of EVA "Replication groups" viz SRM, which is why they chose to not to expose information to the replication group.

• Celerra + SRM and Replication manager

  Hi do anyone knows if its possible to integrate EMC replication manager a Celerra ISCSI / MRS. configuration?

  Replication Manager / SE, I read integrates with Virtual Center, puts the virtual machines in snapshot mode (kind of like the fact of vcb) and then starts the replication to ensure that everything is in order, I also thought with the module for VMware tools with 3.5 update 2 part tools VSS should quiese SQL and make sure that its happy before the virtual machine put in snapshot mode.

  I know with my current Celerra/SRM talks SRM server through the matrix of configuration manager and I expect actually has nothing to do with the real task of replication in celerra manager, im thinking it should be possible to use RM to kickoff between the Celerra replication and still have happy and work SRM.

  I'm way off here?...  If someone knows the answer to this... Please let me know... It would be much appreciated.

  Thank you

  Hello

  I write this as an EMC employee

  «Replication Manager / SE, I read integrates with Virtual Center, puts the virtual machines in snapshot mode (a kind of like vcb) then launches the replication to ensure that everything is in order, I also thought with the VMware tools with 3.5 module update 2 part tools VSS should quiese SQL and make sure that its happy before the virtual machine put in snapshot mode.»

  That's right – Replication Manager is able to do two things - integration with VMware Virtual Center to snapshots by car from Virtual Machines residing in a VMFS volume built on iSCSI.

  Following the call in Virtual Center agent proxy Manager VMFS Replication called Celerra to take the local snapshot. This snapshot can then be mounted to another ESX for backup (if this ESX host is running version ESX console with a backup agent installed in this console - backups for flat file VMDK) or simply to allow the machine virtual administrator to navigate in the data store is presented as a wink on the recovery of ESX host to activate the Virtual Machine defined in full file recovery. The vocation of VMware SnapShot Manager provides a consistent point machine to return where the virtual machine recovery fails

  Replication Manager can create replicas consistent application for such Applications a SQL and Oracle if these scores of applications based on VMFS volumes rather than posing as Raw Device Mappings. The caveat with this is that the volume presented to the Virtual Machine in question must be devoted to this Virtual Machine and a single VMDK file can be built on the VMFS volume) so you would need a volume for your logs, your database, etc. We call this use of replicas of "Virtual disk" case - confused I know

  So two use cases

  VMFS machine restoration for a set of Virtual Machines and integrated individual application VMFS volume consistent replicas for specific virtual machines with their scores of applications built on individually provisioned VMFS volumes

  I don't know why you want to use Replication Manager kickoff the SRM associated Celerra replication. the SRM model is basically continuous replication - i.e. an algorithm runs to determine to what extent the site of DR comes from the primary and push any data the differences across the wire. The bandwidth used for this can be strangled and demand

  Replication Manager leads Celerra replication tends to be regular and non-continuous

  With regard to your query on the integration of Replication Manager and SRM. I prefer to think to Replication manager and SRM for the moment be tolerant to each other. Replication Manager solutions I have just described are focused on the side backup and restoration of the entire equation of continuity of business and focused around that at the local level, so that the RS is more oriented toward the recovery room disaster

  I don't see that going forward, there will be more integration and I hope that Replication Manager may in the future serve to ensure consistency of the request as a level of additional service in the comprehensive proposal of SRM

  Concerning

  Alex Tanner

• vSphere replication vs. SRM

  What are the basic factors which would lead me to choose replication or SRM vsphere in a client environment?

  You ask a comparison of replication on Bay with SRM vs vSphere replication and SRM (SRM can use both) or ask about the differences between replication vSphere autonomous vs. SRM (with an RV or ABR)?

  If this is the first I would recommend this post: Articles VMware SRM - vs vSphere - VMware vSphere Blog - replication array-based replication

  If it's the second, VR does not include all the orchestration, test, reporting and class DR SRM operating company, but allows a protection individual VM and recovery into or through the clusters.  VR works to retrieve a few (less than 5-10) virtual machines as the recovery process must be made individually for each virtual computer. As mentioned made autonomous VR default orchestration, automation, without interruption of service analysis and account of the capabilities of MRS. VR is included in vSphere Essentials more than regulation or newer, the SRM is a VM or per CPU license (within vCloud Suite Enterprise).

• Replication of vSphere SRM - replica of the lack of virtual machines

  Hello

  I use SRM with vSphere replication and all my virtual machines are properly replicated from my site for my recovery.site as you can see:

  

  My problem is that I don't see all the replica of the VMs replicated in the inventory of the recovery site:

  

  So when I was looking for in the web client vSphere replication monitor, I saw that all the virtual machines that are in the inventory of the recovery site are all managed by SRM. And all virtual machines managed by VR finally does not appear in the inventory.

  
  

  Someone at - it never I have this problem or know the solution?

  Concerning

  Hello and welcome to the community of VMware

  The behavior you describe is planned. Between VR and SRM, is SRM work to create what is called 'space reserved VM' on the recovering site.

  If replicate you a virtual machine using vSphere replication but skip protection by SRM, there is no virtual machine being recorded on the recovering Site until you run the RV GUI recovery operation.

  Can I ask you why do you need to see the virtual machine on the recovering site? Even if it is there, you are not able to turn on.

  Best regards

  Stefan Tsonev

• Use SRM with Veeam for replication

  Anyone using Veeam to replicate the data of a site of Prod to a recovery site, also using MRS to create recovery groups and run then planned migration?  Is it still possible?

  No it's not possible - they are independent products - this white paper describes the product isolation - http://www.veeam.com/vmware-srm-veeam-backup-replication-complementing-tools.html

• replication of vSphere in SRM 5.1

  I know that replicaion of vsphere support reprotect and recovery in SRM 5.1.

  In our environment, I am using vcenter 5 u1 to manage several u1 5.0 esxi hosts.

  I intend to deploy MIS. What version of SRM to install the thought. (SRM 5.0 or 5.1 SRM)

  If I decide to deploy SRM 5.1, I improve vCenter 5.1 prior to installation of the SRM 5.1. vCenter 5.1 can support ESXi 5.1 and 5.0 ESXi hosts.

  I want to know if I need to use the feature of vsphere SRM 5.1 replication, what I need to improve 5.0 to 5.1 ESXi ESXi? Dungeon using ESXi 5.0?

  Any mention of the document?

  Hello

  To be specified. You have three options.

  With SRM:

  1. 2 vCenter and 2 servers RS servers. At version 5.1.

  Without RS (no testing and no reprotect):

  2. 2 5.1 vCenter servers.

  3. 1 vCenter server 5.1 (what is called single instance)

  So, if you want to test and automatic failover your choice is option #1.

  Michael.

• SRM Reprotect scenarios

  Hi, ive done some research on SRM that we could implement in a few months.  Had questions about the part reportect of things and some scenarios.

  With the release of SRM 5.1, it now allows reprotect when you use replication of Vsphere.  But from what ive read it only allows it if he were a planned migration not a disaster.  Not sure if this is true, if anyone knows?

  So I was wondering what is happening in some scenarios.  All scenarios are with replication of Vsphere

  
  Lets say the power outage on the main site.  We discover from the power company something bad has happened and power might be down for more than 24 hours.  They decide to use the DR site and switch to it.  Everything works very well after a bit of work, people are working from home or another location.

  After 24 hours power returns to the other site.  We want the failback to the primary site.  So what is happening here.  If reprotect works then just restore us, but if reprotect only works in planned migration then we can just push the button to reprotect.

  We must therefore create a recovery plan, return to the main site.  This part, I don't have a problem with until you get to the part where you want to use the vmdk files that are already on the main site.  But this raises questions

  With Vsphere replication, there may be a delay of 15 minutes between the sites.  Which means the Main Sites (vmdk) virtual machine might have 15 minutes of data that has not been synchronized on the site of DR.  I don't like to get these data in only 15 minutes, but when I goto to reseed these vmdk files to different to use?

  Basically im trying to avoid having to resynchronize the vmdk together via the wan connection, or else copy the VMDK on the site of Dr. and dissemination on say via USB drive and copy them to the main site then.  It would take to long (some disasters require it of course)

  Is smart enough RS to just trash the last 15 minutes that does not get synced to the top and start to synchronize new data on the DR site?

  If that's enough, smart whats a typical cut off the coast before its not able to do it, I can see situations with bad outages of the internet where users can continue to work for an hour or two before decide us actually tipping, in these cases is that long?

  I hope it made sense

  Thank you

  Mike

  You can run 'Restore' operation after a recovery plan was complete. It does not matter that the stimulus plan was executed in planned Migration or recovery mode after a disaster. Usually planned migration is performed when the production and dr site are rising and running and there are some predicted the failure, while the disaster recovery mode is used in case of unexpected events.

  When you configure the VM to be replicated with vSphere Repliacation, one of the parameters that you specify is the RPO (recovery point objective), it can very from 15 minutes to 24 hours. It's time that is acceptable for your company to have a loss of data. In your example, when you click Reprotect, SRM will reverse replication in the opposite direction and production of old VMS files vmdk will be the initial seed. This will cause the changes that have taken place on the site of DR since the event of failover to replicate in return. VR will conduct a parity check and will copy only the differences that occurred in activity on the DR site to the primary site of origin. You don't need to manually download files in the site Dr. back to the original site. Of couse, the more changes on these files on the site of Dr., data more than you need to synchronize again, but, again, it will be only the changed data, not the entire file.

• Different material SRM to the DR site

  Dear people,

  I need clarification on below point.

  We have servers (a few years) running on the DC vSphere site. Now, we are planning for recovery by using MRS. site. But we intend to place newer materials to DR. Does make any incompatibility with MRS? (to my knowledge not as it should be compatible with only vSphere). Please let me know if I'm wrong.

  Thank you and best regards,

  Hari.

  To compute (server) resources compatibility is no need because the VMS failover has cold start.

  Because SAN paintings his most complex issue and to keep the replication health models the table must satisfy certain requirements of compatibility. You should check the compatibility charts.

  In any case, you can use SRM with vsphere replication in order to avoid any restriction of compatibility.