IBM. SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris) IBM System Storage N series GC

Transcription

1 IBM System Storage N series IBM SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris) GC

2

3 Contents Product overview New in this release Fixed issues Upgrade notes Important cautions Known limitations Known issues Websites Copyright and trademark information Trademark information Notices Index Copyright IBM Corp iii

4 iv IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

5 Product overview SnapDrive for UNIX simplifies data management and increases the availability and reliability of application data through simplified storage provisioning and file system consistent Snapshot copies. SnapDrive for UNIX simplifies data backup so that you can recover data even if it is deleted or modified. SnapDrive for UNIX uses Snapshot technology to create an image of the data on a shared or unshared storage system attached to a UNIX host. When you restore a Snapshot copy, it replaces the current data on the storage system with the data from the Snapshot copy. SnapDrive for UNIX provides storage features that enable you to manage the entire storage hierarchy, such as the host-side application-visible file, the volume manager, and the storage system-side logical unit number (LUN). Copyright IBM Corp

6 2 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

7 New in this release You should be familiar with the new features and enhancements included in SnapDrive 5.3 for UNIX. v Provides 64-bit SnapDrive for UNIX binaries on Linux v Supports alias names in a Linux multipathing environment Note: For updated information about SnapDrive for UNIX and its requirements, see the Interoperability Matrix. Fixed issues It is a good practice to review the known issues fixed in a new release before upgrading to it. v v SnapDrive for UNIX does not work as expected if the 32-bit versions of the required libraries are not installed. This limitation persists because SnapDrive for UNIX is a 32-bit binary. SnapDrive for UNIX cannot connect to the cserver when there are more than 20 Vserver Storage Virtual Machine (SVM) in the cluster. v The cloned volume is not deleted automatically after disconnecting and moving the cloned volume to a different aggregate in SnapDrive for UNIX. v v SnapDrive for UNIX snap connect operation is failing when there are multiple volumes to clone when Logical SnapMirror (LSM) is used. SnapDrive for UNIX snap create operation is failing with timeout error during snapshot-get-iter ZAPI call. v This release has been updated to resolve the libxml vulnerabilities in SnapDrive for UNIX, which is tracked by the following: CVE and CVE v This release has been updated to resolve the multiple OpenSSL vulnerabilities in SnapDrive for UNIX, which is tracked by the following: CVE , CVE , CVE , CVE , CVE , CVE , CVE , and CVE v This release has been updated to resolve the multiple OpenSSL vulnerabilities in SnapDrive for UNIX, which is tracked by the following: CVE , CVE , CVE , CVE , CVE , CVE , CVE , CVE , CVE , CVE , CVE , CVE , and CVE v This release has been updated to resolve the multiple OpenSSL vulnerabilities in SnapDrive for UNIX, which is tracked by the following: Copyright IBM Corp

8 CVE , CVE , CVE , CVE , CVE , CVE , and CVE IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

9 Upgrade notes Upgrade notes describe important changes in support between the last release of the product and this one, including any deprecated features. Review this information carefully before upgrading to the new release. Make sure to check the IBM N series interoperability matrix for the most up-to-date information about supported configurations. Supported upgrade path v Upgrading from SnapDrive for UNIX and earlier versions to 5.3 version preserves the former snapdrive.conf file, and the upgrade works fine, without any issues. v When upgrading within SnapDrive for UNIX 5.3 (32-bit version to 64-bit version), you must force the upgrade, and the former snapdrive.conf file is preserved: rpm Uvh snapdrive.rpm --force v You can either install the 64-bit SnapDrive for UNIX in a new environment or you can upgrade your 32-bit SnapDrive for UNIX to 64-bit version on a 64-bit Linux operating system and while installing 64-bit SnapDrive for UNIX you do not require any 32-bit libraries or packages to be installed in the Linux operating system. Copyright IBM Corp

10 6 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

