Biliana's Accepted Solutions

Thanks for your reply. You said that the VRA is on a cluster, is thatcluster HA-enabled? Because in case HA needs to restart the VRA on another host, it does this through the ESX host and this mi... See more...
Thanks for your reply. You said that the VRA is on a cluster, is thatcluster HA-enabled? Because in case HA needs to restart the VRA on another host, it does this through the ESX host and this might have cleared out the OVF environment. And at at the same you will still have a working configuration until you start the upgrade or try to perform any operation through VAMI configuration page. To be on the safe side, I think that before upgrade, you can do power off and then power on the appliance (simple reboot is not enough) to make sure that the OVF env is recreated.
Are you using standalone version of VR , or you have SRM on top installed? When replicated VMs with VR are included in SRM protection groups, the Recover option is greyed out in the vSphere Repli... See more...
Are you using standalone version of VR , or you have SRM on top installed? When replicated VMs with VR are included in SRM protection groups, the Recover option is greyed out in the vSphere Replication UI. Is that your case?
Hi, If you have successfully recovered your VMs from site B to site A, then you can safely remove the replication using the Remove replication button. This will just clear your replication. It... See more...
Hi, If you have successfully recovered your VMs from site B to site A, then you can safely remove the replication using the Remove replication button. This will just clear your replication. It won't remove the running recovered VMs at site A.
If you are using vSphere Replication without SRM on top of it, Test Recovery is not available. The process you could follow in case you would like to keep your primary site online: 1) Perform ... See more...
If you are using vSphere Replication without SRM on top of it, Test Recovery is not available. The process you could follow in case you would like to keep your primary site online: 1) Perform Recovery using the second option (Recover with latest available data). In this way you would not need to power off source VMs and your primary site will be online. 2) After recovery is complete, stop the replications (which will be in Recovered state) 3) Power off recovered VMs, unregister them from VC inventory, but keep the disk files intact. 4) Manually configure all replications using the disks that were left over as initial seeds. This will cause only changes to be synced. To ease step 4, you could use vSphere Replication multi-vm configuration wizard. Just make sure that on the target datastore each disk that will be used as initial copy is put in the folder with VM name. Then, you could try to configure all VMs at once, performing searching for seeds and confirming to use them.
Assuming you are using vCenter Setup then you do not need to connect your site with another target site. In a single setup your site acts as both - a source and a target for replication.  If you ... See more...
Assuming you are using vCenter Setup then you do not need to connect your site with another target site. In a single setup your site acts as both - a source and a target for replication.  If you have setup everything correctly you can right-click a VM and configure it for replication pointing the same site for target site, but placing the virtual files on the NAS2 nfs datastore (the one you would like to store your replicated files).
Hi, Please see the following topics in vSphere Replication 5.1 documentation (Reconfiguring Replications). Yes, you can add another VMDK to a replicated VM. Replication will go into Error s... See more...
Hi, Please see the following topics in vSphere Replication 5.1 documentation (Reconfiguring Replications). Yes, you can add another VMDK to a replicated VM. Replication will go into Error state and you would need to reconfigure the replication and include the newly added disk to be replicated.
Are you using standalone VR or VR as part of SRM? I have checked when using standalone VR through vSphere Web Client that Guest OS quiescing is enabled and not grayed out with VR 5.1.1 build 1079... See more...
Are you using standalone VR or VR as part of SRM? I have checked when using standalone VR through vSphere Web Client that Guest OS quiescing is enabled and not grayed out with VR 5.1.1 build 1079383.
Configuring more than one VM in a consistency group (multi-VM consistency) in vSphere Replication is not supported at the moment. The VR scheduler algorithm runs on each ESX host and schedules th... See more...
Configuring more than one VM in a consistency group (multi-VM consistency) in vSphere Replication is not supported at the moment. The VR scheduler algorithm runs on each ESX host and schedules the transfers of all replicated VMs residing on that host. The scheduler uses information from previous transfers to estimate the time needed to perform the next transfer for each VM and tries to satisfy the RPO of each of them.Hope that this info is helpful.
Hi, Changing the RPO does not cause the replication to enter initial full sync state. When you have launched the wizard in Reconfigure(edit) mode, it will not tell you that it will re-use the ... See more...
Hi, Changing the RPO does not cause the replication to enter initial full sync state. When you have launched the wizard in Reconfigure(edit) mode, it will not tell you that it will re-use the existing disks, but it is aware of that. That said, you can adjust the RPO safely.
You can use either ShutDown Guest OS option in vSphere clients or the Shutdown button in System tab of VAMI UI for the appliance. The dialogs that you see are informative/confirmatory messages.
I guess that the only workaround for you then is to rename the vmdk files. Make sure that you backup your VM first or clone it somewhere for testing purpose to see if this will work for you. Here... See more...
I guess that the only workaround for you then is to rename the vmdk files. Make sure that you backup your VM first or clone it somewhere for testing purpose to see if this will work for you. Here is a KB article that describes how to rename VMDK files of a VM http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002491. Hope that this will be helpful to you.
Hi, Could you please make sure that "VMware VirtualCenter Management Webservices" service is started?
Hi Peter, Is your vCenter Management WebServices started?
Hi, There is no way to schedule a V2V task, while the source VM is powered on. That is because converter has to query the source VM. However, in case it is powered ON, the disks of the VM are... See more...
Hi, There is no way to schedule a V2V task, while the source VM is powered on. That is because converter has to query the source VM. However, in case it is powered ON, the disks of the VM are locked, and query source operation will not succeed. That is why there is a prerequisite the source VM to be powered off in the conversion wizard. Thank you.
In Converter 4.2, the synchronization occurs right after cloning process, and thus the changes occurred to the source during the cloning period are also applied to the destination machine.Current... See more...
In Converter 4.2, the synchronization occurs right after cloning process, and thus the changes occurred to the source during the cloning period are also applied to the destination machine.Currently, with this version of Converter, it is not possible to separate the cloning and syncronization tasks (i.e. you cannot clone the machine on Monday and syncronize it on Tuesday).