IBM System Storage N Series Snapmanager 1.2 for Hyper-V

IBM System Storage N series

SnapManager 1.2 for Hyper-V Release Notes

GC52-1352-02

Contents

What you can do with SnapManager for Hyper-V ...... 1

SnapManager for Hyper-V limitations ...... 3

Data ONTAP requirements ...... 5

License requirements ...... 7

Hotfix requirements ...... 9

Known issues ...... 11 Writer returned failure code 0x800423f3. Writer state is 8 ...... 11 Windows installer does not display installer log file ...... 11 Import (mount) of snapshot LUN from a SAN boot LUN Snapshot copy fails in Windows Server 2008 R2 ...... 12 Error 5605 while backing up ...... 12 SnapManager for Hyper-V does not automatically move files to a changed SnapInfo location . . . 12 SMHV fails to connect to a Hyper-V host ...... 12 SnapDrive fails to create CSV disk on non-English OS ...... 13 Higher memory use on SnapInfo owner node during backup ...... 13

Certification for Windows server logo ...... 15 SnapManager for Hyper-V executables ...... 18 Windows resource protection (WRP) warnings and errors ...... 18 Some assembly attributes are not correct ...... 18

Documentation corrections ...... 19 Vss Requestor - Backup Components failed with partial writer error ...... 19

Websites ...... 21

Notices ...... 27

SnapManager for Hyper-V enables you to back up and restore multiple virtual machines across multiple hosts. You can create datasets and apply policies to them to automate backup tasks such as scheduling, retention, and replication.

You can perform the following tasks with SnapManager for Hyper-V: v Group virtual machines into datasets that have the same protection requirements and apply policies to those datasets v Back up and restore dedicated and clustered virtual machines on storage systems running Data ONTAP software v Back up and restore virtual machines running on cluster shared volumes and using Windows Failover clustering v Automate dataset backups using scheduling policies v Perform on-demand backups of datasets v Retain dataset backups for as long as you need them, using retention policies v Update the SnapMirror destination location after a backup successfully finishes v Specify custom scripts to run before or after a backup v Restore virtual machines from backups v Monitor the status of all scheduled and running jobs v Manage hosts remotely from a management console v Provide consolidated reports for dataset backup, restore, and configuration operations v Perform a combination of crash-consistent and application-consistent backups v Perform disaster recovery operations using PowerShell cmdlets

Some features are not supported in SnapManager 1.2 for Hyper-V. v Canceling, suspending, and resuming backup jobs are not supported. v Canceling a restore job is not supported. v Canceling the backup delete job is not supported. v SnapManager for Hyper-V works with primary storage only. v Policies cannot be copied across datasets. v Role-based access control (RBAC) is not supported. v Excluding Virtual Hard Disks (VHDs) from a SnapManager for Hyper-V Volume Shadow Copy Service (VSS) backup job is not supported. v Single file restore from a backup copy is not natively supported. v SnapVault is not natively supported on SnapManager for Hyper-V. v Cross-version management is not supported; for example, you cannot use a version 1.0 Client Console to manage SnapManager 1.2 for Hyper-V, and vice versa. v If you start to restore a Hyper-V virtual machine (VM), and another backup or restoration of the same VM is in process, your attempt fails. v Restoring a deleted VM from a crash-consistent backup copy is not supported. v Running different versions of SnapManager for Hyper-V on different nodes of a failover cluster is not supported. v Reverting from SnapManager 1.2 for Hyper-V is not supported. v Backup or restore of virtual machines is not supported when users change the cluster ownership node while backing up or restoring. v Mixed-mode backups (of virtual machines containing files on CSV 2.0 volumes and normal shared disks) are not supported. v After you migrate the storage of a VM to another location using Windows Server 2012, you cannot restore on that VM from backups taken before the migration. v For Windows Server 2012, you cannot perform a backup job where the backup set includes both a cluster-shared volume (CSV) and a shared disk.

The Data ONTAP requirements differ depending on the type of licensing you use with SnapManager for Hyper-V.

If you use this type of licensing... Then use this Data ONTAP version... Host-based licensing 7.3.1P1 or later Storage system licensing 7.3.2 or later

The following Data ONTAP versions of MultiStore (vFiler unit) are required for use with SnapManager for Hyper-V: v 7.3.1.1P8 v 7.3.2P1 or later v 8.0P2 or later

To run SnapManager for Hyper-V, you must install either host-based or storage system licenses.

