question of replication vSphere

Similar Questions

• We have configured replication vsphere in our environment and when replication is triggered according to the OFR start us below the questions on the virtual machines that are configured for replication

  Question: We have configured replication vsphere in our environment and when replication is triggered according to the OFR start us below the questions on the virtual machines that are configured for replication.

  Version for esxi: Patch 5.1 level 7

  Virtual center of version 5.1

  Source of storage - IBM v7000

  Destination storage - Hitachi

  
  Questions:
  Events of breach RPO
  Consolidation for the VM disk failure
  Delta abandoned events
  Time change events
  NTFS error and warning (event ID: 137, 57)
  RDP disconnect and ping does matter
  Standby error
  Volsnap error
  Stop the server and offline issue
  Install vmtools emits automatically

  well, in this case, we need to disable the standby of the end of the replication.

  So that everything in triggering replication does not trigger the snapshot of the suspension.

  Then test the if you get these errors.

• Configure replication vSphere fails - there is a virtual machine that has the same UUID instance than the one you are trying to configure

  Hi all

  
  

  My colleague was trying to extend a hard disk of a server 2008R2 who (1) had a snapshot and (2) was being replicated. The operation has failed and they took the snapshot replication can be stopped. Long story short when I got to him, the server could not be configured for replication and could not extend the disk and a vMotion failed.

  Looking at the files of the VM on the data store and the VMs .vmx file we have all the characteristics of a virtual machine always configured for replication of vSphere. If you try to configure replication vSphere causes an instant error "vsphere replication does not support change the length of a replicated disk. After a few changes I can reconfigure vSphere new replication, however, when the wizard has finished, I get a new error message (see below):

  "Try to set up vSphere that replication has failed for the VM"name vm"during the creation of groups"vm". There is a virtual "vm-name" machine that has the same instance UUID ' UUID of the Virtual Machine "that you want to configure. The existing vSphere of replication is configured for site protection.

  A possible solution would be to reset the database embedded VRMS our DR as suggested here VR configure replication after losing a VC site server but I was wondering if there is another solution? I have not reset the database of VRM before and cannot find a document that tells exactly what to do. I guess I need to stop all the rehearsals before resetting the database?

  See you soon,.

  Dean

  Hello

  There is no need to reset the VRMS database.

  If you know the value GID... an orphan replication, you can use the CROWD VRMS (https://vrms_address:8043/mob/?moid=GID-...&vmodl=1) to call the destroy method - it is eliminating simple replication to the site of the source or the target.

  If you don't know the GID... value, it can be found of VRMS DB or log files. Please file an SR for assistance.

  This procedure is already documented in internal KB articles and help using VMware support:

  KB article internal 2056086, section "cannot replicate virtual machine as there is another virtual machine with the same UUID instance"

  and also internal KB article 2060751.

  The admin guide section will be updated as it is confusing right now by suggesting only to reset the DB.

  Kind regards

  Martin

• unit of replication vSphere does not fit with vCenter

  unit of replication vSphere does not fit with vCenter (I don't see vsphere tab replication, configuration of the replication of vSphere even not when right click on a particular virtual machine.)

  Only warning I received during the process of deployment has been warning that it will bind with vCenter vService Extension.

  I registered in vCenter, even restarted vCenter, still nothing...

  Another weird symptom, it's that when I browse the web client vCenter Server Extensions - may not load at all (a circle going round in circles without effect what so ever)-same thing when I try to navigate vApps...

  I tried to cancel registration of vRA vCenter from configuration vRA website, but he told me "Management Extension error: org.apache.http.NoHttpResponseException: the target server has not responded'.»»

  Also the 'VRM service is stopped,' I can read on the bottom of the Setup page (leave it only result in a temporary 'on the road' and 'arrested' status).

  This unit of replication vSphere vSphere Client watch is present (with dependency: Extension Installation vCenter) in vService Manager in vCenter Solutions Manager tab.

  It works when saw vcenter and vRM on the same subnet. Maybe my router/firewall is buggy, too bad. To drop the case.

• Some questions about replication

  Hello

  I have several questions with vSphere replication.

  -Can I replicate a server ESXi isolated VM, without vCenter?

  -If I can, you could turn on the VM as if necessary? because when I turn on the virtual machine, I manage in vcenter console

  -If I reproduce it in vCloud, how should I? I need to download a camera in my office and the other in my cloud?

  Thanks for help

  Hello

  -Can I replicate a server ESXi isolated VM, without vCenter?

  You have vCenter Server to replicate virtual machines inside or between data centers. VR as a product is installed on vCenter level and is only available if you are using vSphere Web Client connected to the server vCenter.

  -If I can, you could turn on the VM as if necessary? because when I turn on the virtual machine, I manage in vcenter console

  vSphere replication is not disrupt the work of the virtual machine. It monitors which changes the VM and the changes are replicated

  -If I reproduce it in vCloud, how should I? I need to download a camera in my office and the other in my cloud?

  If you build your own private cloud using vCloud Director VR allows to respond directly to the vCD, as VR currently supports only VC as target. You can however check VMware vCloud hybrid Service: overview | United States if you want to replicate in VMware vCloud hybrid service, workloads

  Hope this helps

  Kind regards

  -Martin

• replication vSphere vCenter

  Hi all

  I have a small question about implementing replication on a single vCenter vSphere. The deployment, protection is very good for a virtual computer for now. The thing is when I go to the inbound replication to start a recovery, I first stop my primary VM, then I click on recover. I followed the steps and recovery starts on my VC. But after a few minutes, I got the error "the name"VM name"already exists." It is true, that my primary VM is still there on my VC... But is it possible in the config for the secondary virtual machine with a different name? As I saw config wizzard do not allow me to add another name... How can I handle this correctly?

  Thank you very much.

  Renaud

  The trick is to get the VM replicated to a different "folder" (e.g., overdrawn Machines) that allows to add the virtual machine of the same name.

  André

• Agent replication vSphere in esxi 4

  do we need to install the vsphere replication agent in esxi 4?

  Hi Eric,.

  Thanks for posting.

  The first version of ESXi hypervisor that vSphere supports replication (VR) is 5.0.

  Versions of the hypervisor that supports each VR version are listed in the.

  VMware product interoperability matrices

  http://PartnerWeb.VMware.com/comp_guide2/SIM/interop_matrix.php

  Hope this helps,

  Hristo

• replication vSphere size limits

  I looked all around the specific limits to the size of a virtual machine that can be protected through MRS. w/vSphere replication, but I do not see these documents. I saw the 5.0.2 release notes claiming to be able to manage VMDK > 255 better now.

  I initially used 5.0.1 and had a lot of problems trying to synchronize a 3 TB 2 comments, 1.5 to VMDK, I'll finally little works, but it took days and multiple attempts to accomplish.

  Now a customer asks 16TO to be protected. Do not know how the distribution of the VMDK will be, but I came with a few raw numbers ranging from an initial synchronization ranging from 12-21 weeks.

  someone at - it an experince with large capacity disks a vSphere Rpelication?

  Hi Robb,

  The maximum disk size for vSphere replication with MRS 5.0.2 is 2032 GB.

  Thank you

  Stuart

  Docs SRM

• Questions about replication of virtual machines using EMC storage

  Hello

  If we have a configuration on 5200 VNX and ready to replicate to Dominican Republic

  What are EMC replication Solutions, if not use Recoverpoint?
  I have to add licenses of replication with the Suites of the app for that?

  and whether using Recoverpoint, it is essential to use SRM for replication can be configured using Recoverpoint and VNX licenses only?

  and for another program installation is with 10 GB iscsi ports, what are the possible solutions?

  Thank you
  
  

  There are several choices for replication with EMC VNX. You can use Mirrorview. MirrorView/S (synchronous) is for short distances and Mirrorview/A (asynchronous) for longer distances and time of higher latency and low latency. You will need a license from EMC Recoverpoint or Mirrorview. Recoverpoint appliances can now be virtual with version 4. ISCSI is required for a virtual Recoverpoint deployment.

  You don't have to use RS with Recoverpoint, although I would recommend that you do. SRM automates many manual steps that are necessary to retrieve your VMs. SRM will be integrated with Recoverpoint or Mirrowview and you will be able to script recovery plans. In the case of the manual recovery plans would be required and will need to be updated.

  You can also duplicate with suppliers other than EMC software. VMware has built the replication that is fine. Veeam also sells software for replication.

  John

• Question time with vSphere

  Hello

  I have installed 2 guests (demo right now).  I Host A my admin/Vserver etc. vmView Server installation and some other servers.  My host B is going to be my workstations.

  In any case, I had the B host connected to the host a. everything was working fine until today when host B has been disconnected.

  When I try to conenct I get the error "the license evaluation Mode assigned to vCenter Server has expired. Recommend updating of the license".

  The BIOS time is correct, when I ssh in the console it seems correct.

  For the record, I'm in Eastern Canadian Eastern time zone ().

  When I do a show date I get

  Wed Feb 13 17:24:13 UTC 2013

  However when I go to vSphere, it shows me the time of 12:24

  My computer where I use vSphere is in the EAST and has the correct time 17:24.

  My server time take time to vSphere and things get screwed up.

  From anyway to solve.

  Thank you.

  Gary

  Assign you the licenses that you have added and you add a license for vCenter Server more guests?

  When the time of BIOS is changed, it occupies at present time more than 5 hours?

• Questions about upgrading vSphere 4.0 to 4.1

  OK, here's my environment:

  vCenter 4.0 & customer 162856 to build running on a physical server with Windows Server 2003 32-bit.

  vCenter Update Manager DB and (everyone) are on separate physical server to SQL 2005 64-bit Windows Server 2003 R2 64-bit

  -Production Cluster running 3 ESX 4.0 Build 164009, 8 virtual machines running all the updates with the v7 hardware VM and VM Tools

  -1 ESX 4.0 Build 164009 (without clusters), run 1 machine virtual update with material v7 VM and VM Tools

  -1 ESX 3.5 Build 110268 (without clusters), current enforcement 6 VM with a hardware VM and VM Tools v4

  -1 ESX 3.5 Build 110268 (without clusters), current enforcement with a hardware VM and VM Tools 7 VM v4

  * After upgrade, I add a host ESX 4.1 extra (new installation) to create a 2nd group for DMZ using one of the above mentioned existing nonclustered hosts.  My total environment after upgrade will be is a small with only 7 guests and a total of 24 virtual machines.

  Here are my questions after reading all the documentation of VMware:

  1. Although vCenter 4.1 can use SQL Express 2005 built on the same server for small environments, he says that it is only for 5 guests and 50 VM. Is my small enough to continue to use this DB option, or should I stick with the performance of my vCenter & the DB Manager Update on separate SQL Server? I guess if I want to use SQL 2008 now or in the near future I should keep them turned off the local vcenter... thoughts?

  2. it is said that for small environments, we can have vCenter and Update Manager DB as one. I wouldn't mind this because I've never really used the Update Manager and I don't lose a lot, but after upgrade, I plan to use it frequently

  3. I want to move my existing vCenter off SQL 2005 DB and put on a SQL 2008 64 bit server.  If I remove and re - join on SQL 2008 64-bit, which would automatically upgrade my DB to the features of 2008?  Also, if I do that I would be able to add vCenter Update Manager 4.1 existing DB or can I just start over with a new DB vCenter to use Update Manager vCenter as a DB?  If I start with a fresh DB on SQL 2008 64-bit vCenter I lose all of my Cluster, etc correct configuration? or will the cluster and it's stay in tact VM after I added all hosts in vCenter with VM?

  4. I want to take the existing vCenter server and rebuild it as Windows Server 2008 64-bit, then install vCenter 4.1, so should I upgrade current ESX 3.5 to 4.1 via Manager Update before you rebuild or after?

  5. when I started using VMware's vCenter 2.5 and I noticed that I have 2 DB that I'm not grateful.  I want to confirm that it was created automatically by vCenter and if it's necessary as I move forward with the new vCenter 4.1 upgrade.  These 2 DB I noticed after my SQL for the VMware DB backups running.  The DB is 'vmm_db_v2_1' and 'Insight_v50_0_125721458 '?

  This is for now... If I think of anything else, I'll add it.  Thanks in advance for any input... I appreciate it.

  1. If your environment is small (max 5 guests and 50 VM) you can keep SQL Express and AUVS in the same machine.

  Maybe you can consider increasing the 3 GB (minimum) to 4 GB vRAM.

  2. for the small environment, you can use SQL Express for both

  3 SQL 2008 is supported. You can DB (but in this case works as of 2005) of attachment/detachment or use the migration of the data inside the SQL tool.

  Do not forget to manually change the ODBC connections in your vCenter

  4. first of all you must upgrade vCenter, you can use new VUM upgrading of the hosts.

  See the update guide 4.1.

  5. the DB are not used by vCenter

  André

• Questions about replication configuration

  Hello
  
  We currently have the configuration of the following replication to a backup Timesten hot facility:
  
  CREATE REPLICATION REP1
  A store of DATA of ELEMENT
  MASTERS ds on "host1".
  SUBSCRIBED ds on "host2".
  RETURN TWOSAFE
  ELEMENT b DATASTORE
  MASTERS ds on "host2".
  SUBSCRIBED ds on "host1".
  RETURN TWOSAFE
  STORE ftappttprd on "host1" PREMISES COMMETTRE ACTION COMMETTRE
  RETURN SERVICES OFF WHEN REPLICATION STOPPED
  SUSTAINABLE COMMITMENT ON
  RESUME BACK 300
  Ftappttprd on "host2" LOCAL STORE COMMIT ACTION COMMITTING
  RETURN SERVICES OFF WHEN REPLICATION STOPPED
  SUSTAINABLE COMMITMENT ON
  CVS BACK 300;
  
  1)
  (a) only the part of the sentence 'COMMIT LOCAL ACTION VALIDATION' implies whenever replication fails on the Subscriber, so the update will be hired locally on master? that is, it is actually becomes a commit sustainable.
  (b) only apply to the timeout for replication scenario? What about other cases where commit at the Subscriber cannot be done.
  (2) if we do not have the expression of DISABLE RETURN as above, would be 'SUSTAINABLE ON COMMETTRE' and 'SUMMARY BACK' always to news?
  in other words, if we decide to stop the replication agent after failover mode standby
  -service back end
  -txn on master will commit sustainable
  -the return service will resume automatically when the replication agent is started again (after the replication problem is fixed)
  
  Thank you
  
  Mike

  Here are the answers:

  1)
  (a) only the part of the sentence 'COMMIT LOCAL ACTION VALIDATION' implies whenever replication fails on the Subscriber, so the update will be hired locally on master? that is, it is actually becomes a commit sustainable.

  CJ > if there is a timeout of servcie to return for a transaction twosafe the default behavior is that the transaction state remains "pending" and the appl; ication must include logic to keep retrying the validation until it succeeds or the application decides to abandon. By configuring LOCAL ACTION COMMIT ENTER, when a timeout occurs the transaction committed locally the band except manipulation (or ignore) the return servcie timeout warningf application has no need to make special anythnin.

  (b) only apply to the timeout for replication scenario? What about other cases where commit at the Subscriber cannot be done.

  CJ > it applies to delays. If you get a different kind of validation error then the application must decide what to (force a local commit or rollback).

  (2) if we do not have the expression of DISABLE RETURN as above, would be 'SUSTAINABLE ON COMMETTRE' and 'SUMMARY BACK' always to news?

  CJ > COMMETTRE SUSTAINABLE can be valid deoending on other factors, RETIURN RESUME is not valid (or useful)

  in other words, if we decide to stop the replication agent after failover mode standby
  -service back end
  -txn on master will commit sustainable
  -the return service will resume automatically when the replication agent is started again (after the replication problem is fixed)

  CJ > I guess you mean "failure" of the day before. Yes, with this configuration, you should see the behavior that yopu described above. The curriculum VITAE of RETURN should not be necessary.

