snapdrive 6.4.1 for windows release notes - ibm...v the snapdrive for windows flr api does not...

IBM System Storage N series

SnapDrive 6.4.1 for Windows ReleaseNotes

GC26-7881-19

��

Contents

SnapDrive 6.4.1 for Windows Release Notes . . . . . . . . . . . . . . . . . . . 1New features in SnapDrive 6.4.1 for Windows . . . . . . . . . . . . . . . . . . . . 1SnapDrive system requirements . . . . . . . . . . . . . . . . . . . . . . . . 1

Fixed issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Documentation changes . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . 27Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

© Copyright IBM Corp. 2012 iii

iv IBM System Storage N series: SnapDrive 6.4.1 for Windows Release Notes

SnapDrive 6.4.1 for Windows Release Notes

These release notes describe new features, installation requirements, fixedissues, and known issues for SnapDrive 6.4.1 for Windows. You can check therelease notes for the latest installation and system configuration information,as well as workarounds for common known problems.

New features in SnapDrive 6.4.1 for Windows

SnapDrive 6.4.1 for Windows is a maintenance and performance-improvementrelease. For information about the issues fixed in this release, see the "Fixedissues" section. For detailed information about SnapDrive for Windows, seethe SnapDrive 6.4 for Windows Installation and Administration Guide.

SnapDrive system requirements

You must ensure that your storage system and your Windows system meet atleast the minimum requirements to properly install and run SnapDrive forWindows.

The storage system and Windows system components that you use withSnapDrive, as well as the minimum versions the SnapDrive requires, are asfollows:

Operating system on the storage systemv Data ONTAP 7.3.1 and later releases in the 7.3 release familyv Data ONTAP 8.0.x 7-Modev Data ONTAP 8.1 7-Mode or later

Note: For the most current list of supported Data ONTAP software versions,see the IBM N series interoperability matrix (accessed and navigated asdescribed in “Websites” on page 25).

Licenses enabled on the storage systemv iSCSI, if you want to use iSCSI-accessed LUNsv FC, if you want to use FC-accessed LUNsv SnapRestore, if you want to restore LUNs from Snapshot copiesv SnapMirror, if you want to use the SnapMirror optionv FlexClone, if you want to enable volume clone functionality

© Copyright IBM Corp. 2012 1

v SnapVault, if you want to use SnapVault for archiving LUN backup sets.This is supported in SnapDrive only for 7-Mode.

v MultiStore, if you want to create iSCSI LUNs on vFiler units

Note: The iSCSI and FC licenses supplied with SnapDrive enable all the CIFSfunctionality necessary for using SnapDrive. If you also want full-featured,direct CIFS access to a particular storage system, you must install a separateCIFS license on that storage system.

DataFabric Manager server

If you are using DataFabric Manager server to provide RBAC with SnapDrive,you must upgrade to OnCommand Core Package 5.0.2. This is supported onlyin 7-Mode. For information about using RBAC with SnapDrive for Windows,see the SnapDrive 6.4 for Windows Installation and Administration Guide.

Hardware on the Windows host

The minimum hardware requirements on the Windows host are as follows:v CPU

– For 32-bit: 2.8 GHz Pentium 4 or any compatible version– For 64-bit: Intel Xeon, AMD Opteron

v Memory– 1-GB RAM

v HBA and NICsTo determine the number and types of HBAs and NICs required by eachsystem in your SnapDrive configuration, see the section on selecting aSnapDrive configuration in the SnapDrive 6.4 for Windows Installation andAdministration Guide.The NIC you use to facilitate data transfer for Microsoft iSCSI SoftwareInitiator can come from any vendor, but it must be approved by Microsoftfor use with Windows Server.

v Host Utilities and Software InitiatorTo ensure high network bandwidth and ease of configuration, obtain thelatest firmware and drivers for the HBAs and NICs you are using. You canaccomplish this by installing the appropriate N series Host Utilities orMicrosoft iSCSI Software Initiator, and by following these best practices:– For the latest supported iSCSI and FC HBAs and drivers, see the

appropriate Interoperability Matrix for your N series product, located onthe IBM N series support website (accessed and navigated as describedin “Websites” on page 25).

