IBM System Storage N Series Snapdrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris)

Home , Split (Unix)

IBM System Storage N series

SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris)

GC26-7877-16

Contents

SnapDrive 5.1 for UNIX Release Notes ...... 1

Limitations ...... 3

Fixed issues in SnapDrive 5.1 for UNIX ...... 5

Known Issues ...... 7 Known issues related to all hosts ...... 7 Changes to known issues ...... 11

Changes to published documentation ...... 13

Where to find additional information ...... 15

Websites ...... 17

Notices ...... 23

These release notes provide detailed information about new features, enhancements, and known issues. New features

SnapDrive 5.1 for UNIX contains the following new features and enhancements: v A new configuration wizard configures your settings in SnapDrive for UNIX. v SnapDrive allows connecting to a host volume of the cloned disk group or a subset file system without connecting the entire volume group by using the allow-partial-clone-connect variable. v SnapDrive operations are supported in Storage Area Network (SAN) boot environment. v SnapDrive supports Live Partition Mobility (LPM) and Live Application Mobility (LAM).

Note: – SnapDrive 5.1 does not support the HP-UX operating system. However, SnapDrive 5.0.x or earlier versions support HP-UX. – For updated information about SnapDrive and its requirements, see the Interoperability Matrix.

The following is a list of the current known limitations in SnapDrive for UNIX. Generic limitations of SnapDrive for UNIX v SnapDrive 5.1 for UNIX does not support snap operations on a Network File System (NFS) mount point when the volume is exported with Kerberos authentication security type such as krb5, krb5i, or krb5p. v Snap operations might be inconsistent if you perform SnapRestore on a mount point where a different entity is mounted other than what was created by the Snapshot copy. v SnapDrive modifies the mount point permissions from non-root user to root user for a qtree after volume-based SnapRestore (VBSR) operations. v From SnapDrive for UNIX 5.1, only asynchronous mode is supported for clone split operations. The split-clone-async configuration variable and -splitmode command-line options are removed. v The clone split operation is not supported on a filespec, which is a combination of either volume clone and LUN clone, LUN clone and LUN, or volume clone and LUN. v Restoring the storage stack on the host fails if you have removed a LUN by using an external command. v SnapDrive for UNIX does not allow you to restore a Snapshot copy of a qtree if the Snapshot copy is mounted on a Network File System (NFS) in the SnapMirror destination. Limitations of SnapDrive for UNIX on Linux platform v SnapDrive for UNIX does not support operations on a file specification/LUNs, which span across Data ONTAP operating in 7-Mode storage systems. Limitations of SnapDrive for UNIX on Solaris platform v SnapDrive 5.1 for UNIX supports Veritas 5.0 MP1 RP4. v LUNs greater than 1 TB with SMI label is not supported v SnapDrive for UNIX does not support the EFI and SMI LUNs in the same disk group.

© Copyright IBM Corp. 2012 3 Limitations of SnapDrive for UNIX on AIX platform v The SnapDrive daemon takes a long time to restart if one or more FCP ports links are down or not available. However, SnapDrive daemon starts irrespective of the state of the FCP ports. v SnapDrive for UNIX, by default, creates disk groups with non-concurrent settings, and you need to change or provide storage provisioning operations manually.

4 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) Fixed issues in SnapDrive 5.1 for UNIX

The following known issues are fixed in SnapDrive 5.1 for UNIX. SnapDrive storage provisioning commands fail when you specify both the -nolvm and -nopersist options during file system creation

When you create or connect a file system by using both the -nolvm and -nopersist options, snapdrive storage create, snapdrive storage connect, and snapdrive host connect commands fail in AIX. Restoring NFS directories with symbolic links fail in Data ONTAP operating in 7-Mode

In Data ONTAP operating in 7-Mode, if you use SnapDrive for UNIX to restore an NFS directory that contains symbolic links, the operation fails. Clone split cannot be performed for a LUN clone that is inside a FlexClone

When you execute the snapdrive clone split start command, the clone split operation fails for a LUN clone that resides inside the FlexClone. SnapDrive log files have read-write permissions only for the root users