SnapManager A SnapManager license is required on the Windows host system. You can choose either host-based licensing or storage system licensing. Per server This is also known as host-based licensing. If you license select host-based licensing, you must provide a license key during installation. You can change the license key after installation by clicking License settings in the SnapManager for Hyper-V Welcome window. Each parent host requires a license. Host-based licensing requires Data ONTAP 7.3.1P1 or later. Per storage This is also known as storage system licensing. If system license you select storage system licensing, you must add the SnapManager for Hyper-V license to all storage systems to run the SnapManager for Hyper-V operations. Storage system licensing requires Data ONTAP 7.3.2 or later. Per client system Use this licensing option when you are installing license the management console.

You must manually install hotfixes to Microsoft Windows Server 2008 R2 and R2 SP1 operating system environments.

Operating system Required hotfixes

Windows Server 2008 R2 v KB978157 v KB979743 v KB2406705 v KB974909 v KB975354 v KB977096 v KB974930 v KB2517329 v KB2779768

Windows Server 2008 R2 SP1 v KB2406705 v KB2531907 v KB2263829 v KB2494016 v KB2637197 v KB2517329 v KB2779768

Windows Server 2012 v KB2770917 v KB2779768

Note: See the SnapManager 1.2 for Hyper-V Release Notes for the latest Microsoft-recommended hotfixes.

Some unexpected and potentially undesired behaviors are known to affect functionality in this release of SnapManager for Hyper-V. You can take actions to work around some of these behaviors. v “Writer returned failure code 0x800423f3. Writer state is 8” v “Windows installer does not display installer log file” v “Import (mount) of snapshot LUN from a SAN boot LUN Snapshot copy fails in Windows Server 2008 R2” on page 12 v “Error 5605 while backing up” on page 12 v “SnapManager for Hyper-V does not automatically move files to a changed SnapInfo location” on page 12 v “SMHV fails to connect to a Hyper-V host” on page 12 v “SnapDrive fails to create CSV disk on non-English OS” on page 13 v “Higher memory use on SnapInfo owner node during backup” on page 13

Writer returned failure code 0x800423f3. Writer state is 8

Message Vss Requestor - Backup Components failed. Writer Microsoft Hyper-V VSS Writer involved in backup or restore encountered a retryable error. Writer returned failure code 0x800423f3. Writer state is 8 Description This is a Windows Server 2012 issue that is caused by the inclusion of direct attached iSCSI LUNs or pass-through disks in the VSS backups. The fix was released as a Windows update for Windows Server 2012. Corrective Perform these two steps to resolve this issue: action 1. Install the Windows Server 2012 update KB2770917. 2. Update the integration service in all the virtual machines (VMs) which have SnapDrive for Windows installed and have direct-attached iSCSI LUNs or pass-through disks on them.

Windows installer does not display installer log file

Issue Windows installer does not display the Windows installer log file after installation finishes on the following operating systems: v Windows Server 2003 v Windows XP v Windows Vista

© Copyright IBM Corp. 2013 11 Cause This is a known limitation in the Windows installer. Corrective To view the log file manually, go to \windows\temp and find the MSI log file action (MSI####.log) that is stamped with a time close to the time that the installation completed.

Import (mount) of snapshot LUN from a SAN boot LUN Snapshot copy fails in Windows Server 2008 R2 SnapManager for Hyper-V does not support the backup and restore of virtual machines running on SAN boot LUNs. This is a limitation of SnapDrive 6.4.1 for Windows.

Error 5605 while backing up

Message The root\MSCluster namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again. Description This message occurs during SnapManager for Hyper-V backups. It occurs because SnapManager for Hyper-V sets the authentication level each time a call is made to WMI (Windows Management Instrumentation). SnapManager for Hyper-V uses packet privacy as the authentication level. If SnapManager for Hyper-V receives this warning, the application modifies the authentication level temporarily and sets it to the packet privacy. Corrective The next set of calls works without triggering an error. These warnings can be safely action ignored.

SnapManager for Hyper-V does not automatically move files to a changed SnapInfo location If you change SnapInfo settings after a host has been added to SnapManager for Hyper-V, you must manually move all files on the old SnapInfo LUN to the new location; SnapManager for Hyper-V does not update them automatically. If you do not copy over the files, you cannot restore from or manage the backup taken using the old SnapInfo LUN, and SnapManager for Hyper-V does not list the backup.

SMHV fails to connect to a Hyper-V host

Issue SnapManager for Hyper-V intermittently fails to connect to a Hyper-V host, even though the host is up and can be reached over the network.

12 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes Cause Smsvchost.exe for the WCF service stops responding. See Microsoft Knowledge Base article 2536617 for more information. Corrective action See Microsoft Knowledge Base article 2504602 for a possible workaround.

SnapDrive 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). SnapManager for Hyper-V first checks the current user locale, and next finds the default cluster group name using Windows Management Instrumentation (WMI). Therefore, when creating or connecting a CSV disk on a non-English-language operating system, you must modify the Region and Language Settings of your OS to match your settings in SnapManager for Hyper-V.

