OpsManager rnote

Release NotesFor Use with DataFabric® Manager Server 4.0,Supporting Operations Manager, Provisioning Manager, and Protection Manager

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 USATelephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPPDocumentation comments: [email protected] Web: http://www.netapp.com

Part number: 215-05109_A0February 2010

Contents

Copyright information ................................................................................. 7Trademark information ............................................................................... 9Release notes ................................................................................................ 11Known issues with Data ONTAP .............................................................. 13

Snapshot query fails in a scaled cluster setup ............................................................ 13

Issue with determining the storage capacity of the default volume ........................... 13

SNMP timed out error message ................................................................................. 14

Data ONTAP is unable to perform SnapVault activities on a secondary storage

system .................................................................................................................. 14

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts Operations

Manager ............................................................................................................... 15

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts Provisioning

Manager ............................................................................................................... 15

hosts.equiv and httpd.admin.access fail with IPv6 .................................................... 15

System panics due to deleted vFiler user groups ....................................................... 16

New and changed features ......................................................................... 17Known issues with DataFabric Manager ................................................. 21

Known issues with installation and upgrade ............................................................. 21

Delay in upgrading from DataFabric Manager server 3.2 or earlier ............. 21

Delay in upgrading from DataFabric Manager 3.5 or earlier ........................ 22

The dfm report view command fails .............................................................. 22

Cluster group in VCS setup fails ................................................................... 22

Cluster setup scripts in Windows 2008 fail ................................................... 23

Upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 on

Windows Server 2008 might fail ............................................................. 23

Known issues with Operations Manager ................................................................... 23

Slow response time for Performance Summary reports in a scaled setup ..... 24

Striped aggregates are not displayed in the Aggregate custom report ........... 24

Volume backup fails from the Operations Manager UI ................................ 25

Slow response time in displaying the Group status in a scaled setup ............ 25

Source aggregate is detached from the DataFabric Manager resource

group ........................................................................................................ 25

Table of Contents | 3

Setting the clock backwards causes the DataFabric Manager server to

perform a core dump ................................................................................ 26

DSN is not created on Windows .................................................................... 26

Restoration of the DataFabric Manager database fails in DataFabric

Manager 3.8 or later ................................................................................. 26

IPv6 source address is incorrectly displayed in the trap receiver .................. 27

IPv4-mapped IPv6 addresses are not supported ............................................ 27

Inconsistent capacity graphs .......................................................................... 27

rsh commands fail on Windows Server 2008 ................................................ 27

Some DataFabric Manager CLI commands fail on Windows Server

2008 .......................................................................................................... 28

IPv6 link-local address is not supported ........................................................ 28

DataFabric Manager database stops responding on a VMware server .......... 29

Incorrect interface reporting during failover ................................................. 29

Unusable database on the DataFabric Manager server .................................. 29

Delayed display of Snapshot-based backup list ............................................ 30

Issue with Snapshot-based backups on Linux ............................................... 30

Inconsistent display of disk names for failed-over nodes .............................. 30

Limitations of LUN management .................................................................. 30

Known issues with Performance Advisor ................................................................. 31

Delayed CLI response to the dfm perf clientstat collect command ............... 32

Delayed UI response on the Set Up Hosts window ....................................... 32

Delayed UI response in advanced views ....................................................... 32



Data ONTAP panic during Performance Advisor data collection ................. 33

Data ONTAP global disable counter group option ....................................... 33

Alarm scripts fail ........................................................................................... 33

Performance view options are not supported ................................................ 33

Import and export in XML format are not supported .................................... 34

Unique view names ....................................................................................... 34

Alarm wizard lists all event names ................................................................ 34

Performance Advisor windows and panes are not refreshed ......................... 34

Data collection cannot be enabled ................................................................. 34

Known issues with Protection Manager .................................................................... 35

4 | Release Notes For Use with DataFabric® Manager Server 4.0

Job Failure protection status is displayed for a dataset after an external

relationship is imported ............................................................................ 36

Restored files are overwritten ........................................................................ 36



The compression option for SnapMirror connections is not preserved ......... 36

Cluster-Mode objects are not supported ........................................................ 37

Cannot import some external relationships from a qtree on the same

source volume .......................................................................................... 37

Stale SnapMirror relationships might be left after an NDMP migration ...... 37

Open Systems SnapVault relationship baseline is not registered as a

backup version ......................................................................................... 37

Incorrect dataset conformance status is displayed when the protection

status is "Baseline Failure" ...................................................................... 38

Operations Manager and Protection Manager display different qtree and

volume counts .......................................................................................... 38

Relationship create jobs fail to register baseline version on destination

storage systems running Data ONTAP 7.2.3 or earlier ........................... 38

Resizing of disaster recovery volumes for conformance after failover ......... 39

Restoration to conformance dataset members with deleted baseline

Snapshot copies ........................................................................................ 39

Support for Windows path names containing non-ASCII characters ............ 41

Spare disk capacities are not counted as "available size" for a resource

pool .......................................................................................................... 41

Aggregate "Nearly full" and "Full" threshold settings are not used to

determine whether an aggregate should be excluded as a resource in

a dataset .................................................................................................... 41

Dynamic volume resizing must be disabled to support deduplication plus

"Mirror, then back up" protection policy ................................................. 41

No data protection transfer reports when an OSSV primary directory

name contains spaces ............................................................................... 42

Known issues and limitations with Provisioning Manager ....................................... 42

Some dataset migration details are not displayed after migration cutover .... 43



vFiler unit migration cutover fails when source volumes are full ................. 44

Table of Contents | 5

The migration feature allows you to start unnecessary duplicate cleanup

and cancel jobs ......................................................................................... 44

Changing the IPspace of a vFiler unit causes migration cutover to fail ........ 44

Volume-based SnapRestore during migration cutover causes failure ........... 45

Migration rollback fails if the migrated source volume contained no

Snapshot copies ........................................................................................ 45

Newly added quotas are not migrated during rollback and subsequent

cutover or rollbacks .................................................................................. 45

The vFiler unit on the destination storage system is destroyed when

cutover fails in the reincarnate phase ....................................................... 46

Cutover operation fails to stop any active CIFS session on a vFiler unit ...... 46

Long-running operations not associated with the migration fail during

the cutover phase ...................................................................................... 46

Data ONTAP 8.0 7-Mode does not support rollback operation .................... 46

Backup initiated during cutover operation might fail .................................... 46

Online migration fails between a FAS system and an IBM N series

storage system .......................................................................................... 47

Cannot clone volumes in a migrated vFiler unit ............................................ 47

Data access to a migrated vFiler unit is blocked ........................................... 47

Qtree details do not appear after DR failover ................................................ 47

Management Console can set but not modify the vFiler unit root

password .................................................................................................. 48

Changes to published documentation ....................................................... 49Where to find product documentation and other information .............. 51


Copyright information

Copyright © 1994–2010 NetApp, Inc. All rights reserved. Printed in the U.S.A.

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.A. patents, foreignpatents, 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).

Copyright information | 7

Trademark information

