SnapDrive 7.1.

3 for Windows

Release Notes

June 2016 | 215-10774_A0_ur003

[email protected]

Table of Contents | 3

Contents
New in this release ........................................................................................ 4
New features in SnapDrive 7.1.3 for Windows ........................................................... 4
Upgrade notes .............................................................................................................. 4
Verifying support for your configuration in the IMT .................................................. 4
SnapDrive for Windows supported components and system
requirements .............................................................................................. 5
Changed commands .................................................................................................... 7
Fixed issues ................................................................................................................. 8

Important cautions ....................................................................................... 9

Known limitations ...................................................................................... 11
Known issues ............................................................................................... 13
Documentation errors and omissions ....................................................... 15
How to get help and find more information ............................................. 16
Copyright information ............................................................................... 17
Trademark information ............................................................................. 18
How to send comments about documentation and receive update
notifications ............................................................................................ 19

New in this release

SnapDrive 7.1.3 for Windows introduces bug fixes to critical issues found in the previous release.

New features in SnapDrive 7.1.3 for Windows

SnapDrive 7.1.3 for Windows is a maintenance release that includes important enhancements.

Support for copy-free transitioning and rehosting of transitioned volumes for clustered Data
ONTAP 8.3.2

Critical bug fixes

Upgrade notes
Upgrade notes describe important changes in support between the previous release of SnapDrive for
Windows and this one, including any deprecated features. You should review this information
carefully before upgrading SnapDrive for Windows. You should also check the NetApp
Interoperability Matrix (IMT) for the most up-to-date information about supported configurations.
Supported upgrade paths
You can upgrade to SnapDrive 7.1.3 for Windows from the following previous versions:

SnapDrive 7.1.2 for Windows

SnapDrive 7.1.1 for Windows

SnapDrive 7.1 for Windows

SnapDrive 7.0.x for Windows

SnapDrive 6.5 for Windows

SnapDrive 6.4.2 for Windows

Verifying support for your configuration in the IMT

You can use the NetApp Interoperability Matrix Tool (IMT) to verify SnapDrive for Windows
support for your configuration: ONTAP software, host operating system, and so on. You should
verify your configuration before you install or upgrade to SnapDrive 7.1.3 for Windows.
Steps

1. Log in to the IMT.

NetApp Interoperability Matrix Tool

2. If SnapDrive for Windows is not the selected storage solution, click Change, and select
SnapDrive for Windows under the Software > Management Software > Server Suite category

New in this release | 5

3. In the Component Explorer pane, select each component that you want to verify.
Tip: Select the parent of a set of components to select all its children.

You are prompted to add the components to the worksheet.

4. Click Add.
5. Click Show Results.
The IMT lists all the supported configurations.
6. Perform one of the following actions:

Scroll across a configuration to view the supported components and any notes or alerts for the
configuration.

Click the configuration name to display complete information for the supported components,
including support history and NetApp policies and guidelines for the selected storage solution
category.

If no results are returned for your configuration, you should provide feedback using the Feedback
control in the upper right corner of the IMT.

SnapDrive for Windows supported components and system requirements

You must ensure that your storage system and Windows system meet the minimum requirements to
properly install and run SnapDrive for Windows.
Note: These SnapDrive for Windows system requirements are accurate as of the date of
publication. However, requirements and supported versions might change after the release. For the
latest system requirements information, see the Interoperability Matrix.

NetApp Interoperability Matrix Tool

Component

Supported versions

Supported ONTAP storage

system versions

ONTAP 9.0

Data ONTAP 8.3.2

Data ONTAP 8.3.1

Data ONTAP 8.2.4 operating in 7-Mode and cluster environments

Data ONTAP 8.2.3 operating in 7-Mode and cluster environments

Data ONTAP 8.1.4 operating in 7-Mode and cluster environments

Data ONTAP Edge

Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

Operating systems on the

Windows host machine

6 | Release Notes

Component

Supported versions

.NET Framework
requirements

.NET Framework 4.0

.NET Framework 3.5 SP1

Note: You must install both .NET Framework 3.5 SP1 and .NET
Framework 4.0.

DSM

Windows hotfixes required

for your operating system

Native Microsoft DSM

Data ONTAP DSM 4.1 P1

Data ONTAP DSM 4.0 (supports Windows Server versions

earlier than 2012 R2)

Windows Server 2012 R2:

2903939
Windows Server 2012:

2859162

2894032

Windows Server 2008 R2:

Windows PowerShell

Windows Host Utilities

Kit

ESXi

2522766

2528357

2494016

2520235

2531907

974930

Windows PowerShell 4.0

Windows PowerShell 3.0

Windows Host Utilities Kit 7.0

Windows Host Utilities Kit 6.0.2