– Download Microsoft iSCSI Software Initiator from the Microsoft site.

2 IBM System Storage N series: SnapDrive 6.4.1 for Windows Release Notes

Multipath I/O

DSM software support version for Windows MPIO.

Download and installation instructions as well as a Reference Guide for theuse of Data ONTAP DSM for Windows MPIO are available to registered Nseries customers from the Data ONTAP DSM for Windows MPIO publicationmatrices on the Data ONTAP DSM for Windows MPIO support web pagelocated on the IBM N series support website (accessed and navigated asdescribed in “Websites” on page 25).

Operating system on the Windows host machinev Windows Server 2003 SP2

– Edition: Standard, Enterprise, or Data Center– Platforms: x86, x64

v Windows Server 2008, Windows Server 2008 R2 Server Core and non-Server Core installations, and Windows Server 2008 R2 SP1 Server Core andnon-Server Core installations:– Edition: Standard, Enterprise, or Data Center– Platforms: x86, x64

.NET Framework

.NET Framework 3.5 SP1 is required before installing SnapDrive.

.NET is not supported on Windows Server 2008 Server Core; it is, however,supported on Windows Server 2008 R2 Server Core and later versions.

ESX/ESXi server OS supportv ESX/ESXi 3.5 update 5v ESX/ESXi 4.0 or 4.0 Update 3v ESX/ESXi 4.1 Update 1

Paravirtual SCSI adapter support

VMware paravirtual SCSI (PVSCSI) adapters are supported.

Note:

v PVSCSI adapters require ESX 4.0 or later.v The PVSCSI controller must exist prior to creating a LUN.

SnapDrive 6.4.1 for Windows Release Notes 3

Microsoft Windows hotfixes

Before you can install SnapDrive 6.4.1 for Windows, your host system musthave the appropriate Microsoft hotfixes installed.

Note: The following Microsoft hotfixes must be requested directly fromMicrosoft Product Support Services.

Windows Server 2003 SP2 (x86, x64 or DC edition)

If your system is running Windows Server 2003 with Service Pack 2, you mustinstall the following hotfixes:v 919117v 931300v 932755v 937382

Windows Server 2008

If your system is running Windows Server 2008 (x86, x64 or DC edition), youmust install the following hotfixes:v 950927v 952790v 955656

If your system is running Windows Server 2008 x64, you must install thefollowing hotfix:v 956697 (This hotfix is not required on virtual machines.)

Windows Server 2008 R2

If your system is running Windows Server 2008 R2, either Server Core or non-Server Core, and you are using the Hyper-V feature, you must install thefollowing hotfixes:v 977096v 974930v 2494016v 2520235v 2636573

If your system is running Windows Server 2008 R2 SP1, see the followingKnowledge Base articles to install the required hotfixes:


v Knowledge Base article 2494016 Virtual Machines crash when CSV goes intoredirected mode

v Knowledge Base article 2520235 Stop error when more than 200 hard disks arepresented to a WSFC

v Knowledge Base article 2531907 SCSI Device Vital Product Data (VPD) testruns on online disks causing data corruption

For more information visit the Microsoft Product Support website.

Note: For the most up-to-date information on the system requirements, seethe IBM N series interoperability matrix (accessed and navigated as describedin “Websites” on page 25).

SnapDrive 6.4.1 for Windows Release Notes 5

http://support.microsoft.com/KB/2494016






http://support.microsoft.com/

Fixed issues

SnapDrive 6.4.1 for Windows includes the following fixed issues.v The communication object System.ServiceMode1 is in a faulted state while

performing SnapRestore operations.v The SnapDrive command-line interface hyperv list command does not

report clustered VM resource parameters.v SnapDrive for Windows does not check for missing hotfixes on VMs.v Pass-through disk delete and disconnect operations in Hyper-V VM

environments fail with the following error message: Removing mountpointis not supported for Pass-through disks.

v If the host machine is configured in workgroup mode, FlexClone-relatedactivities do not behave as expected and SnapDrive logs a GetComputerNamefailed: 1351 error in the log. When SnapDrive for Windows is configuredwith a local service account, clone-related activities do not behave asexpected.

v SnapDrive crashes while running command-line interface activities throughautomation.

