mmarinov's Posts

Hi, Shutting down the VR management VMs on the source site would not pause/stop the traffic since the traffic goes from the source ESXi. What version of VR you use? In VR 6.0 we introduced Tr... See more...
Hi, Shutting down the VR management VMs on the source site would not pause/stop the traffic since the traffic goes from the source ESXi. What version of VR you use? In VR 6.0 we introduced Traffic isolation feature - vSphere Replication 6.0 Documentation Center‌. So this is one option. Another option is to select all the replications and manually trigger pause. This is better than un-configure them since you are going to have much troubles later on when you want to re-configure them back again. Regards, --Martin
Hi, Thanks for providing this feedback. Some clarification questions * Is there any pattern/wizard page/view you observe this slow performance in the vSphere Replication * Is it only the th... See more...
Hi, Thanks for providing this feedback. Some clarification questions * Is there any pattern/wizard page/view you observe this slow performance in the vSphere Replication * Is it only the the VR UI that is slow or there is slow performance in the Web Client as well? Thanks Regards, --Martin
Hi, There isn't a built-in way in the product. However, you could probably want to take a look at https://communities.vmware.com/thread/509660 Regards, --Martin
Hi, Understand that manual configuration here is a pain task. Few questions though: * Do you use seeds on the target site? * Did you consider as an option to use some automation tool, such a... See more...
Hi, Understand that manual configuration here is a pain task. Few questions though: * Do you use seeds on the target site? * Did you consider as an option to use some automation tool, such as vRO? You can look here VMware vCenter Orchestrator Plug-In for vSphere Replication 6.0 Release Notes Regards, --Martin
Hi, As of vSphere Replication 5.8 there are some useful graphics that could help you in your case. If you have only 1:1 pair of sites, e.g. one source and one target site, then: - go to the ... See more...
Hi, As of vSphere Replication 5.8 there are some useful graphics that could help you in your case. If you have only 1:1 pair of sites, e.g. one source and one target site, then: - go to the source site's VC - Navigate to VC's Monitor -> vSphere Replication -> Reports In this page you will notice several graphics that display different metrics. The one you are interested in is titled "Transferred bytes". If you want more detailed information look at this blob on how you can retrieve information through vCenter Server's Events: http://www.virtu-al.net/2013/06/14/reporting-on-rpo-violations-from-vsphere-replication/ with PowerCLI. The same way but using hbr.primary.DeltaCompletedEvent event (more info on vSphere Replication events can be found here: List of vSphere Replication Events) you can extract and manipulate the data for your needs. Another way of monitor this is by using the new feature in vSphere Replication 6.0 for network isolation by setting the replication traffic to a specific NIC and then monitor its traffic. See more info on traffic isolation feature in vSphere Replication 6.0 at Isolating the Network Traffic of vSphere Replication Regards, --Martin
Hi, As of vSphere Replication 6.0 you are required to configure the solution to work with the Platform Service Controller (PSC) the vCenter is working with. In order to do that : - Navigate ... See more...
Hi, As of vSphere Replication 6.0 you are required to configure the solution to work with the Platform Service Controller (PSC) the vCenter is working with. In order to do that : - Navigate to the the https://VR_appliance_IP:5480 - Login with credentials you have provided during deployment process of the appliance - Go to VR -> Configuration tab - Provide the address of PSC within the Lookup service address box - Provide the administrative credentials for your SSO - Click "Save and Restart Service" button Regards, --Martin
Hi, Can you check the vSphere Web Client logs if com.vmware.vcHms is logged somewhere. Sometimes, because of network issues, the web client is unable to download properly provided plugins. Not... See more...
Hi, Can you check the vSphere Web Client logs if com.vmware.vcHms is logged somewhere. Sometimes, because of network issues, the web client is unable to download properly provided plugins. Not a good solution at all, but in most of the times, restart of the web client service resolves the problem. Also please be sure that the web client machine can resolve the address of the vSphere Replication server. Also keep in mind that as of vSphere Replication 6.0 you are required to configure the solution to work with the Platform Service Controller (PSC) the vCenter is working with. In order to do that : - Navigate to the the https://VR_appliance_IP:5480 - Login with credentials you have provided during deployment process of the appliance - Go to VR -> Configuration tab - Provide the address of PSC within the Lookup service address box - Provide the administrative credentials for your SSO - Click "Save and Restart Service" button Regards, --Martin
Hi Manuel, vSphere Replication support using seeds during the initial sync of the virtual machine. To achieve that you need to manual download the vmdk files from the source, through the vSphe... See more...
Hi Manuel, vSphere Replication support using seeds during the initial sync of the virtual machine. To achieve that you need to manual download the vmdk files from the source, through the vSphere Web Client, ship them to the other site and manually upload them on a the desired datastore. Please consider upload them in a manually created folder on the datastore rather on the root folder. Then from the source site start the configuration wizard and point the destination folder the one that you have created vSphere Replication will recognize the vmdks and will sync just the changes. Hope this helps. Regards, --Martin
Hi, Moving the appliance via Vmware technologies is perfectly fine. The message/warning you are receiving is just to warn you that this VM is a critical one and you should be careful. The sam... See more...
Hi, Moving the appliance via Vmware technologies is perfectly fine. The message/warning you are receiving is just to warn you that this VM is a critical one and you should be careful. The same message will appear if you invoke power off of this machine. Regards, --Martin
Hi again, The VMware engineering nail down the issue and it turns out that it is observed only when VR 5.8 and SRM 5.8 are running in the same vSphere Web Client. Release notes of VR 5.8 have ... See more...
Hi again, The VMware engineering nail down the issue and it turns out that it is observed only when VR 5.8 and SRM 5.8 are running in the same vSphere Web Client. Release notes of VR 5.8 have been updated: VMware vSphere Replication 5.8 Release Notes.Unfortunately there is no workaround. We are working to resolve the issue. Regards, --Martin
Hi, There is a known issue after upgrade VR : vSphere Replication actions in vSphere Web Client are not available after upgrade. If you follow the steps in Finish Upgrading the vSphere Repl... See more...
Hi, There is a known issue after upgrade VR : vSphere Replication actions in vSphere Web Client are not available after upgrade. If you follow the steps in Finish Upgrading the vSphere Replication Appliance If the vCenter Server IP Changes but use vSphere Web Client 5.5 before you upgrade the vSphere Replication appliance, replication actions through the vSphere Replication plugin are not available. Workaround: Restart the vSphere Web Client service in Windows Services, or in the vCenter Server virtual appliance management interface (VAMI) if you are using the vCenter Server Appliance. Source: VMware vSphere Replication 5.5 Release Notes Hope this helps.
Glad I've been in help. Regarding other blank charts - Can you try configure a new "fake" replication and see if this picture is changing - you should open an SR and provide VR logs so Vmwar... See more...
Glad I've been in help. Regarding other blank charts - Can you try configure a new "fake" replication and see if this picture is changing - you should open an SR and provide VR logs so Vmware employes can troubleshoot the problem.
Sorry, for bringing the confusion. When I said maximize I meant to maximize just the portlet where the hosts are shown. You can see a maximize icon next to the tile Replicated VMs (by host) on th... See more...
Sorry, for bringing the confusion. When I said maximize I meant to maximize just the portlet where the hosts are shown. You can see a maximize icon next to the tile Replicated VMs (by host) on the right side.
Hi, Regarding the replication stats: The stats for VR are not loaded from the vpxd, but rather internal implementation. Is this the same behavior when you chose custom time interval? Also, ... See more...
Hi, Regarding the replication stats: The stats for VR are not loaded from the vpxd, but rather internal implementation. Is this the same behavior when you chose custom time interval? Also, could you share what is the average RPO you are using for your replications? Regarding the hosts: When the portlet is in original size it shows just the top two hosts. However if you maximize the portlet you will see all the hosts and the statistics about how many VMs are replicated per host.
Hi, In order to use vSphere Replication you need to deploy vSphere Replication Appliance on each VC. Once you do that, go on the source VC, navigate to its Manage -> vSphere Replication ->Tar... See more...
Hi, In order to use vSphere Replication you need to deploy vSphere Replication Appliance on each VC. Once you do that, go on the source VC, navigate to its Manage -> vSphere Replication ->Target sites tab within the vSphere Web Client and create a connection to the other site (VC+VRA). Once you complete this connection creation you can use it to replication from the source VC to the other site. Hope this helps. Regards, --Martin
Hi, Showing that the VR is enabled means VR registered in VC's ExtensionManager correctly. However, the VR UI is not able to communicate with the VR management server. Can you check if: -... See more...
Hi, Showing that the VR is enabled means VR registered in VC's ExtensionManager correctly. However, the VR UI is not able to communicate with the VR management server. Can you check if: - https://vr_management_server_ip:5480 is operational and you are able to log in - If yes, please restart the service from the this VAMI UI - If no, check please if the appliance is correctly accessible through the network - If no, you will need to open an SR and provide the logs from the appliance Regards, --Martin
Hi, vSphere Replication as a product requires VC to be installed and is fully operational. from VR 5.1 and above you can replicate within the same VC or between different VCs. With VR 5.8 th... See more...
Hi, vSphere Replication as a product requires VC to be installed and is fully operational. from VR 5.1 and above you can replicate within the same VC or between different VCs. With VR 5.8 there is an option to protect your workloads within vCloud Air as a target site where everything will be pre-setup for you and no installations are required from the customer. You can read more on: http://www.vmware.com/files/pdf/vchs/VMware-vCloud-Hybrid-Service-Disaster-Recovery-DS.pdf http://www.vmware.com/files/pdf/vchs/vCloud-Hybrid-Service-Disaster-Recovery-FAQ.pdf
Hi Chris, If the initial sync was not completed the status of the replication must be Initial Full sync. Once it completes there are still some diffs between the original VM and its replica fi... See more...
Hi Chris, If the initial sync was not completed the status of the replication must be Initial Full sync. Once it completes there are still some diffs between the original VM and its replica files. Hence the product need to perform some additional sync - thus the replication status is changed to sync. The amount of transferred bytes is published when the sync completes - yes. However you should check when previously the inital full sync has completed. I strongly believe you should have event published 2 days ago for this.
You can look in the VM's and VC's events to check how much time it took for the sync and the amount of data that was transferred. Thus you can do the math if 12 hours is enough or you need to cha... See more...
You can look in the VM's and VC's events to check how much time it took for the sync and the amount of data that was transferred. Thus you can do the math if 12 hours is enough or you need to change it. Keep in mind that IO is changing in time then 12 hours could be enough at some point and insufficient in another. Hope this helps. Regards, --Martin
Hi, Are you using VR from within the desktop client or from within the web client?