Corrective action 1. Go to your operating system's Region and Language settings. 2. From the Formats option, select the appropriate language.

Higher memory use on SnapInfo owner node during backup

Issue The SnapInfo owner node shows higher memory use by the SnapManager for Hyper-V service when a backup is in progress. Cause This is an expected behavior in SnapManager 1.1 for Hyper-V. After the backup is completed, memory use returns to normal. Corrective action None required.

Known issues 13 14 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes Certification for Windows server logo

There are some requirements for the Windows server logo certification.

SnapManager for Hyper-V custom actions

There are custom actions implemented in the SnapManager for Hyper-V MSI package.

Custom action Description AbortOnInvalidAccount Abort installation when invalid account is found CheckSMHVLicense Validate SnapManager for Hyper-V installation license information CheckForProductUpdates MSI custom action CheckForProductUpdatesOnReboot MSI custom action CleanUp_SMHV_WS_ConfigFile Remove SnapManager for Hyper-V WebService configuration file CreateNetShare Create SnapManager for Hyper-V product report file share information CreateSmhosts Create the SnapManager for Hyper-V WebService configuration file CreateSmhv_ConfigFile Create the SnapManager for Hyper-V WebService configuration file detectIBMSMHV Detect the IBM-based SnapManager for Hyper-V installation DetectNetAppSMHV Detect the NetApp-based SnapManager for Hyper-V installation DetectSDWInstallStatus Detect the SnapDrive installation status to configure virtual machine backup performance parameters DisplayCustomHelp Display SnapManager for Hyper-V unattended installation switch information DLLWrapCleanup InstallShield custom action DLLWrapStartup InstallShield custom action

© Copyright IBM Corp. 2013 15 Custom action Description EmptySMHV_Install_Folder Remove SnapManager for Hyper-V product files from SnapManager for Hyper-V installation folder (executed during SnapManager for Hyper-V uninstall) GetSMHVLicenseFromRegistry Retrieve SnapManager for Hyper-V product license information from the registry GetSMHVServiceAccount Retrieve SnapManager for Hyper-V service account information InstallNativeImageCache Launch Ngen.exe to create native image for CLR IsDotNetInstalled Validate.NET 3.5 SP1 installed on the system IsPowerShellInstalled Validate PowerShell 1.0 installed on the system ISPreventDowngrade InstallShield custom action ISPrint InstallShield custom action ISSetAllUsers InstallShield custom action IsSMHVAccountValid Validate the SnapManager for Hyper-V account information IsWindows2008ServerCoreR2 Ensure that the target system is Windows Server 2008 R2 MSIRESTARTMANAGERCONTROL Set MSI property to Disable for disabling MSI system restart MSIDISABLERMRESTART Set MSI property 1 to disable automatic shutdown using Restart Manager PreserveLicenseCode Preserve the SnapManager for Hyper-V license information REBOOTPROMPT Suppress the REBOOT prompt REBOOTSUPPRESS Disable the system reboot action ReadSMHV_WebSrvPortFromConfigFile Read SnapManager for Hyper-V TCP port from SnapManager for Hyper-V WebService configuration file Reg_SMHV_VssLib Register the SnapManager for Hyper-V VSS component RemoveNativeImageCache Launch nget.exe to remove the native image for CLR (executed during SnapManager for Hyper-V uninstall)