v Volume-based SnapRestore (VBSR) using -force does not work if a newerSnapshot copy exists.

v During SnapManager for Exchange verifications, you might encountererrors stating that the volume clone that SnapDrive for Windows isattempting to create already exists.

v If more than one SnapDrive backup verification job is started fromSnapManager for Exchange, one of them might fail when SnapManager forExchange, the storage system, network, or DataFabric Manager server areunder heavy load. For example, if you have Microsoft Exchange Server 2010DAG with three nodes, each hosting copies of Exchange databases, andthen start three concurrent verification jobs from three DAG nodes, one ofthem might fail and others might succeed.

v The Snapshot copy operation fails when you attempt to make a Snapshotcopy of a LUN that does not exist.

v Over time, SnapDrive service memory utilization can increase slowly.Eventually, the memory utilization can utilize a very large amount ofmemory. Memory utilization can increase faster with more active SnapDriveactivity. For example, frequent backups with SnapManager products canincrease the memory utilization rate.

v When you use FlexClone recycling and the part style is MBR, SnapDrive forWindows fails to mount Snapshot copies.


v You might experience significant SnapDrive for Windows performanceissues when many files exist on the filer.

v You might see performance degradation while performing diskenumeration or delete operations in a Microsoft Windows failover clusterenvironment.

v SnapDrive for Windows should use the scalable volume-list-info-iter-*Zephyr-style API (ZAPI) instead of volume-list-info.

v The SnapDrive for Windows FLR API does not restore a shared disk from apassive node.

v Windows 2008 R2 SP1 fails to install if SnapDrive is installed.v When you click resize in the SnapDrive GUI, the next screen can take a

long time to display. During this time, the SnapDrive GUI hangs, and youmight receive messages that the SnapDrive for Windows ManagementConsole has hung as well.

v SnapDrive for Windows creates backing and backup Snapshot copies tosupport automatic recovery in a 7-Mode environment. These two Snapshotcopies are currently treated as regular independent Snapshot copies.However, in reality, these two Snapshot copies are dependent on each otherand must be treated as a unit.

v Microsoft Exchange Server 2007 CCR or Microsoft Exchange Server 2010Data Availability Groups do not expose the disks to all of the nodes.SnapDrive for Windows tries to enumerate all of the disks and fails if thereare firewall or port restrictions.


Known Issues

Some unexpected and potentially undesired behaviors are known to affectfunctionality in this release of SnapDrive for Windows. You can take actionsto work around some of these behaviors.

SnapDrive for Windows installation fails after .NET 4.0 isinstalled

Message SnapDrive installation detected that the .Net 3.5 Framework SP1is not installed in the system. Please install .Net 3.5 FrameworkSP1 and launch the installation again.

Description This message is displayed when you attempt to install SnapDrive forWindows after installing .NET 4.0 Framework on your Windows server.

Cause SnapDrive requires .NET 3.5 SP1 during installation. If .NET 3.5 SP1 isnot installed, the SnapDrive installation fails.

Correctiveaction

Install both .NET 3.5 SP1 and SnapDrive for Windows beforeupgrading to .NET 4.0.

Error adding raw device mapping -GetLunInformationreturned false

Message Error adding raw device mapping -GetLunInformation returnedfalse.

Description This message is displayed when running the sdcli disk createcommand in a virtual machine.

Cause The VMware ESX device paths are no longer valid.

Corrective action Remove the invalid paths on the ESX server, and run the diskcreate command again.

SnapDrive does not recognize virtual machines

Issue SnapDrive does not recognize virtual machines created on aplatform other than an ESX server (for instance, a VMwareworkstation) and then migrated to an ESX server configurationuntil VMware tools are upgraded.

Cause This issue occurs when registry keys required by SnapDrive aremissing.


Corrective action 1. Uninstall VMware Tools on the ESX server.

2. Reboot the system.

3. Reinstall VMware Tools.

4. Reboot the system.

RBAC access check fails when correct account informationis not provided

Issue This issue occurs when using the SnapManager Configurationwizard to create or reuse a dataset within Operations Managerfor SnapVault with SnapDrive 6.4 for Windows installed.