Windows Host Utilities Kit 6.0.1

ESXi 6.0

ESXi 5.0

ESXi 5.5

ESXi 5.1

New in this release | 7

Component

Supported versions

Virtual Storage Console

Virtual Storage Console 6.0

Virtual Storage Console 5.0

Virtual Storage Console 4.2.2

Virtual Storage Console 4.2.1

Changed commands
You should review the changes to SnapDrive for Windows commands before upgrading to SnapDrive
7.1.3 for Windows or later. You must ensure that the changes do not disable any scripts that you use
to execute SDCLI commands or PowerShell cmdlets.
SDCLI and PowerShell cmdlet changes introduced in SnapDrive 7.1.3 for Windows
New and changed commands

Change

sdcli clone_split
clone_estimate

Introduces SDCLI support for split clone operations.

sdcli clone_split
clone_start

sdcli clone_split
clone_status

sdcli clone_split
clone_stop

GetSdVolumeCloneSplitEstimate

Start-SdVolumeCloneSplit

Get-SdVolumeCloneSplit

Stop-SdVolumeCloneSplit

Introduces PowerShell cmdlet support for split clone

operations.

-ValidateCloneDepth in MountSdSnapshot

Stops your mount request if you are attempting to

mount a child clone that exceeds the clone depth. The
default clone depth is two.

-DeleteParentClones in
Dismount-SdSnapshot

Indicates that you want to unmount and delete any

offline parent volume clones. You are prompted for
confirmation before a parent volume clone is deleted.

sdcli snap mount -cn

Specifies the name of the volume clone that you want to

mount.

sdcli disk connect -cn

Specifies the name of the volume clone that you want to

connect.

sdcli disk create -thin

Specifies that you want to create a thinly provisioned

LUN.

8 | Release Notes

Fixed issues
It is a good practice to review the fixed issues before upgrading to the new release of SnapDrive for
Windows.
Fixed issues in SnapDrive 7.1.3 for Windows
The following issues have been fixed in this release of SnapDrive for Windows. Issues that have
public reports in Bugs Online are hyperlinked. You can click the hyperlink to view additional details.
Issue

Description

921355

SnapDrive for Windows cannot access the SnapMirror

destination details while cloning the Snapshot copy of the
source.

961647

SnapDrive for Windows returns an incorrect virtual machine

(VM) reference when there are multiple VMs with fully
qualified domain names (FQDN) in the vCenter.

Important cautions
Important cautions identify issues that might cause data loss or system failure. You should review
these cautions carefully.
SnapDrive is not supported with SVM disaster recovery
Storage Virtual Machine (SVM) disaster recovery (SVM DR) is supported in clustered Data ONTAP
8.3.1. If you use SnapDrive for Windows to manage volumes, LUNs, or SMB shares in an SVM and
the SVM is configured for disaster recovery, then SnapDrive is not supported in this configuration.
Restoring Snapshot copies after 7-Mode to clustered Data ONTAP 8.3.0 transition
You cannot use SnapManager products to restore or perform verification operations on Snapshot
copies that reside on volumes that have been transitioned from 7-Mode to clustered Data ONTAP
8.3.0 using the 7-Mode Transition Tool. After you have transitioned from 7-Mode to clustered Data
ONTAP 8.3.0, you should immediately back up your transitioned data, and then you can perform
backup, restore, and cloning operations on the new Snapshot copies that you created in clustered
Data ONTAP 8.3.0.
To learn more about the 7-Mode Transition Tool capabilities and limitations, see the 7-Mode
Transition Tool documentation set.
Accessing dedicated and shared LUNs after transition
If you want to access your dedicated and shared LUNs after transition, you must perform the
following steps :
1. After you have transitioned to clustered Data ONTAP using the 7-Mode Transition Tool, add the
clustered Data ONTAP SVM management LIF to the SnapDrive for Windows transport protocol
settings.
2. Refresh Disks in the SnapDrive for Windows GUI or use sdcli to see the SnapDrive for Windows
disks that were created prior to the transition.
3. When the disks are available in SnapDrive for Windows, perform all regular SnapDrive for
Windows operations in clustered Data ONTAP.
4. After your disks are available, perform an immediate backup on all the LUNs that you have
transitioned to clustered Data ONTAP.
For complete details about accessing disks in disk management, see the 7-Mode Transition
Supplement for SAN Hosts.
Rehosting transitioned volumes to a different SVM
To access your LUNs using SnapDrive for Windows, perform the following steps after rehosting:
1. Enter the new SVM in the transport protocol setting (TPS).
2. Establish an FC or iSCSI connection from the host to the new SVM.
3. When the LUN is available in the disk management , bring it online.
4. Refresh the SnapDrive for Windows disk management screen to view the LUNs.
Note: Rehosting of volumes should be done along with LUN mapping.