The log files in SnapDrive for UNIX such as trace, audit, and recovery have read-write permissions only for the root users and read permission for all users.

To use the SnapDrive for UNIX product more effectively, you should be aware of the following known issues and workaround for some features.

Known issues related to all hosts Some potentially undesirable behaviors that impact all supported host platforms have been identified in this release. Workaround is provided where available. Database clone creation fails in an NFS environment

After you upgrade to SnapDrive 5.1, in an NFS environment, SnapManager fails to create database clones by using the secondary backups or on to the secondary host (does not have export permissions on the parent volume).

The following error message is displayed:

0001-859 Admin error: The host's Host_Name interfaces, Interface_Names are not allowed to access the path Volume_Path on the storage system Storage_Name. To resolve this problem, please configure the export permission for path Volume_Path on the storage system Storage_Name so that host Host_Name can access the path.

This issue occurs because the default value of the check-export-permission- nfs-clone parameter in the snapdrive.conf file is ON.

Workaround

You can perform one of the following: v Configure the export permissions for the volume so that the host can access the volume. v Set the check-export-permission-nfs-clone parameter value to OFF. SnapDrive operations might fail when multiple operations are performed simultaneously

When multiple SnapDrive operations are performed simultaneously, SnapDrive fails to free the OnCommand Unified Manager server resources. Therefore, the SnapDrive operations fail.

© Copyright IBM Corp. 2012 7 For example, you might have scheduled multiple backup operations for different profiles. The second backup operation might get triggered before the first backup operation is completed, resulting in both the operations failing.

You might also get the following error messages when multiple SnapDrive operations are performed in quick succession: v Auto detection of file_spec(s) in progress... Error -1 fault: SOAPENV: Client v 9000-015 Unknown Error : -1 : Please check if the daemon has been stopped

Workaround

Increase the value of the master-daemon-soap-call-send-recv-timeout variable in the snapdrive.conf file to ensure that the operations are performed successfully. The value assigned to the variable must be in seconds. The recommended minimum value that you can assign is 60 seconds.

Note: The default value for the master-daemon-soap-call-send-recv-timeout variable is 3 seconds. Special characters in the AutoSupport messages result in garble values in the EMS log view of the storage system

When AutoSupport is enabled in SnapDrive for UNIX and if any operation fails, the error messages are logged in the EMS log view of the storage system. If the error message contains any special characters such as <, >, &, ', ", and \r, garble values are displayed in the EMS log view of the storage system.

Workaround:

None. Snapshot copies created on the FlexClone volume are deleted after the clone split operation

While performing a clone split operation on the FlexClone volume, all the Snapshot copies on the volume are deleted.

You can run the clone split estimate command to determine the Snapshot copies that were created in the cloned volume before the volume clone was split.

Workaround:

8 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) None. SnapDrive clone split estimate using Snapshot copy name along with the - volclone option does not display the underlying volume names

SnapDrive clone split estimate using Snapshot copy with the -volclone option displays the resource name as Snapshot copy names. If there are multiple volumes, it is difficult to identify the corresponding estimates for the underlying volumes.

Workaround:

None. SnapDrive clone split estimate using the -fs or -dg option does not display the underlying multiple LUNs

When you execute the SnapDrive clone split estimate command by using the -fs or -dg option on a FlexClone containing multiple LUNs, it displays the file specifications instead of the corresponding underlying LUNs. Therefore, it is difficult to identify the clone split estimate for the corresponding underlying LUNs.

Workaround:

None. Autodetect does not work for more than one LUN in a secondary volume

If you delete more than one LUN in a secondary volume, and execute the snapdrive storage delete command, SnapDrive for UNIX displays the following error message:

Could not detect type of the entity...

The snapdrive storage delete command deletes only the first LUN in the secondary volume:

Known Issues 9 # snapdrive storage delete storagesystem:/vol/user/test1 test2 /vol/user/test3 test4 Auto detection of file_spec(s) in progress ... - ’storagesystem:/vol/user/test1’ detected as LUN - ’test2’ detected as LUN - ’/vol/user/test3’ detected as LUN 9000-305 Command error: Could not detect type of the entity test4. Provide a specific option (-lun, -dg, -fs or -lvol) if you know the type of the entity.

