OpsManager Rnote

Release Notes
For Use with DataFabric® Manager Server 4.0,

Supporting Operations Manager, Provisioning Manager, and
Protection Manager
NetApp, Inc.
495 East Java Drive
Sunnyvale, CA 94089 USA
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 4-NETAPP
Documentation comments: doccomments@netapp.com
Information Web: http://www.netapp.com
Part number: 215-05109_A0
February 2010
Table of Contents | 3
Contents
Copyright information ................................................................................. 7
Trademark information ............................................................................... 9
Release notes ................................................................................................ 11
Known 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 ......................................................................... 17
Known 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
4 | Release Notes For Use with DataFabric® Manager Server 4.0
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
Table of Contents | 5
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
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 ....................................................... 49
Where to find product documentation and other information .............. 51
Copyright information | 7
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 an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S.A. patents, foreign
patents, or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark information | 9
Trademark information
NetApp; the NetApp logo; the Network Appliance logo; Cryptainer; Cryptoshred; DataFabric; Data
ONTAP; 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 other
countries. 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. The
StoreVault 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 are
trademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful and Select are service
marks of NetApp, Inc. in the U.S.A.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or
other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft
Corporation in the U.S.A. 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 U.S.A. and/or other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.
NetApp, Inc. NetCache is certified RealSystem compatible.
Release notes | 11
Release notes
These release notes provide information about the new and changed features, and known issues in
DataFabric 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
Known issues with Data ONTAP | 13
Known issues with Data ONTAP

Some unexpected and potentially undesired behaviors in Data ONTAP are known to affect
functionality 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 storage
system 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 Provisioning
Manager 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 volumes
and aggregates. Therefore, you cannot monitor the Snapshot copies of such clusters by using
Operations Manager.
Workaround
None.
Issue with determining the storage capacity of the default

volume
The SNMP response for volTable does not list the root volume vol0 belonging to the nodes of a
cluster. Therefore, the default volumes of these nodes are not reported in the SNMP response. You
cannot discover these default volumes or generate reports to determine their storage capacity by
using Operations Manager. Since there is no visibility to the root volume, you cannot generate
reports using Operations Manager to determine the storage capacity of these volumes.
Workaround
None.
SNMP timed out error message

When multiple DataFabric Manager servers monitor a single cluster, it results in an SNMP timed out
error message.
Workaround
Use only one DataFabric Manager server for monitoring a cluster at a time.
Data ONTAP is unable to perform SnapVault activities on a

secondary storage system
When you use SnapVault or Open Systems SnapVault with Protection Manager with DataFabric
Manager server 3.8 on a Data ONTAP 7.3.1 storage system, the storage system might run out of
resources (NDMP threads).
This occurs because Protection Manager uses a new API for data transfer. Normal data protection
activities are possible until the NDMP thread count in Data ONTAP is exceeded. The number of
threads available is platform dependent and the threads cannot be recovered after they have been
consumed. Normal activity continues in Data ONTAP, but additional NDMP transfers are blocked
after the maximum thread count is reached.
Note: After Data ONTAP reaches the NDMP thread limit, additional NDMP requests are not
serviced, whether they are for SnapVault, SnapMirror, or other activities. This issue does not
affect tasks initiated from the Backup Manager or Disaster Recovery Manager tabs in Operations
Manager.
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 Data
ONTAP that contains a fix for bug 354933.
Known issues with Data ONTAP | 15
Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts

