virtualhelp's Posts

Hello everyone, I have a virtual machine that has RDM disks attached in virtual mode, and configured with the Failover Clustering Role at the operating system level. The client wants to convert those RDMs to VMDK For that, use vmware converter, it converts the RDM into VMDK without problems, however when validating the disks in the failover clustering, they appear as blocked with the following error. Or would it be advisable to disable failvoer clustering before migrating the cm with vmware converter? and then when lifting in the other site, activate the river, from failvoer clustering? Any suggestions so that I can see those disks in the failover clustering.        

Good night I have the following scenario to replicate some VMs: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + SRM 8.5 and VR 8.5. Site 3 (Recovery Site): vCenter 7.0 + SRM 8.5 and VR 8.5. We have the scenario where we want to replicate some critical VMs that are in Site 1. This Site would be temporary. We have the SRM and vsphere Replication instances connected from Site 1 to Site 2. However, when we want to connect the SRM instances from Site 2 to Site 3, it does not allow it, it gives us an error indicating that the previous sites are already connected. Basically the plan consists of replicating some VMs from Site 1 to Site 2 and then to Site 3, where Site 3 would be our recovery site. Since Site 1 would be left out due to obsolescence issues. We want to validate if this idea is feasible, we would display: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + Two instances SRM 8.5 and VR 8.5. (Here you would have Two SRM instances and two vsphere Replication instances connected to a single vcenter instance.) Between Site 1 and Site 2 it will make the connection of sites between them. Here you would use the first instance of SRM and vsphere Replication belonging to Site 2. Between site 2 and Site 3 it would make a new site connection between them, here what it would do is make the second SRM instance and vsphere Replication point to Site 3. Site 3 (Recovery Site): vCenter 7.0 + SRM 8.5 and VR 8.5. Any comment or suggestion is very helpful. Thank you.

Good night I have the following scenario to replicate some VMs: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + SRM 8.5 and VR 8.5. Site 3 (Recovery Site): vCenter 7.0 + SRM 8.5 and VR 8.5. We have the scenario where we want to replicate some critical VMs that are in Site 1. This Site would be temporary. We have the SRM and vsphere Replication instances connected from Site 1 to Site 2. However, when we want to connect the SRM instances from Site 2 to Site 3, it does not allow it, it gives us an error indicating that the previous sites are already connected. Basically the plan consists of replicating some VMs from Site 1 to Site 2 and then to Site 3, where Site 3 would be our recovery site. Since Site 1 would be left out due to obsolescence issues. We want to validate if this idea is feasible, we would display: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + Two instances SRM 8.5 and VR 8.5. (Here you would have Two SRM instances and two vsphere Replication instances connected to a single vcenter instance.) Between Site 1 and Site 2 it will make the connection of sites between them. Here you would use the first instance of SRM and vsphere Replication belonging to Site 2. Between site 2 and Site 3 it would make a new site connection between them, here what it would do is make the second SRM instance and vsphere Replication point to Site 3. Site 3 (Recovery Site): vCenter 7.0 + SRM 8.5 and VR 8.5. Any comment or suggestion is very helpful. Thank you.

Hello, I have to replicate a pool of VMS that have RDM disks attached. On my main site I have Site Recovery Manager and vsphere Replication. The secondary site is Vxrail nodes, here I also have an SRM instance and another vsphere Replication. Reviewing some KBs, they tell me that I must change the disk controller from physical to virtual mode and I can replicate the vm without any problem. Motivated that vsphere replication only supports virtual mode and not physical mode. However, I would like to validate if I should take into account another consideration to replicate these VMs with RDM.

Hello, I currently have two Sites, with Site Recovery Manager (Primary Site and Secondary Site). Each site has its respective licensing. Soon we are about to receive new physical servers, what we want is for these new servers to become our new Secondary Site, which would lead to deploying and configuring a new instance of Site Recovery Manager. The Secondary Site that we currently have would be our new main Site. Of course all this once we run the replica of our VMs. The question I have is about licensing. Can we reuse the license from the First Site once we replicate to the Secondary Site? Or should we buy a new license for the new SRM instance?

I have some questions about Site Recovery manager, I hope you can help me: Could you configure Site Recovery Manager 8.4 on a site with VMFS storage and the alternate SRM 8.5 site with vSAN storage? Do the primary site hosts have vSwitch Standard and the alternate site hosts have distributed vSwitch. (This would cause problems)? Can both SRM appliances be in the same IP range of the vCenter, or should the range be different?

Hello, The deployment of a new vCenter belonging to a vxrail cluster with three nodes began. Both the ESXi and vCenter of the new vxrail cluster are 7.0.   The client has a productive vCenter with version 6.7 and ESXi with version 6.5, where all their virtual machines run. Now they want to migrate some VMs to the new vxrail cluster.   What options would you have to perform this migration from your vCenter 6.5 to the new VxRail cluster with vCenter 7.0.   Could you perform a vMotion accroos vCenter? For that I need to configure link mode?   If you can give me suggestions please.

Good evening, I would like to validate how I can obtain the amount of IOPS that a VM has generated in a period of one month. Is there any tool that can give me this info? vRealize Operations manager can give me this information?, or rvtools? Or some specific command? regards

Hello I have a Powerdeg R440 server with an intel xeon bronze 3106 cpu running ESXi 6.5 U2 GA version, and I want to upgrade it to ESXi 7.0 U3F. Looking at the compatibility matrix I see that the R440 is compatible with the intel bronze 3200 series CPU.   The other Powerdeg R640 server with an intel xeon platinum 8168 cpu with ESXi 6.5 U2 GA version, and I want to upgrade it to ESXi 7.0 U3F. Looking at the compatibility matrix I see that the R640 is compatible with the intel 8100 and 8200 series CPUs. My question is if that intel xeon bronze 3106 and intel xeon platinum 8168 CPU family support ESXi 7.0 U3

Hello, I currently have a vCenter and ESxi in version 5.1. I just deployed a new vCenter and ESxi in versions 7.0 One option would be to export those VMs to ova and then import them to the new vcenter. But I would like to know if it is feasible to add those vCenter 5.1 nodes to the new vCenter 7.0 cluster and then with a vmotion move those VMs to the new ESxi 7.0

Hello, I am about to upgrade a vCenter 6.5 and ESXi 6.5 U2 to version 7.0 U3. I understand that it is possible to upgrade directly to version 7.0 U3. My question is about licensing, because the client has licensing. At the end of the upgrade both vCenter and ESXi, new version 7 licenses must be placed? I mean if the client buys a new license. Because I understand that when upgrading from a version 6.xx to another version 6.xx the same license can be used. But for this case, as it is version 7, I have my doubts.

Hello partners, Today a strange situation arose, in an ESXi host I decided to disable the IPv6 configuration and after the reboot, the host did not respond to ping, causing it to not be able to reach the graphical interface. In the Ipv4 configuration, you have your respective Ip, mask and gateway. I even activated IPv6 again to see if it could respond and nothing. The problem arose after rebooting ESXi. Any suggestion.