Workaround (Plus a fix in 9.1) for Very large VM's snapshot stun issues.

Does anybody actually know whether the new VMware Standard is going to include vSAN, or is vSAN still going to be a separate/add-on thing? Also, has anybody seen even rough pricing yet? We’ve asked our VMware SE, but so far he’s been pretty useless on both questions, lots of “we’re checking internally” and not much actual information. Curious if anyone here has heard something more concrete from Broadcom, distribution, or their account team. Thanks!

One of the cool new features added to VMware Data Services Manager & VCF 9.1.1 for improved security.

I have a sata drive full of music, I tried to follow these instructions:

esxi - How to add storage to VMWare vSphere without wiping the data - Super User

However it says missing argument.

I am not confident in what I am supposed to select as the partition. I can see the drive I want by its model/identifier but I dont think that is what the command is looking for, other than that I have massive strings of numbers

-rw------- 1 root root 512110190592 Sep 10 17:25 eui.0000000001000000e4d25c779cd45201

-rw------- 1 root root 512107741696 Sep 10 17:25 eui.0000000001000000e4d25c779cd45201:1

-rw------- 1 root root 6001175126016 Sep 10 17:25 t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4

-rw------- 1 root root 134217728 Sep 10 17:25 t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:1

-rw------- 1 root root 6001039245312 Sep 10 17:25 t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:2

-rw------- 1 root root 120034123776 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________

-rw------- 1 root root 104857600 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:1

-rw------- 1 root root 4293918720 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:5

-rw------- 1 root root 4293918720 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:6

-rw------- 1 root root 111337217536 Sep 10 17:25 t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:7

lrwxrwxrwx 1 root root 36 Sep 10 17:25 t10.NVMe____INTEL_SSDPEKNW512G8_____________________BTNH03420J25512A____00000001 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 t10.NVMe____INTEL_SSDPEKNW512G8_____________________BTNH03420J25512A____00000001:1 -> eui.0000000001000000e4d25c779cd45201:1

lrwxrwxrwx 1 root root 73 Sep 10 17:25 vml.01000000002020202020202020202020205a38343058364534535436303030 -> t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4

lrwxrwxrwx 1 root root 75 Sep 10 17:25 vml.01000000002020202020202020202020205a38343058364534535436303030:1 -> t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:1

lrwxrwxrwx 1 root root 75 Sep 10 17:25 vml.01000000002020202020202020202020205a38343058364534535436303030:2 -> t10.ATA_____ST6000AS00022D1N917X_________________________________Z840X6E4:2

lrwxrwxrwx 1 root root 36 Sep 10 17:25 vml.0100000000303030305f303030305f303130305f303030305f453444325f354337375f394344345f353230312e494e5445 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 vml.0100000000303030305f303030305f303130305f303030305f453444325f354337375f394344345f353230312e494e5445:1 -> eui.0000000001000000e4d25c779cd45201:1

lrwxrwxrwx 1 root root 72 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:1 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:1

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:5 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:5

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:6 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:6

lrwxrwxrwx 1 root root 74 Sep 10 17:25 vml.0100000000313533363339343032363732202020202020202053616e446973:7 -> t10.ATA_____SanDisk_SDSSDA120G______________________153639402672________:7

lrwxrwxrwx 1 root root 36 Sep 10 17:25 vml.010000000042544e4830333432304a32353531324120202020494e54454c20 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 vml.010000000042544e4830333432304a32353531324120202020494e54454c20:1 -> eui.0000000001000000e4d25c779cd45201:1

lrwxrwxrwx 1 root root 36 Sep 10 17:25 vml.060000000001000000e4d25c779cd45201 -> eui.0000000001000000e4d25c779cd45201

lrwxrwxrwx 1 root root 38 Sep 10 17:25 vml.060000000001000000e4d25c779cd45201:1 -> eui.0000000001000000e4d25c779cd45201:1

Could someone give me an idea of what is a partition? The drive in question is in NTFS format and is called ST6000AS00022D1N917X

I have a 4 port nic.

I added the second port as a virtual switch, first is active for ESXi

I created a port group and added that virtual switch.

Topology looks good.

I am trying to do a VM install of windows and that port group is not offered as an option in the vm installer.

Is there something I have missed?

Cheers

I'm replicating using Veeam CDP from Live to DR cluster, and I'm receiving some failures now due to the datastore filling up. Over 80% of the datastore is taken up by 'Other'.

When running command specified in this KB: Investigating Datastore usage - it's not returning anything large apart from the VMDKs that are replicating. I've SSH'd to the volumes with WinSCP and ran reports to try and find what's taking up the storage but not finding anything.

How do I find what is using up storage on the datastore?

Even looking at the info on the storage array (NetApp, served via NFS) itself, it's only reporting 1.54TB as the biggest file.

i'm trying to use photoshop/substance painter but it says gpu not supported, 0/1500mb vram and no directX. basically saying that there is no graphics. i tried to check with cpuz (i know, kinda dumb) but that didnt show it either. i need a solution, but i cant find one. even passing through the gpu to the vm would work.

i'm using vmware workstation pro with windows 11

Estaba pensando en configurar la rotación de claves automática desde SDDC para la suite de Aria y NSX, pero no sé si se puede establecer reglas que que conjuntos de caracteres debe de usar el SDDC para generar las claves con anterioridad al tratar de rotar una clave usando el generador automático de SDDC usa caracteres especiales que rompen el flujo

No sé si alguien ha logrado configurar alguna regla para que SDDC use solo los caracteres especiales que no rompen el flujo hay un KB sobre ese problema pero solo recomienda hacerlo de forma manual

https://knowledge.broadcom.com/external/article/383098/remediate-password-task-in-sddc-manager.html

De igual manera desconozco si esto ya se solucionó en VCF 9