Cause This issue occurs when you are running DataFabric Managerserver 3.7 or later on a Linux-based Operations Manager serverto provide role-based access control with SnapDrive 6.4 forWindows or later.

Corrective action Make sure the following conditions exist for your Linux-basedconfiguration and try again:

v The sdcli user account must be a valid Operations Managerserver user account with the appropriate roles assigned.

v The SnapManager service account must be added to theOperations Manager server with the appropriate rolesassigned.

New OnCommand user entry example

The following example shows a new user and the roles for that user beingadded to a Linux-based DataFabric Manager server:

# dfm user add windomain\\snapuserWarning: windomain\snapuser does not exist in theadministrator database(s), so login is disabledfor this administrator.Added administrator windomain\snapuser.

# dfm user listId Administrator Email Pager----- ---------------------- ------------------------------------------------5980 windomain\snapuser windomain\snapuser29 Everyone30 root

Assign a role or roles to the user:# dfm user role addwindowsdomain\\snapuser GlobalFullControlAdded 1 role to administratorwindowsdomain\snapuser.

# dfm user role list windowsdomain\\snapuserRole Id Role Name------- -------------------------28 GlobalFullControl


LUN includes SCSI reservation but is not mapped

Description Connecting a LUN on a Microsoft cluster fails.

Cause A bug in Microsoft failover clusters and in Data ONTAPsoftware.

Corrective action You can resolve this problem in one of the following three ways:

v Clear the SCSI reservation on your storage system by enteringthe following command:

lun persistent_resv clear

v Clear the persistent reservation (PR) bit on the Windowsserver by entering the following command:

cluster nodename /clearpr:disk#

v Complete the following steps on one of the Microsoft clusternodes:

1. Note the dependencies in the associated cluster resourcegroup, and then delete the group.

2. Remove the disk from the Available Storage list.

3. On the same server or a new one, add the disk back to theAvailable Storage list and re-create the cluster resourcegroup with the dependencies you noted in Step 1.

Snapshot copy LUN import operations fail when mounting toa Windows Server 2008 R2 host

Issue Operations that try to import (mount) a Snapshot copy LUNonto the host fail, including file-level restoration for files in theboot LUN, generic Snapshot copy mount for copying files or fileverification by third-party tools, and VSS Snapshot copy ofscenarios that require Snapshot copy mount.

Cause This is caused by a limitation with the Snapshot copy of theLUN when using the system reserved partition introduced byMicrosoft in Windows Server 2008 R2. The system reservedpartition is created by the Windows installer during a freshinstallation unless you choose not to include the boot LUNsystem recovery option. The problem only occurs if the systemreserved partition is on the boot volume when the Snapshotcopy is created.

Known Issues 11

Corrective action You can avoid this problem in one of three ways, depending onyour environment:

v During Windows installation, choose the option not to createthe recovery partition.

v Delete the recovery partition later, if possible.

v If you are using Windows Server 2008 before upgrading toWindows Server 2008 R2, choose the option to upgrade ratherthan performing a fresh installation.

Requested LUN size is too large

Description This message occurs when, using Data ONTAP 7.3.1, you usethe lun create -o nonreserve -s 16t command in an attemptto increase LUN size.

In earlier versions of Data ONTAP, this command succeeded andautomatically created the largest possible non-space-reservedLUN (17,555,552,340,480 bytes or 16439 GB).

This problem also exists for the lun-create-by-size ZAPI that isused by SnapDrive for Windows. When you use SnapDrive forLUN management, creating a LUN by entering the LUN size as16 TB fails.

Corrective action Create a non-space-reserved LUN sized 16349 GB.

Input string was not in a correct format

Cause The message occurs in SnapDrive 6.x during LUN enumeration,when you change the Regional and Language options from thedefault of English (US), which might cause the thousandsseparator to change to a character other than a period (.).

Corrective action In the Regional and Language options, change the value in theDecimal symbol field to a period (.) instead of a comma (,) orany other symbol.

Drive letter missing for MBR disk during a SnapRestoreoperation

Cause This issue occurs when the size of the LUN and the Snapshotcopy LUN do not match.


Corrective action 1. Go to diskmgmt.msc and locate the disk independent of thedrive letter or mount point.

