SnapManager® 7.0 for Microsoft® Exchange Server

Release Notes

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089U.S.

Telephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 463-8277Web: www.netapp.comFeedback: doccomments@netapp.com

Part number: 215-07918_A0 ur001September 2013

Contents

Overview of this release ............................................................................... 4Upgrade notes ............................................................................................... 5Changed cmdlets ........................................................................................... 6Fixed issues .................................................................................................... 8Limitations .................................................................................................... 9Known issues ............................................................................................... 10Changes to published documentation ....................................................... 14

SnapManager service account requirements ............................................................. 14

Restriction when setting UTM retention and backup retention ................................ 15

FlexClone license requirements ................................................................................ 15

DAG requirements .................................................................................................... 15

Protection Manager reference ................................................................................... 15

Certification for Windows Server Logo ................................................... 16SnapManager custom actions .................................................................... 17Copyright information ............................................................................... 21Trademark information ............................................................................. 22How to send your comments ...................................................................... 23

Table of Contents | 3

Overview of this release

SnapManager 7.0 for Microsoft Exchange Server includes several new features, enhancements, andsupport for additional configurations. Some features were also removed.

Support for additional configurations

• Microsoft Exchange Server 2013 is now supported.SnapManager 7.0 does not support any other versions of Microsoft Exchange Server.

• Clustered Data ONTAP 8.2 is now supported.• Windows Server 2012 is now supported.

To identify supported configurations, go to the Interoperability Matrix located at support.netapp.com/matrix

New features and enhancements

• Gapless backup support on DAG systems has been improved from three nodes to nine nodes.• UTM retention can be triggered independently from backup retention.• When specifying backup options, the backup retention setting for remote backups now applies to

the selected management group.In previous releases, this always applied to the Management Group Standard option.

Host requirement changes

• Support for Windows Server 2008 R2 SP1 and Windows Server 2012 only.• SnapDrive for Windows version 6.5 or 7.0 is now required.• Microsoft .NET Framework 4.0 is now required.• PowerShell 3.0 is now required.

To identify supported configurations, go to the Interoperability Matrix located at support.netapp.com/matrix

Discontinued features

• Support for Local Continuous Replication (LCR), Single Continuous Replica (SCR), andBusiness Continuance (BC) has been removed.

• Support for Cluster Replication (CCR) has been replaced by Database Availability Group (DAG)support.

• Support for restoring backup sets from unmanaged media using the Restore wizard has beenremoved.

• Support for Exchange Server 2003, 2007, and 2010 has been removed.

4 | Release Notes

Upgrade notes

Upgrades are not supported in this release. You need to install a fresh copy of SnapManager 7.0 forMicrosoft Exchange Server.

5

Changed cmdlets

A number of PowerShell cmdlets have either changed or been removed in this release.

The following cmdlets were changed.

cmdlet Change

delete-backup • The -Database parameter was added.• The -StorageGroup parameter was removed.

get-backup • The -Database parameter was added.• The -StorageGroup parameter was removed.

new-backup • The -Database parameter was added.• The following parameters were removed:

• -ArchiveBackupCopyRemoteCCRNode

• -BackupCopyRemoteCCRNode

• -StorageGroup

restore-backup The following parameters were added:

• -Database

• -TargetDatabase

The following parameters were removed:

• -RestoreFromUnmanagedMedia

• -StorageGroup

• -TargetStorageGroup

verify-backup • The -Database parameter was added.• The following parameters were removed:

• -ArchiveBackupCopyRemoteCCRNode

• -lcr

• -StorageGroup

The following cmdlets were removed:

• break-mirrors

• exec-bc

• get-mirrors

6 | Release Notes

• release-mirrors

• resync-mirrors

Changed cmdlets | 7

Fixed issues

Several issues have been fixed in this release.

Bug ID Description

553170 SnapManager does not properly retain backup copies when using multiplemanagement groups.

573548 Job Monitoring reports a database that no longer exists.

628282 Up-to-the-minute (UTM) restore retention does not enforce the retention policyuntil the backup retention policy has been triggered.

649767 Backup job schedules are not working after an upgrade to the product releaselevel.

652488 SnapManager might crash on a remote verification server if there are concurrentverifications.

659863 The Backup wizard pre-populates the names of the DAG database copies andnames of the servers when scheduling a backup.

681376 SnapManager retains one SnapInfo folder too many for each database andmanagement group.

681629 AutoSupport and EMS messages do not display the correct version ofSnapManager.

