I have been told that VSC 2.0.1 should be out next week so my SQL project can move forward. This is what I have done so far:
1. Carved out 4 volumes on my filer, one each for SystemDB, UserDB, Logs, and SnapInfo
2. Created 4 NFS exports corresponding to each of these volumes
3. Add the 4 shares to each of my VSphere hosts using the Configuration tab of the Virtual Center client
4. Shutdown what will be my new SQL 2008 server.
5. Edited its settings using the Virtual Center client and added 4 hard disks corresponding to the 4 datastores created in step 3
6. Brought the SQL server back up and using the Manage MMC, added the 4 volumes to my server giving them the proper names and drive letters. Now I have a SQL 2008 server with of course a C drive and 4 other drives labeled SystemDB, UserDB, Logs and SnapInfo
From here it should be straightforward to install SQL 2008, Snapdrive 6.3, and Snapmanager for SQL 5.1. My understanding is when using NFS, Snapdrive does not create or manage the NFS share it strictly is there to help assist with making snapshots via Snapmanager for SQL. This is in contrast to iSCSI and FCP where Snapdrive is actually used to create and manage the LUNs on the filer along with assisting in the snapshot process.
From here I can bring up what will be a new Virtual Center (vSphere 4.1). On that machine I will install VSC 2.0.1 and SMVI
Do all these steps sound about right?