vSphere replication device 5.5.1.2 Build 1999430 to 5.5.8 upgrade?

Similar Questions

• Cannot download vSphere replication device 5.8.0.2

  Hi all

  just a quick question, I am trying to download the replication 5.8.0.2 vSphere device of my vmware but it gives me an error:

  You are not allowed or are not authorized to download this product.

  I wonder if anyone knows why? I downloaded the previous version without problem (5.8.0.1) and don't know why it isn't available?

  D.

  If someone else runs into the same problem, just to say that I solved it by contacting support and they fixed what appeared to be a bug.

• vSphere replication device Placement

  I am currently in research by deploying the vSphere unit of replication.  We have only a single vCenter on our main site that manages our DR site as well.  Place the appliance in the Data Center Dr, or on the main Site?

  As, can a question I replicate our vCenter with the camera as well?

  Thanks in advance!

  In the case of unique vCenter replicating virtual machines between hosts of the VC and VR device is good to be placed on the more reliable from the site host. The reason for this is that if the VC drops little matter where the VR device that you will not be able to do the recovery because it is necessary to connect on the VC. Speaking like that, your recovery site should be the most reliable host and the main site (host) must be the other guests.

  In fact does not require to do this because the VR device to write the data in the data store when replication is pointed. If this is the VC scenario then the reliability of the system is what defines your deployment history. If it's more than a scenario of VCs - then the history is clear - a device of VR by VC, regardless of what VC you call primary or DR.

  Hope this helps

• Unable to connect target - vSphere replication Sites

  I hope someone here can help me understand a problem connecting between my two servers of VRM.

  Background:

  After passage of 6.0U2 5.5, I had problems with re-login Site Recovery Manager. Because SRM was not really in use yet (testing), I decided to redeploy fresh from the base, including replication of vSphere components.

  After removing all the rehearsals and not record old vSphere replication devices, I transferred the latest packages of EGGS to the VRM.  Everything was fine.  I have updated certificates for certificates customized our company certification and placed the root certificate in the file /opt/vmware/hms/security/hms-truststore.jks .  Then, I recorded each VRM with their respective vCenters and had no problems.

  

  Both VRM active lounge and OK in vSphere replication of the Web Client:

  

  When you attempt to connect to the target Site, the following error is received:

  

  But then in the list of tasks, it ends with success and shows the connection, but with a connection problem error:

  

  This is the architecture of our PSC and vCenters and each VRM.  All use of our certification of Enterprise SSL certificates:

  

  There is no firewall between one of these servers.

  HMS logs are attached here as well.

  Any help would be appreciated.

  Thank you

  After that I originally posted this, a new version of vSphere replication was released.  After the upgrade to the latest version, my problem magically disappeared.

• 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

• After upgrading vSphere 5.5 replication device cannot add VM replication

  Dear all,

  We have improved our server vcenter and device of replicaion of vpshere of version 5.1 to 5.5. after upgrade cannot add new virtual machine replication replication vsphere device. Configure the replication vsphere option grey out on VM right click menu. See the image below.

  

  Please advice how to solve this problem.

  Thank you and best regards,

  Lasa.

  Hello

  There is a known issue for this behavior described in VMware vSphere replication 5.5 Release Notes (shares of vSphere in vSphere Client Web replication are not available after the upgrade.) The solution is to restart your Web Client vSphere

• vSphere replication

  I just have a few questions on vSphere replication, I deployed the device on one of my ESXi hosts and I have the replication of configuration for some of my virtual machines.

  They must reproduce successfully, these replicate to a computer host which is another of my sites (although it all on the same network that the other site is linked directly via the BT 100 MB fiber connection)

  My question is this: If something happens to the building where our servers are located and also where I have the installer of vCenter server to manage my environment ESXi, how do I get the VMs back to work on the host, they have replicated too?

  Hope this makes sense, I know that I can use the web management interface to manage vreplication device to retrieve the VMS and deploy them to any host you want. But if the basic site is down I will not have access to a vsphere web management interface or you vreplication.

  So, how do you bring the replicated VMs online?

  I've been using vRanger connection for replication of VMs and during replication to the host who is off site, they appear only as VMs and I turn on logging to the server directly using the vsphere client, as they just normally appear as VMS on that host. But this doesn't seem to be the case with the unit of replication vSphere.

  Hoping someone enlighten us on that.

  As vSphere replication is a feature of vSphere, its features are accessible at the vc level. So in order to perform a recovery through the user interface in the single vc use case you have vc and vr servers upward and running. If there is crushing of the CV so you can check out this http://www.yellow-bricks.com/2012/09/21/can-i-protect-my-vcenter-server-with-vsphere-replication/article. It is for the recovery of the CR but should work for all virtual machines

• Automate the network port group selection in vsphere replication

  Hi, when you use the vsphere replication tool to recover servers in the data center of DR, the tool does not gives option to select network settings. I have to manually add the port groups and turn on the system remotely vcenter. Is it possible to automate this process, when the replication of a major part of the vms ~ 100-150. I would like to know if there is another way to fix the process and avoid the manual load.

  I use replication of vsphere device version 5.8

  Thank you

  The only way to automate this process is through the Site Recovery Manager.  Automate and orchestrate BC/DR is a big part of the value offered by SRM. The other advantage is the ability to test your recovery plans without disruption of service.

  Does that answer your question?