2. Right-click the disk and assign it the appropriate drive letter.

3. Ignore the Format disk dialog box.

4. Refresh SnapDrive MMC and the disk and its assigned driveletter is displayed.

Pass-through disk might not be enumerated after it isrestored to a smaller size

Issue After you restore a pass-through disk to a smaller size, it is notlisted when you try to view all the LUNs connected to the host.The Microsoft Windows format dialog box is displayed.

Corrective action 1. Click Cancel in the format dialog box.

2. Open Disk Management in MMC.

3. Rescan all the disks.

4. Refresh the Disks list in MMC snap-in. Alternatively, enterthe sdcli disk list command.

Result The disk is displayed in the list.

SnapDrive host lists LUNs of the original virtual machineafter a reboot

Issue When you stop the SnapDrive service and reboot the host aftercloning LUNs to a destination virtual machine, SnapDrive listsLUNs that are not related to the host.

Corrective action Reinstall SnapDrive for Windows.

Pass-through disk provisioning in high-availability virtualmachine fails

Issue Pass-through disk provisioning (create and connect operations)fails on a high-availability virtual machine (HA VM).

Cause This issue occurs when a dedicated pass-through disk alreadyexists in the HA VM - for example, while mounting a Snapshotcopy as a pass-through disk from the HA VM using SnapDrivefor Windows.

Corrective action Detach the dedicated pass-through disk before performingprovisioning operations on HA VMs.

Known Issues 13

Independent disks are excluded during backup when VMwaresnapshots are used

Issue When a VMware snapshot of a VMDK disk already exists, youcannot use a SnapDrive Snapshot copy created on anindependent disk (persistent or nonpersistent) to mount orrestore a VMDK disk.

Corrective action To use a SnapDrive Snapshot copy created on an independentdisk to mount or restore a VMDK, perform the following steps:

1. Remove the VMware snapshot.

2. Create a Snapshot copy of VMDK disks.

Silent install feature does not setDFM_SERVER_COMM_PORT_SELECTION switch to HTTPS

Issue The silent install feature does not set theDFM_SERVER_COMM_PORT_SELECTION command-line installationswitch to HTTPS. You can reset the switch through manualinstallation. However, manual installation to reset the switchevery time can be a potential issue for mass deploymentrequirements in large physical environments.

Corrective action Install SnapDrive for Windows without OnCommand. You caninstall OnCommand later using sdcli.exe.

SnapDrive cannot mount a LUN

Issue SnapDrive might fail to mount a LUN or a clone and displaysthe following error message:

VDS volume object for the LUN s/n ’xxxxx’ has notbeen found.

Corrective action v Restart VDS service.

v If it is a shared disk on Windows 2003, install Data ONTAPDSM 3.5.

Unable to reset DFM_SERVER_COMM_PORT_SELECTIONcommand-line installation switch

Issue During an unattended installation of SnapDrive, theDFM_SERVER_COMM_PORT_SELECTION switch is not updated whenyou reset it to HTTPS protocol. The switch displays HTTP bydefault.

Corrective action None.


LUN creation fails on an ESX cluster setup with iSCSIinitiator

Issue Shared LUN creation fails on a cluster setup with iSCSI initiator,displaying the following error message:

Mixed initiators across nodes are notsupported for shared disks.

Corrective action Create the shared LUN using automatic igroup selectionoption.

Error in RDM LUN creation in SnapDrive

Issue When two nodes in the cluster are VMs in different sites andregister with different vCenters, SnapDrive fails to create RDMLUN with the following error message:

Error in fetching number of VMFS datastores.

Corrective action Disable the cluster service on both the cluster nodes.

SnapMirror relationship is broken after SnapRestore isperformed

Issue SnapMirror relationship is broken after SnapRestore isperformed in Data ONTAP 8.1 7-Mode. This causesSnapManager for Exchange Business Continuance to fail duringreverse resync SnapMirror operation.

Corrective action Update the SnapMirror configuration file.

SnapDrive service takes time to start

Issue SnapDrive service takes time to start because SnapDrive istrying to locate the VM in the primary vCenter.

Corrective action Do not enable ESX or vCenter credentials if you are not usingRDM and VMDK in the same VM.