693284 SnapManager retains SnapInfo directory Snapshot copies even if the -NoUTMRestore parameter is enabled in the backup job.

721246 When using a Microsoft Exchange Server version that supports RecoveryDatabase, the following error might appear when you use the Delete Backupoption: "An Error occurred while loading the Backup set information. Details:Object reference not set to an instance of an object." After this error appears, thewindow does not display databases.

747736 If you attempt to restore passive database (replica copy) when SnapManager forExchange is connected through DAG level from the MMC GUI and the Recoverand mount databases after restore option is unchecked (not selected), an error(VSS_E_WRITERERROR_RETRYABLE) is produced during the restore operation.

8 | Release Notes

Limitations

While working with SnapManager 7.0 for Microsoft Exchange, you should be aware of limitationsthat might affect your environment.

The following are not supported in this release:

• Creation and restoration of backups of Microsoft Exchange databases that are stored on storagedevices provided by companies other than NetApp.

• Restoring databases to an alternate location.• Windows Server 2008 IA-64 editions.• Configuration of datasets outside member servers of the Database Availability Group (DAG).• Use of the Delete window outside member servers of the DAG.• Running Microsoft Exchange cmdlets from the SnapManager shell.

The default SnapManager PowerShell does not include the Microsoft Exchange ManagementShell snap-in. You will get an error if you run Microsoft Exchange cmdlets from theSnapManager shell. To run Microsoft Exchange cmdlets, use the Microsoft ExchangeManagement shell.

9

Known issues

Some unexpected and potentially undesired behaviors are known to affect functionality in thisrelease.

Known issues identified in this release

A new issue has been added to this version of the Release Notes.

Click the bug ID to view the latest status of the bug in Bugs Online, including a workaround, ifavailable. Bugs Online provides the most up-to-date information about a bug.

Bug ID Description

703616 "Database Filter" missing from Action pane in MMC GUI when SnapManager forMicrosoft Exchange is connected at DAG-level on Windows Server 2012.

Known issues identified in previous releases

Some issues listed in previous versions of the Release Notes are present in this release.

Bug ID Description and workaround

322235 Title: Mountpoint directories are not deleted if mounting of a Snapshot copy failsduring verification.

Description: If mounting of a Snapshot copy fails, SnapDrive does not delete themountpoint created.

Workaround: Manually delete all empty directories with the naming convention“MPDisk0nn” under SnapManager installation directory, normally at C:\ProgramFiles\NetApp\SnapManager for Exchange

\SnapMgrMountPoint.

323771 Title: The Configuration wizard does not show Storage Groups when ActiveDirectory (AD) group nesting is used.

Description: If the account to be used by SnapManager is only a member ofDomain local group and not assigned any exchange administrator roles andpermissions, SnapManager is unable to get exchange information. Accordingly, noinformation is displayed on the user interface.

Workaround: Get information that describes Exchange Server roles, permissions,and security groups from the Microsoft TechNet Web site.

10 | Release Notes

Bug ID Description and workaround

355496 Title: Make the SMEService port number configurable.

Description: Make the SMEService WCF port number configurable, in case ofsome application locks in the current default port number 810.

Workaround: To override the default port number 810, follow these steps:

1. Add the registry string (text) value and set it to a new port number:SOFTWARE\Network Appliance\SnapManager for Exchange\Server

\ServerPort

2. Replace the default port text value 810 with the new port value in the followingconfiguration files from the SnapManager installation directory:

• SnapMgrService.exe.config• SMEUISnapin.dll.config• SMEPSSnapin.dll.config

3. Restart SnapManagerService and the SnapManager for Exchange user interface(UI).

4. Make sure that the SnapManager UI can connect to SnapManagerService.

359071 Title: PowerShell deferred verification fails because requested registry access is notallowed.

Description: PowerShell deferred verification fails because requested registryaccess is not allowed.

Workaround: On a Windows Server 2008 system with User Access Controlenabled, use the menu option Run As Administrator to prevent any access errorsrelated to the Windows Registry or any other Windows server resources.

Known issues | 11

Bug ID Description and workaround

373964 Title: Event log failure “log copier was unable to communicate with server” mightoccur for successful DAG migration.

Description: The MSExchangeRepl service logs error events when you run theSnapManager Configuration wizard. The MSExchangeRepl service might log thefollowing error event when SnapManager migrates databases in a DAGconfiguration:The log copier was unable to communicate with server. The copy

of database 'f1\DTC4' is in a disconnected state. The