• Simple question vSphere replication NAS/SAN

  We have two remote sites running vSphere and our main office, also running vSphere.  We think of you use vSphere replication to provide a DR solution for two of our critical applications in these remote sites.  One of these applications is running on a virtual machine on the remote site and is connected to a NetApp NAS.  The second application is using EMC SAN to the other remote site.  Our main office using EMC SAN for our vSphere.

  I have a few questions about it.

  1 can use replication of vSphere on the site that uses the NetApp storage?  Will be replicated on our main site, EMC SAN disk data on NetApp storage?

  2. don't only need 1 unit of replication vSphere on the site of the main office?  And then another at each remote site?  Or do we need a separate vSphere replication device at Headquarters for each remote site?

  Thank you.  Sorry for the newb questions.

  Hello

  1 vSphere replication is independent of the peripheral type storage. The changes are to the hard level. You can use different bays of storage on different sites.

  2. If the remote sites have their own server vCenter Server, then you need a VR device at a remote site. If all sites are under same vCenter Server, then you need a device of VR. VRMS (server administration VR) is extension of vCenter Server and there's only a VRMS will be deployed by vCenter Server. The combined unit of VR contains VRMS + embedded DB for server VRMS + VR. There are also some additional device VR-server only, in case you have some hosts within the same server vCenter Server, but on a larger distance and replication traffic can benefit if she moves directly to the VR server closed to the target data store.

  Kind regards

  Martin