• Unable to deploy vSphere replication

  Hi people,

  I am studying towards my VCP 5.5 so please forgive me if I am ignorant even at some of the basics.

  I want to experiment a bit with the replication of vSphere in my lab at home and I am struck because I can't download/deploy the right thing.

  Study material said that it should be deployed as an appliance virtual fron an OVA/OVF file.
  then I tried to locate the latest 5.5 of vSphere replication subversion and I just this one:

  https://my.VMware.com/group/VMware/details?downloadGroup=VR5121_OSS & ProductID = 285

  That one did not work since I couldn't unpack the tar.gz on Windows file (tried with 7zip and Total Commander). So I downloaded some

  version 5.5 which I could decompress successfully but it contains a lot of RPM files, and I can't go any further.

  I also tried to Search Administration guide of replication on the vSphere deployment process

  1. connect to the vSphere Web Client on the source site.

  2select vCenter > hosts and Clusters.

  3 right-click a host and select deploy OVF model.

  4. specify the location of the file OVF in which you want to deploy the unit of replication vSphere and click Next.

  -Select the URL and enter the URL to deploy the unit from a URL online.

  -Select the Local file: Browse to locate the file .ovf if you have downloaded the zip on a local computer.

  So what now?

  Hello

  VR 5.8.x and 5.5.x is compatible with vCenter 5.5.x.

  Following the links on vmware.com, here's the download pages:

  RV 5.8.x:

  https://my.VMware.com/Web/VMware/details?downloadGroup=VR5802&ProductID=353&rPId=7710

  RV 5.5.x:

  https://my.VMware.com/Web/VMware/details?ProductID=353&rPId=7710&downloadGroup=VR5514

  The .zip file contains the .ovfs (of the unit combined VR and VR-Server device only) and two .vmdks.

  The .iso image files are the same and in addition .rpms focused on the CDROM to upgrade from previous versions.

  THE OSS. tar.gz file you found are the sources of packages based OS and other open source / third-party packages, including license requires VMware publish their sources along with RV parts.

  Kind regards

  Martin

• VRM Service is stopped - replication device Root Partition full

  Hello

  We recently had an upgrade to vsphere 5.5 and a replication device (version of the device: 5.8.0.1).

  Everything was fine to begin with, but now the service VRM stops and does not start.

  Of the survey, we found that the partition root unit was full.  We followed it down to the a directory called 16384 in the directory/var/lib/vrmsdb/base.

  I guess that's why the VRM service does not start.

  Can you tell me what that fills this directory and the size of this directory can be controlled or do we just add more disk space?

  Thanks in advance.

  S.

  Hello

  Please open an SR to get help with adding additional disk space and move the embedded DB vPostgres to a partition with an extra space.

  Once the DB is running, the DB tables can be analyzed to see the root cause for the full DB.

  HMS - configuration.xml file there is a hms-eventlog-maxage parameter that can be lowered (for example to 604800, 7 days), in order to limit older data stored in tables IncomingEventLogEntity and OutgoingEventLogEntity. Without the DB dump, it would be difficult to know what is the origin of the complete BD, but it reported problems with busy environment and occasional VR server disconnects which have led to large number of notifications between servers VRM and fills the tables IncomingEventLogEntity and OutgoingEventLogEntity.

  Kind regards

  Martin

• with vSphere replication to replicate vCenter Server in a VM

  Hi guys,.

  I am trying to find some info on this. I currently have vCenter 5.5 running on a Windows 2008 R2 VM server. I was wondering can I use replication to replicate it in some shared storage for backup purposes, and if I had to lose it could I recover and this and be good to go? He runs a database integrated. or is it as AD/SQL/Exchange and in general you shouldn't use replication or something of the sort for them.

  Also, if I have reproduced on the recovering site, I could pick it up and re protect him using MRS. and migrate to the main site once I had everything back up and restart? Is there a difference if I ran the vCenter device instead of the version of Windows inside a virtual machine?

  My apologies if this has been answered before that somewhere, it just went through my mind randomly and Googling gives me really a lot of results, so if its been answered somewhere, please point me in that direction.

  Hello

  vSphere replication requires vCenter to function, you cannot use VR to protect it that you wouldn't have a way to recover, unless it has been replicated on a different vCenter (whereby it might be recovered, but only inside the other vCenter) or if it has been managed by a different vCenter.

  If you are in the second option, where you have a vCenter management appliance RV, and you have an another vCenter, so yes, you can use RS in this model to protect and auto restore your internal vCenter.

  No difference in the functionality between vCA and windows version of vCenter.

  As for your statement: "or is it as AD/SQL/Exchange and in general you shouldn't use replication or something of the sort for them."

  -vSphere replication supports VSS suspension

  -I'm Okay I wouldn't recommend AD replication (SQL and Exchange or if you can use the built in replication at the application level)

  -If you can not however, most modern applications work very well in a consistent state of crash (VR normal replication) and the rest works with VSS

  Hope that answers your questions