16 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes Custom action Description RemoveNetShare Remove the SnapManager for Hyper-V report directory net share information (executed during SnapManager for Hyper-V uninstall) RemoveSDWConfigurationSettings RemoveSnapDrive related configuration information (executed during SnapManager for Hyper-V uninstall) ResetLicense_Silence_Install Reset the SnapManager for Hyper-V license information during unattended SnapManager for Hyper-V installation ResetLicenseCode Reset the SnapManager for Hyper-V license information SelectUser Display and selecting the Windows domain admin users setAllUsersProfile2K InstallShield custom action SetAllUsersProfileNT InstallShield custom action SetARPINSTALLLOCATION InstallShield custom action SetReportPath Validate the set SnapManager for Hyper-V product report file path SetSDWConfigurationSettings Set the SnapDrive configuration information SetSMHVConfigurationSettings Set SnapManager for Hyper-V service configuration parameters in the registry SetUpdatedProductVersion InstallShield custom action setUserProfileNT InstallShield custom action ShowMsiLog InstallShield custom action SilentInstall_Lic_Check Validate the SnapManager for Hyper-V license during SnapManager for Hyper-V unattended installation SMHVLicenseValidate Validate the SnapManager for Hyper-V license information StartNetTcpPortShareService Start the .NET Tcp Port Sharing Service StopSMHVService Temporarily stop SnapManager for Hyper-V service SxsInstallCA InstallShield custom action SxsUninstallCA InstallShield custom action UnReg_SMHV_VssLib Unregister the SnapManager for Hyper-V VSS component (executed during SnapManager for Hyper- V uninstallation)

Certification for Windows server logo 17 SnapManager for Hyper-V executables The SnapManager for Hyper-V Microsoft Installer (MSI) package is signed, but the .NET assemblies in it are not. This is due to a known issue where the .NET framework loads signed assemblies on to systems that are not connected to the Internet. Windows resource protection (WRP) warnings and errors A 3323 warning and a 331B error might occur when testing appverifier.exe. SnapManager for Hyper-V installation proprietary custom actions do not cause the 3323 warning and 331B error; rather, both originate from the Microsoft Installer (MSI) engine. This warning and error do not cause any compact issues while installing SnapManager for Hyper-V. Some assembly attributes are not correct

Issue Some DLLs that shipped with SnapManager 1.0 for Hyper-V do not have the proper assembly attributes set. Assembly attributes include, but are not limited to, company name, product name, and version. Cause DevExpress.Charts.v9.1.Core.dll Windows Explorer displays the correct information for all fields. You can locate the DLL in the %systemroot\assembly folder. SnapMgrUISkins.dll This DLL is a custom skin library generated for the MMC GUI snap-in, using the DevExpress tool SkinEditor. This tool does not provide the option to set the assembly attribute. This issue is a limitation of this tool and has been acknowledged by DevExpress. See issue Q236087 on the DevExpress support site. Corrective Correct the assembly attributes. action

18 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes Documentation corrections

Some information becomes available after the guides provided with this release are published. You should use these corrections in conjunction with the guides provided with this release. You can be sure that you have the latest information by monitoring the N series support site (accessed and navigated as described in Websites) for updates to the Release Notes.

Vss Requestor - Backup Components failed with partial writer error

Message Error: Vss Requestor - Backup Components failed with partial writer error. Writer Microsoft Hyper-V VSS Writer involved in backup or restore operation reported partial failure. Writer returned failure code 0x80042336. Writer state is 5. Application specific error information: Application error code: 0x1 Application error message: - Failed component information: Failed component: VM GUID XXX Writer error code: 0x800423f3 Application error code: 0x8004230f Application error message: Failed to revert to VSS snapshot on the virtual hard disk ’volume_guid’ of the virtual machine ’vm_name’. (Virtual machine ID XXX)

The following errors appear in the Windows Application event log on the Hyper-V host: Volume Shadow Copy Service error: Unexpected error calling routine GetOverlappedResult. hr = 0x80070057, The parameter is incorrect.

Operation: Revert a Shadow Copy

Context: Execution Context: System Provider Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details RevertToSnapshot [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information.].

Operation: Revert a Shadow Copy

Context: Execution Context: Coordinator

© Copyright IBM Corp. 2013 19 Description This message appears when performing an application-consistent backup of a dataset. This error causes the backup to fail for some of the virtual machines in the dataset.

Corrective v Retry the dataset backup. action v If the retry attempt fails again, split the dataset into two datasets so that all the VMs whose backup failed will be placed into a single dataset and all other VMs will be put into another dataset. Then run the backup again.

20 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes 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: 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, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

© Copyright IBM Corp. 2013 23 (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, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,

24 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes 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 is a licensee of the CompactFlash and CF Logo trademarks.

NetApp NetCache is certified RealSystem compatible.

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.

28 IBM System Storage N series: SnapManager 1.2 for Hyper-V Release Notes Notices 29

NA 210_05723, Printed in USA

GC52-1352-02