• vSphere replication seeding

  Hi guys,.

  Basically the standard way to do a seed must turn off the virtual machine on the source site, make a copy of it and then she picks up on the site of DR to put it on a data store and the replication source site VM instance point to posterity.

  My question is rather than this cant you just use a POS/Veeam backup restore on the target site, itll be a bit outdated and replication of vSphere point to that?

  I take its probably not possible, I'm sure he would have been on the internet somewhere, if not I'm curious as to why not?

  See you soon,.

  Bilal

  vSphere replication requires that source and target UUID drives match. When restoring machines virtual/VMDK POS, Veeam, etc., restored disks get new UUID. You can manually change the UUID of each restored disc, but it's a little heavy. See this FAQ for more information: vSphere replication frequently asked Questions (FAQ) - the current version of this doc has moved to: https://storagehub.vmware.com/#! / vsphere-replication/vsphere-replication-faq

• replication ports 6 VMkernel vSphere

  Thanks to Jeff Hunter for his recent updates and documentation on vSphere for replication 6.0.  Read the docs online, I have a few questions on the vSphere newly supported, dedicated replication VMkernel profits.

  Here (vSphere replication 6.0 Documentation Center) and here (vSphere replication 6.0 Documentation Center) are notes on configuring the VMkernel ports dedicated to the RV on a source host and RV traffic on a target host (one for the VR traffic and another for VR NFC traffic, respectively).

  Considering that it is probably a common practice to use VR as the replication engine with SRM with the intention to fail on the original production site, what is the value in the configuration of two ports VMkernel for VR?

  On the protected Site, you configure a VR VMkernel port to send traffic.  He sends the replicated data from VM for device of recovery of the RV Site, who turns and sends that data replicated for recovery Site ESXi hosts VR NFC VMkernel ports.

  To not return, then the recovery Site can (should?) have an additional port of VR VMkernel, which sends the data replicated VM for device of original VR protected site, which in turn sends the data replicated to the ports of VR NFS VMkernel from the original host protected Site ESXi.

  This looks like it may or must be a distinction between the traffic between the sites and traffic of VR NFC within a site since there are two types of traffic for VMkernel (VR and VR NFC) VR.

  What is this distinction that guarantees a dedicated RV NFC VMkernel port? Why not just use VR VMkernel port? Thank you!

  Edit: I consider these types of traffic to be at the same level of importance and safety.  I have no problem to put two VMkernel ports in the same VLAN.  If I did this, it would put two VMkernel ports per host, in the same network segment.  I wonder why I don't want to do that rather than just use a single VMkernel port or multiple VLANs.

  Post edited by: Mike Brown

  I think it boils down essentially to the options. you don't have to do that, but based on the reviews, it has been estimated that US aircraft enough requests from customers to provide a mechanism which not only allows you to control the path allows the replication traffic (incoming and outgoing) (the source host and VR target devices), and routes it takes on the network but also control the card used for the VR NFC traffic on the target sites. As you RV relies on the NFC to push the data down to the storage of data target on the target sites and some desired customers be able to separate this circulation as well.

  So in the case of the NFC, you can if you want things together (optional) upwards so that the traffic is storage hosts (and I mean here the hosts VR has determined have access to data target stores) can be sent on a physical LAN separated if you wanted that... and a lot of people have asked that flexibility. Allows customers to isolate the common VR NFC (and traffic pass VR) of management traffic not VR "regular".

  Once VRM note that a host has a vmknic marked as RV NFC, only this address is reported on the VR server, which means when it comes to this host in the future that we will only use this address for traffic from VR NFC.

  just my 2cents on why we did it.