Workaround:

None. The storage show commands for LUNs fail if volume group is unavailable in AIX®

On AIX hosts, the snapdrive storage show -lun lun_name and snapdrive storage show -all commands fail if any volume group on the system is varied off.

SnapDrive for UNIX cannot determine the volume groups to which the LUNs belong. This issue might occur because the storage show commands specify one or more LUNs using the options -lun and -all, and the volume to which the LUN belongs may be inactive. If you use one of the other command options such as, -dg, -hostvol,or-fs, the command captures the information for that entity. Other forms of the snapdrive storage show command work without issues if you do not specify an inactive or varied-off volume group.

Workaround:

You can activate the inactive volume group by using the varyon command in AIX. If you have a host cluster, activating all the volumes might not be practical. In this case, use the snapdrive storage show command with the -dg, -hostvol,or-fs option rather than the -lun or -all option. SnapDrive for UNIX daemon start process fails if performed immediately after a stop

If the SnapDrive for UNIX daemon is started immediately after a stop, sometimes the start may fail due to child processes waiting on the port for a longer period. The waiting period usually depends on the TCP timeouts and the life of that child process. If the child process is waiting on the port for long, the daemon cannot use that port and the daemon start might fail.

Workaround:

10 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) Wait until processes in the Time Wait state are timed out. This wait period can be as long as five minutes.

Note: This issue might occur more frequently on Solaris platforms. If the Operations Manager server fails to discover the LUNs, SnapDrive for UNIX commands fail with an error message "Could not check"

SnapDrive for UNIX commands fail, if the Operations Manager server fails to discover the LUNs. The following error message is displayed: 0002-332 Admin error: Could not check SD.Storage.Write access on lun storage_array1:/vol/vol1/lun1 for user unix-host\root on Operations Manager server(s) ops-mngr-server1

Workaround:

None. Access control permissions file does not work as intended

The local access control mechanism does not work as intended when the storage system does not have a vol0.

By default, SnapDrive for UNIX can find the permissions file for local access control at /vol/ vol0/sdprbac/sdhostname.prbac, where hostname is the name of the local host. This issue does not occur if the vol0 volume is on the storage system.

Workaround:

You can use the rbac-vol-name parameter in the snapdrive.conf file to specify a different volume name where SnapDrive for UNIX looks for the permissions file. Do not specify the name of the volume with "/vol" suffix. For example, you can specify rbac-vol-name="vol1".

SnapDrive for UNIX then uses that volume name for all the storage systems accessed from the local host.

Changes to known issues In the release notes, some topics that were previously in the known issues section have been moved to a different section of the release notes or to a different document, such as the installation guide.

Topics moved to the Installation and Administration Guide

Known Issues 11 The following topics have been moved: v Snap management operation fails in RHEL/OEL 5.x due to an issue with umount command v SSL error occurs due to unsupported version

Topics moved to limitations section

The following topics have been moved to the limitations section: v Restoring the storage stack on the host after removing a LUN v Restoring qtrees in NFS-mounted file systems on SnapMirror destination

Topics removed

The following topics have been removed because they are not issues anymore: v Snapdrive storage delete operation hangs for a LUN in DMP configuration v Directory access and ownership rights change during the Snapshot restore operation v Restore operation fails with a message that the file system is mounted

12 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) Changes to published documentation

There are changes to the documentation provided with SnapDrive 5.1 for Linux. Update to the Partitioning support in Red Hat Enterprise Linux and SUSE Linux Enterprise Server topic

The information about the partitioned devices on Linux is missing in the SnapDrive for UNIX Installation and Administration Guide. The following table provides the missing information:

File Non- system Supported partitioning Supported Operating Single Multiple partition or RAW method in non-MPIO partitioning method system partition partition devices devices environment in MPIO environment RHEL or Yes No No ext 3 Enter the following Enter the following OEL 4x or command: sfdisk -uS -f command: 5x -L -q /dev/ device_name v sfdisk -uS -f -L RHEL 6x Yes No No ext3 or -q /dev/ ext4 device_name v kpartx -a -p p SLES 11 Yes No No ext3 /dev/mapper/ device_name SLES 10 No No Yes ext3 Not applicable Not applicable