SnapDrive operations fail when the storage system is intakeover mode

Issue When the storage system is in takeover mode, SnapDriveoperations fail because there is no connection between the hostand the storage system.


Known Issues 15

SnapDrive fails while testing Broadcom 57712 convergednetwork adapter

Issue The command sdcli snap unmount fails as there is an existingmount point in the storage system.

Corrective action 1. Add the storage system in Preferred Storage System IPAddresses list.

2. Configure the storage system and host with same IP protocol(IPv4 or IPv6).

Scheduled backup and concurrent verification jobs fail tomount Snapshot copy

Message The parameter is incorrect.

Issue Running scheduled backup and concurrent verification jobs failto mount a Snapshot copy.


SnapDrive displays 0 MB LUN size

Issue The command sdcli disk resize cannot be executed.

Corrective action Set the preferred IP in the storage system.

Mounting a Snapshot copy as a pass-through disk can fail

Message The system cannot find the file specified.

Description This message occurs when you are trying to mount a LUN in aSnapshot copy with a soft link to a volume mount point.

Corrective action 1. From the SnapDrive command-line interface, type disk list, orrefresh your GUI.

2. When the mounted Snapshot copy displays without a letterdrive, right-click the SnapDrive Disk.

3. To add a soft link for the volume mount point, assign a driveletter to the SnapDrive disk.

SnapDrive fails to locate active LUNs on a system

Issue SnapDrive fails to locate active LUNs on a system. However,Disk Management in MMC snap-in displays all the LUNs.

Corrective action Add the virtual server entry to the transport protocol setting byusing MMC snap-in or sdcli.exe.


System fails to create CSV disk on non-English OS

Message Disk Create operation on server -HOST01 failed for reason Error 0x1395 occurred.Description is not found.

Description This issue occurs when you are creating a cluster-shared volume(CSV). first checks the current user locale, and next finds thedefault cluster group name using Windows ManagementInstrumentation (WMI). Therefore, when creating or connecting aCSV disk on a non-English-language operating system, you mustmodify the Region and Language Settings of your OS to matchyour settings in.

Corrective action 1. Go to your operating system's Region and Language settings.

2. From the Formats option, select the appropriate language.

VMDK Snap Restore fails when the VM is hosted on Qtree

Message Error caused by file[BR3_27_SDW_641_FFT_Vfiler_107_On_Qtree_DD(Backup snap1)]W2k3EER2_x86_ESXiSCSI_BR3vfiler_/W2k3EER2_x86_ESXiSCSI_BR3vfiler_-flat.vmdk)

Description This message occurs when you perform a VMDK Snap Restoreon a VM hosted on Qtree.


Unable to perform space reclamation on VMDK files backedby NFS

Message Error: Space reclamation is supportedon VMDK files backed by only NFS volumes.

Description This message occurs when you perform space reclamation onVMDK files backed by NFS.


Known Issues 17

VMDK mount fails for VMs hosted on a qtree backed by NFS

Message Server Error: Mounting the backup snap8 failedwith following reason: Error mounting10.225.137.50:/vol/VSA_VM_DS_VOL_ON_QTREE_NFS_KIRAN_HELSINKI_1_DONT_DELETE_mount_vmdk_99fcac7183a04e61a33274e8dec91511/QTREE_on_NFS as datastore0affe6bb-611a-4144-afa9-8c07dbd0a550 to10.226.234.112: An error occurred duringhost configuration.

Description This message occurs when you perform an VMDK Snap Mountoperation on a virtual machine (VM) hosted on a qtree backed byNFS, which causes your operation to fail.


Error: The LUN may not be connected, because its mountpoint cannot be found

Message Error: The LUN may not be connected, because its mountpoint cannot be found.

Description This message occurs when you use the SnapDrive command-lineinterface to create a Snapshot copy of a disk that is inmaintenance mode or a failed state, as shown in the followingexample:

C:\Users\administrator.MVA>sdcli snap create -snew_snapshot_name_04 -D C:\ClusterStorage\Volume2\Initializing...MVA-S43 : Checking policiesMVA-S43 : Checking access controlMVA-S43 : Ready to create snapshot copyUnable to create a Snapshot of a LUN.Error: The LUN may not be connected, because its mount pointcannot be found.


