Information about physical storage elements appears on the Storage Views tab. It includes such data as storage arrays, array IDs, and so on. This type of information can be helpful when you need to track virtual machine-to-storage relationships and configuration, or to identify any changes in physical storage configuration. You can simply establish this relation by selecting appropriate menu from drop down as shown below
Below is the view while selecting “Show all Virtual Machines”
You can see above as the view changes, the options column changes to provide you more relevant information
For each path you can also display the path’s name. The name includes parameters that describe the path:
adapter ID, target ID, and device ID. Usually, the path’s name has the format similar to the following:
fc.adapterID-fc.targetID-naa.deviceID as shown below
You can determine whether your virtual disk is in thick or thin format.
1 Select the virtual machine in the inventory.
2 Click Edit Settings to display the Virtual Machine Properties dialog box.
3 Click the Hardware tab and select the appropriate hard disk in the Hardware list.
The Disk Provisioning section on the right shows the type of your virtual disk.
4 Click OK.
- First step is to unmount the datastore, right the datastore and select unmount
Second step is select the device and select detach
Below figure shows how iSCSI initiator gets authenticated by target.
Second part of the figure explains when metadata gets updated
Metadata is updated each time you perform datastore or virtual machine management operations. Examples of operations requiring metadata updates include the following:
- Creating, growing, or locking a virtual machine file
- Powering a virtual machine on or off
- Creating or deleting a VMFS datastore
- Expanding a VMFS datastore
- Changing a file’s attributes
- Creating a template
- Deploying a virtual machine from a template
- Migrating a virtual machine with vMotion
esxcli storage core device vaai status get
In above screen VAAI is not supported by storage, it is my local drive.
In above screen block zeroing supported, every thing else is not supported. In Configuration->storage tab, you’ll see status as Unknown. If all status was unsupported it will provide status as unsupported.
Recently I came across excellent presentation from VMUG (VMware User Group) Scotland. They have uploaded very good slides here
- VSA (vSphere Storage Appliance)
- New features on vSphere Storage
Both slides are full of information. I think it will help you preparing for VCP5.0
After reading all the 10 links posted in below blog here, I came up with following likely questions. Even if they do not come in exam, these are basic things you must know about vSphere 5.0 Storage.
- What is the block size in VMFS-5?
- What is the largest single extend possible on VMFS-5
- What is the size sub block in VMFS5?
- Where does the file with less than 1 KB size get stored?
- What is the maximum file count size supported by VMFS-5
- Is there any disruption of VM when you upgrade VMFS-3 to VMFS-5
- Upgraded VMFS-5 supports which 3 new features
- VMFS-5 upgraded from VMFS-3 crosses 2 TB limits what happens to partition type?
- What is starting partition sector start for VMFS-5 and what is starting partition sector for VMFS-5 upgraded from VMFS-3
- What is the maximum supported size for passthrough(Virtual) RDM
- What is the new technology used for Storage vMotion?
- What is latest features offered by Storage vMotion?
- What are three new features offered via VAAI?
- List down four hardware acceleration for NAS?
- How ATS is more effectively used in vStorage, what mechanism is used?
- In Storage DRS can you mix VMFS & NFS datastores?
- After initial placement when else you have opportunity to select DRS datastore? And what are the decision parameters
- What are the two main metrics which SRDS use to make decisions and what are their thresholds set at?
- What is the default percentage of utilization difference before SRDS recommends the move?
- What is the observation period before SRDS can start making any recommendations?
- What is the name of the tool used for managing GPT partitions?
- What four partition types observed on ESXi5.0
- How does SDRS uses VASA?
- What does vendor provider do in VASA?
- What information would be included in storage capability?
- What other information will be made available by VASA?
If you need the answers go through all the 10 links again. I have created document for my own reference, I have uploaded it here. You can use it.