Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
When deploying a new VA to a second site vRanger says that it cannot deploy because the VA already exists (even though there is not a VA deployed)
원인
Setting up replication and could deploy a VA to the production site which had a VC but could not deploy to the remote site VC. The environments were set up with clusters on each site that were identically named. vRangers naming scheme does not delineate that the clusters are associated with different VC's so it sees the VA at the first site associated with the cluster and assumes that the second VA being deployed is going to the same cluster, you can see that within the MOB that the 2 clusters one separate hosts and VC's share the same name within VMware.
해결 방안
Create a new cluster at the remote site and move all hosts from old cluster to the new cluster at this site, deploy the VA to the new cluster.