© Copyright IBM Corp. 2012 13 File Non- system Supported partitioning Supported Operating Single Multiple partition or RAW method in non-MPIO partitioning method system partition partition devices devices environment in MPIO environment RHEL or YesNoNoASMEnter the following Enter the following OEL 4x with command: fdisk /dev/ commands: ASMLib device_name v fdisk /dev/ RHEL or Yes No Yes ASM Command (m for mapper/ OEL 5x with help):n device_name Command action ASMLib Command(m for e extended help):n p Partition Command action number (1-4):1 e extended Using default p primary value 1 partition(1-4)p Last cylinder Partition or +size number (1-4):1 or +sizeM or First +sizeK cylinder(1-3917 (1-3917,default , 3917):3917 default 1):1 Using default Using default value 3917 value 1 Command (m for Last cylinder help):x or +size or Expertcommand(m +sizeM or for help):b +sizeK 1-3917, Partition default 3917): number(1-4):1 3917 New beginning Using default of data value 3917 63-62926604, Command (m for default 63):64 help):x Expert command Expert command (m for help) m for help):b :w Partition number(1-4):1 New beginning of data 63-62926604, default 63):64 Expert command (m for help) :w v kpartx -a -p p /dev/mapper/ device_name SLES 10 No No Yes ASM Not applicable Not applicable with ASMLib

14 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) Where to find additional information

The following table describes documents with the most current information about host requirements, supported configurations, and procedures for installing and managing SnapDrive for UNIX.

If you want... Go to... The latest supported www.ibm.com/storage/support/nseries/ configurations Configuring and managing the The following documents for your Data ONTAP storage system release in the Data ONTAP information library: v The Data ONTAP Software Setup Guide v The Data ONTAP SAN Administration Guide (formerly the Data ONTAP Block Access Management Guide for iSCSI and FC) v Data ONTAP Release Notes® v The Data ONTAP Commands: Manual Page Reference, Volume 1 v The Data ONTAP Commands: Manual Page Reference, Volume 2 v The Data ONTAP Upgrade Guide Supported Fibre Channel SAN The Data ONTAP SAN Administration Guide topologies (formerly the Data ONTAP Block Access Management Guide for iSCSI and FC) How to download and install The SnapDrive for UNIX Installation and SnapDrive for UNIX Administration Guide Configuring your host for the The HP-UX Host Utilities Installation and Setup Host Utilities Guide

The Linux Host Utilities Installation and Setup Guide

The AIX Host Utilities Installation and Setup Guide

The Windows Host Utilities Installation and Setup Guide

IBM® maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates. The following 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 register in order to obtain access to N series support content on the web. To understand how the N series support web content is organized and navigated, and to access the N series support website, refer to the following publicly accessible web page: www.ibm.com/storage/support/nseries/ This web page also provides links to AutoSupport information as well as other important N series product resources. v IBM System Storage N series products attach to a variety of servers and operating systems. To determine the latest supported attachments, go to the IBM 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, including planning, installation and setup, and hardware monitoring, service and diagnostics, see the IBM N series Information Center at the following web page: http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

This section includes copyright and trademark information, and important notices. Copyright information

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

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 system—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM’s product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM’s or NetApp’s intellectual property rights may be used instead of the IBM or NetApp product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM and NetApp, are the user’s responsibility.

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,

© Copyright IBM Corp. 2012 19 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.A. 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).

Trademark information

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

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

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

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

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

20 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) 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, Service Builder, 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, Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States, other countries, or both.

All other brands or products are trademarks or registered trademarks of their respective 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 21 22 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) Notices

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

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

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

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, N.Y. 10504-1785 U.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 other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS 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. Some states do not allow disclaimer of express or implied warranties in certain transactions, 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 will be incorporated in new editions of the publication. IBM may make

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this 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 it believes appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

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

24 IBM System Storage N series: SnapDrive 5.1 for UNIX Release Notes (AIX, Linux, and Solaris) Notices 25

NA 210-05533_A0, Printed in USA

GC26-7877-16