communication error was: An error occurred while attempting to

access remote resources. Error: Communication was terminated

by server. Data could not be read because the communication

channel was closed. The copier will automatically retry after

a short delay.

Workaround: None.

This is the expected behavior. When you run the SnapManager Configurationwizard, SnapManager removes database copies from the DAG, changes thedatabase paths, and adds database copies back to the DAG. During this process theMSExchangeRepl service will log error event logs.

Note: This problem is due to a Microsoft issue.

376362 Title: DAG level schedule backup does not provide “View Status” in the Currentjob status.

Description: When you select a server in the Scope pane, SnapManager displaysthe queued and running jobs for that server. The “View Status” element in theResults pane provides a link to the SnapManager report associated with the runningjob. However, when you connect to the DAG while a job is running and click“View Status,” you get an error.

Workaround: Go to the Reports directory and manually view the report files afterthe job is done, watch the job output while the job is running, select to see the last-job-run dashboard, and so on.

382115 Title: The SnapManager Configuration wizard at the DAG level fails if disk spaceis not sufficient to hold the migrated SnapInfo directory.

Workaround: Make sure there is enough disk space on all nodes during the DAGmigration.

12 | Release Notes

Bug ID Description and workaround

383873 Title: A Restore backup with the “Cancel conflicting backup that is in progress”option does not cancel scheduled backup jobs.

Description: When you run a restore operation with the option to cancel aconflicting backup that is in progress, the scheduled backup job is not cancelledautomatically. The “Cancel conflicting backup that is in progress” is an optionavailable through the “Verify Options” window of the Restore wizard.

Workaround: Cancel the conflicting backup job by using the SnapManager userinterface or the delete-backup cmdlet.

385259 Title: Microsoft hotfix is required for Hyper-V environments.

Description: Some problems may occur when you back up or restore Hyper-Vvirtual machines. If you run Exchange in a Hyper-V environment, and you useSnapManager to back up the Exchange, the application backup operation in thevirtual machine is affected by the virtual machine backup operation. This could leadto truncated logs and loss of data.

Workaround: Follow these steps:

1. Install Microsoft hotfix 975354.

2. Set the registry key for Volume Shadow Copy Service (VSS) to disable Hyper-V host backups.

3. Set the registry value to the following:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtualization

\VssRequestor]"BackupType"=dword:00000001

388864 Title: The DAG SnapManager reconnect operation might fail after a clusterfailover.

Description: After moving the active cluster node from one machine to the other,the SnapManager user interface might lose the active communication connectionwith the active SnapManager server.

Workaround: Restart the SnapManager user interface to reestablish theconnection.

Known issues | 13

Changes to published documentation

Some new information about SnapManager for Microsoft Exchange has become available since theSnapManager for Microsoft Exchange Installation and Administration Guide was published. Youshould use this new information in conjunction with that guide.

SnapManager service account requirementsWhen you install SnapManager, you specify the Windows account under which SnapManager willrun (the SnapManager service account). This account must meet specific requirements.

The SnapManager service account must meet the following requirements:

• The account must be a domain user.• The account must be a member of the local Administrators group of each Exchange server.• The account must be a member of the "Organization Management" group which is part of the

"Microsoft Exchange Security Groups" in Active Directory.• If you want to archive backups to a SnapVault backup (Data ONTAP operating in 7-Mode only),

the SnapManager service account must be one of the following:

• The same account that you setup SnapDrive to use with the DataFabric Manager server (youset this up using the sdcli dfm_config set command).

• A different account that is assigned a role on the DataFabric Manager server with thefollowing capabilities:

• DFM.DataBase.Read Global• DFM.DataSet.Write Global• DFM.Policy.Read Global• DFM.BackupManager.Backup Global• DFM.BackupManager.Read Global• DFM.BackupManager.Restore Global

You can use the dfm role create, dfm role add, and dfm user add commands tocreate the role, add the capabilities, and create the user.Alternatively, you can assign the SnapManager service account full control rights on theDataFabric Manager server. For example:

• Windows:

dfm user add -r GlobalFullControl MyDomain\snapuser

• UNIX:

14 | Release Notes

dfm user add -r GlobalFullControl MyDomain\\snapuser

This requirement is necessary because SnapDrive uses the SnapManager service account to editdatasets and request backups.

Restriction when setting UTM retention and backupretention

You should not specify different types of values (number of days and number of copies) for UTMretention and backup retention. For example, you should not specify the number of days to retainbackup copies and the number of copies to retain. You should instead do one or the other.