The requested operation is not permitted since thisfunctionality is not licensed

Message Error code : The requested operation is not permitted sincethis functionality is not licensed.


Description This message occurs when you install SnapDrive in a mixedserver-based and filer-based SnapDrive license environmentwithin a Windows cluster environment, SnapDrive is unable tofind the license on one of the clustered nodes.

It is recommended that all the Windows clustered nodes haveeither a Windows server-based licenses or filer-based licenses.Any mix might cause errors.

Cause Prior to creating a LUN, SnapDrive checks the licenses on all theWindows cluster nodes. If any of the nodes do not have aSnapDrive server-based license, a SnapDrive, SnapManager forExchange or SnapManager for SQL Server filer-based licensemust already on the storage system on which you are creatingthe LUN. Consequently, SnapDrive bypasses the existence of theSnapDrive filer-based license, if a SnapManager for Exchange orSnapManager for SQL Server filer-based license exists.

When this happens, you receive an error message similar to thisone:

Error message:Log Name: ApplicationSource: SnapDriveDate: 10.10.2011 14:59:36Event ID: 1118Task Category: LUN eventLevel: ErrorKeywords: ClassicUser: N/AComputer: hnombx01.corp.atmel.comDescription:Failed to retrieve information required for creating theLUN.Details:Log Name: ApplicationSource: SnapDriveDate: 10.10.2011 14:59:36Event ID: 1118Task Category: LUN eventLevel: ErrorKeywords: ClassicUser: N/AComputer: hnombx01.corp.atmel.comDescription:Failed to retrieve information required for creating theLUN.LUN Name = test01.lunStorage Path = /vol/mbx02_luntest/Protocol Type = LUNStorage System Name = hnonetapp02Error code : The requested operation is not permitted sincethisfunctionality is not licensed.

Known Issues 19

Corrective action Use one of these supported license configurations:

v Option 1

– Windows cluster clusterA with cluster NodeA1, NodeA2,NodeA3.

– All Windows cluster nodes have a server-based SnapDrivelicense.

In this case, all three nodes, (NodeA1, NodeA2, and NodeA3)can create LUNs on any storage system, regardless of whetherthe storage system has a server-based license.

v Option 2

– Windows cluster clusterB with cluster NodeB1, NodeB2,NodeB3.

– No Windows cluster nodes have Server-based SnapDriveLicense.

In this case, the three nodes (NodeB1, NodeB2, and NodeB3)can create LUNs only on storage systems with a storage-basedSnapDrive license.

v Option 3

– Windows cluster clusterC with cluster NodeC1, NodeC2,NodeC3.

– Windows cluster node NodeC1 and NodeC2 haveserver-based SnapDrive licenses.

– Windows cluster node NodeC3 does not have a server-basedSnapDrive license.

In this case, you can create LUNs from SnapDrive, only onstorage systems with one of the following filer-based licenses:SnapDrive, snapmanagerexchange, or SMSQL.

VM enumeration failure after a change to the configuration orSnapshot file location

Message WARN: map for CSV_location NOT FOUND!

Description This message occurs when you change the default location of thevirtual machine (VM) configuration or Snapshot file to point tothe root directory of your mount point, causing SnapManager forHyper-V backups to fail because SnapDrive for Windows cannotfind the corresponding storage footprint.

Corrective action Move your VHDs to a subdirectory under the root of your CSV.


Pass-through disk delete/disconnect fails after changingdriver letter

Description This message occurs when you change the assigned drive letteror mount point for existing pass-through disks.

Corrective action You can manually delete or disconnect your pass-through disks.

v You can manually delete or disconnect your pass-throughdisks using the Hyper-V Manager, as follows:

1. Navigate to VM Settings.

2. Under SCSI Controller, use the bus, LUN, and targetnumbers to choose the physical disk.

3. Click Remove, and then click OK.

v You can manually delete or disconnect your pass-throughdisks by using SnapDrive for Windows Management Consoleon the parent host, as follows:

1. Navigate to Disk Management and bring your disk online.

2. Refresh SnapDrive for Windows Management Console sothat the LUN is displayed with the volume name.

