I had an opportunity to play with beta version & must admit I'm loving the fact that MS SQL can now run over NFS end-to-end (well, you need the latest & greatest SMSQL as well, but I've heard it was supposed to be released together with SDW6.3)
I can't use it in production if the release notes don't support it:
Note: Support for performing Snapshot copy operations on virtual machine disks (VMDKs) in an NFS or VMFS datastore requires SnapDrive 6.3 for Windows or later and Virtual Storage Console 2.0.1 or later. Please check the availability of SnapDrive 6.3 for Windows and Virtual Storage Console 2.0.1 and install it before using this feature.
ok, this is starting to make a little bit of sense... I would like to make use of the new snap drive vmdk on NFS feature, but once I have installed snapdrive 6.3 and try to create a disk there is no option to create it on a nfs volume.
I have looked through the admin guide and it mentions that all of this is possible within snapdrive 6.3 but there is no information on how to do it, only info on how to create a new lun.
can anyone possibly point me in the right direction?
As I read in the Admin guide, the RDM file (of VMDK file) still needs to be on a VMFS datastore. So we are still stuck with those VMFS datastore only because the raw device mapping files needs to reside on a VMFS datastore.
The disk create command om page 221 of the admin guide tell us:
If the virtual machine resides on an NFS datastore, you must specify a VMFS datastore for the VMDK file.
I've tested it in our test enviroment and it's working as described in the admin guide. It seems that this is a VMware issue because when I want to move this machine from a VMFS datastore to a NFS datastore. This is not working and I get the message:
"Virtual Disk '...' is a mapped Direct-Access LUN which is not supported on the datastore "nfs_datastore"
I tought this was solved in 6.3 but it's NOT
"Support for VMDKs in NFS and VMFS datastores" on page 37 in the admin guide is not clear to me. I need to do more investigation on this topic.
OK, I need to revisit it with the official code then (I was using beta version)
What I can say though is it did work nicely for me, without pestering for any RDM references, etc. - it was a 'plain' VMDK file (crated by 'add new disk' in vCenter \ edit VM properties), located in an NFS datastore, seen & being fully manageable via SDW interface.