FlexClone license requirementsThe SnapManager for Microsoft Exchange Installation and Administration Guide notes that aFlexClone license is required if you plan to use the integrity verification feature. It should state that aFlexClone license is not required if planning to use the feature for any database; however, it is onlyrequired when restoring to the recovery database.

Note: This requirement is associated with SnapDrive's FlexClone license requirement forpersistent mount operations.

DAG requirementsA DNS service entry must exist for the name of a Database Availability Group (DAG) and ActiveDirectory/DNS needs to grant permissions to write the entry. Make sure the DNS service is active onthe Windows domain with the Exchange Server DAG. If the entry has not been created, theadministrator must create it manually.

Protection Manager referenceIn the SnapManager for Microsoft Exchange Installation and Administration Guide, "ProtectionManager" should be replaced with "OnCommand Unified Manager Core Package 5.2 or later, whichincludes the NetApp Management Console".

After the initial full reference described above, "OnCommand Unified Manager Core Package" canbe used.

Changes to published documentation | 15

Certification for Windows Server Logo

NetApp certifies the SnapManager 7.0 for Exchange Microsoft Installer (MSI) package but not theMicrosoft .NET assemblies in it intentionally. This is done to avoid the known issue of the .NETframework loading signed assemblies on systems that are not connected to the Internet. For moreinformation, see http://support.microsoft.com.

16 | Release Notes

SnapManager custom actions

You can use custom actions in SnapManager for Microsoft Exchange to perform various functions.

The following table lists and describes custom actions implemented in the SnapManager 7.0 forMicrosoft Exchange MSI package:

Custom action Description

AbortInstallation Generates a popup error message and aborts installation.

AbortInstallation_0 Generates a popup error message and aborts installation.

AbortInstallation_1 Generates a popup error message and aborts installation.

AbortInstallation_2 Generates a popup error message and aborts installation.

AbortInstallation_3 Generates a popup error message and aborts installation.

CA_GetMissingSWList Gets a list of missing software that needs to be installed anddisplays a dialog with the list if not running silently.

CA_RefreshStartMenuIcons Sets and broadcasts SnapDrive for Windows environmentvariables.

CA_SetSWNeeded Sets flags for missing software.

CheckInstalledProductVersion Checks the installed product version to set the default FSRmonitoring registry value.

CheckMMC30 Checks the existence of the filemicrosoft.managementconsole.dll. If this file doesnot exist, aborts the installation.

CheckNetFrameworkVersion Checks if .Net Framework 4.0 is installed. If not, aborts theinstallation.

CheckPowerShellVersion Checks if Microsoft PowerShell 3.0 is installed. If not,aborts the installation.

ClusterRegRestore Restores Cluster Registry Keys from the temporary file.

ClusterRegSave Saves Cluster Registry Keys into a temporary file.

CreateJobManagementRegistryValue

Creates the registry key and value required by jobmanagement.

CreateSMDebugFolder Creates a subfolder for a debug trace.

Custom_Action1 Debugs

17

Custom action Description

DCOMPerm Sets the DCOM permissions.

DeleteLegacyFile Deletes the files from older versions of the product but thatwere removed in this version and also deletes some .Nettracing files.

DeleteOldShortcut Deletes the shortcut to the old version of the product,because the company name was added in the path.

DeleteRegKey Deletes the legacy SnapManager registry key.

EventLogLicenseType Reports the license type to event log - Not used.

fix_AllUsers Resets ALLUSERS to NULL.

GetLicenseKey Gets the SnapManager per-server license key from theregistry.

GetSMEUserIdentity Gets the user name and password set by SnapManager asRunAs user.

GetSVCUserName Gets a SnapDrive service account.

IsInstallationRunning Checks if another SnapManager for Exchange installationinstance is running. If so, aborts the installation.

IsSMESrvrRunning Checks if the SnapManager server is still running. If so,aborts the installation.

LicenseAgreementMsg Displays the license agreement in a message box during anunattended install.

LicenseValidate Validates the license key entered by the user.

NetTcpPortSharingServiceEnable Enables the NetTcpPortSharing service if it is disabled.

NetTcpPortSharingServiceStart Starts the NetTcpPortSharing service.

NetTcpPortSharingStartTypeWarning

Displays a warning message about changing the start type ofNetTcpPortSharing service.

OldProductFound Displays a warning message if an old version ofSnapManager was installed.

OldVLDMgrFound Sets a warning message if an old version of SnapDrive wasinstalled.