• vSphere Replication options missing in 5.8.0.1 SRM

  In my lab, I have the following Setup and can not get any vSphere replication to be available within the SRM options.  Single table according to replication is an option.  I looked and looked for a solution and we tried everything I could think to get the options will appear and I had no luck so far.

  vcenter1 - 5.5 U2 windows install

  esxi1 - 5.5

  SRM1 - MRS. 5.8.0.1 (install file 5.8.0 - 2336305)

  vR1 - vSphere replication 5.8.0.1

  vcenter2 - 5.5 U2 windows install

  esxi2 - 5.5

  SRM2 - MRS. 5.8.0.1 (install file 5.8.0 - 2336305)

  vR2 - vSphere replication 5.8.0.1

  I started my lab tests by deploying the lefthand VSA with MRS.  Now, I'm moving on using SRM with replication of vSphere.  The steps I've taken since the tests on the left:

  Devices removed from Lefthand VSA

  Uninstalled SRM and chose to clear the contents of the database also

  Confirmed SRM is not displayed in the Web Client more

  VSphere installed a replication on both sites or set to 1 VM - replication is complete

  Installed SRM on the same servers as before and matching installation

  Market thought the SRM configuration theres no reference and no vSphere replication option.  There's also no mention of any SRM integration when in vSphere replication interface.  Now I remember to deploy the same configuration in 5.1 which gave vR deployment options in RS, but that was then.  Now, says the documentation, you're supposed to first deploy vR, which set up and deploy the SRM.  SRM then detects vR installation and I guess that, in theory, these display options. I checked the permissions and everything seems good.  My lab account is the account I use to save and install everything.  Fine RV, by MRS replication pairs, they do not know that they could work together.  I even reinstalled SRM again and confirmed the installation files have been correct on the interoperability matrix and everything seems good.  MRS. acts just like theres nothing, but the options table replication.  I think theres a version special MRS or vSphere replication, which is necessary for the two to work together, but I can't find any documentation on this topic.

  Help, please.  Thank you!

  Joe

  Hello

  Since 5.8 SRM and VR are decoupled. The only way to install vSphere replication is for download and by deploying the vSphere unit of replication.

  Once you do this, you should be able to right click on a virtual machine, and then select Configure replication. When replication is set up for at least a virtual computer, you can include it in a group of Protection of SRM. You can do this by going to SRM UI, select "create Protection Group and selecting"vSphere replication"replication type.»

  See: VMware vCenter Site Recovery Manager 5.8 Documentation Center

  Good luck

  Stefan

• vSphere replication upgrade from 5.5 to 5.8 active server (not accessible)

  I was doing a vsphere replication update today from 5.5 to 5.8 and upgrade part seems to be okay.  After restarting the device however my vcenter reports that the server is not accessible.  I did something wrong?

  I followed the steps here. VMware vSphere replication 5.8 Documentation Center

  I searched a bit, but the only solution I found was to ensure and powering of the device and the Tower back on rather than just restart it a fix, but that has not seemed to help in my case.

  Thank you

  If anyone is curious who don't end up fixing it was the certificate as I feared.  So after all this ironed out, which was still two days of work because of how long I would have this vcenter install go.  Everything has been fixed after replacing my old self signed cert with a new.

• vSphere replication 5.1 - no Active

  When I set up replication vSphare, it says "Non-Active". I tried with no luck

  
  Rebooted device of VR on the two sites (NY & Dallas)

  Restarted vCenter Server on both sites (NY & Dallas)

  Appliane VR upgraded with the latest update available in both sites (NY & Dallas)

  Reset the database onboard on RV sites (NY & Dallas)

  
  No change in the environment. The replication worked very well in the past

  The problem has been resolved by activating vSphere replication on the properties of the port traffic.

• vSphere replication ports

  Hi guys

  We will be deploying vsphere replication between 2 sites that are geographically far apart.

  My question is to confirm if only this 2 ports must be open for replicatio to work?

  Port of 44046 31031

  any other port?

  I found this for Site Recovery manager

  http://pubs.VMware.com/SRM-51/index.jsp?topic=%2Fcom.VMware.SRM.install_config.doc%2FGUID-019985CE-1024-47B0-80AF-B96D1837916A.html

  

  Thank you very much

  Hello

  This is the same topic as part of vSphere documentation Replication - http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.replication_admin.doc/GUID-88B96DAB-8389-40A5-849B-D94ED5A3C4AD.html - in case you are using vSphere replication without SRM.

  The ports listed by you are for replication traffic and the source host must have access to these ports on the secondary site server VR devices to send deltas of the replica.

  VRMS uses the reverse proxy Server vCenter and management traffic to the other VRM through port 80 between the tunnels sites.

  In order to have 31031, 44046 ports and port 80 should be sufficient.

  I have not checked the c# Client UI SRM - I see that direct access to the port remote VRM 8043 was explicitly mentioned. It might be useful to check if it is really necessary in 5.1.

  The plugin of vSphere in vSphere client Web replication does not need to directly access the 8043 remote site port, it uses the vCenter Server proxy port 80.

  Kind regards

  Martin