11 Important cautions Important cautions identify issues that might cause data loss or system failure. You should review these cautions carefully. Migrating using 7-Mode Transition Tool For information about how to migrate using the 7-Mode Transition Tool, see 7-Mode Transition Tool Data and Configuration Transition Guide. For more information about migration from a 7-Mode environment to clustered Data ONTAP, see TR If the migration is successful, you should be able to see the NFS mount points and the volumes on the host from the Vserver Storage Virtual Machine (SVM, formerly known as Vserver). The Snapshot copies on the secondary storage system cannot be migrated because OnCommand Unified Manager 5.x is not supported with clustered Data ONTAP After migration from a 7-Mode storage environment to clustered Data ONTAP, you must perform the following post-migration steps to ensure successful operation of SnapDrive commands: 1. Configure the new clustered Data ONTAP storage system name in SnapDrive for UNIX: snapdrive config migrate set <old_storage_system_name> <new_storage_system_name>. 2. Perform an OS-level rescan to remove any stale devices: rescan-scsi-bus.sh -r. 3. Create an iscsi session with the new clustered Data ONTAP storage system: iscsiadm -m discovery -t st -p IP address of clustered Data ONTAP storage system :3260 -l. 4. If you are working in a Fibre Channel Protocol (FCP) environment, add the new clustered Data ONTAP storage worldwide port names (WWPNs) to the existing igroup and configure the zone details in the FC fabric. 5. Verify the LUNs from clustered Data ONTAP volumes: sanlun lun show. If the LUNs are not discovered, run the OS command to perform discovery: v v rescan-scsi-bus.sh -r -s, if you are using Linux 6.4 or earlier rescan-scsi-bus.sh -r -a, if you are using Linux 6.5 or later Copyright IBM Corp

12 6. For a SAN volume, you must use the snapdrive storage connect command to make the volume visible in the host. You can now start using SnapDrive to create Snapshot copies. 8 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

13 Known limitations Known limitations identify platforms, devices, or functions that are not supported by this release of the product, or that do not interoperate correctly with it. Review these limitations carefully. General limitations v SnapDrive for UNIX does not support MetroCluster in an RDM (Raw Device Mapping) environment in a guest operating system. v SnapDrive for UNIX does not support Snapshot operations on an NFS mount point when the volume is exported with Kerberos security authentication types krb5, krb5i, or krb5p. v In clustered Data ONTAP, SnapDrive for UNIX does not support symbolic links for any mount points. v SnapDrive for UNIX does not support operations on file specifications or LUNs if they are located across Data ONTAP operating in 7-Mode and clustered Data ONTAP storage systems. v If you are using clustered DATA ONTAP to configure a Vserver with SnapDrive for UNIX, ensure that the IP address of the Vserver LIF is mapped to the Vserver name, either in the DNS or in /etc/hosts. You must also ensure that the Vserver name is configured in SnapDrive for UNIX by using the snapdrive config set vsadmin Vserver name command. v You must assign the aggregates that contain Vserver volumes to the Vserver aggregate list to configure the Vserver and execute SnapDrive for UNIX operations. v v Snapshot operations might be inconsistent if you perform a snap restore operation on a mount point where an entity other than the one created in the Snapshot copy is mounted. SnapDrive for UNIX modifies the mount point permissions from a nonroot user to a root user for a qtree after volume-based SnapRestore (VBSR) operations. v Starting with SnapDrive 5.1 for UNIX, 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 a volume clone and LUN clone, LUN clone and LUN, or volume clone and LUN. Copyright IBM Corp

