For a SAN to SAN migration I need to list all our datastores and blocksizes, It couldn’t be easier to do this with a script. LucD has written a great script to list VMFS Name, VMFS Version and VMFS Blocksize

New-VIProperty -Name VMFSVersion -ObjectType Datastore `      -Value {           param($ds)           $ds.ExtensionData.Info.Vmfs.Version      } `      -BasedONextensionProperty ‘Info’ `      -Force

New-VIProperty -Name VMFSBlockSizeMB -ObjectType Datastore `      -Value {           param($ds)           $ds.ExtensionData.Info.Vmfs.BlockSizeMB      } `      -BasedONextensionProperty ‘Info’ `      -Force

Get-Datastore | Select Name,VMFSVersion,VMFSBlockSizeMB

Output:

Credits goto: Luc Dekens

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:

When Creating a snapshot for a virtual machine fails

Or you receive the error:
File is larger than the maximum size supported by datastore

Note: This error does not occur on ESX 3.5 or earlier.

ESX 4.0 is able to detect when a snapshot file at maximum size cannot fit into a datastore. Instead of allowing the file to be created, which may not work correctly if it grows to big, ESX cancels the operation and displays the above error.

To confirm if the snapshot files may be too big, compare the size of the virtual machine’s base disks against the block size of the datastore which contains the virtual machine’s working directory.

Note: If you are using Raw Device Map, you should compare the size of the RDMs instead of the base disks.

Read more…

Daniel Buonocore

More Posts - Website