About watan

watan · ‎2010-10-04

Hi Mohit, Can you confirm the following is ok? Guidelines for mapping LUNs to igroups There are several important guidelines you must follow when mapping LUNs to an igroup. • You can map two different LUNs with the same LUN ID to two different igroups without having a conflict, provided that the igroups do not share any initiators or only one of the LUNs is online at a given time. • Make sure the LUNs are online before mapping them to an igroup. Do not map LUNs that are in the offline state. • You can map a LUN only once to an igroup or a specific initiator. • You can add a single initiator to multiple igroups. but the initiator can be mapped to a LUN only once. You cannot map a LUN to multiple igroups that contain the same initiator. • You cannot use the same LUN ID for two LUNs mapped to the same igroup. • You cannot map a LUN to both FC and iSCSI igroups if ALUA is enabled on one of the igroups. Run the lun config_check command to determine if any such conflicts exist. http://now.netapp.com/NOW/knowledge/docs/ontap/rel733/pdfs/ontap/bsag.pdf Page 53

watan · ‎2010-10-04

Hi Markus, The burt that I originally mentioned has been fixed in the newer releases and your version should be ok. Can you try the following from STORACL? STORACL> spacereserve get -vol "volname"

watan · ‎2010-10-04

Thanks for chiming in Qing. Customer is using 1 volume for logs and 1 volume for db. 21 luns in DB_vol 1 lun in Log_Vol See any concerns with this?

watan · ‎2010-10-04

Yes. 1 of the notable key features in SDW 6.3 was the integration of SMSQL, VSC - Virtual Storage Console (aka SMVI) , and SDW which allows for creation of VMDKs in NFS & VMFS datastores. SMSQL - for SQL application snapshot management VSC - for VMware integration SDW - for LUN management Unfortunately, VSC 2.0.1is still in beta and not available yet but should expect a release soon. Partial support list - Please check IMT for full details. SMSQL 5.1 SDW 6.3 VSC 2.0.1 ONTAP version - 7.2.7, 7.3.1 or later,8.0 and 8.0.1 ESX version : ESX 3.5U5, ESX 4.0U1 and ESX 4.1 VC version : vSphere 4.0 and vSphere 4.1 VMware Guest OSes : Windows 2003, Windows 2008 and Windows 2008R2

watan · ‎2010-10-04

Hi Moncy, I apologize for the bad experience and will try to help you out here. 1. Its a good thing you opened the support case as this gives us a window straight into escalations if needed. 2. We will need logs to understand where the problems are coming from. It may be a enumeration issue but could stem from something else which the logs will help to explain. Please send more details on the environment. Windows 2003 Cluster Exchange 2007 SDW 6.3 SME 5.0 FC connectivity Host Util kit? DSM? Ontap version? P.S. I also sent you a direct email.

watan · ‎2010-10-01

Thanks for chiming in Qing!

watan · ‎2010-10-01

We have a public report that will be posted soon. http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=447078 The following is the content that will be posted in the public report. ============================== You may notice that after upgrading from ESX 4.0.x to 4.1, SnapDrive for Windows doesn't enumerate the FC initiators within Windows 2003 Virtual Machines; as a consequence of that,you would not able to connect an RDM (Raw Device Mapping) LUN or create a new RDM LUN, %%% WORKAROUND: Workaround #1: Please go to device Manager and disable the IDE channel. Workaround #2: From Virtual Center, Add a new CD-ROM drive on the free IDE free channel for that VM. Workaround #3: Go to registry : HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi And You will see some entries like SCSI Port 0 SCSI Port 1 SCSI Port 2 These must be expandable and contain sub-keys like for example "SCSI bus 0" -> "Initiator ID" and "Target Id" So if Scsi Port 0 does not contain scsi bus, initiator id and target id, just delete this scsi port 0 reg entry. (You may want to export it to your hard disk before deleting). Same goes for SCSI port 1 and SCSI port 2: if they do not contain sub-folders, delete them. Once you have done the step above, you need to restart the SnapDrive service and check if SnapDrive sees the FCP initiators. This workaround is not consistent across VM reboots, as the keys will be regenerated."

watan · ‎2010-09-29

Not sure if this was mentioned or if this will fix it but there is a burt 145575 that looks similar to your problem. http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=145575

watan · ‎2010-09-28

This has recently been spotted internally and the dev team is working on a resolution. Burt#447078 There seems to be a problem with the 4.0 to 4.1 upgrade and fcp initiators. Not much else has been established but dev team is investigating and hope to have a fix out soon.

watan · ‎2010-09-27

Are you getting any errors in the storage array logs? It may be a esx/sdw authentication issue. Can you provide more info?

watan · ‎2010-09-21