14 v Restoring the storage stack on the host fails if you remove 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 an NFS in the SnapMirror destination. v SnapDrive for UNIX does not support Broadcom Converged Network Adapters (CNA). v In clustered Data ONTAP, aggregates that contain data Vserver volumes must be assigned to the data Vserver aggregate list to configure the data Vserver and perform SnapDrive operations. v In clustered Data ONTAP, SnapDrive for UNIX does not support the snap connect operation with the -readonly option from the secondary host, which does not have export permissions on the parent volume. v In clustered Data ONTAP, the export policy is defined only at the volume level. Therefore, the.snapshot directory cannot be exported to the secondary host, which does not have export permission on the parent volume. SnapDrive for UNIX does not support non-english language environments. v The snap restore operation fails if it is attempted from the Snapshot copy that was created before the LUNs were moved to another volume. v If you are using clustered Data ONTAP 8.2 or later, the Snapshot operations on a Snapshot copy might fail if a cloning operation that is in progress uses the same Snapshot copy. You must retry the operation later. v OnCommand Unified Manager 6.0 or later does not support Protection Manager on clustered Data ONTAP; therefore, integration between OnCommand Unified Manager 6.0 or later and Snapdrive for UNIX is not supported. Due to this, the following SnapDrive for UNIX features are not supported: Role-based access control (RBAC) integration with Unified Manager 6.0 or later on clustered Data ONTAP Protection Manager integration with Unified Manager 6.0 or later on clustered Data ONTAP Limitations of SnapDrive for UNIX on Linux v In multipath environment, snapdrive snap list -v or snapdrive snap show -v operation does not show the dev path in raw LUN and snapdrive storage show -all operation does not show raw device and mount point while in case of host LVM not involved. v SnapDrive for UNIX does not show the complete alias name if the alias name has special character: "-". SnapDrive for UNIX support only "_" special character in alias name. 10 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

15 v The snapdrive config prepare luns command is not supported in the RDM LUN environment. v The snapdrive lun fixpaths command is not supported in a guest operating system. Limitations of SnapDrive for UNIX on Solaris v LUNs greater than 1 TB with the Storage Management Initiative (SMI) label are not supported. v Extensible Firmware Interface (EFI) and SMI LUNs in the same disk group are not supported. v The snapdrive lun fixpaths command is not supported in a guest operating system. Limitations of SnapDrive for UNIX on AIX v The SnapDrive for UNIX daemon takes longer to restart if one or more FC port links are down or unavailable. v However, the SnapDrive for UNIX daemon can start regardless of the state of the FC ports. By default, SnapDrive for UNIX creates disk groups with nonconcurrent settings; you need to manually change or perform storage provisioning operations. Known limitations 11

16 12 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

17 Known issues Known issues identify problems that might prevent you from using this release of the product successfully. Known issues identified in this release The following issues have been added to the release notes since the last release: v SnapDrive for UNIX fails to add the newly mapped LUNs in Red Hat Enterprise Linux 6.6 and later. v In 64-bit SnapDrive for UNIX, snap wizard disconnect and storage wizard delete operations fail due to a segmentation error. v The configuration checker tool does not detect the supported configurations for SLES 12 and SLES 11 SP3. v AutoSupport (ASUP) messages are not showing the proper file system, multipath type, and host volume manager details for a Veritas stack. This issue is noted only in a Solaris SPARC environment. v In RHEL 7 and RHEL 7.1, while rebooting the operating system, the operating system state change to emergency mode when the SAN file specification have persistent entry. v In RHEL 7 and RHEL 7.1 operating system the SnapDrive snap connect operation fails. v In RHEL 7 during the clone, backup, mount, verify, and mount operation, SnapDrive for UNIX and SnapManager for Oracle command fails. This issue is noted only in RHEL 7 NOASMLIB environment. Known issues identified in previous releases The following issues were reported in previous editions of the release notes: v SnapDrive for UNIX operations might fail if multiple IP address mappings exist. v Dataset operations, such as restore and cloning, fail from tertiary storage if the protection policy is set to Mirror, then Back up. This issue occurs if you are using either SnapDrive 5.1 for UNIX or SnapDrive 5.2 for UNIX. v If you delete more than one LUN in a secondary volume and run 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. Copyright IBM Corp

