ashilkrishnan's Posts

Hi @thhg , vSphere replication appliance will only list VMs from vCenter to which it is registered. Please deploy another vSphere replication appliance in 2nd vCenter server and register it.  
Yes, you would have to stop and reconfigure replication after applying the KB.
Hi @lsarr , To begin with, I would suggest reviewing VMware tools compatibility with SRM version, time sync issues for these VMs and ESXi hosts. SRM and VMware tools interoperability  There is a n... See more...
Hi @lsarr , To begin with, I would suggest reviewing VMware tools compatibility with SRM version, time sync issues for these VMs and ESXi hosts. SRM and VMware tools interoperability  There is a note about this error in SRM release notes SRM 8.2 release notes  Hope that helps
Hi @AptitudeL , If your replication is managed by vSphere replication, it can consume additional space if you had configured point in time instances. If not,  you can also check --> https://kb.vmwar... See more...
Hi @AptitudeL , If your replication is managed by vSphere replication, it can consume additional space if you had configured point in time instances. If not,  you can also check --> https://kb.vmware.com/s/article/2150251  If this is storage based replication, It is better to check with storage vendor as well once. 
Hi @Elhadi88 , This should not impact vCenter functions. Please refer this article --> https://kb.vmware.com/s/article/57829 
Hi @thhg , vSphere replication VAMI portal can only be accessed using root credentials. Did you try to login to VR VAMI using root credentials ?  
Hi @JhonPaul1992 , vSphere HA is a cluster feature that protects VMs against host isolation/failure's and I don't see a reason why Microsoft would charge you for this cluster feature.  For ex: If t... See more...
Hi @JhonPaul1992 , vSphere HA is a cluster feature that protects VMs against host isolation/failure's and I don't see a reason why Microsoft would charge you for this cluster feature.  For ex: If the VM is residing on host1 and it is not accessible/down for some reason, vSphere HA will restart this VM on 2nd host.   Why are they charging you for additional license unless you are running 2 SQL server instances ?  
@Petersaints , You cannot change add-on server to primary or vice-versa.
Hi @padulka , Default behavior is to recover VMs in a bubble network when you perform test recovery to avoid conflicts with production environment. If you have a configured an isolated VM port grou... See more...
Hi @padulka , Default behavior is to recover VMs in a bubble network when you perform test recovery to avoid conflicts with production environment. If you have a configured an isolated VM port group just for test recovery and mapped the same in network mapping, VMs should recover in them. Hope that helps
Hi @Petersaints , If you cannot add 2nd interface on VR appliance at Site B, then you can deploy a add on server here and add 2nd interface on it for replications. Note: You cannot add more than on... See more...
Hi @Petersaints , If you cannot add 2nd interface on VR appliance at Site B, then you can deploy a add on server here and add 2nd interface on it for replications. Note: You cannot add more than one VR appliance(management/primary appliance), however you can add additional servers under it for load balancing/managing replications.  Pairing from Site B to C would use the existing appliances and when you configure VM replications, you can select the add-on servers. Deploy add-on VR server  Register add-on VR server to primary server  Isolate traffic on add-on server  Hope that helps  
@John_Helios Hi, There could be an issue with the key, if add(not assign) license key process itself is reporting this error. Can you confirm that the key correctly entered ?
@Rayes , SRM orchestrates and automates certain recovery tasks (Recover multiple VMs, storage mount, VM register, IP customization, custom power on scripts,etc.) for you when triggered. SRM works wi... See more...
@Rayes , SRM orchestrates and automates certain recovery tasks (Recover multiple VMs, storage mount, VM register, IP customization, custom power on scripts,etc.) for you when triggered. SRM works with two replication technologies: vSphere replication and storage based replication. SRM itself does not replicate any objects. SRM can either be combined with vSphere replication or a storage array level replication for recovery tasks: This should answer most of the questions:  SRM FAQs  (Refer questions under 'Product Requirements' & 'Product Features') https://blogs.vmware.com/virtualblocks/2017/06/22/srm-array-based-replication-vs-vsphere-replication/  I am not aware of any automatic failover solutions from VMware.
Hi @xspader , vCenter server is a management server and I don't see a reason to replicate it. You can replicate it and the option to recovery it would mostly be manual. If vCenter goes down, you won... See more...
Hi @xspader , vCenter server is a management server and I don't see a reason to replicate it. You can replicate it and the option to recovery it would mostly be manual. If vCenter goes down, you won't have access to vSphere replication plug-in and you need to manually browse and register vCenter VM by connecting directly to one of the hosts.  Additionally, you should look at other available options: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-226A925F-BF20-4A58-BF15-4A76B4CEDC84.html 
Hi @yasharsaatchi , Yes, you should be able to do that. To add, VMs can only be replicated between 2 sites. For ex: VM1 can only be replicated from Site-A to Site-B and the same VM cannot be replica... See more...
Hi @yasharsaatchi , Yes, you should be able to do that. To add, VMs can only be replicated between 2 sites. For ex: VM1 can only be replicated from Site-A to Site-B and the same VM cannot be replicated from Site-A to Site-C.
@Rayes , Yes that's right. If Site-A goes down, you need to login from Site-B and perform recovery of required plans.  
Hi @AhhhOK , SRM has to be on 8.3 windows to support migration to 8.4 appliance. Please prerequisites here --> Migrate SRM on windows to appliance  Either you can upgrade SRM 8.2 windows to 8.2 app... See more...
Hi @AhhhOK , SRM has to be on 8.3 windows to support migration to 8.4 appliance. Please prerequisites here --> Migrate SRM on windows to appliance  Either you can upgrade SRM 8.2 windows to 8.2 appliance and then upgrade to 8.4 appliance Or Upgrade SRM 8.2 to 8.3 windows and migrate to 8.4 appliance Hope that helps.
Hi @Omid_Heravi , Current SRM releases are more of 'no.of VMs' based and not CPU which was an option provided in earlier versions.  Note: Always provide product version when raising such queries. ... See more...
Hi @Omid_Heravi , Current SRM releases are more of 'no.of VMs' based and not CPU which was an option provided in earlier versions.  Note: Always provide product version when raising such queries. From the screenshot, you have a SRM enterprise license to protect 100 VMs. To check the license usage, please login to vCenter web client --> Licensing --> Solutions --> Assets and look for license usage against your SRM server. Hope that helps.
Hi @Sam0054 , If it's deleted from disk, there is no supported way of recovering it. For best advises on such matters, try reaching out to continuum  https://communities.vmware.com/t5/user/viewprof... See more...
Hi @Sam0054 , If it's deleted from disk, there is no supported way of recovering it. For best advises on such matters, try reaching out to continuum  https://communities.vmware.com/t5/user/viewprofilepage/user-id/2443 Hope that helps
Hi @Petersaints ,  Yes, you got that right.
Hi @iloinfotec , HP DL160 Gen 10 supports ESXi versions 6.0 U3 and later. For more information, please refer compatibility matrix here --> HP DL160 Gen10 - vSphere interoperability  Note: vSphere 5... See more...
Hi @iloinfotec , HP DL160 Gen 10 supports ESXi versions 6.0 U3 and later. For more information, please refer compatibility matrix here --> HP DL160 Gen10 - vSphere interoperability  Note: vSphere 5.5 and 6.0 are already end of support, so you should consider installing a newer and stable version. Hope that helps