Data Backup and Recovery

Snap Drive 6.3

itmsnetapp

Is there any word on release date of snap drive 6.3? We are right in the middle of a migration project and would rather go straight to 6.3 for NFS support.

cheers

26 REPLIES 26

kris_boeckx

Hi,

As far as I know it will be there 1ste week op september.

See http://blogs.netapp.com/storage_nuts_n_bolts/2010/07/snapdrive-63-support-for-vmfs-and-nfs.html for more info.

greetings,

Kris Boeckx

Pidpa

kris_boeckx

Snapdrive 6.3 is here ...

https://now.netapp.com/NOW/download/software/snapdrive_win/6.3/

Greetings to you all !

Kris Boeckx

Pidpa

radek_kubka

Wow, awesome - thanks for the heads up!

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)

Regards,
Radek

erick_moore

Don't forget to read the fine print, you need VSC 2.0.1 for SMSQL 5.1 and SD 6.3 to do VMDK snaps on NFS.  Unfortunately VSC 2.0.1 is no where to be found.

radek_kubka

It actually worked for me with VSC 2.0.

erick_moore

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.
  • radek_kubka

    Yeah, no argument here - fully appreciated.

    I was just happy as a kid when I managed to successfully set it up in our lab Requirement for official support in a prodcution environment is a different story though.

    Having said this, I have a gut feeling VSC 2.0.1 should surface soon, so people can actually make a practical use of this cool feature (unless someone made a typo writing the note! )

    chriszurich

    I'm having issues with viewing LUNs provisioned over FC from a filer running 8.0.1.  I'm curious what version of Data ONTAP you're running?

    Test Environment

    FAS3140 8.0.1 7-Mode

    FAS3170 (HA Cluster) 7.3.3 7-Mode

    Windows 2003 Professional Server (32-bit)

    NetApp Host Agent ver. 2.7

    DFM 4.0

    SnapDrive 6.1.1 Shows LUNs provisioned from filers running 7.3.3 but fails to show LUNs from filers running 8.0.1.

    SnapDrive 6.2 works with no errors

    SnapDrive 6.3: Shows LUNs provisioned from filers running 7.3.3 but fails to show LUNs from filers running 8.0.1.

    Error:

    Failed to enumerate LUNs.

    Error code : An attempt to obtain list of volumes on the storage system <8.0.1 array name>' failed. Error code: 13011. Error description: No netapp element in response.

    itmsnetapp

    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?

    I have the latest vsc installed.

    radek_kubka

    Hi,

    This may be a tad confusing - you actually can manage NFS VMDKs with SDW6.3, but you cannot create them from within SDW console.

    What you have to do is: add virtual disks on vSphere side via vCenter, edit VM config, add disk(s) and choose their location within NFS datastore of choice.

    When you go back to SDW, you will be then able to see added disks.

    Regards,
    Radek

    kris_boeckx

    Hi,

    So this means that creating a disk with snapdrive within the virtual machine is not working ? Or is it not supported ?

    This would be very stupid because you always should create your luns with snapdrive to be fully supported.

    Greetings,

    Kris Boeckx

    Pidpa

    radek_kubka

    So this means that creating a disk with snapdrive within the virtual machine is not working ?

    It is not working if you want to use NFS datastore.

    This would be very stupid because you always should create your luns with snapdrive to be fully supported.

    Arguably it is confusing, but bear in mind these are no longer LUNs - you are dealing with VMDK files located within NFS datastore!

    Regards,
    Radek

    kris_boeckx

    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.

    Greetings,

    Kris Boeckx

    Pidpa

    radek_kubka

    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.

    itmsnetapp

    Hi Radek - so I have done what you have suggested.

    I created a new nas volume on the filer and a qtree to go with it.

    I then added the nfs storage to the esx host

    I edited the VM and created a new hard disk on this storage

    I opened the console of the VM and started snapdrive 6.3 - the disk didn't show up

    I opened computer management - windows wants to initialize the disk.

    Are you able to say where it is going wrong?

    I have the latest version of VSC installed

    Windows 2008 R2

    esx host is 4.0.1

    filer is running 7.3.3 (from what I gather I dont need 7.3.4 unless I want to make use of the space reclaim feature)

    cheers

    radek_kubka

    Hi,

    NFS integration is not supported until VSC 2.0.1 is available - http://communities.netapp.com/message/39590#39590

    It looks like this has worked for me before only because I've used beta build of SDW 6.3.

    I tested it now with official build & it plainly does not work - may be purposely blocked when SDW finds out VSC is not 2.0.1.

    Regards,
    Radek

    radek_kubka

    I'm running ONTAP 7.3.4.

    WillFulmer

    Chris,

    Ran into a similar issue as you with regards to both SD 6.2.1 as well as SD 6.3, Data ONTAP 8.0.1 7-mode....

    [02:12:41.796]  The destination volume of the source Logical Disk H FlexClone State is Success and SnapMirror State is Unknown.
    [02:12:48.797]  Mounting Snapshot [exchsnap__ex01j_02-11-2011_02.00.21__daily] for LUN H created from Computer EX01J
    [02:12:48.797]  Mount point directory [C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint]
    [02:12:50.328]  Snapshot will be mounted on subdirectory [MPDisk001]
    [02:12:52.453]  [SnapDrive Error]:An attempt to obtain list of volumes on the storage system 'netapp01aca' failed. Error code: 13040. Error description: No volume named '' was found.
    (SnapDrive Error Code: 0xc0040331)
    [02:12:52.453]  SnapDrive failed to mount the snapshot.
    [02:12:52.469]  [SnapDrive Error]:An attempt to obtain list of volumes on the storage system 'netapp01aca' failed. Error code: 13040. Error description: No volume named '' was found.

    Have a case open w/ NetApp support but trying to get this fixed? Any thoughts?

    HendersonD

    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?

    kris_boeckx

    SnapDrive - 6.3P1

    Date Posted: 17-NOV-2010
    SnapDrive 6.3P1
    Based on SnapDrive 6.3

    Bugs fixed in this release:

    6.3P1
    ===========
    445705 SDW is not allowing snapshot operations of LUNs on FlexClone volumes.
    455839 SnapDrive in Hyper-V VM Tries to Connect to Unroutable IP on Filer
    437376 Should not check for vol_move_status for BR.0 
    447254 Unable to take backup of VMs in a Hyper-V CSV Cluster environment
    440822 The SnapDrive Service in an ESX VM takes too long to start up in large ESX environments 
    447078 SDW 6.2 fails to show FCP initiators when ESX upgraded from 4.0.x to 4.1
    434153 DFM RBAC:SDW to provide configurable cache timeout value.
    458869 dataset backup failing with "Error: Qtree 1880 was not found in the dataset"

    Download link: http://now.netapp.com/NOW/download/software/snapdrive_win/6.3P1/



    Public