10 | Release Notes

Related information

7-Mode Transition Tool 2.1 Data and Configuration Transition Guide

7-Mode Transition Tool 2.1 SAN Host Transition and Remediation Supplemental Guide
7-Mode Transition Tool 2.1 Release Notes

11

Known limitations
Known limitations identify platforms, devices, or functions that are not supported by SnapDrive 7.1.3
for Windows, or that do not interoperate correctly with SnapDrive for Windows. You should review
these limitations carefully before installing or upgrading to SnapDrive 7.1.3 for Windows.
Support for non-English qtree names
Although ONTAP 9.0 supports non-English qtree names, SnapDrive for Windows does not support
non-English names for qtrees.
Support for SnapManager verifications with load sharing mirrors
SnapManager verification operations with load sharing mirrors do not work in clustered Data
ONTAP environments.
Support for concurrent SnapDrive operations
SnapDrive for Windows does not support concurrent SnapDrive operations.
Support for selective LUN mapping
SnapDrive for Windows does not support selective LUN mapping. You must ensure that you have a
data LIF on each cluster node.
Support for VHDX
VHDX sharing is not supported in NAS volumes from Data ONTAP.
7-Mode to clustered Data ONTAP transition limitations
You cannot transition a VMDK because Virtual Storage Console does not support the 7-Mode
Transition Tool. Transitioning from 7-Mode to clustered Data ONTAP using the 7-Mode Transition
Tool has the following limitations in SnapDrive 7.1.2 for Windows and later versions:

Mount and file-level restore operations fail on Snapshot copies that are transitioned from 7-Mode
environments.
After you transition to Data ONTAP 8.3.0, if you immediately back up your transitioned data, you
can perform these operations from the new Snapshot copies that you created in Data ONTAP
8.3.0.

Cloning a clone is not supported on Snapshot copies that are transitioned from a 7-Mode
environment to Data ONTAP 8.3.0.

Interoperability issues with Windows Server versions 2012 and 2012 R2

In Windows Server 2012 and later, you should install Windows Host Utilities (WHU) or Data
ONTAP DSM, which enables the UNMAP feature. For more information, see the KB article.

3013991

Data ONTAP 8.3 does not support native thin provisioning in Windows Server versions 2012 and
2012 R2.

You should not perform any SnapDrive for Windows disk-related operations on the LUN that
hosts the virtual machines during live virtual machine migration and storage migration.

12 | Release Notes

Although Windows Server versions 2012 and 2012 R2 enable you to create a disk larger than 16
TB in size, you cannot create an ONTAP LUN that is larger than 16 TB in size.

When you add new nodes to your cluster on Windows Server versions 2012 and 2012 R2, you
must remap the LUNs to the new nodes.

13

Known issues
Known issues identify problems that might cause you inconvenience but do not prevent you from
using SnapDrive 7.1.3 for Windows successfully.
NetApp Bugs Online provides complete information about most bugs, including any workarounds. If
a Bugs Online report is available, the bug ID column in the table contains a hyperlink that you can
click to view the report.
Known issues identified in this release
No known issues have been identified in this release.
Known issues identified in previous releases
The following issues are reported in previous editions of the release notes:
Bug ID

Description

870108

Storage Virtual Machine (SVM) name resolution in SnapDrive for

Windows transport protocol settings truncates any characters in an
SVM name following the . character, if the SVM name contains
a . character in it.

864540

Splitting multiple clones of multiple Cluster Shared Volumes

(CSV) disks using one command does not split all the clones.

864547

SnapDrive for Windows fails silently if the IP returned by Virtual

Storage Console is not the same as the IP registered in the
transport protocol for SnapDrive. SnapDrive for Windows is
restricted to accessing the cluster mode storage system only
through the IP returned by Virtual Storage Console.

885161

In a VMware cluster environment, SnapDrive for Windows does

not display or use initiators from each ESXi host when creating or
choosing an igroup for mapping the shared raw device mapping
(RDM) LUN.

934785

SnapDrive for Windows does not allow 7-Mode controllers to be

configured in the Transport Protocol Settings using HTTPS.

817755
401641

Downgrading SnapDrive 7.1 to earlier versions might not work as

expected. For example, when you try to install SnapDrive for
Windows 7.0 or 7.0.2 on an ESX guest operating system
(Windows machines) on which SnapDrive for Windows 7.1 is
installed currently, either an error message (on x86) is produced,
or SnapDrive for Windows fails to detect the ESX machine as a
physical machine (on x64) after the installation.

768623

Your FlexClone volume disk disconnect operations fail if SMI-S

Agent and SnapDrive are using the same virtual storage server.

