Sure thing! Glad I could help

Wow that was quick!  Thanks a lot!

And if you want the 'sync' to happen automatically when you create new LUNs in the future, then check the 'Auto Sync' box next to the VNX array in question.  But keep an eye on the performance of VSI, because these syncs can sometimes be expensive.

NYSP wrote: I also had a question about the LUN expansion.  When expanding, does it create a metaLUN or not?  From what we could tell, it does not, which is what we prefer anyway.

To answer your last question, seeing the reference to "VRAID", that corresponds to an underlying Pool (LUN: thin or thick).  You are correct that it doesn't create a metaLUN, but simply expands the existing pool LUN.  It is similar to if in Unisphere you were to right-click on the LUN and select "Expand", you specify "New user capacity".  Then, if it is a thick LUN only reserves that space or in the case of a thin LUN lets the system consume up to the new allocated size. 

Basically from the user's perspective you are just increasing the container (which underneath is made up of as many 1GB extents as required: reserved and/or allocated-on-demand).

We noticed something else after the lun was created.  In Unisphere, the Physical Drive and Logical Drive shows as Unknown.  I've attached a screen shot.

Is this still an issue?  I'm thinking it probably updated on its own by now.  The default "Update Interval in Hours" is 24 (unless it was modified).

However, next time try clicking on the "Update Host Info" button at the bottom of the same page from which you took the above screenshot.

Yep.  It appears to have updated on 4/27.  Thanks for the info!

Just FYI, if you're usiing VSI USM to extend a datastore, after the LUN is expanded, it will add new extent to the LUN so that the datastore is extended as well.

Adding new extent can be done outside of USM as well, details on page 136, section “Adding extents to Datastores” in  http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_3_server_config.pdf .