3. Select and run Disconnect or Delete LUN.

v You can manually delete or disconnect your pass-through diskfrom a clustered parent host using the Failover ClusterManager as follows:

1. Navigate to VM Group.

2. Right-click your virtual machine and select Settings.

3. Under SCSI Controller, use the bus, LUN, and targetnumbers to choose the physical disk.

4. Click Remove and then click OK.Note: This also removes the LUN from the VM Group. TheLUN is placed back to the Available Storage Group.

5. Using owner node's SnapDrive for Windows ManagementConsole, navigate to the Available Storage Group and runDisconnect or Delete LUN.

Known Issues 21

Documentation changes

Some additional information to the SnapDrive 6.4 for Windows Installation andAdministration Guide is as follows:v Add the following section under Using SnapMirror with SnapDrive for

Windows > SnapMirror overview:Data consistency is ensured in SnapDrive with up-to-date SnapMirrorsynchronous operation. If the synchronous operation is not updated,SnapDrive reverts to previous Snapshot copies. However, if the SnapMirrorsynchronous operation is up-to-date, the destination system containsSnapshot copies and SnapDrive connects to the current active file system,ensuring that the data is consistent.

v Add the following note under Managing SnapDrive > Adding andremoving initiators with SnapDrive:Add/Remove initiator is not a valid operation in an ESX environment.

New command-line switches for an unattended installation

SnapDrive 6.4.1 for Windows includes two new additional unattendedinstallation switches. You can use these switches to perform an upgrade whenSnapManager products are installed, and to install SnapDrive withoutchecking for the required hotfixes.

Switch name Values

CONFIRM_SDW_UPGRADE You can use this switch when SnapDriveis installed with SnapManager products.

Yes Specifies that the SnapDriveupgrade proceeds whenSnapManager products areinstalled.

SKIP_HOTFIX_CHECK You can use this switch to proceed withthe SnapDrive installation or upgradewhen the target system does not yet haveall of the required hotfixes installed.

1 Specifies that the SnapDriveupgrade or installation shouldproceed without the requiredhotfixes.


Websites

IBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates. Thefollowing web pages provide N series information:v A listing of currently available N series products and features can be found

at the following web page:www.ibm.com/storage/nas

v The IBM System Storage N series support website requires users to registerin order to obtain access to N series support content on the web. Tounderstand how the N series support web content is organized andnavigated, and to access the N series support website, refer to the followingpublicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well asother important N series product resources.

v IBM System Storage N series products attach to a variety of servers andoperating systems. To determine the latest supported attachments, go to theIBM N series interoperability matrix at the following web page:www.ibm.com/systems/storage/network/interophome.html

v For the latest N series hardware product documentation, includingplanning, installation and setup, and hardware monitoring, service anddiagnostics, see the IBM N series Information Center at the following webpage:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp


http://www.ibm.com/storage/nas

http://www.ibm.com/storage/support/nseries/

http://www.ibm.com/systems/storage/network/interophome.html

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Copyright and trademark information

This section includes copyright and trademark information, and importantnotices.

Copyright information

Copyright ©1994 - 2012 Network Appliance, Inc. All rights reserved. Printedin the U.S.A.

Portions copyright © 2012 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services donot imply that IBM intends to make these available in all countries in whichIBM operates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM’s product, program, or service maybe used. Any functionally equivalent product, program, or service that doesnot infringe any of IBM’s or NetApp’s intellectual property rights may beused instead of the IBM or NetApp product, program, or service. Evaluationand verification of operation in conjunction with other products, except thoseexpressly designated by IBM and NetApp, are the user’s responsibility.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to thefollowing license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,


INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty rights of NetApp.

The product described in this manual may be protected by one or more U.S.A.patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofthe Rights in Technical Data and Computer Software clause at DFARS252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the Web at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,


FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster,MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro,OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, ServiceBuilder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Copyright and trademark information 29

Notices

This information was developed for products and services offered in theU.S.A.

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.


Notices 33

��

NA 210-05556_A0, Printed in USA

GC26-7881-19

snapdrive 6.4.1 for windows release notes - ibm...v the snapdrive for windows flr api does not...

Documents