Also to add further. Main features and enhancements in this release. 1. Enable VMware VMDK NFS and VMFS support - Ensures SMSQL can protect SQL databases when databases are stored on VMware VMDK backed by NFS or VMFS datastore. -- SME will NOT be supported because of VMDK VSS limitations. 2. VMDK NFS Space Reclamation - Increases the efficiency of snapshot copies on the NFS volume, reducing the amount of space. Note: Support for VMDKs in an NFS or VMFS datastore requires Virtual Storage Console 2.0.1 or later. Please check the availability of Virtual Storage Console 2.0.1 and install it before using this feature. 3. LUN scalability and performance improvements - Improved backup and restores operations. 4. RBAC credential caching - Continued SnapDrive operations during transient Operations Manager outage. 5. SDW and VMware SRM interoperability - Enables automated disaster recovery failover of Microsoft Applications

watan · ‎2010-09-20

The prereq video from the Getting Started Series has a troubleshooting section that may help with this issue. http://communities.netapp.com/docs/DOC-5654

watan · ‎2010-09-20

I'm not absolutely sure but looks like it is scheduled to release within the next 2 weeks.

watan · ‎2010-09-20

Hi Radek, VSC 2.0.1 is the official release with supported features for the SDW 6.3 , SMSQL 5.1, VSC 2.0.1 integration. There may have been a few bits in 2.0 but supported version is 2.0.1. New release includes: All features of VSC 2.0 + VMDK integration with SDW 6.3 and SMSQL 5.1. SnapDrive for Windows 6.3 provides support for backup/restore operation on VMDK disks in VMware Windows GuestOS created on VMware ESX hosts. SnapManager products should be able to host the application data on VMDK disk backed by NetApp storage( NFS and VMFS) and do their backup and restore operation on these disks as they do on normal NetApp LUN. In this release, a wizard has been added in the installation screen to provide VSC 2.0.1 (SMVI) configuration details.SDW uses https protocol 8043 to communicate to the VSC (SMVI) server. The availability of VMDK disks will be dependent on the VSC (SMVI) server. If VSC (SMVI)server is not available due to some reason, the RDMs(FC,ESX iSCSI,HW iSCSI) and MS iSCSI LUNs must be available for all SDW operations. Users can create VMDK files in NFS and / or VMFS datastores and attach these VMDK files as virtual disks to the virtual machines. SDW 6.3 uses the APIs provided by VSC (SMV)I to discover these virtual disks and present them to the host. SMSQL 5.1 will treat the VMDK disks as any other normal luns and let the user perform Configuration / Backup / Restore / Clone. & VMware View 4.5 support (backwards compatible with View 4.0 also)

watan · ‎2010-09-20

DOWNLOAD NOW Features of This Release SnapDrive 6.3 for Windows includes the following major new and enhanced features: Support for performing Snapshot copy operations on virtual machine disks (VMDKs) in an NFS or VMFS datastore, which requires Virtual Storage Console 2.0.1 or later. Please check the availability of Virtual Storage Console 2.0.1 and install it before using this feature. Support for space reclamation when using VMDKs in an NFS datastore Support for DataFabric Manager caching with RBAC Automatic download of the storage system access control (storacl.exe) tool as part of your SnapDrive 6.3 for Windows installation Bug fixes For more information, see the SnapDrive 6.3 for Windows Release Notes. Limitations SnapDrive 6.3 currently has the following limitations: iSCSI RDM LUNs are not supported across two physical Microsoft cluster machines. Customers using SnapDrive 5.0 and earlier on Windows Server 2003 IA64 systems must upgrade to Windows Server 2008 on IA64 systems before they can use SnapDrive 6.3. A LUN managed by SnapDrive cannot be configured as a "dynamic" disk (a storage device that is divided into volumes rather than partitions); it can serve only as a "basic" disk (a storage device for host-side application data). A LUN cannot be configured as an extended partition; SnapDrive supports only a single, primary partition on a LUN. A LUN created with FilerView® or at the storage system command line can be managed only if certain steps (documented in the Installation and Administration Guide) are taken to prepare these LUNs for SnapDrive. Conversion of a LUN with an MBR partition to a GPT partition is not supported. Permanent clones are not supported. Snapshot™ copies that are created from the storage system console are not supported; because this can lead to inconsistencies within the NTFS file system, only SnapDrive should be used to create Snapshot copies of LUNs. Volume-level SnapVault® configurations are not supported (however, qtree SnapVault configurations are supported). Space reclamation on VMDKs in VMFS datastores is not supported. Considerations when using Microsoft iSCSI Software Initiator include the following: In an MSCS configuration that uses volume mountpoints, install Microsoft hotfix 925677 on all cluster nodes if you encounter the issue described in Knowledge Base article KB925677. In a noncluster configuration, configure the Exchange® service and the SQL service with a dependency on the iSCSI Software Initiator service.

watan · ‎2010-08-03

SNAPDRIVE FOR WINDOWS STORAGE SYSTEM SERVICE ACCOUNT CAPABILITIES This report was developed for administrators who require the NetApp® SnapDrive® for Windows® storage system service account to have minimal capabilities to perform its function. Technical Report has been posted and can be found here. http://media.netapp.com/documents/tr-3864.pdf