RemoveReportFolder Removes the report folder and the subfolder inside.

RemoveReportFolderShare Removes the NetShare created in the report folder.

18 | Release Notes

Custom action Description

RemoveReportFolderWarning Displays a warning when the option to remove a reportfolder is clicked in the user interface.

RemoveReportFolderWarning Deletes the SnapManager installation directory if it isempty.

RemoveSnapManagerFolder Removes the SnapManager installation folder.

RemoveSnapManagerSubFolders Removes the FractSpaceData, Debug, andSnapMgrMountPoint folders created by SnapManager.

SelectSvcUser Not used.

SetATTENDEDFLAG Sets the ATTENDEDFLAG property to indicate UI install.

SetFileVersionInReg Sets the file version in the registry.

SetNoReboot Sets REBOOT to ReallySuppress.

SetRemoveFlag Sets ISREMOVED to 1.

SetSMUserIdentity Sets SnapManager DCOM server identity.

SetStringToProperty Gets a string from the String table and sets it to the publicproperty.

SetUseCheckSgFilesVerify Checks if the ChksgFiles.dll file exists. If so, sets theregistry UseCheckSgFilesVerify to 1.

SetVersionInMMCSnapIns Sets the version number and build timestamp inSMEUISnapin and SMEBCSnapin.

SMESrvrpsRegister Registers SMESrvrps.dll.

SMESrvrpsUnRegister Unregisters the SnapManager COM server proxy.

SMESrvrRegister Registers the SnapManager COM server.

SMESrvrUnRegister Unregisters the SnapManager COM server.

SnapDriveNotInstalled Sets the property to indicate that SnapDrive is not installed.

SnapManagerConfigFileModify Replaces #HostName# withSnapMgrService.exe.config.

SnapManagerServiceAccountChange Updates the SnapManagerService account with the specifieduser credentials.

SnapManagerServiceAddDependency

Sets the SnapManagerService dependency onNetTcpPortSharing.

SnapManagerServiceInstall Installs SnapManagerService using intallutil.exe.

SnapManager custom actions | 19

Custom action Description

SnapManagerServiceRemove Removes the SnapManagerService by using InstallscriptAPI ServiceRemoveService().

SnapManagerServiceStart Starts the SnapManagerService by using the "net startSnapManagerService" command.

SnapManagerServiceStop Stops the SnapMgrService by using the install script APIServiceStopService().

SnapManagerServiceUninstall Uninstalls the SnapManagerService usingintallutil.exe.

SnapMgrServicePSRegister Registers SnapMgrServicePS.dll.

SnapMgrServicePSUnRegister Unregisters SnapMgrServicePS.dll.

SnapMgrServiceRemove Removes the old SnapMgrService service that has beenrenamed "SnapManagerService.”

SnapMgrServiceStop Stops the old SnapMgrService by using the install scriptAPI ServiceStopService().

SVCValidateAccountInfo Validates the credentials entered by the user.

SyntaxError Results in a fatal error if there is a syntax error at thecommand line.

UnRegisterClusterKey Unregisters the cluster keys.

WaitForSnapManagerProcess Waits for SnapManagerService process stops

DLLWrapCleanup InstallShield custom action.

DLLWrapStartup InstallShield custom action.

ISSetAllUsers InstallShield custom action.

ISSetupFilesCleanup InstallShield custom action.

ISSetupFilesExtract InstallShield custom action.

SxsInstallCA InstallShield custom action.

SxsUninstallCA InstallShield custom action.

20 | Release Notes

Copyright information

Copyright © 1994–2013 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 anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED 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 notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

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 torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

21

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Cryptainer, CryptoShred, CyberSnap, Data Center Fitness, DataONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack,ExpressPod, FAServer, FastStak, FilerView, Flash Accel, 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, Mars,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, Snap Creator, SnapDirector, SnapDrive, SnapFilter,SnapIntegrator, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect,SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, theStoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, VelocityStak, vFiler,VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or registeredtrademarks of NetApp, Inc. in the United States, other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United Statesand/or other countries. Microsoft is a registered trademark and Windows Media is a trademark ofMicrosoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or othercountries.

All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.

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

NetApp, Inc. NetCache is certified RealSystem compatible.

22 | Release Notes

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us to provide the most accurate and high-quality information.If you have suggestions for improving this document, send us your comments by email to doccomments@netapp.com. To help us direct your comments to the correct division, include in thesubject line the product name, version, and operating system.

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

23