dbalcaraz's Posts

Hi, Really weird... So, you created a clone and obviously you have a full independent VM with the same specs as the original. Why do you have to use vCCS to "move" it to another ESXi? Anyway, verify that you're using the correct VM when using vCCS, never see that error and I made many P2V and V2V. Another thing to check is the .vmx file of the clone and see which are the vmdk files that are using (maybe something wrong is there, who knows...) Hope this helps.

Hello alainap84, A couple of ideas for your DR. vSAN is as redundant as you want to configure it, of course, more disk groups with more disks will become in something more robust. Depending on the corruption for vSAN, the data could be useless, I mean, if your RAID5/6/whatever fails, all your data couldn't be re-constructed, therefore, no data. Best thing for redundancy is replication to another site/location, more disks per diskgroup, in order to increase resiliency and have a good VMware contract, is always a must! Hope this helps. Regards,

Hello, Is the HW supported by the HCL? If so, have you applied any recommendations from Supermicro? I know Supermicro has some gaps about the Hardware Compatibility List so, I suggest you take a deep look into that. Also, you could update your ESXi 6.5 to the latest update available (which could help to mitigate any issue)

Hi, 1. The witness must be on the same subnet as the active and passive node? Yes because they have to communicate in order to sync. Check this article: vCenter HA Deployment Options 2. If it doesn't have to be how much better it is in the same subnet or another? Check the previous article. You need a subnet for the nodes (an internal subnet) and then an additional interface for the active node. 3. What will happen if the latency is not guaranteed between all nodes? Failures can occur and they won't be on sync. 4. What if the witness cannot be reached? The VCHA could be broken if there is a lot of time since they have been on sync. Hope this helps.

What I am saying is that a KVM switch must work because is not OS aware. That means that whatever OS or Hypervisor are you using, it must work. I never saw a KVM switch that works for certain OSes...

Using CPU reservation is not a common thing, I mean if you reserver a certain amount of CPU compute it can have it's cons. Anyway, a thing you can do is (and probably the only one) is to multiply the speed of a singe core to the amount of times you want to "reserve". That would be an approximation because it's not always the exact amount. If you take 2300 MHz x 16 = 36800 MHz, that would be the amount of CPU compute to reserve. You could find more information here: Calculating Maximum CPU Reservation For a VM With 6 CPU Hope this helps.

Let's see if I can help. You are installing ESXi 6.7 in the HW, and when you try to use a KVM it's not working? THe KVM is not OS oriented so, if there is a Hypervisor like ESXi, Windows Server or any other OS it doesn't matter. Could you explain it again?

As daphnissov states, this is not related to the VMware product. From my experience, I can tell you that, what you see in the console it can be related to Windows Server Core or to the Windows Server booted in Safe Mode with command prompt. Probably is the last one but, be sure before making any changes.

So, as I said there isn't a recommended environment based on the version of the Hypervisor (in this case ESXi 6.0U3), if you can get one that is supported instead than a legacy one, better for you

Hi, I really don't understand what are you asking for... the recommended environment, do you mean only the Guest OS? It can be whatever you want from Windows Server (just be aware of the EOS versions) and regarding the ESXi the same. There isn't a "recommended" environment, the one you can support, the latest should be the best but also can have some bugs.

Hi, I updated several hosts this week to 6.7.0 U2a and didn't try this. I could check tomorrow to see if I experienced the same. I was going to say to restart the Management services but, as you already re-installed the hypervisor there is no need to do it. I will let you know.

Hi, To export/import a VM  as OVF, you're good with Essentials, Essentials plus gives you DRS and HA. And well, if you don't mind yes, you can export the vCSA and import it in your ESXi host destination without problem. Then you just have to register the host in the new vCenter (would be great disconnect the previous host from this vCenter before exporting it).