In ESX I relocated VMDKS drives for SQLDATA,LOGS and SNAPINFO into their respective SQLTEST1_X folders, so now each VMDK was located on its own datastore.
Great so now snapdrive/SMSQL should talk to the storage and snap the distinct volumes where the VMDK's reside? Only it doesn't it simply snaps the volumes mounted at into ESX and doesn't follow the junctions in the namespace.
Does anyone out there know of anyway I can make this work? Is snapdrive still not aware of the namespace in CDOT and can't tell that it is in fact a distinct netapp volume under a junction.
This would be the neatest solution I can think of for getting rid of luns and still using snapdrive/SMSQL, does anyone know if this likely to ever work in future release?
Thanks in advance for anyone who can offer up any guidance\assistance.
Hi, I had similar discussion with the support team about deployment of Exchange in a VM over SMB and in that case there is no possibility to use SnapManager. Only deployment over SAN Is supported. I guess it is the same situation with VMWare. Also check Microsoft compatibility, there is a big chance that such deployment is not supported by them