Operations Manager
Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts the vFiler quota monitoring, and
LUN monitoring for storage systems and vFiler units (vFiler igroup, vFiler LUN, storage system
LUN, 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 impacts

Provisioning Manager
Lack of RSH-over-IPv6 support in Data ONTAP 7.3.1 impacts the following in Provisioning
Manager: (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 IPv6

The hosts.equiv authentication does not support IPv6 addresses. APIs over HTTPS do not work for
IPv6 addresses in Data ONTAP 7.3.1 when the httpd.admin.access option on a storage system is
set to a value other than legacy.
System panics due to deleted vFiler user groups

You must avoid deleting user groups on vFiler units running Data ONTAP 7.0 and 7.1. Deleting user
groups 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 | 17
New and changed features

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

This section describes new features and changes in Operations Manager in DataFabric Manager
server 4.0. Detailed information about the features, including lists of new or changed CLI commands
and 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 with
DataFabric Manager server 4.0. For detailed information about the features, see the NetApp
Management Console Help.
The changes in NetApp Management Console include the following:
• Custom fields
You can add and configure user-defined custom fields for datasets, protection policies, and
provisioning policies. You can use these fields to enter custom information, such as cost center or
chargeback codes.
• Multiple selection filtering
When filtering data that is displayed in a column, you can select multiple values from a column
drop-down list.
Provisioning Manager features

This section describes new features and changes in Provisioning Manager for use with DataFabric
Manager server 4.0. For detailed information about tasks and concepts related to the features, see the
NetApp 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
limitations, see “What is new in this release” in the Provisioning Manager and Protection Manager
Guide to Common Workflows for Administrators.
The new features in Provisioning Manager include the following:
• Secondary storage space management
For more details, see the "Protection Manager features" section.
• Automated online migration for datasets and vFiler units
You can migrate your data from one storage system to another without disrupting access to that
data by the users or applications. You do so by enabling online migration (a component of the
NetApp Data Motion solution). In addition to migration without disruption of data availability,
online migration also enables automatic cutover and migration rollback.
• Storage services
You can preconfigure one or more combinations of protection, provisioning, resource pool, and
vFiler template configurations into standard storage service packages that can readily be assigned
to datasets requiring those specific storage services. Your storage service packages listed together
can constitute a technical service catalog as described by the Information Technology
Infrastructure Library, version 3 (ITIL V3).
• Support for larger aggregates
You 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 16
TB) in Data ONTAP 8.0 (7-Mode only) or later.
The changes in Provisioning Manager include the following:
Protection Manager features

This section describes new features and changes in Protection Manager for use with DataFabric
limitations, see “What is new in this release” in the Provisioning Manager and Protection Manager
Guide to Common Workflows for Administrators.
The new features in Protection Manager include the following:
• Secondary storage space management
When the licensed protection application or provisioning application displays an aggregate space
problem, you can use the Secondary Space Management feature to plan and implement tasks to
resolve 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 status
of 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
New and changed features | 19
• Plan and implement tasks for deleting backups and Snapshot copies (primary, secondary, and
tertiary storage), increasing or decreasing the volume size (primary, secondary, and tertiary
storage), and performing volume deduplication (primary storage only)
• View the estimated space that will be reclaimed on an aggregate as a result of performing the
tasks that you plan
• Support for bidirectional SnapVault backups
Protection Manager supports SnapVault Primary and SnapVault Secondary licenses on the same
storage system. This allows you to perform SnapVault host-to-host backups of primary and
secondary dataset nodes within the same storage system.
Note: Backups of volumes within the same aggregate are not supported. However, backups of
aggregates 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.
• Licensing
When you install the Protection Manager license, the provisioning functions provided by
Provisioning Manager are also enabled.
The changes in Protection Manager include the following:
• Unprotected data
The definition of unprotected data is changed. External relationships are no longer counted as
unprotected data.
• AutoSupport
Additional protection information is sent to AutoSupport if you have Protection Manager
enabled.
• Protection status error messages
Because error messages related to protection status now provide more information, you can
troubleshoot protection problems more easily.
Performance Advisor features

This section describes new features and changes in Performance Advisor for use with DataFabric
limitations, see “What is new in this release” in the Performance Advisor Administration Guide.
The new features in Performance Advisor include the following:
• Data collection configuration
You can view the counters for which data collection is enabled or disabled on a per storage
system basis. The following are the other advantages that are available with this feature:
• 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 views
You can use advanced views to establish a baseline for the data collected by applying statistical
parameters such as minimum, maximum, mean, and percentile. Time filters enable you to retrieve
the baseline data based on selected business hours and week days. You can use the baseline data
in advanced views to set appropriate thresholds.
• Data export
This feature helps you to export the Performance Advisor data collected on the DataFabric
Manager server. The data is collected in CMA format. However, you should use this feature only
when NetApp requests the data from you.
• Performance diagnosis
You can diagnose the storage system for any performance-related issue during the given period
and get recommendations to resolve the issue. The event correlation chart allows you to plot
events of related objects. Also, the chart plots the Operations Manager events, which can help you
diagnose the cause of a performance degradation.
• Client statistics
You can collect the statistics related to CIFS and NFS client operations to find the cause of
latency. Also, you can use this feature to automatically collect per-client statistics when a set of
thresholds on a storage system is breached.
The changes in Performance Advisor include the following:
• Flexible custom views
You 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 | 21
Known issues with DataFabric Manager

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds to
avoid 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 upgrade

avoid these behaviors, are identified while installing or upgrading to this release of the DataFabric
Manager 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 might
fail on page 23
Delay in upgrading from DataFabric Manager server 3.2 or earlier

Due to database schema changes, you might experience several minutes to a few hours of delay when
upgrading 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 history
in the database, the CPU speed, and I/O throughput of the system. The upgrade process might take 30
to 50 minutes for large databases.
The following tasks require the most time:
• 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 earlier

If you are upgrading from DataFabric Manager 3.5 or earlier to DataFabric Manager 3.6 or later, the
time taken to upgrade the performance data files (data of 20 GB or more) is long. The length of time
is 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 fails

If you have created custom reports with GUILink and SecureGUILink as fields in DataFabric
Manager 3.7.1 or earlier, upgrading to DataFabric Manager 3.8 causes the dfm report view
command to fail.
Workaround
Edit the custom reports in Operations Manager by removing the fields, and save the reports before
you can view them.
Cluster group in VCS setup fails

In a Veritas Cluster Server (VCS) setup, if you are upgrading the cluster nodes from DataFabric
Manager 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 the
MonitorProcess 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 fail

DataFabric Manager cluster setup scripts fail to run on a 64-bit Windows 2008 server using 32-bit
ActivePerl.
Workaround
Install 64-bit ActivePerl.
Upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 on

Windows Server 2008 might fail
When you upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 on Windows Server
2008, 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 using
the above-mentioned procedure.
Known issues with Operations Manager

avoid these behaviors, are identified in Operations Manager for use with this release of the
DataFabric 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 core
dump on page 26
DSN is not created on Windows on page 26
Restoration of the DataFabric Manager database fails in DataFabric Manager 3.8 or
later 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 setup

In a scaled setup with a large number of monitored objects, you might not be able to view the
Performance Summary reports through the Web UI.
Workaround
Run the dfm report view report_name-performance-summary command from the
DataFabric Manager CLI to view the Performance Summary reports. However, the response time to
view these reports through CLI might be more than 20 minutes, depending on the number of objects
that are monitored.
For more information about bug 279167, see Bugs Online.
Related information
Striped aggregates are not displayed in the Aggregate custom report

When you create a custom report with Aggregate and Appliance as the base catalog in DataFabric
Manager 3.8.1 or earlier, and then you upgrade to DataFabric Manager 4.0 with all the aggregates in
the Data ONTAP 8.0 cluster discovered, the striped aggregates for Data ONTAP 8.0 cluster are not
displayed in the custom report.
Workaround
After you upgrade to DataFabric Manager 4.0, create another custom report with Aggregate as the
base catalog.
Volume backup fails from the Operations Manager UI

When you have a storage system that has both the SnapVault primary (sv_ontap_pri) and secondary
licenses (sv_ontap_sec) enabled, you cannot create volume backups using the Operations Manager
UI (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 setup

The Operations Manager takes some time to display the Group status in a scaled setup. It might take
approximately 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 group

In Data ONTAP 8.0 Cluster-Mode systems, when a volume is moved from its source aggregate to
another aggregate, the source aggregate loses its resource group membership in DataFabric Manager
monitoring 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 DataFabric
Manager 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

perform a core dump
If you set the clock backwards while any DataFabric Manager services are running, the DataFabric
Manager server performs a core dump.
Workaround
Shut down the DataFabric Manager server and NetApp Management Console before setting the clock
backwards.
DSN is not created on Windows

On the 64-bit versions of Windows Server 2003 and Windows Server 2008 servers, the default Open
Database Connectivity (ODBC) application does not list the System Data Source Names (DSNs) and
drivers 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 DataFabric

Manager 3.8 or later
You cannot directly restore the following backup types: (a) Snapshot-based backups created in
DataFabric Manager 3.7.1 or earlier; (b) Archive-based backups created in DataFabric Manager 3.4.1
or earlier; (c) Archive-based backups created from Snapshot-based backups using the dfm backup
export 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 database
failed
Workaround
You can restore each of these types using the version of DataFabric Manager in which the backups
were 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 DataFabric
Manager 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 immediately
following the upgrade.
IPv6 source address is incorrectly displayed in the trap receiver

When the DataFabric Manager server generates traps and sends it to an IPv6 destination host, the
IPv6 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 supported

DataFabric Manager does not support IPv4-mapped IPv6 addresses such as ::ffff:10.72.184.251.
Workaround
None.
Inconsistent capacity graphs

Capacity graphs such as Volume Capacity Used vs Total on the Group Summary page (Control
Center > Home > Group Status > Summary) do not show a drop in reported capacity when a
storage system is down.
You can observe the drop only when the system is down for a long period and the period coincides
with the start time of the graph.
Workaround
None.
rsh commands fail on Windows Server 2008

You cannot execute commands on storage systems by using the RSH protocol on Windows Server
2008.
You can use either of the following workarounds to resolve this issue. However, Workaround 1
ensures greater security for your storage systems.
Workaround 1: Set up DataFabric Manager server and storage systems to use SSH
protocol
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 Windows
Server 2008.
2. Use the rsh binary from Microsoft SUA utilities and SDK by downloading Utilities and SDK for
UNIX-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 2008

When you use the command-line utility for DataFabric Manager installed on a Windows Server 2008
server 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 as
any other user with administrative rights.
IPv6 link-local address is not supported

DataFabric Manager does not support connection to storage systems and host agents over an IPv6
link-local address using protocols such as RSH and SSH.
Workaround
None.
DataFabric Manager database stops responding on a VMware server

DataFabric Manager deployed on a VMware server might cause the DataFabric Manager database to
fail or stop responding. The virtual machine snaphost functionality locks the database transaction log
and 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 dfm
service stop sql command.
2. Restart the sql service using the dfm service start sql command after the snapshot is
taken.
Incorrect interface reporting during failover

When a storage system is taken over by its partner during a failover, DataFabric Manager reports
incorrect 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 server

The DataFabric Manager server requires exclusive access to the database and transaction log files. If
a virus scanner responds to activity by opening the database or log files with exclusive access, this
action prevents the database server from accessing the files, which causes the database to become
unusable.
Workaround
Configure your virus scanner to ignore access activity on the database file (monitordb.db) and its
transaction log (monitordb.log), which are located in the subdirectories listed in the dbDir and
dbLogDir 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 and
its transaction log.
Delayed display of Snapshot-based backup list

The listing of Snapshot-based backups on Linux is slow because the SnapDrive commands are
executed internally by the DataFabric Manager backup commands.
You can list the Snapshot-based backups by using either the dfm backup list command or the
Database Backup List report (Control Center > Setup > Database Backup > List Database
Backups) in Operations Manager.
Workaround
None.
Issue with Snapshot-based backups on Linux

You must create storage space on the DataFabric Manager server for Snapshot-based backups to be
created on Linux.
You can create storage space by using the snapdrive storage create command with the -fs
option. The DataFabric Manager server uses the mountpoint of the file system created by the
command to create Snapshot-based backups.
Inconsistent display of disk names for failed-over nodes

When a controller fails over to its partner in an active/active configuration, Operations Manager
temporarily disables disk monitoring. This prevents existing disks from being added erroneously as
new disks when their names change during failover.
However, the following events are generated for a failed-over controller that might have disk names
inconsistent 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 management

In SnapDrive for Windows releases earlier than 6.0, you must create LUNs in a volume-level CIFS
share, which requires a Uniform Naming Convention (UNC) path. However, in SnapDrive for
Windows 6.0 and later, you can create LUNs without a UNC path (not in a volume-level CIFS
share).
NetApp Host Agent 2.6 is required when the DataFabric Manager server is used to monitor and
manage 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 CIFS
share 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 not
recognized 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 be
expanded 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 are
recognized 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 Advisor

avoid these behaviors, are identified in Performance Advisor for use with this release of the
DataFabric 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
dump on page 26
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 command

If a storage system receives many service requests, there might be a delay in the CLI response to the
dfm perf clientstat collect command. The delay in response might be more than 30
minutes.
Workaround
None.
Delayed UI response on the Set Up Hosts window

If DataFabric Manager server is monitoring many hosts, the Set Up Hosts window takes a long time
to 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 response
time improves with the subsequent access of this window, provided the number of hosts is not
increased.
Delayed UI response in advanced views

If 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.

perform a core dump
Workaround
backwards.
Data ONTAP panic during Performance Advisor data collection

The DataFabric Manager server can cause Data ONTAP to panic during Performance Advisor data
collection. 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 Data
ONTAP bug 254833. You need to obtain the fix for bug 254833 to avoid all chance of a panic.
Data ONTAP global disable counter group option

In DataFabric Manager 3.7 or later, the Performance Advisor qtree monitoring feature is enabled by
default on storage systems running Data ONTAP 7.3 or later. The qtree monitoring feature is
disabled 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 system
monitoring, 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 data
collection.
Alarm scripts fail

Alarm scripts that use perf:counter-name:[high|low] do not function properly in DataFabric
Manager 3.7 or later.
Because you can have both upper and lower thresholds on counters in DataFabric Manager 3.7 or
later, the event perf:threshold-eventname: breached replaces perf:counter-name:[high|low].
Workaround
None.
Performance view options are not supported

Performance Advisor does not support the following Performance view options when using the *.npv
file format: Save, Save As, Open.
Workaround
None.
Import and export in XML format are not supported

Performance Advisor supports only the Export option that uses the *.csv file format. Import and
Export options that use the *.xml file format are not supported.
Workaround
None.
Unique view names

Non-unique view names for multiple Custom Views that were created in Performance Advisor for
DataFabric Manager 3.6 or earlier versions are made unique during the upgrade by appending an ID.
Alarm wizard lists all event names

The Alarm wizard lists all of the event names known to the DataFabric Manager server. Names for
events generated by Performance Advisor are prefixed with "perf:".
Performance Advisor windows and panes are not refreshed

Some Performance Advisor windows and panes are not automatically refreshed when objects are
added 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 enabled

If you disabled data collection prior to the upgrade, Performance Advisor does not allow you to
enable data collection for a custom view.
Workaround
Use the dfm perf view start command to enable data collection.
Known issues with Protection Manager

avoid these behaviors, are identified in Protection Manager for use with this release of the DataFabric
Manager server.
Next topics
Job Failure protection status is displayed for a dataset after an external relationship is
imported on page 36
Restored files are overwritten on page 36
dump on page 26
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 "Baseline
Failure" on page 38
Operations Manager and Protection Manager display different qtree and volume
counts on page 38
Relationship create jobs fail to register baseline version on destination storage systems running
Data 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 an
aggregate 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 contains
spaces on page 42
Job Failure protection status is displayed for a dataset after an external

relationship is imported
When you import an external relationship into a dataset, the dataset protection status changes to Job
Failure. When the next scheduled backup or mirror backup job runs, or when you run an on-demand
backup, 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 the
dataset.
Restored files are overwritten

If you attempt to simultaneously restore several files that have a common name and are located in
multiple qtrees, and you are restoring them back to a single qtree, then all the restored files with that
name are overwritten except the last restored file. Protection Manager does not issue a warning or
prevent this overwrite from occurring.
Workaround
None.

perform a core dump
Workaround
backwards.
The compression option for SnapMirror connections is not preserved

When Protection Manager imports a SnapMirror relationship that has compression enabled, it does
not preserve the compression option for SnapMirror connections that have the dfm option
hostPreferredAddr1 set for both the source and destination storage systems.
After the SnapMirror relationship is imported, the next transfer update job for the dataset creates a
new connection using the preferred host addresses, and modifies the snapmirror.conf entry. This
entry does not have the compression=enable option.
If you manually edit the snapmirror.conf file and add the compression=enable option for any
existing 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 and
deletes the compression option.
If hostPreferredAddr1 is not set for the source and destination storage systems, Protection
Manager leaves the compression=enable option intact in the snapmirror.conf file.
Workaround
None.
Cluster-Mode objects are not supported

Protection Manager does not support Cluster-Mode objects. Therefore, mirroring and backup
operations cannot be performed on storage systems running Data ONTAP 8.0 Cluster-Mode, and
external relationships on storage systems running Data ONTAP 8.0 Cluster-Mode cannot be
discovered by Protection Manager.
Cannot import some external relationships from a qtree on the same

source volume
Protection Manager cannot import both a volume-to-volume SnapMirror relationship and a backup
relationship 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 migration

If you abort a migration that is using NDMP, a stale SnapMirror relationship might be left on the
migration source storage system.
Workaround
None.
Open Systems SnapVault relationship baseline is not registered as a

backup version
When Protection Manager creates a new SnapVault relationship that uses extended ASCII characters
in the source Open Systems SnapVault directory path, the relationship gets created but a baseline
backup 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 to
match 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 the
next scheduled job to run. These options work because neither on-demand or scheduled jobs require
extra information from the storage system to create a backup version.
Incorrect dataset conformance status is displayed when the protection

status is "Baseline Failure"
When Protection Manager displays the protection status "Baseline Failure" for a dataset, the
conformance status might be displayed incorrectly as "Conformant" for that dataset when the dataset
is not, in fact, in conformance.
Workaround
None.
Operations Manager and Protection Manager display different qtree and

volume counts
The Protection Manager count of a group's qtrees and volumes differs from the Operations Manager
count of a group's qtrees and volumes.
The qtree count differs because the NetApp Management Console count includes root qtree0 in every
volume, and the Operations Manager count does not. The volume count differs because the
Operations 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 and
Unprotected Data panel in the Protection Dashboards window. In Operations Manager, this
information is displayed in the Group members panel on the Group Summary tab.
Workaround
None.
Relationship create jobs fail to register baseline version on destination

storage systems running Data ONTAP 7.2.3 or earlier
Protection Manager does not support registering the SnapVault baseline backup versions with
destination 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 baseline
backup transfer will not register the baseline backup version if the secondary or tertiary storage
volume 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 versions
accordingly.
Resizing of disaster recovery volumes for conformance after failover

Failover might cause the newly activated volumes in the disaster recovery node to fall into
nonconformance.
This occurs in the following case: Thickly provisioned primary volumes are assigned a provisioning
policy that specifies volume space guarantee, and their NAS backup volumes on the disaster recovery
node 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 than
required 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 storage
volumes, you need to resize them to free enough space on the containing aggregate to support the
volume 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 much
volume resizing is possible.
• Reduce the size of the disaster recovery node volumes, making sure that the containing aggregate
has enough free space to support the volume space guarantee and the volume has enough space
for data plus Snapshot copies.
Note: The common formula to estimate the space requirement for data plus Snapshot copies
for a volume is to multiply the probable data space requirement by 1.3. If necessary, delete
unnecessary Snapshot copies from the disaster recovery node volumes to reduce volume space
requirements.
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 is
a number.
Restoration to conformance dataset members with deleted baseline

Snapshot copies
If the baseline Snapshot copy for a protected dataset member is deleted, its dataset becomes
nonconformant and data protection operations are suspended.
For example, because Data ONTAP has a limit of 255 Snapshot copies on a volume, it is possible for
Data ONTAP to delete a protected volume's baseline Snapshot copy if that limit is reached. If this
happens to a member of a dataset, then Protection Manager displays the following nonconformance
error 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 new
baseline 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 the
following 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 destination
objects 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 objects
in 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 the
following command:
dfpm dataset status data-set
Support for Windows path names containing non-ASCII characters

Protection Manager supports Windows path names that contain non-ASCII UTF- 8 characters only
for storage systems that are running Data ONTAP 7.3.1 or later or hosts that are running Open
Systems SnapVault 2.6.1 or later.
Hosts require Open Systems SnapVault 2.6.1 or later. Storage systems require Data ONTAP 7.3.1 or
later.
Spare disk capacities are not counted as "available size" for a resource
pool
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 when
displaying "available size" for that resource pool.
Workaround
None.
Aggregate "Nearly full" and "Full" threshold settings are not used to
determine whether an aggregate should be excluded as a resource in a
dataset
The "Nearly full threshold" and "Full threshold" parameters only specify the thresholds at which the
provisioning application generates warning and error events regarding used space on aggregates in a
resource pool. The settings are not used to determine whether an aggregate should be excluded as a
resource in a dataset.
For example, if a resource pool contains an aggregate whose used space exceeds the "Nearly full
threshold" or "Full threshold" settings, and you attempt to add that resource pool to a dataset, the
conformance check performed when adding the resource pool will not exclude that aggregate as a
resource 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 the
Operations Manager settings, rather than on the Protection Manager "Nearly full threshold" and "Full
threshold" 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, then
back 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 tertiary
node will fail.
If you need to support both deduplication and the "Mirror, then back up" protection policy, disable
the global dpDynamicSecondaryResize option in the Operations Manager. Disabling this option
causes 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 name

contains spaces
If the name of an Open Systems SnapVault primary directory contains spaces, you cannot get data
protection transfer reports for those Open Systems SnapVault relationships.
Workaround
None.
Known issues and limitations with Provisioning Manager

Some 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 this
release of the DataFabric Manager server.
Next topics
Some dataset migration details are not displayed after migration cutover on page 43
dump on page 26
vFiler unit migration cutover fails when source volumes are full on page 44
The migration feature allows you to start unnecessary duplicate cleanup and cancel
jobs 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 or
rollbacks on page 45
The vFiler unit on the destination storage system is destroyed when cutover fails in the reincarnate
phase 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 cutover
phase 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 cutover
After migration cutover is complete, the Details tab on the Datasets window Migration tab does not
display some details about the migrated dataset.
The following details, normally displayed during other migration operations, are not displayed after
migration 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, the
state is normally "broken off."
Status The status of the source-destination protection relationship. After cutover, the
status is normally "idle."
Even though no data for these details is displayed, the "migrated, cleanup required" state indicates
that the cutover is successful.
Workaround
No workaround is necessary. After migration cutover is complete, you can proceed with the
migration cleanup or migration rollback operations.

perform a core dump
Workaround
backwards.
vFiler unit migration cutover fails when source volumes are full
If source volumes undergoing migration are full and the cutover operation is started, the cutover
operation fails with an error message "process was aborted." This failure occurs because full source
volumes leave no room for the Snapshot copies that the cutover operation requires.
Workaround
If this problem occurs, free some space in the source volumes and retry the cutover operation.
The migration feature allows you to start unnecessary duplicate cleanup

and cancel jobs
If you click either the Clean up button or the Cancel button on either the Datasets window
Migration 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 cancel
migration 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 or
duplicate 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 multiple
times. Doing so might cause the DataFabric Manager server to crash.
Changing the IPspace of a vFiler unit causes migration cutover to fail

Changing the IPspace of a vFiler unit during or after a migration start operation causes migration
cutover to fail.
Workaround
After migration of a vFiler unit is started, avoid changing its IPspace until after the post migration
cleanup operation is complete.
Volume-based SnapRestore during migration cutover causes failure

Running 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 data
migration 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. After
the cancel operation is complete, stop the VBSR operation and retry the cutover or rollback
operation.
Migration rollback fails if the migrated source volume contained no

Snapshot copies
If a migration rollback operation is necessary after the cutover operation, it fails if a source volume
contained 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 protection
operations; however, they might not exist if normal data protection operations are not enabled, or if
the data in the source volume is newly imported and no scheduled protection operation has yet taken
place.
Workaround
You can confirm the existence of Snapshot copies for any source volume before starting migration by
clicking the "Delete Snapshots" button on the Provisioning tab and viewing the Snapshot copy
listing in the dialog box.
Newly added quotas are not migrated during rollback and subsequent
cutover 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 to
the destination during subsequent cutovers.
Workaround
None.
The vFiler unit on the destination storage system is destroyed when

cutover fails in the reincarnate phase
When cutover fails in the reincarnate phase during online migration, the vFiler unit on the destination
storage system cannot be used. This is because Provisioning Manager destroys the vFiler unit on the
destination 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 unit
Although a dataset with CIFS policy cannot be created for online migration, you can attach the
dataset to a vFiler unit and perform online migration. However, during an active CIFS session, you
cannot detect the vFiler unit and perform online migration. The cutover operation fails with the
following error message: The "-t minutes" option must be specified when
terminating CIFS from rsh.
Workaround
Specify the -t minutes option while ending any CIFS session in Data ONTAP and retry cutover
operation.
Long-running operations not associated with the migration fail during the
cutover phase
Provisioning Manager detects long-running operations that hold active volume references during the
cutover 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 operation

During vFiler unit migration, the rollback operation fails in 7-Mode storage systems.
Backup initiated during cutover operation might fail

If you initiate a backup during the cutover operation of a vFiler unit online migration, the backup
operation might fail.
Online migration fails between a FAS system and an IBM N series storage
system
You cannot perform online migration from a FAS system to an N series system or from an N series
system to a FAS system.
Cannot clone volumes in a migrated vFiler unit

Volumes within a migrated vFiler unit on a SnapDrive host cannot be cloned if the
vfiler.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 blocked

Data access to a migrated vFiler unit can be blocked if the trusted.hosts option on the destination
hosting storage system is set to specific hosts and the migrated vFiler unit has the
httpd.admin.access option set to legacy.
Workaround
Set the trusted.hosts option on the hosting storage system to * or to hosts that access data from
the migrated vFiler unit.
Qtree details do not appear after DR failover

After completion of the failover process, the Provisioning tab does not display space information for
qtrees in the failed-over dataset. Even if the failover is successful, the Total space and Available
space 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 disaster
recovery node has probably succeeded and the secondary qtrees probably contain backup data from
the last update before the failover. This data is probably ready for restoration to or resynchronization
with the original primary containers.
To confirm the success of the last mirror or backup job on the failed-over dataset, see the System
Jobs window.
To confirm the success of the failover process as a whole, see the dataset's Failover status on the
Disaster Recovery tab.
Management Console can set but not modify the vFiler unit root password
You can use the Add vFiler Unit wizard or the Setup vFiler Unit wizard to set the password for the
root user of a newly created vFiler unit. After you specify the root password and use it to access the
vFiler 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 UNIX
workstation, 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 | 49
Changes to published documentation

There are changes to the documentation provided with this release of DataFabric Manager. This
information 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 and
management" 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, and
Provisioning Manager) supports the Web services feature and Web services APIs. These Web
services APIs, defined in the WSDL file, use SOAP 1.2 over HTTP or HTTPS. You can use
various SOAP toolkits, such as gSOAP, Axis, Apache CXF, and Perl SOAP::Lite, to develop a
Web service application from the WSDL file. The WSDL file, dfm.wsdl, is packaged with
DataFabric 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, which
you 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 "What
is new in this release" chapter:
Larger Aggregates: DataFabric Manager 4.0 provides support for larger aggregates for maximum
aggregate size of 64-bit aggregates.
• The link, http://now.netapp.com/ NOW/products/interoperability/, in "Prerequisites to manage
targets 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 migration
Online migration in ATA, SATA, FC, SAS, and BSAS based disks
Provisioning Manager allows online migration between systems with ATA, SATA, FC, SAS, and
BSAS 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 from
higher-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
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 ONTAP
Storage 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 to
disable 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 the
DataFabric Manager server to enable the corresponding functions. You do not need to indicate which
license 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 software

requirements" topic should be replaced with http://now.netapp.com/matrix/.
Where to find product documentation and other information | 51
Where to find product documentation and other

information
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 and
Operations Manager.
To learn about... Go to this information source...
New features, enhancements, and known issues in this Release Notes and the Administration Guide for each
release product
How to monitor and manage multiple NetApp Operations Manager Administration Guide and the
systems, storage resources, user quotas, File SRM, Operations Manager Help
content distribution, and appliance configuration
How to download and install NetApp Management Installation and Upgrade Guide
Console
How to use the Performance Advisor application to Performance Advisor Administration Guide and the
view performance data and customize the tools; also, NetApp Management Console Help
how to use the statistical counters for storage system
performance that are contained in Data ONTAP
The workflows you might use in Provisioning The workflow examples in the Provisioning Manager
Manager and Protection Manager to provision space and Protection Manager Guide to Common
and protect data, using real-life scenarios Workflows for Administrators
The tasks involved when you use the Protection Protection Manager and Disaster Recovery Help in
Manager application to set up and manage both your NetApp Management Console
data protection relationships and disaster recovery
capability, as well as related concepts and reference
information
The tasks involved when you use the Provisioning Provisioning Manager Help in NetApp Management
Manager application to provision space for your data, Console
as well as to monitor and manage space utilization
How to back up and recover data using Backup Operations Manager Administration Guide, the
Manager and Disaster Recovery Manager Operations Manager Help, and the NetApp
Management Console Help
To learn about... Go to this information source...
How to use the DataFabric Manager, Backup The manual (man) pages in the Operations Manager
Manager, Content Management System, Provisioning Help
Manager, Protection Manager, and Disaster Recovery
Manager commands
How to troubleshoot and maintain the physical The FAQ (in the Operations Manager Help and on the
resources of a system DataFabric Manager 4.0 Documentation page), the
troubleshooting module in the Help, and Operations
Manager Administration Guide
Any other topic of interest The DataFabric Manager FAQ (in the Operations
Manager Help and on the DataFabric Manager 4.0
Documentation 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.
Online Included with your DataFabric Manager software is a Web-based

documentation administration tool, Operations Manager, and its Help.
Included with your NetApp Management Console software is Help for
Provisioning Manager, Protection Manager, and Performance Advisor.
You can also obtain online documentation and answers to frequently asked
questions from the NOW site.
Other resources The NOW Natural Language PowerSearch tool on the Service and Support
page on the NOW site enables you to search the following sources of
information:
• 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-licensed
packages, which are available at ftp://ftp.netapp.com/frm-ntap/opensource.

OpsManager Rnote

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OpsManager Rnote

Caricato da

Copyright:

Formati disponibili

Release Notes

For Use with DataFabric® Manager Server 4.0,

Setting the clock backwards causes the DataFabric Manager server to

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

The migration feature allows you to start unnecessary duplicate cleanup

Known issues with Data ONTAP

Snapshot query fails in a scaled cluster setup

Issue with determining the storage capacity of the default

SNMP timed out error message

Data ONTAP is unable to perform SnapVault activities on a

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

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

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

System panics due to deleted vFiler user groups

New and changed features

Operations Manager features

NetApp Management Console changes

Provisioning Manager features

Protection Manager features

Performance Advisor features

Known issues with DataFabric Manager

Known issues with installation and upgrade

Delay in upgrading from DataFabric Manager server 3.2 or earlier

• Merging rotating history tables

Delay in upgrading from DataFabric Manager 3.5 or earlier

The dfm report view command fails

Cluster group in VCS setup fails

Cluster setup scripts in Windows 2008 fail

Upgrade to DataFabric Manager 4.0 from DataFabric Manager 3.8 on

Known issues with Operations Manager

IPv4-mapped IPv6 addresses are not supported on page 27

Slow response time for Performance Summary reports in a scaled setup

Striped aggregates are not displayed in the Aggregate custom report

Volume backup fails from the Operations Manager UI

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

Source aggregate is detached from the DataFabric Manager resource group

Setting the clock backwards causes the DataFabric Manager server to

DSN is not created on Windows

Restoration of the DataFabric Manager database fails in DataFabric

IPv6 source address is incorrectly displayed in the trap receiver

IPv4-mapped IPv6 addresses are not supported

Inconsistent capacity graphs

rsh commands fail on Windows Server 2008

Workaround 2: Configure RSH protocol on the DataFabric Manager server

b. Enter the following command:

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

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

Some DataFabric Manager CLI commands fail on Windows Server 2008

IPv6 link-local address is not supported

DataFabric Manager database stops responding on a VMware server

Incorrect interface reporting during failover

Unusable database on the DataFabric Manager server

Delayed display of Snapshot-based backup list

Issue with Snapshot-based backups on Linux

Inconsistent display of disk names for failed-over nodes

Limitations of LUN management

Known issues with Performance Advisor

Delayed CLI response to the dfm perf clientstat collect command

Delayed UI response on the Set Up Hosts window

Delayed UI response in advanced views

Setting the clock backwards causes the DataFabric Manager server to

Data ONTAP panic during Performance Advisor data collection