NetApp; the NetApp logo; the Network Appliance logo; Cryptainer; Cryptoshred; DataFabric; DataONTAP; Decru; Decru DataFort; FAServer; FilerView; FlexCache; FlexClone; FlexShare; FlexVol;FPolicy; gFiler; Go further, faster; Manage ONTAP; MultiStore; NearStore; NetCache; NOW(NetApp on the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; Simulate ONTAP;SnapCopy; SnapDrive; SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore;SnapValidator; SnapVault; Spinnaker Networks; Spinnaker Networks logo; SpinAccess;SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove; SpinServer; SpinStor; StoreVault; SyncMirror;Topio; vFiler; VFM; and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or othercountries. Network Appliance, Snapshot, and The evolution of storage are trademarks of NetApp,Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. TheStoreVault logo, ApplianceWatch, ApplianceWatch PRO, ASUP, AutoSupport, ComplianceClock,DataFort, Data Motion, FlexScale, FlexSuite, Lifetime Key Management, LockVault, NOW,MetroCluster, OpenKey, ReplicatorX, SecureAdmin, Shadow Tape, SnapDirector, SnapFilter,SnapMigrator, SnapSuite, Tech OnTap, Virtual File Manager, VPolicy, and Web Filer aretrademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful and Select are servicemarks of NetApp, Inc. in the U.S.A.

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 http://www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/orother countries. Microsoft is a registered trademark and Windows Media is a trademark of MicrosoftCorporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, andSureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.

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.

Trademark information | 9

Release notes

These release notes provide information about the new and changed features, and known issues inDataFabric Manager 4.0.

You can find detailed information about feature enhancements, new and changed CLI commands,and new events in the What is new section in the administration guide of each product.

The following information is present in the Installation and Upgrade Guide:

• Supported platforms• Supported applications• Limitations• License requirements• Instructions for installing and upgrading the software

Release notes | 11

Known issues with Data ONTAP

Some unexpected and potentially undesired behaviors in Data ONTAP are known to affectfunctionality in this release of the DataFabric Manager server.

For more details, enter the bug ID on the Bugs Online & Release Tools page.

Next topics

Snapshot query fails in a scaled cluster setup on page 13

Issue with determining the storage capacity of the default volume on page 13

SNMP timed out error message on page 14

Data ONTAP is unable to perform SnapVault activities on a secondary storagesystem on page 14

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts Operations Manager on page 15

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts ProvisioningManager on page 15

hosts.equiv and httpd.admin.access fail with IPv6 on page 15

System panics due to deleted vFiler user groups on page 16

Related information

Bugs Online - now.netapp.com/NOW/cgi-bin/bol

Snapshot query fails in a scaled cluster setup

Snapshot query fails in a scaled cluster setup with a high number of cluster objects, such as volumesand aggregates. Therefore, you cannot monitor the Snapshot copies of such clusters by usingOperations Manager.

Workaround

None.

Issue with determining the storage capacity of the defaultvolume

The SNMP response for volTable does not list the root volume vol0 belonging to the nodes of acluster. Therefore, the default volumes of these nodes are not reported in the SNMP response. Youcannot discover these default volumes or generate reports to determine their storage capacity by

Known issues with Data ONTAP | 13

http://now.netapp.com/NOW/cgi-bin/bol

using Operations Manager. Since there is no visibility to the root volume, you cannot generatereports using Operations Manager to determine the storage capacity of these volumes.

Workaround

None.

SNMP timed out error messageWhen multiple DataFabric Manager servers monitor a single cluster, it results in an SNMP timed outerror message.

Workaround

Use only one DataFabric Manager server for monitoring a cluster at a time.

Data ONTAP is unable to perform SnapVault activities on asecondary storage system

When you use SnapVault or Open Systems SnapVault with Protection Manager with DataFabricManager server 3.8 on a Data ONTAP 7.3.1 storage system, the storage system might run out ofresources (NDMP threads).

This occurs because Protection Manager uses a new API for data transfer. Normal data protectionactivities are possible until the NDMP thread count in Data ONTAP is exceeded. The number ofthreads available is platform dependent and the threads cannot be recovered after they have beenconsumed. Normal activity continues in Data ONTAP, but additional NDMP transfers are blockedafter the maximum thread count is reached.

Note: After Data ONTAP reaches the NDMP thread limit, additional NDMP requests are notserviced, whether they are for SnapVault, SnapMirror, or other activities. This issue does notaffect tasks initiated from the Backup Manager or Disaster Recovery Manager tabs in OperationsManager.

For more information, enter the bug ID 354933 on the Bugs Online & Release Tools page.

Workaround

None. The only recovery solution is to reboot the storage system or upgrade to a version of DataONTAP that contains a fix for bug 354933.


Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impactsOperations Manager

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts the vFiler quota monitoring, andLUN monitoring for storage systems and vFiler units (vFiler igroup, vFiler LUN, storage systemLUN, vFiler iSCSI initiator) in Operations Manager.

In addition, it impacts the following functions in Operations Manager:

• dfm run command• RLM commands• Password management• Host RBAC management• vFiler quota management• Cluster Console

Workaround

Use SSH.

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impactsProvisioning Manager

Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts the following in ProvisioningManager: (a) CIFS setup of a vFiler unit; and (b) NFS exports of storage owned by a vFiler unit.

Workaround

Use SSH.

hosts.equiv and httpd.admin.access fail with IPv6The hosts.equiv authentication does not support IPv6 addresses. APIs over HTTPS do not work forIPv6 addresses in Data ONTAP 7.3.1 when the httpd.admin.access option on a storage system isset to a value other than legacy.

Known issues with Data ONTAP | 15

System panics due to deleted vFiler user groupsYou must avoid deleting user groups on vFiler units running Data ONTAP 7.0 and 7.1. Deleting usergroups can cause the storage system to panic or reboot.

For more information, enter the bug ID 176163 on the Bugs Online & Release Tools page.


New and changed features

DataFabric Manager 4.0 contains several new features and enhancements. This release supportsVMware VMotion and VMware High Availability features.

Operations Manager features

This section describes new features and changes in Operations Manager in DataFabric Managerserver 4.0. Detailed information about the features, including lists of new or changed CLI commandsand events, is contained in the Operations Manager Administration Guide.

The new features in Operations Manager include the following:

• Discovery, monitoring, and reporting of Data ONTAP 8.0 Cluster-Mode systems• Monitoring and reporting of SAN-attached storage of V-Series systems• Support for larger aggregates with a maximum size for 64-bit aggregates• Support for the Web services features and the DataFabric Manager APIs

The changes in Operations Manager include the following:

• A link to My AutoSupport (a Web-based self-service support application)• Usability improvements to the graphical user interface

NetApp Management Console changes

This section describes new features and changes in NetApp Management Console for use withDataFabric Manager server 4.0. For detailed information about the features, see the NetAppManagement Console Help.

The changes in NetApp Management Console include the following:

• Custom fieldsYou can add and configure user-defined custom fields for datasets, protection policies, andprovisioning policies. You can use these fields to enter custom information, such as cost center orchargeback codes.

• Multiple selection filteringWhen filtering data that is displayed in a column, you can select multiple values from a columndrop-down list.

Provisioning Manager features

This section describes new features and changes in Provisioning Manager for use with DataFabricManager server 4.0. For detailed information about tasks and concepts related to the features, see theNetApp Management Console Help. For additional information about new and updated features,changes to the graphical user interface, lists of new and changed CLI commands, and product

New and changed features | 17

limitations, see “What is new in this release” in the Provisioning Manager and Protection ManagerGuide to Common Workflows for Administrators.

The new features in Provisioning Manager include the following:

• Secondary storage space managementFor more details, see the "Protection Manager features" section.

• Automated online migration for datasets and vFiler unitsYou can migrate your data from one storage system to another without disrupting access to thatdata by the users or applications. You do so by enabling online migration (a component of theNetApp Data Motion solution). In addition to migration without disruption of data availability,online migration also enables automatic cutover and migration rollback.

• Storage servicesYou can preconfigure one or more combinations of protection, provisioning, resource pool, andvFiler template configurations into standard storage service packages that can readily be assignedto datasets requiring those specific storage services. Your storage service packages listed togethercan constitute a technical service catalog as described by the Information TechnologyInfrastructure Library, version 3 (ITIL V3).

• Support for larger aggregatesYou can now use Provisioning Manager to manage large (64-bit) aggregates in Data ONTAP 8.0(7-Mode only) or later. In addition, you can provision large volumes (volumes greater than 16TB) in Data ONTAP 8.0 (7-Mode only) or later.

The changes in Provisioning Manager include the following:

• Usability improvements to the graphical user interface

Protection Manager features

This section describes new features and changes in Protection Manager for use with DataFabricManager server 4.0. For detailed information about tasks and concepts related to the features, see theNetApp Management Console Help. For additional information about new and updated features,changes to the graphical user interface, lists of new and changed CLI commands, and productlimitations, see “What is new in this release” in the Provisioning Manager and Protection ManagerGuide to Common Workflows for Administrators.

The new features in Protection Manager include the following:

• Secondary storage space managementWhen the licensed protection application or provisioning application displays an aggregate spaceproblem, you can use the Secondary Space Management feature to plan and implement tasks toresolve it. You can use the secondary space management feature to do the following:

• View detailed information about the space status of your aggregates and about the space statusof the volumes and datasets in those aggregates

• View space management jobs that are associated with an aggregate• Plan and implement migration of volumes on secondary storage


• Plan and implement tasks for deleting backups and Snapshot copies (primary, secondary, andtertiary storage), increasing or decreasing the volume size (primary, secondary, and tertiarystorage), and performing volume deduplication (primary storage only)

• View the estimated space that will be reclaimed on an aggregate as a result of performing thetasks that you plan

• Support for bidirectional SnapVault backupsProtection Manager supports SnapVault Primary and SnapVault Secondary licenses on the samestorage system. This allows you to perform SnapVault host-to-host backups of primary andsecondary dataset nodes within the same storage system.

Note: Backups of volumes within the same aggregate are not supported. However, backups ofaggregates within the same storage system are supported.

You cannot use a vFiler unit as the secondary dataset node.• Support for larger aggregates

You can use Protection Manager to manage large (64-bit) aggregates in Data ONTAP 8.0 (7-Mode only) or later.

• LicensingWhen you install the Protection Manager license, the provisioning functions provided byProvisioning Manager are also enabled.

The changes in Protection Manager include the following:

• Unprotected dataThe definition of unprotected data is changed. External relationships are no longer counted asunprotected data.

• AutoSupportAdditional protection information is sent to AutoSupport if you have Protection Managerenabled.

• Protection status error messagesBecause error messages related to protection status now provide more information, you cantroubleshoot protection problems more easily.


Performance Advisor features

This section describes new features and changes in Performance Advisor for use with DataFabricManager server 4.0. For detailed information about tasks and concepts related to the features, see theNetApp Management Console Help. For additional information about new and updated features,changes to the graphical user interface, lists of new and changed CLI commands, and productlimitations, see “What is new in this release” in the Performance Advisor Administration Guide.

The new features in Performance Advisor include the following:

• Data collection configurationYou can view the counters for which data collection is enabled or disabled on a per storagesystem basis. The following are the other advantages that are available with this feature:

New and changed features | 19

• Disable and enable data collection for selected counters per storage system• Configure sample rate and retention period for selected counter groups per storage system• Copy the data collection configuration to other storage systems

• Advanced viewsYou can use advanced views to establish a baseline for the data collected by applying statisticalparameters such as minimum, maximum, mean, and percentile. Time filters enable you to retrievethe baseline data based on selected business hours and week days. You can use the baseline datain advanced views to set appropriate thresholds.

• Data exportThis feature helps you to export the Performance Advisor data collected on the DataFabricManager server. The data is collected in CMA format. However, you should use this feature onlywhen NetApp requests the data from you.

• Performance diagnosisYou can diagnose the storage system for any performance-related issue during the given periodand get recommendations to resolve the issue. The event correlation chart allows you to plotevents of related objects. Also, the chart plots the Operations Manager events, which can help youdiagnose the cause of a performance degradation.

• Client statisticsYou can collect the statistics related to CIFS and NFS client operations to find the cause oflatency. Also, you can use this feature to automatically collect per-client statistics when a set ofthresholds on a storage system is breached.

The changes in Performance Advisor include the following:

• Flexible custom viewsYou can apply custom views on either a particular object or every instance of the selected object.The following are the other advantages that are available with this feature:

• Make copies of canned views and modify them• Display data for historical periods in custom views• Compare the data collected for a counter on multiple instances of an object• Configure bar chart preferences such as the number of objects and the kind of chart



Known issues with DataFabric Manager

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds toavoid these behaviors, are identified in this release of the DataFabric Manager server.

For more details, enter the bug ID on the Bugs Online & Release Tools page.

Next topics

Known issues with installation and upgrade on page 21

Known issues with Operations Manager on page 23

Known issues with Performance Advisor on page 31

Known issues with Protection Manager on page 35

Known issues and limitations with Provisioning Manager on page 42

Related information


Known issues with installation and upgradeSome unexpected and potentially undesired behaviors, as well as, in some cases, workarounds toavoid these behaviors, are identified while installing or upgrading to this release of the DataFabricManager server.

Next topics

Delay in upgrading from DataFabric Manager server 3.2 or earlier on page 21

Delay in upgrading from DataFabric Manager 3.5 or earlier on page 22

The dfm report view command fails on page 22

Cluster group in VCS setup fails on page 22

Cluster setup scripts in Windows 2008 fail on page 23

Upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 on Windows Server 2008 mightfail on page 23

Delay in upgrading from DataFabric Manager server 3.2 or earlierDue to database schema changes, you might experience several minutes to a few hours of delay whenupgrading to DataFabric Manager 3.3 or later from an earlier release.

The time required to perform the upgrade depends on the size of the database, the amount of historyin the database, the CPU speed, and I/O throughput of the system. The upgrade process might take 30to 50 minutes for large databases.

The following tasks require the most time:

Known issues with DataFabric Manager | 21


• Merging rotating history tables• Populating history tables• Populating volume history tables• Populating aggregate history tables• Reloading the database into the most recent file format (at the end of the database upgrade)

Workaround

None.

Delay in upgrading from DataFabric Manager 3.5 or earlierIf you are upgrading from DataFabric Manager 3.5 or earlier to DataFabric Manager 3.6 or later, thetime taken to upgrade the performance data files (data of 20 GB or more) is long. The length of timeis dependent on the platform used.

The space used by the performance data files increases by about 65% during the upgrade.

Workaround

None.

The dfm report view command failsIf you have created custom reports with GUILink and SecureGUILink as fields in DataFabricManager 3.7.1 or earlier, upgrading to DataFabric Manager 3.8 causes the dfm report viewcommand to fail.

Workaround

Edit the custom reports in Operations Manager by removing the fields, and save the reports beforeyou can view them.

Cluster group in VCS setup failsIn a Veritas Cluster Server (VCS) setup, if you are upgrading the cluster nodes from DataFabricManager 3.7.1 or earlier, then the cluster group fails.

Workaround

In the VCS Cluster Explorer window, click the Properties tab for dfm-dbserver, and then change theMonitorProcess value dbsrv9 to dbsrv10 in the following entry:

install-dir/sbin/dbsrv9 @install-dir/conf/sybase.conf

Alternatively, you can use the following command to change the value:

/opt/VRTSvcs/bin/hares -modify dfm-dbserver MonitorProcesses "install-dir/

sbin/dbsrv10 @install-dir/conf/sybase.conf"


Cluster setup scripts in Windows 2008 failDataFabric Manager cluster setup scripts fail to run on a 64-bit Windows 2008 server using 32-bitActivePerl.

Workaround

Install 64-bit ActivePerl.

Upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 onWindows Server 2008 might fail

When you upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 on Windows Server2008, the upgrade might fail.

Workaround

Complete the following steps to install DataFabric Manager 4.0.

1. Stop all the DataFabric Manager services by using the dfm service stop command.

2. Install DataFabric Manager 4.0 on Windows 2008.

Note: You need not uninstall DataFabric Manager 3.8 to upgrade to DataFabric Manager 4.0 usingthe above-mentioned procedure.

Known issues with Operations ManagerSome unexpected and potentially undesired behaviors, as well as, in some cases, workarounds toavoid these behaviors, are identified in Operations Manager for use with this release of theDataFabric Manager server.

Next topics

Slow response time for Performance Summary reports in a scaled setup on page 24

Striped aggregates are not displayed in the Aggregate custom report on page 24

Volume backup fails from the Operations Manager UI on page 25

Slow response time in displaying the Group status in a scaled setup on page 25

Source aggregate is detached from the DataFabric Manager resource group on page 25

Setting the clock backwards causes the DataFabric Manager server to perform a coredump on page 26

DSN is not created on Windows on page 26

Restoration of the DataFabric Manager database fails in DataFabric Manager 3.8 orlater on page 26

IPv6 source address is incorrectly displayed in the trap receiver on page 27


IPv4-mapped IPv6 addresses are not supported on page 27

Inconsistent capacity graphs on page 27

rsh commands fail on Windows Server 2008 on page 27

Some DataFabric Manager CLI commands fail on Windows Server 2008 on page 28

IPv6 link-local address is not supported on page 28

DataFabric Manager database stops responding on a VMware server on page 29

Incorrect interface reporting during failover on page 29

Unusable database on the DataFabric Manager server on page 29

Delayed display of Snapshot-based backup list on page 30

Issue with Snapshot-based backups on Linux on page 30

Inconsistent display of disk names for failed-over nodes on page 30

Limitations of LUN management on page 30

Slow response time for Performance Summary reports in a scaled setupIn a scaled setup with a large number of monitored objects, you might not be able to view thePerformance Summary reports through the Web UI.

Workaround

Run the dfm report view report_name-performance-summary command from theDataFabric Manager CLI to view the Performance Summary reports. However, the response time toview these reports through CLI might be more than 20 minutes, depending on the number of objectsthat are monitored.

For more information about bug 279167, see Bugs Online.

Related information


Striped aggregates are not displayed in the Aggregate custom reportWhen you create a custom report with Aggregate and Appliance as the base catalog in DataFabricManager 3.8.1 or earlier, and then you upgrade to DataFabric Manager 4.0 with all the aggregates inthe Data ONTAP 8.0 cluster discovered, the striped aggregates for Data ONTAP 8.0 cluster are notdisplayed in the custom report.

Workaround

After you upgrade to DataFabric Manager 4.0, create another custom report with Aggregate as thebase catalog.



Volume backup fails from the Operations Manager UIWhen you have a storage system that has both the SnapVault primary (sv_ontap_pri) and secondarylicenses (sv_ontap_sec) enabled, you cannot create volume backups using the Operations ManagerUI (Backup > Summary > Add a new backup).

Workaround

To create volume backups, run the following command from the DataFabric Manager CLI:

dfbm primary dir add [ options ] secondary-host:/volume primary-host:/

path...

You can view the job log to track the creation of the relationship. After the relationship is created,you can perform backup-related tasks such as restore from the Operations Manager UI.

Slow response time in displaying the Group status in a scaled setupThe Operations Manager takes some time to display the Group status in a scaled setup. It might takeapproximately around 5 to 15 seconds for the respective icons (status) of the groups to load.

Workaround

None.

Source aggregate is detached from the DataFabric Manager resource groupIn Data ONTAP 8.0 Cluster-Mode systems, when a volume is moved from its source aggregate toanother aggregate, the source aggregate loses its resource group membership in DataFabric Managermonitoring the cluster. However, all the volumes of the aggregate maintain their group memberships.

DataFabric Manager automatically resolves the memberships within of 24 hours.

Workaround

To resolve the issue immediately, run the dfm dbcache verify command from the DataFabricManager CLI whenever the group membership is broken.

For more information about bug 393303, see Bugs Online.

Related information

Bugs online - http://now.netapp.com/NOW/cgi-bin/bol


HTTP://NOW.NETAPP.COM/NOW/CGI-BIN/BOL

Setting the clock backwards causes the DataFabric Manager server toperform a core dump

If you set the clock backwards while any DataFabric Manager services are running, the DataFabricManager server performs a core dump.

Workaround

Shut down the DataFabric Manager server and NetApp Management Console before setting the clockbackwards.

DSN is not created on WindowsOn the 64-bit versions of Windows Server 2003 and Windows Server 2008 servers, the default OpenDatabase Connectivity (ODBC) application does not list the System Data Source Names (DSNs) anddrivers related to DataFabric Manager.

Workaround

Use the ODBC Data Source Administrator application (odbcad32.exe) located at C:\WINDOWS\SysWOW64 to list the drivers and the DSNs.

Restoration of the DataFabric Manager database fails in DataFabricManager 3.8 or later

You cannot directly restore the following backup types: (a) Snapshot-based backups created inDataFabric Manager 3.7.1 or earlier; (b) Archive-based backups created in DataFabric Manager 3.4.1or earlier; (c) Archive-based backups created from Snapshot-based backups using the dfm backupexport command in DataFabric Manager 3.7.1 or earlier.

Any attempt to restore such backups fails and displays the following error message:**** SQL error: Unable to start specified database: autostarting databasefailed

Workaround

You can restore each of these types using the version of DataFabric Manager in which the backupswere created (or later), and then upgrade to DataFabric Manager 3.8 or later after that restoration.

For example, if you want to restore a backup created in DataFabric Manager 3.4.1 on DataFabricManager 3.8 or later, you must first restore that backup in DataFabric Manager 3.4.1 or later(excluding DataFabric Manager 3.8 or later), and then upgrade to DataFabric Manager 3.8 or later.

If you are upgrading to DataFabric Manager 3.8 or later, you must back up the database immediatelyfollowing the upgrade.


IPv6 source address is incorrectly displayed in the trap receiverWhen the DataFabric Manager server generates traps and sends it to an IPv6 destination host, theIPv6 source address is incorrectly displayed as 0.0.0.0 in the trap receiver.

This is a limitation of the DataFabric Manager server when it uses SNMPv1 to generate traps.

Workaround

None.

IPv4-mapped IPv6 addresses are not supportedDataFabric Manager does not support IPv4-mapped IPv6 addresses such as ::ffff:10.72.184.251.

Workaround

None.

Inconsistent capacity graphsCapacity graphs such as Volume Capacity Used vs Total on the Group Summary page (ControlCenter > Home > Group Status > Summary) do not show a drop in reported capacity when astorage system is down.

You can observe the drop only when the system is down for a long period and the period coincideswith the start time of the graph.

Workaround

None.

rsh commands fail on Windows Server 2008You cannot execute commands on storage systems by using the RSH protocol on Windows Server2008.

You can use either of the following workarounds to resolve this issue. However, Workaround 1ensures greater security for your storage systems.

Workaround 1: Set up DataFabric Manager server and storage systems to use SSHprotocol

1. Ensure that you have SSH enabled on the storage system.

2. Run the following command on the DataFabric Manager server to enable SSH:

dfm option set hostLoginProtocol=ssh


Workaround 2: Configure RSH protocol on the DataFabric Manager server

Complete the following steps to enable rsh commands on the DataFabric Manager server:

1. Install Subsystem for UNIX-based Applications (SUA) or Service for UNIX (SFU) on WindowsServer 2008.

2. Use the rsh binary from Microsoft SUA utilities and SDK by downloading Utilities and SDK forUNIX-based Applications_X86 (for Windows Server 2008).

3. Complete the following steps to configure the DataFabric Manager server:

a. At the command prompt, enter the following command:

dfm option set rshBinary="posix /c rsh_binary_path\rsh"

b. Enter the following command:

dfm service runas -u administrator -p admin_password http eventd

monitor scheduler server watchdog

c. Stop the DataFabric Manager service by entering the following command:

dfm service stop

d. Restart the DataFabric Manager service by entering the following command:

dfm service start

Some DataFabric Manager CLI commands fail on Windows Server 2008When you use the command-line utility for DataFabric Manager installed on a Windows Server 2008server as a domain user, you cannot execute some DataFabric Manager commands.

For example, the dfm backup create command returns the following error message:You must be root/administrator to create a database backup.

Workaround

To ensure successful execution of all of the commands, launch the command as Administrator, not asany other user with administrative rights.

IPv6 link-local address is not supportedDataFabric Manager does not support connection to storage systems and host agents over an IPv6link-local address using protocols such as RSH and SSH.

Workaround

None.


DataFabric Manager database stops responding on a VMware serverDataFabric Manager deployed on a VMware server might cause the DataFabric Manager database tofail or stop responding. The virtual machine snaphost functionality locks the database transaction logand prevents the Sybase iAnywhere database from writing to it.

Workaround

To prevent the DataFabric Manager database from failing, complete the following steps:

1. Before you take a VMware snapshot, stop the DataFabric Manager sql service using the dfmservice stop sql command.

2. Restart the sql service using the dfm service start sql command after the snapshot istaken.

Incorrect interface reporting during failoverWhen a storage system is taken over by its partner during a failover, DataFabric Manager reportsincorrect interfaces for the failed storage system.

Workaround

Use the ifconfig -a command to obtain the correct interfaces.

Note: The interfaces are accurately reported only after the giveback.

Unusable database on the DataFabric Manager serverThe DataFabric Manager server requires exclusive access to the database and transaction log files. Ifa virus scanner responds to activity by opening the database or log files with exclusive access, thisaction prevents the database server from accessing the files, which causes the database to becomeunusable.

Workaround

Configure your virus scanner to ignore access activity on the database file (monitordb.db) and itstransaction log (monitordb.log), which are located in the subdirectories listed in the dbDir anddbLogDir options shown by using the dfm database get command.

If you have other utilities that scan files, ensure that those utilities do not access the database file andits transaction log.


Delayed display of Snapshot-based backup listThe listing of Snapshot-based backups on Linux is slow because the SnapDrive commands areexecuted internally by the DataFabric Manager backup commands.

You can list the Snapshot-based backups by using either the dfm backup list command or theDatabase Backup List report (Control Center > Setup > Database Backup > List DatabaseBackups) in Operations Manager.

Workaround

None.

Issue with Snapshot-based backups on LinuxYou must create storage space on the DataFabric Manager server for Snapshot-based backups to becreated on Linux.

You can create storage space by using the snapdrive storage create command with the -fsoption. The DataFabric Manager server uses the mountpoint of the file system created by thecommand to create Snapshot-based backups.

Inconsistent display of disk names for failed-over nodesWhen a controller fails over to its partner in an active/active configuration, Operations Managertemporarily disables disk monitoring. This prevents existing disks from being added erroneously asnew disks when their names change during failover.

However, the following events are generated for a failed-over controller that might have disk namesinconsistent with the names in disk reports:

• Disks No Spares• Disks None Failed• Disks None Reconstructing• Disks Some Failed• Disks Some Reconstructing• Disks Spares Available

Limitations of LUN managementIn SnapDrive for Windows releases earlier than 6.0, you must create LUNs in a volume-level CIFSshare, which requires a Uniform Naming Convention (UNC) path. However, in SnapDrive forWindows 6.0 and later, you can create LUNs without a UNC path (not in a volume-level CIFSshare).

NetApp Host Agent 2.6 is required when the DataFabric Manager server is used to monitor andmanage LUNs on hosts (servers) that use SnapDrive for Windows 6.0.


Using DataFabric Manager server and NetApp Host Agent requires that you create a LUN in a CIFSshare for full functionality; otherwise, the following limitations exist:

• In DataFabric Manager server 3.6 or earlier, LUNs that are not created in a CIFS share are notrecognized properly:

• The LUN discovery events list only the drive letter and no other information.• The LUN on the host side is not associated with the storage system on the Host Agent Details

page of Operations Manager, or on reports such as SAN Host LUNs, All, and they cannot beexpanded or deleted using the DataFabric Manager server.

• You can use the DataFabric Manager server to create LUNs, but you must specify a UNC path(and, therefore, the LUNs are created in a CIFS share).

• In DataFabric Manager server 3.7 or later, LUNs that are not created in a CIFS share arerecognized properly (discovery events) and are associated with the storage system:

• You cannot use the DataFabric Manager server to expand or delete LUNs on the host side.• You can use the DataFabric Manager server to create LUNs but you must specify a UNC path

(and, therefore, the LUNs are created in a CIFS share).

Known issues with Performance AdvisorSome unexpected and potentially undesired behaviors, as well as, in some cases, workarounds toavoid these behaviors, are identified in Performance Advisor for use with this release of theDataFabric Manager server.

Next topics

Delayed CLI response to the dfm perf clientstat collect command on page 32

Delayed UI response on the Set Up Hosts window on page 32

Delayed UI response in advanced views on page 32


Data ONTAP panic during Performance Advisor data collection on page 33

Data ONTAP global disable counter group option on page 33

Alarm scripts fail on page 33

Performance view options are not supported on page 33

Import and export in XML format are not supported on page 34

Unique view names on page 34

Alarm wizard lists all event names on page 34

Performance Advisor windows and panes are not refreshed on page 34

Data collection cannot be enabled on page 34


Delayed CLI response to the dfm perf clientstat collect commandIf a storage system receives many service requests, there might be a delay in the CLI response to thedfm perf clientstat collect command. The delay in response might be more than 30minutes.

Workaround

None.

Delayed UI response on the Set Up Hosts windowIf DataFabric Manager server is monitoring many hosts, the Set Up Hosts window takes a long timeto display the list of hosts in NetApp Management Console.

However, this issue is observed only when the list of hosts is accessed for the first time. The responsetime improves with the subsequent access of this window, provided the number of hosts is notincreased.

Delayed UI response in advanced viewsIf the range of data in advanced views exceeds a month, applying metrics such as Minimum,Maximum, Mean, or Percentile delays the UI response in NetApp Management Console.

Workaround

None.



Workaround



Data ONTAP panic during Performance Advisor data collectionThe DataFabric Manager server can cause Data ONTAP to panic during Performance Advisor datacollection. For more information, enter the bug IDs 261233 and 254833 on the Bugs Online &Release Tools page.

Workaround

The DataFabric Manager fix for the bug 261233 greatly reduces the likelihood of a panic due to DataONTAP bug 254833. You need to obtain the fix for bug 254833 to avoid all chance of a panic.

Data ONTAP global disable counter group optionIn DataFabric Manager 3.7 or later, the Performance Advisor qtree monitoring feature is enabled bydefault on storage systems running Data ONTAP 7.3 or later. The qtree monitoring feature isdisabled on storage systems running versions of Data ONTAP earlier than 7.3 due to bug 254833.

However, you can disable qtree or any other counter groups, such as volume, LUN, and systemmonitoring, for a particular host.

To disable data collection for counters at the host level, enter the following command on one line:

dfm perf data disable [-p] host-name-or-id perf-object-type { all |counter-name ...}

Alternatively, you can use the Data Collection Configuration Wizard to enable or disable the datacollection.

Alarm scripts failAlarm scripts that use perf:counter-name:[high|low] do not function properly in DataFabricManager 3.7 or later.

Because you can have both upper and lower thresholds on counters in DataFabric Manager 3.7 orlater, the event perf:threshold-eventname: breached replaces perf:counter-name:[high|low].

Workaround

None.

Performance view options are not supportedPerformance Advisor does not support the following Performance view options when using the *.npvfile format: Save, Save As, Open.

Workaround

None.


Import and export in XML format are not supportedPerformance Advisor supports only the Export option that uses the *.csv file format. Import andExport options that use the *.xml file format are not supported.

Workaround

None.

Unique view namesNon-unique view names for multiple Custom Views that were created in Performance Advisor forDataFabric Manager 3.6 or earlier versions are made unique during the upgrade by appending an ID.

Alarm wizard lists all event namesThe Alarm wizard lists all of the event names known to the DataFabric Manager server. Names forevents generated by Performance Advisor are prefixed with "perf:".

Performance Advisor windows and panes are not refreshedSome Performance Advisor windows and panes are not automatically refreshed when objects areadded outside of the Performance Advisor client.

The following is a list of panes and windows that are not refreshed:

• Logical hierarchy pane• Physical hierarchy pane• Alarms window• Hosts window• Custom Views window

Workaround

None.

Data collection cannot be enabledIf you disabled data collection prior to the upgrade, Performance Advisor does not allow you toenable data collection for a custom view.

Workaround

Use the dfm perf view start command to enable data collection.


Known issues with Protection ManagerSome unexpected and potentially undesired behaviors, as well as, in some cases, workarounds toavoid these behaviors, are identified in Protection Manager for use with this release of the DataFabricManager server.

Next topics

Job Failure protection status is displayed for a dataset after an external relationship isimported on page 36

Restored files are overwritten on page 36


The compression option for SnapMirror connections is not preserved on page 36

Cluster-Mode objects are not supported on page 37

Cannot import some external relationships from a qtree on the same source volume on page 37

Stale SnapMirror relationships might be left after an NDMP migration on page 37

Open Systems SnapVault relationship baseline is not registered as a backup version on page 37

Incorrect dataset conformance status is displayed when the protection status is "BaselineFailure" on page 38

Operations Manager and Protection Manager display different qtree and volumecounts on page 38

Relationship create jobs fail to register baseline version on destination storage systems runningData ONTAP 7.2.3 or earlier on page 38

Resizing of disaster recovery volumes for conformance after failover on page 39

Restoration to conformance dataset members with deleted baseline Snapshot copies on page 39

Support for Windows path names containing non-ASCII characters on page 41

Spare disk capacities are not counted as "available size" for a resource pool on page 41

Aggregate "Nearly full" and "Full" threshold settings are not used to determine whether anaggregate should be excluded as a resource in a dataset on page 41

Dynamic volume resizing must be disabled to support deduplication plus "Mirror, then back up"protection policy on page 41

No data protection transfer reports when an OSSV primary directory name containsspaces on page 42


Job Failure protection status is displayed for a dataset after an externalrelationship is imported

When you import an external relationship into a dataset, the dataset protection status changes to JobFailure. When the next scheduled backup or mirror backup job runs, or when you run an on-demandbackup, the protection status changes to reflect the results of the protection job.

Workaround

After you import an external relationship, click Protect Now to start an on-demand backup for thedataset.

Restored files are overwrittenIf you attempt to simultaneously restore several files that have a common name and are located inmultiple qtrees, and you are restoring them back to a single qtree, then all the restored files with thatname are overwritten except the last restored file. Protection Manager does not issue a warning orprevent this overwrite from occurring.

Workaround

None.



Workaround


The compression option for SnapMirror connections is not preservedWhen Protection Manager imports a SnapMirror relationship that has compression enabled, it doesnot preserve the compression option for SnapMirror connections that have the dfm optionhostPreferredAddr1 set for both the source and destination storage systems.

After the SnapMirror relationship is imported, the next transfer update job for the dataset creates anew connection using the preferred host addresses, and modifies the snapmirror.conf entry. Thisentry does not have the compression=enable option.

If you manually edit the snapmirror.conf file and add the compression=enable option for anyexisting connections, and if hostPreferredAddr1 is set for both the source and destination storage


systems, the next transfer update job for the dataset overwrites the entry in snapmirror.conf anddeletes the compression option.

If hostPreferredAddr1 is not set for the source and destination storage systems, ProtectionManager leaves the compression=enable option intact in the snapmirror.conf file.

Workaround

None.

Cluster-Mode objects are not supportedProtection Manager does not support Cluster-Mode objects. Therefore, mirroring and backupoperations cannot be performed on storage systems running Data ONTAP 8.0 Cluster-Mode, andexternal relationships on storage systems running Data ONTAP 8.0 Cluster-Mode cannot bediscovered by Protection Manager.

Cannot import some external relationships from a qtree on the samesource volume

Protection Manager cannot import both a volume-to-volume SnapMirror relationship and a backuprelationship from a qtree that is on the same source volume as the first relationship.

Workaround

None.

Stale SnapMirror relationships might be left after an NDMP migrationIf you abort a migration that is using NDMP, a stale SnapMirror relationship might be left on themigration source storage system.

Workaround

None.

Open Systems SnapVault relationship baseline is not registered as abackup version

When Protection Manager creates a new SnapVault relationship that uses extended ASCII charactersin the source Open Systems SnapVault directory path, the relationship gets created but a baselinebackup version is not registered. This occurs because the create job includes a name from the storage


system that is encoded differently from what it expects, which causes the job to fail when trying tomatch the Open Systems SnapVault directory with the newly created relationship.

Workaround

Either manually run the backup job immediately after the relationship create job ends, or wait for thenext scheduled job to run. These options work because neither on-demand or scheduled jobs requireextra information from the storage system to create a backup version.

Incorrect dataset conformance status is displayed when the protectionstatus is "Baseline Failure"

When Protection Manager displays the protection status "Baseline Failure" for a dataset, theconformance status might be displayed incorrectly as "Conformant" for that dataset when the datasetis not, in fact, in conformance.

Workaround

None.

Operations Manager and Protection Manager display different qtree andvolume counts

The Protection Manager count of a group's qtrees and volumes differs from the Operations Managercount of a group's qtrees and volumes.

The qtree count differs because the NetApp Management Console count includes root qtree0 in everyvolume, and the Operations Manager count does not. The volume count differs because theOperations Manager count includes offline volumes, and the NetApp Management Console does not.

In Protection Manager, the qtree and volume counts are displayed in the Protected Data panel andUnprotected Data panel in the Protection Dashboards window. In Operations Manager, thisinformation is displayed in the Group members panel on the Group Summary tab.

Workaround

None.

Relationship create jobs fail to register baseline version on destinationstorage systems running Data ONTAP 7.2.3 or earlier

Protection Manager does not support registering the SnapVault baseline backup versions withdestination secondary or tertiary storage systems running Data ONTAP 7.2.3 or earlier.

Consequently, if you use NetApp Management Console to create a dataset, the initial baselinebackup transfer will not register the baseline backup version if the secondary or tertiary storagevolume resides on a storage system that runs Data ONTAP 7.2.3 or earlier.


Subsequent scheduled or on-demand backup jobs will succeed and register backup versionsaccordingly.

Resizing of disaster recovery volumes for conformance after failoverFailover might cause the newly activated volumes in the disaster recovery node to fall intononconformance.

This occurs in the following case: Thickly provisioned primary volumes are assigned a provisioningpolicy that specifies volume space guarantee, and their NAS backup volumes on the disaster recoverynode are thinly provisioned, with each volume sized as large as its containing aggregate.

This is because the available unassigned space in the containing aggregate (none) is less thanrequired for the volume space guarantee feature.

Workaround

If you plan to fail back to the original primary node, ignore the non-conformant state and fail back.

If you plan to continue using the disaster recovery node volumes as the new primary storagevolumes, you need to resize them to free enough space on the containing aggregate to support thevolume space guarantee requirement. Use NetApp Management Console (Data > Datasets >Provisioning) to perform the following tasks:

• Survey the current and free space in the disaster recovery node volumes to determine how muchvolume resizing is possible.

• Reduce the size of the disaster recovery node volumes, making sure that the containing aggregatehas enough free space to support the volume space guarantee and the volume has enough spacefor data plus Snapshot copies.

Note: The common formula to estimate the space requirement for data plus Snapshot copiesfor a volume is to multiply the probable data space requirement by 1.3. If necessary, deleteunnecessary Snapshot copies from the disaster recovery node volumes to reduce volume spacerequirements.

Note: You can also resize the disaster recovery node volumes by using FilerView (Filer >Volumes > Manage) or by using the CLI command vol size volname [[+|-]sizeMB], where size isa number.

Restoration to conformance dataset members with deleted baselineSnapshot copies

If the baseline Snapshot copy for a protected dataset member is deleted, its dataset becomesnonconformant and data protection operations are suspended.

For example, because Data ONTAP has a limit of 255 Snapshot copies on a volume, it is possible forData ONTAP to delete a protected volume's baseline Snapshot copy if that limit is reached. If thishappens to a member of a dataset, then Protection Manager displays the following nonconformanceerror message for that dataset:


volume_name: Could not create snapshot for volume 'filername:volumename'(371).Reason: No more snapshots available.

Workaround

You can invoke CLI commands on the DataFabric Manager server to immediately establish a newbaseline for individual containers and return the dataset to conformance.

To immediately create a new baseline Snapshot copy for the nonconformant storage containers,complete the following steps:

1. Note the primary source volume names in the nonconformance error message.

2. Log in to the DataFabric Manager server CLI.

3. List the secondary SnapMirror destination objects for the nonconformant dataset by using thefollowing command:

dfpm dataset list -R data-set

data-set is the name of the nonconformant dataset.

4. Quiesce SnapMirror activity between the nonconforming primary volumes and their destinationobjects by using the following command:

dfdrm mirror quiesce dest_obj1 dest_obj2 dest_obj...

dest_obj... are the destination objects of the nonconformant primary source objects.

5. Break the nonconformant SnapMirror relationships by using the following command:

dfdrm mirror break dest_obj1 dest_obj2 dest_obj...

6. Delete the SnapMirror relationships that you just broke by using the following command:

dfdrm mirror delete dest_obj1 dest_obj2 dest_obj...

7. Create new SnapMirror relationships between all primary containers and their destination objectsin this dataset by using the following command:

dfpm dataset conform data-set

8. After a few minutes, verify that the dataset has returned to a conformant state by using thefollowing command:

dfpm dataset status data-set


Support for Windows path names containing non-ASCII charactersProtection Manager supports Windows path names that contain non-ASCII UTF- 8 characters onlyfor storage systems that are running Data ONTAP 7.3.1 or later or hosts that are running OpenSystems SnapVault 2.6.1 or later.

Hosts require Open Systems SnapVault 2.6.1 or later. Storage systems require Data ONTAP 7.3.1 orlater.

Spare disk capacities are not counted as "available size" for a resourcepool

If a resource pool includes a storage system with spare disks, the Resource Pools window (Data >Resource Pools) in NetApp Management Console does not count the spare disk capacities whendisplaying "available size" for that resource pool.

Workaround

None.

Aggregate "Nearly full" and "Full" threshold settings are not used todetermine whether an aggregate should be excluded as a resource in adataset

The "Nearly full threshold" and "Full threshold" parameters only specify the thresholds at which theprovisioning application generates warning and error events regarding used space on aggregates in aresource pool. The settings are not used to determine whether an aggregate should be excluded as aresource in a dataset.

For example, if a resource pool contains an aggregate whose used space exceeds the "Nearly fullthreshold" or "Full threshold" settings, and you attempt to add that resource pool to a dataset, theconformance check performed when adding the resource pool will not exclude that aggregate as aresource based on this condition.

Instead, the conformance check references the global "Aggregate Nearly Full threshold" or"Aggregate Full threshold" settings in Operations Manager to possibly exclude that aggregate.

Similarly, the provisioning application flags the need for relationship migration based on theOperations Manager settings, rather than on the Protection Manager "Nearly full threshold" and "Fullthreshold" settings of the assigned resource pool.

Dynamic volume resizing must be disabled to support deduplication plus"Mirror, then back up" protection policy

If you enable deduplication on the primary node volumes in a dataset that is assigned a "Mirror, thenback up" protection policy, then you must disable the dynamic secondary volume resizing feature, or


the backup from the mirrored volumes on the secondary node to the backup objects on the tertiarynode will fail.

If you need to support both deduplication and the "Mirror, then back up" protection policy, disablethe global dpDynamicSecondaryResize option in the Operations Manager. Disabling this optioncauses the tertiary volume to be automatically sized to the full size of its containing aggregate.

No data protection transfer reports when an OSSV primary directory namecontains spaces

If the name of an Open Systems SnapVault primary directory contains spaces, you cannot get dataprotection transfer reports for those Open Systems SnapVault relationships.

Workaround

None.

Known issues and limitations with Provisioning ManagerSome unexpected and potentially undesired behaviors, limitations, as well as, in some cases,workarounds to avoid these behaviors, are identified in Provisioning Manager for use with thisrelease of the DataFabric Manager server.

Next topics

Some dataset migration details are not displayed after migration cutover on page 43


vFiler unit migration cutover fails when source volumes are full on page 44

The migration feature allows you to start unnecessary duplicate cleanup and canceljobs on page 44

Changing the IPspace of a vFiler unit causes migration cutover to fail on page 44

Volume-based SnapRestore during migration cutover causes failure on page 45

Migration rollback fails if the migrated source volume contained no Snapshot copies on page 45

Newly added quotas are not migrated during rollback and subsequent cutover orrollbacks on page 45

The vFiler unit on the destination storage system is destroyed when cutover fails in the reincarnatephase on page 46

Cutover operation fails to stop any active CIFS session on a vFiler unit on page 46

Long-running operations not associated with the migration fail during the cutoverphase on page 46

Data ONTAP 8.0 7-Mode does not support rollback operation on page 46

Backup initiated during cutover operation might fail on page 46


Online migration fails between a FAS system and an IBM N series storage system on page 47

Cannot clone volumes in a migrated vFiler unit on page 47

Data access to a migrated vFiler unit is blocked on page 47

Qtree details do not appear after DR failover on page 47

Management Console can set but not modify the vFiler unit root password on page 48

Some dataset migration details are not displayed after migration cutoverAfter migration cutover is complete, the Details tab on the Datasets window Migration tab does notdisplay some details about the migrated dataset.

The following details, normally displayed during other migration operations, are not displayed aftermigration cutover and before the next operation:

Physical resource The volume containing the migrated data

Lag The time elapsed since the last successful migration

State The state of the source-destination protection relationship. After cutover, thestate is normally "broken off."

Status The status of the source-destination protection relationship. After cutover, thestatus is normally "idle."

Even though no data for these details is displayed, the "migrated, cleanup required" state indicatesthat the cutover is successful.

Workaround

No workaround is necessary. After migration cutover is complete, you can proceed with themigration cleanup or migration rollback operations.



Workaround



vFiler unit migration cutover fails when source volumes are fullIf source volumes undergoing migration are full and the cutover operation is started, the cutoveroperation fails with an error message "process was aborted." This failure occurs because full sourcevolumes leave no room for the Snapshot copies that the cutover operation requires.

WorkaroundIf this problem occurs, free some space in the source volumes and retry the cutover operation.

The migration feature allows you to start unnecessary duplicate cleanupand cancel jobs

If you click either the Clean up button or the Cancel button on either the Datasets windowMigration tab or the vFiler Units window to start a migration cleanup job or a migration cancel job,Provisioning Manager starts the associated cleanup or cancel job but does not disable its button.

It is, therefore, possible to perform an unnecessary duplicate cleanup job or duplicate cancelmigration job. The duplicate job runs and fails after the first job finishes.

Workaround

No workaround is necessary. If you accidentally start an unnecessary duplicate migration cleanup orduplicate migration cancel job, those duplicate jobs fail with no adverse consequence.

Attention: Do not attempt to cancel a duplicate job by pressing Cancel on your keyboard multipletimes. Doing so might cause the DataFabric Manager server to crash.

Changing the IPspace of a vFiler unit causes migration cutover to failChanging the IPspace of a vFiler unit during or after a migration start operation causes migrationcutover to fail.

Workaround

After migration of a vFiler unit is started, avoid changing its IPspace until after the post migrationcleanup operation is complete.


Volume-based SnapRestore during migration cutover causes failureRunning a VBSR (volume-based SnapRestore) operation or any application that invokes VBSR(such as SnapDrive for UNIX or SnapManager for Oracle) during the cutover phase of datamigration or during a rollback operation causes the cutover or rollback operation to fail.

Workaround

In the case of cutover or rollback failure due to this cause, invoke the Migrate cancel operation. Afterthe cancel operation is complete, stop the VBSR operation and retry the cutover or rollbackoperation.

Migration rollback fails if the migrated source volume contained noSnapshot copies

If a migration rollback operation is necessary after the cutover operation, it fails if a source volumecontained no Snapshot copies before you launched the original migration start operation.

In most cases, Snapshot copies of the source volumes exist as a result of normal data protectionoperations; however, they might not exist if normal data protection operations are not enabled, or ifthe data in the source volume is newly imported and no scheduled protection operation has yet takenplace.

Workaround

You can confirm the existence of Snapshot copies for any source volume before starting migration byclicking the "Delete Snapshots" button on the Provisioning tab and viewing the Snapshot copylisting in the dialog box.

Newly added quotas are not migrated during rollback and subsequentcutover or rollbacks

During online migration, newly added quotes are not migrated.

New quotas that are added after initial cutover are not migrated to the source during rollback and tothe destination during subsequent cutovers.

Workaround

None.


The vFiler unit on the destination storage system is destroyed whencutover fails in the reincarnate phase

When cutover fails in the reincarnate phase during online migration, the vFiler unit on the destinationstorage system cannot be used. This is because Provisioning Manager destroys the vFiler unit on thedestination storage system and the volumes are moved to the hosting storage system.

Workaround

Retry the cutover operation and the vFiler unit is re-created on the destination storage system.

Cutover operation fails to stop any active CIFS session on a vFiler unitAlthough a dataset with CIFS policy cannot be created for online migration, you can attach thedataset to a vFiler unit and perform online migration. However, during an active CIFS session, youcannot detect the vFiler unit and perform online migration. The cutover operation fails with thefollowing error message: The "-t minutes" option must be specified whenterminating CIFS from rsh.

Workaround

Specify the -t minutes option while ending any CIFS session in Data ONTAP and retry cutoveroperation.

Long-running operations not associated with the migration fail during thecutover phase

Provisioning Manager detects long-running operations that hold active volume references during thecutover phase of the migration process. These long-running operations fail during the cutover phase,leading to cutover failure.

Workaround

These operations are aborted during the cutover phase of the migration process.

Data ONTAP 8.0 7-Mode does not support rollback operationDuring vFiler unit migration, the rollback operation fails in 7-Mode storage systems.

Backup initiated during cutover operation might failIf you initiate a backup during the cutover operation of a vFiler unit online migration, the backupoperation might fail.


Online migration fails between a FAS system and an IBM N series storagesystem

You cannot perform online migration from a FAS system to an N series system or from an N seriessystem to a FAS system.

Cannot clone volumes in a migrated vFiler unitVolumes within a migrated vFiler unit on a SnapDrive host cannot be cloned if thevfiler.vol_clone_zapi_allow option is not enabled on the destination storage system.

Workaround

Set the vfiler.vol_clone_zapi_allow option on the destination hosting storage system to on.

Data access to a migrated vFiler unit is blockedData access to a migrated vFiler unit can be blocked if the trusted.hosts option on the destinationhosting storage system is set to specific hosts and the migrated vFiler unit has thehttpd.admin.access option set to legacy.

Workaround

Set the trusted.hosts option on the hosting storage system to * or to hosts that access data fromthe migrated vFiler unit.

Qtree details do not appear after DR failoverAfter completion of the failover process, the Provisioning tab does not display space information forqtrees in the failed-over dataset. Even if the failover is successful, the Total space and Availablespace for qtrees in the failed-over dataset is listed as 0 KB.

Despite the 0 KB reading on these qtrees, the data protection update and failover to the disasterrecovery node has probably succeeded and the secondary qtrees probably contain backup data fromthe last update before the failover. This data is probably ready for restoration to or resynchronizationwith the original primary containers.

To confirm the success of the last mirror or backup job on the failed-over dataset, see the SystemJobs window.

To confirm the success of the failover process as a whole, see the dataset's Failover status on theDisaster Recovery tab.


Management Console can set but not modify the vFiler unit root passwordYou can use the Add vFiler Unit wizard or the Setup vFiler Unit wizard to set the password for theroot user of a newly created vFiler unit. After you specify the root password and use it to access thevFiler unit, you cannot use either wizard to modify that password.

Workaround 1

To modify passwords of a vFiler unit's existing root user account from either a Windows or a UNIXworkstation, complete the following steps:

1. Enter the following command to connect to the vFiler unit's hosting storage system:

telnet host_storage_system_dns_name

2. Enter the following command to specify the vFiler unit context:

vfiler context vFiler_dns_name

3. Enter the following command to specify the new password:

passwd old_password new_password

Workaround 2

To modify passwords of a vFiler unit's existing root user account from a UNIX workstation only,complete the following command:

rsh -l root:vfiler_old_passwd vfiler_dns_name passwd old_passwd new_passwd


Changes to published documentation

There are changes to the documentation provided with this release of DataFabric Manager. Thisinformation is new and it should be added to the documentation.

Changes to the Operations Manager Administration Guide

• Add the Web service topic in the "What is new in this release" topic of the "Maintenance andmanagement" section. The correct version of the text in the Web service topic is as follows:DataFabric Manager server 4.0 (including Operations Manager, Protection Manager, andProvisioning Manager) supports the Web services feature and Web services APIs. These Webservices APIs, defined in the WSDL file, use SOAP 1.2 over HTTP or HTTPS. You can usevarious SOAP toolkits, such as gSOAP, Axis, Apache CXF, and Perl SOAP::Lite, to develop aWeb service application from the WSDL file. The WSDL file, dfm.wsdl, is packaged withDataFabric Manager and is available in the misc directory.

• Add the following note to the Web service topic:You can access the DataFabric Manager APIs by using the NetApp Manageability SDK, whichyou can download from http://communities.netapp.com/docs/DOC-1152.

• The following content is part of the "Overview of new and changed features" topic in the "Whatis new in this release" chapter:Larger Aggregates: DataFabric Manager 4.0 provides support for larger aggregates for maximumaggregate size of 64-bit aggregates.

• The link, http://now.netapp.com/ NOW/products/interoperability/, in "Prerequisites to managetargets and initiators" topic should be replaced with http://now.netapp.com/matrix/.

Changes to the NetApp Management Console Help for Provisioning Manager

• Add this topic under Datasets > About data migrationOnline migration in ATA, SATA, FC, SAS, and BSAS based disksProvisioning Manager allows online migration between systems with ATA, SATA, FC, SAS, andBSAS based disks. You can perform online migration between disks of the same type. However,for migration between different disk types, only certain disk types are supported.You can migrate from lower-end disks to higher-end disks. However, you cannot migrate fromhigher-end disks to lower-end disks. Online migration is possible for the following disk types:

• SATA to FC• SATA to SAS• ATA to FC• ATA to SAS• BSAS to FC• BSAS to SAS

Changes to published documentation | 49

HTTP://COMMUNITIES.NETAPP.COM/DOCS/DOC-1152

For similar disk types, online migration is possible for the following disk types:

• FC to FC• SAS to SAS• SATA to SATA• BSAS to BSAS• ATA to ATA

For different disk types, online migration is possible only for the following disk types:

• ATA to SATA• ATA to BSAS• SAS to FC• FC to SAS

For more information about the disk types supported by Data ONTAP, see the Data ONTAPStorage Management Guide.

• Rearrange the action buttons in the NMC Data > Datasets > Overview tab

Changes to the NetApp Management Console Help for Performance Advisor

Add the following note in the Set Up > Hosts context-sensitive help topic

Note: To reduce Max Projected Space for a counter group, you must disable all the counters,including the diagnostics counters in the counter group. You can use the following command todisable the diagnostics counters:

dfm option set perfAdvisorShowDiagCounters=Disabled

Changes to the NetApp Management Console Help

Correction in the Licenses topic in the online Help

Replace the second paragraph with the following: “You must enter a software license code on theDataFabric Manager server to enable the corresponding functions. You do not need to indicate whichlicense the code enables. The code is matched automatically to the appropriate service license.”

Changes to the Installation and Upgrade Guide

• The link, http://now.netapp.com/ NOW/products/interoperability/, in the "Hardware and softwarerequirements" topic should be replaced with http://now.netapp.com/matrix/.


Where to find product documentation and otherinformation

There are additional sources of information for this release of DataFabric Manager.

Documentation roadmap

The following table describes where to find additional information about DataFabric Manager andOperations Manager.

To learn about... Go to this information source...

New features, enhancements, and known issues in thisrelease

Release Notes and the Administration Guide for eachproduct

How to monitor and manage multiple NetAppsystems, storage resources, user quotas, File SRM,content distribution, and appliance configuration

Operations Manager Administration Guide and theOperations Manager Help

How to download and install NetApp ManagementConsole

Installation and Upgrade Guide

How to use the Performance Advisor application toview performance data and customize the tools; also,how to use the statistical counters for storage systemperformance that are contained in Data ONTAP

Performance Advisor Administration Guide and theNetApp Management Console Help

The workflows you might use in ProvisioningManager and Protection Manager to provision spaceand protect data, using real-life scenarios

The workflow examples in the Provisioning Managerand Protection Manager Guide to CommonWorkflows for Administrators

The tasks involved when you use the ProtectionManager application to set up and manage both yourdata protection relationships and disaster recoverycapability, as well as related concepts and referenceinformation

Protection Manager and Disaster Recovery Help inNetApp Management Console

The tasks involved when you use the ProvisioningManager application to provision space for your data,as well as to monitor and manage space utilization

Provisioning Manager Help in NetApp ManagementConsole

How to back up and recover data using BackupManager and Disaster Recovery Manager

Operations Manager Administration Guide, theOperations Manager Help, and the NetAppManagement Console Help

Where to find product documentation and other information | 51

To learn about... Go to this information source...

How to use the DataFabric Manager, BackupManager, Content Management System, ProvisioningManager, Protection Manager, and Disaster RecoveryManager commands

The manual (man) pages in the Operations ManagerHelp

How to troubleshoot and maintain the physicalresources of a system

The FAQ (in the Operations Manager Help and on theDataFabric Manager 4.0 Documentation page), thetroubleshooting module in the Help, and OperationsManager Administration Guide

Any other topic of interest The DataFabric Manager FAQ (in the OperationsManager Help and on the DataFabric Manager 4.0Documentation page)

Documentation on NOW

The DataFabric Manager documentation set is available on the NOW site at http://now.netapp.com.

Online information

There are several ways to access online documentation and technical resources.

Onlinedocumentation

Included with your DataFabric Manager software is a Web-basedadministration tool, Operations Manager, and its Help.

Included with your NetApp Management Console software is Help forProvisioning Manager, Protection Manager, and Performance Advisor.

You can also obtain online documentation and answers to frequently askedquestions from the NOW site.

Other resources The NOW Natural Language PowerSearch tool on the Service and Supportpage on the NOW site enables you to search the following sources ofinformation:

• Product documents• Knowledgebase solutions• Bugs online• NOW forums• Tools and other documentation• Partner knowledgebases

Where to find third-party source material

Operations Manager, Provisioning Manager, and Protection Manager contain LGPL-licensedpackages, which are available at ftp://ftp.netapp.com/frm-ntap/opensource.


Documents

OpsManager rnote