757590

You might experience difficulty installing SnapDrive on systems

without Internet access.

743215

You might not be able to immediately create Snapshot copy

backups on volume shares when a restore operation is in progress.

739462

You encounter error messages when SnapDrive deletes certain

LUNs.

14 | Release Notes

Bug ID

Description

724404

SnapManager for SQL Server backup verification or mount

operations fail on a Windows Failover Cluster running on VMware
when using FC RDM LUNs.

708057

When you perform VMDK SnapRestore operations on a VM

running Windows Server 2012 and ESX 5.0U2, data is not
restored.

664512

You experience slow restarts when the hotfixes associated with

Microsoft KB 2729452 or 2742599 are installed on a Windows
Guest account with SnapDrive and ESX integration.

656135

You cannot create an RDM LUN larger than 2 TB when

SnapDrive is configured with vCenter credentials.
This issue is fixed in vSphere versions 5.0U3, 5.1U2, and 5.5 GA;
this issue still exists if you are working on systems with earlier
versions of these vSphere version families.

642832

You cannot automatically rename CSV reparse points.

567067

Your pass-through disk delete or disconnect operations fail after

changing the drive letter.

851497

Shrinking a Cluster Shared Volume (CSV) LUN that shares

VHDX using SnapDrive might result in inconsistent behavior.

The following issues are not addressed on the Bugs Online web site:
Bug ID

Description

861781

Issue: Your SnapDrive for Windows GUI displays the storage system IP address
instead of the Storage Virtual Machine (SVM) host name for VMDK disks when
you are using MetroCluster configurations in switchover mode.
Workaround: None.

851995

Issue: SnapDrive for Windows does not limit the clone level to two when cloning
VMDK disks on VMFS datastores.
Workaround: None.

826201

Issue: Shrinking a thinly provisioned LUN fails with a connection timeout error.
Workaround: Shrink the LUN in smaller increments.

850838

Issue: In MetroCluster environments, after you perform a switchover and

switchback operation, the Storage Virtual Machine (SVM) name is changed from
vs1 to vs1-mc, and vice versa. In this case, if the SnapDrive for Windows host is
using VMDK disks exclusively, restore and mount workflows might fail.
Workaround: Restart the SnapDrive service (SWSVC).

Microsoft
hotfix
2908783

Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2
environments display data corruption issues when there are connections to multiple
iSCSI storage array targets.
Workaround: Download and install Microsoft hotfix 2908783.

Microsoft Support Article 2908783: Data corruption occurs on iSCSI LUNs in

Windows

15

Documentation errors and omissions

Review these errors and omissions in the published SnapDrive for Windows 7.1 documentation
carefully.
Wrong syntax for sdcli snap delete command
The syntax of the snap delete command is referred as -D MountPointList [. . .] in the
SnapDrive 7.1 for Windows Administration Guide for SAN Environments. The correct syntax is -d
MountPoint.
No information regarding SnapDrive versions to be installed on cluster nodes
The SnapDrive for Windows documents do not specify that all the nodes in the cluster must be
running the same version of SnapDrive for Windows.

16

How to get help and find more information

The NetApp Support Site provides access to troubleshooting tools, product documentation, and
technical assistance. You can use NetApp Community forums to connect with peers, and the NetApp
Library to access technical reports and white papers.
Resource

Description

NetApp Support Site

Access troubleshooting tools, product

documentation, and technical support
assistance.

NetApp Community public forum

Connect with peers, ask questions, exchange

ideas, find resources, and share best practices.

NetApp Library

Access technical reports, white papers, and

other documents.

17

Copyright information
Copyright 19942016 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval systemwithout prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

18

Trademark information
NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express,
Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash
Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale,
FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster,
MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity,
SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive,
SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,
Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL and
other names are trademarks or registered trademarks of NetApp, Inc., in the United States, and/or
other countries. All other brands or products are trademarks or registered trademarks of their
respective holders and should be treated as such. A current list of NetApp trademarks is available on
the web.

http://www.netapp.com/us/legal/netapptmlist.aspx

19

How to send comments about documentation and

receive update notifications
You can help us to improve the quality of our documentation by sending us your feedback. You can
receive automatic notification when production-level (GA/FCS) documentation is initially released or
important changes are made to existing production-level documents.
If you have suggestions for improving this document, send us your comments by email.

[email protected]
To help us direct your comments to the correct division, include in the subject line the product name,
version, and operating system.
If you want to be notified automatically when production-level documentation is released or
important changes are made to existing production-level documents, follow Twitter account
@NetAppDoc.
You can also contact us in the following ways:

NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.

Telephone: +1 (408) 822-6000

Fax: +1 (408) 822-4501

Support telephone: +1 (888) 463-8277