watan · ‎2010-08-02

*Will need different roles for 2.1 but most should remain the same. We will be adding more roles as new functionality has been released in 2.1*

watan · ‎2010-08-02

We've been getting a lot of questions regarding AppWatch security. Here's a list from 2.0 that will help lock down users with specific roles/tasks within AppWatch. The following list of roles needs to be created on a specific user or group on the storage array. You can add or remove functionality as you like. AppWatch MP, discovery & monitoring aggr-list-info aggr-options-list-info cf-status disk-list-info ems-autosupport-log lun-get-attribute lun-get-serial-number lun-get-space-reservation-info lun-list-info perf-object-get-instances qtree-list quota-report-iter-start/next/end snapmirror-get-status snmp-get storage-shelf-environment-list-info storage-shelf-list-info system-get-info system-get-ontapi-version system-get-version system-get-vendor-info vfiler-list-info volume-list-info AppWatch MP, console tasks These tasks have GUI interfaces that allow alternate credentials to be entered. license-list-info lun-list-info sis-disable sis-enable sis-start sis-stop system-get-version volume-autosize-get volume-autosize-set volume-list-info volume-size AppWatch PRO MP, discovery & monitoring license-list-info lun-list-info system-get-version volume-list-info AppWatch PRO MP, PRO Tip auto-remediation license-list-info lun-list-info lun-online sis-enable sis-start system-get-version volume-list-info volume-online volume-size

watan · ‎2010-07-22

Glad to hear its been resolved.

watan · ‎2010-07-22

Take a look at the following kb https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb26568 Also, the PDC error may be some sort of communication problem with the domain controller. Try a cifs domaininfo and see what ip address/DC the storage array discovered. If it looks good, test DNS from both host and storage to see if everything resolves correctly. cifs resetdc and can also try to run cifs setup again to ensure everything is ok.

watan · ‎2010-07-22

Thanks for the suggestions Rob. FieldPortal is a Sales based NetApp site and unfortunately is not externally available to all users. For general information the best place to go is http://now.netapp.com

watan · ‎2010-07-21

Missed the live session? Not a problem, the sessions are all recorded and will be available for "on-demand" viewing. Just hop on over here and find what you need. https://communities.netapp.com/docs/DOC-5654 ApplianceWatch session is -> Efficient Storage Mgmt with MS System Center and video will be uploaded soon.

watan · ‎2010-07-20

Just another quick reminder. ApplianceWatch PRO - Getting Started Series will start in just a little over 1 hour!

watan · ‎2010-07-16

GSS for ApplianceWatch PRO will be held on Tuesday 7/20 from 10am PST. For more details , https://communities.netapp.com/docs/DOC-5654

watan · ‎2010-06-30

I got a hold of the dev crew and here's what they said. ##### Dev writes: For LUN missing issue, what we have observed is sometimes during a reboot of a VM it is not getting registered properly to Vcenter and SDW isn't able to get information from VI-SDK so we disable the communication with VC during startup so SnapDrive service can startup. In these cases, the work around is to enable VC communication again manually by calling VS_Config set command and restart the SDW service, so it can see the FC LUNs and initiators which are not enumerable due to non-communication with VC. ##### If you send me your SDW logs, I will forward this to the team to analyze the problem. If you haven't already, you may want to open a support ticket so we can track this internally.

Re: SnapDrive for Windows and cluster iGroups

Re: SnapDrive 6.1 "not designated for thin provisioning"

Re: SnapManger Crap Software

Re: SQL databases stored on NFS share with the release of Snapdrive 6.3?

Re: SnapManger Crap Software

Re: SMSQL 5.0r1p2 Error Parsing Time

Re: FC RDM Luns in ESX4.1 virtual machines

Re: SMSQL 5.0r1p2 Error Parsing Time

Re: FC RDM Luns in ESX4.1 virtual machines

Re: VMware RDM and SnapDrive CLI error

Re: SnapDrive 6.3 for Windows - Available on NOW

Re: ApplianceWatch unable to connect to Storage Controllers

Re: SnapDrive 6.3 for Windows - Available on NOW

Re: SnapDrive 6.3 for Windows - Available on NOW

SnapDrive 6.3 for Windows - Available on NOW

SnapDrive for Windows 6.2 in a Least Privilege Environment

Re: ApplianceWatch PRO - OnTap Roles

ApplianceWatch PRO - OnTap Roles

Re: AUTH: Unable to acquire filer credentials: (0x96c73a18) Invalid password.

Re: AUTH: Unable to acquire filer credentials: (0x96c73a18) Invalid password.

Re: how to manage the Netapp FAS

Re: Getting Started Series - ApplianceWatch PRO

Re: Getting Started Series - ApplianceWatch PRO

Getting Started Series - ApplianceWatch PRO

Re: SD6.2 with pass through FCP RDM LUN in vShere4