18 # 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 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. v SnapDrive for UNIX commands fail if the Operations Manager server fails to discover the LUNs. The following error message is displayed: Admin error: Could not check SD.Storage.Write access on lun storage_array1:/vol/vol1/lun1 for user unixhost\root on Operations Manager server(s) ops-mngr-server1. v The local access control mechanism does not work as intended when the storage system does not have a vol0 volume. 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. v A new exportfs policy is created when a clone is created on a host, where it does not have exportfs permission. v Note: If you are using clustered Data ONTAP 8.2.1, the newly created exportfs policy cannot be cleared even if you delete the clone. SnapDrive for UNIX leverages Virtual Storage Control (VSC) for storage provisioning on the guest operating system (OS). Storage provisioning and snap management operations might fail intermittently on the guest OS because of VSC scalability limitations. v When using SnapDrive for UNIX in the Symantec Storage Foundation for Oracle RAC (SFRAC) environment, you cannot use Telnet or Secure Shell (SSH) on the host if you restart the host after performing a clone operation. v In clustered Data ONTAP, if you use SnapDrive for UNIX to restore an NFS directory that contains symbolic links, the operation fails. v SnapDrive for UNIX operations in Linux might fail, when sg_* commands that run against Device Mapper (DM) multipath devices fail, due to a path group switch with insufficient input or output operations to activate the path group. The failure might occur in SnapDrive 5.0 for UNIX and later versions, for the hosts on Red Hat Enterprise Linux 5.6 and later, using Qlogic Fibre Channel adapters. v When you perform the snap connect operation on the Network File System (NFS) file specification from the secondary host, which does not have export permissions on the parent volume in clustered Data ONTAP, 14 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

19 SnapDrive creates a new export policy. In the newly created export policy, SnapDrive inherits the parent export policy rules and also appends the rules for the secondary host if it does not have the export permission on the parent volume. When you perform the snap disconnect operation on the NFS file specification from the secondary host, clustered Data ONTAP deletes the newly created export policy and creates unexport_policy, which is a stale export policy. The unexport_policy does not contain any rules. v 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. v 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. SnapDrive for UNIX delete and disconnect of disk groups operations fail because the host volumes are not completely disconnected or deleted. Known issues 15

20 16 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

21 Websites 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: 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: 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: 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: Copyright IBM Corp

22 18 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

23 Copyright and trademark information This section includes copyright and trademark information, and important notices. Copyright information Copyright NetApp, Inc. All rights reserved. Printed in the U.S.A. Portions copyright 2015 IBM Corporation. All rights reserved. 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. 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. 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 Copyright IBM Corp

24 (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 (October 1988) and FAR (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 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, Customer Fitness, Cryptainer, CryptoShred, CyberSnap, Data Center Fitness, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, ExpressPod, FAServer, FastStak, FilerView, Fitness, Flash Accel, 20 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

25 Flash Cache, Flash Pool, FlashRay, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gfiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault, Manage ONTAP, Mars, 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, Snap Creator, SnapDirector, SnapDrive, SnapFilter, SnapIntegrator, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, VelocityStak, 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 is a licensee of the CompactFlash and CF Logo trademarks. NetApp NetCache is certified RealSystem compatible. Copyright and trademark information 21

26 22 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

27 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 U.S.A. For additional information, visit the web at: 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 Copyright IBM Corp

28 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 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.3 for UNIX Release Notes (AIX, Linux, and Solaris)

29 Index B benefits and features overview of 1 bugs considerations before upgrading to this release 13 C changes considerations before upgrading 5 considerations before upgrading to this release 5 copyright and trademark information 19 copyright information 19 E enhancements new in this release 3 F features new in this release 3 features and benefits overview of 1 fixed issues in this release 3 functions new in this release 3 I issues considerations before upgrading to this release 13 fixed in this release of SnapDrive for UNIX 3 K known issues considerations before upgrading to this release 13 known limitations considerations before upgrading to this release 9 L limitations considerations before upgrading to this release 9 N notices 23 Notices 23 P prerequisites for upgrading to this release 5 product overview features and benefits 1 R release notes considerations before upgrading to this release 5 issues fixed in this release of SnapDrive for UNIX 3 known issues in this release 13 known limitations in this release 9 overview of features and benefits 1 requirements for upgrading to this release 5 S SnapDrive for UNIX post-migration limitations for 7 post-migration steps for SnapDrive for UNIX 7 support changes considerations before upgrading 5 T trademark information 20 U upgrade considerations changes from last release to this release 5 issues fixed in this release of SnapDrive for UNIX 3 known issues in this release 13 known limitations in this release 9 V Vservers See SVMs Copyright IBM Corp

30 26 IBM System Storage N series: SnapDrive 5.3 for UNIX Release Notes (AIX, Linux, and Solaris)

31

32 IBM NA _A0_ur002, Printed in USA GC