Professional Documents
Culture Documents
Always check the EMC Online Support site https://support.emc.com for the latest version
of this document. Any printed or CD-based version of this document may be out of date.
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Please send your opinions of this document to
DPAD.Doc.Feedback@emc.com.
l
l
l
l
l
l
l
l
RELEASE NOTES
For detailed information on installing DD Boost for OpenStorage, see the Data Domain
Boost for OpenStorage Administration Guide. For upgrade information, see the Data Domain
Boost Compatibility Guide.
Note
For information about accessing DD Boost documents on the EMC Online Support site,
see DD Boost for OpenStorage Documentation on page 7.
On HA-enabled Data Domain systems, failovers of the DD server occur in less than 10
minutes. However, recovery of DD Boost applications may take longer than this,
because Boost application recovery cannot begin until the DD server failover is
complete. In addition, Boost application recovery cannot start until the application
invokes the Boost library.
MFR will fail over seamlessly when both the source and destination systems are HAenabled. MFR is also supported on partial HA configurations (that is, when either the
source or destination system is HA-enabled, but not both) when the failure occurs on
the HA-enabled system. For more information, see the EMC DD Boost for OpenStorage
Administration Guide.
Dynamic interface groups should not include IP addresses associated with the direct
interconnection between the active and standby Data Domain systems.
Consult the EMC Data Domain DD Boost Compatibility Guide for compatible backup
applications, FC HBAs and switches supported in DD OS 5.7 (available Q4 2015).
Dynamic Interface Groups Support for Managed File Replication and Network Address
Translation
The Dynamic Interface Groups (DIG) policy engine has been updated to support
clients on subnets that reside behind network address translation (NAT) gateways.
This innovation allows the Data Domain system to decipher DD Boost client IP and
DDR IP addresses modified by NAT, which allows these client groups to take
advantage of features such as load balancing and failover. The enhancement applies
in these situations:
l
IPv4 or IPv6.
Includes all SDK versions (v3.0, v3.1 & v3.2) that support DD OS 5.7.
Dynamic Interface Groups are now available for DD Boost managed file replication
(MFR). Dynamic interface groups with MFR provide greater replication performance
via link aggregation and better resiliency through link failover with these features:
l
l
NAT translation support between source and target Data Domain systems.
Available to all DD Boost ecosystem partners that support MFR and DD OS 5.7.
See the EMC Data Domain Boost for OpenStorage Administration Guide, the EMC Data
Domain Operating System Command Reference Guide, and the EMC Data Domain
Operating System Administration Guide for details.
DD Boost Hard Stream Limits per Storage Unit
Users now have the ability to set hard stream limits per MTree or storage unit.
l
Hard stream limits are configured and enforced at the storage unit or MTree
level.
RELEASE NOTES
The DD Boost client notifies the application if it has exceeded the limit.
Import-to-Client Feature
The import-to client option is applicable when the AIR filecopy feature has been
configured to run, and it lets you specify a single NetBackup media server client to
receive AIR filecopy events from the target Data Domain system.
Bug #
Description
146540
This release fixes the issue in which the user's system would experience a file
system panic during a DD Boost backup when the client attempts to correct certain
fanout errors.
152811
After a DDOS 5.5.x.x and 5.4.2.x upgrade, the Data Domain system is hard-coded to
use an NFS_FILECOPY_TIMEOUT of 43200 (12 hours) for NetBackup Auto Image
Replication (NBU AIR). Even if the NFS_FILECOPY_TIMEOUT is set to a value larger
than 43200, the setting will not be honored and will default back to 12 hours. For
some environments, a 12-hour timeout may be insufficient, and a longer timeout
will be required. Refer to KB article 18302 for additional information for this
workaround.
While running a full system accelerator backup with forced rescan and change journal
options, NetBackup may fail with error 27 (child process killed by signal). This is a
known problem (ETrack 34211834). There is an EEB for 7.5.0.7 and 7.6.0.2. It will be
fixed in 7.6.0.3.
High Availability
Backup jobs run from AIX clients to HA systems via Fibre Channel do not survive an
HA failover. AIX clients work the same way on an HA pair as they do on a single-node
systemthe AIX device driver does not recognize changes to the fiber environment
once loaded into memory. To have the AIX client recognize the new server, run these
two AIX-specific commands on the client:
This issue is resolved by Oracle patch 150531-01 for Oracle Solaris on SPARC (32-bit).
Starting with the DD Boost 3.0 plug-ins, a plug-in code change is being made to avoid the
crash by reverting to a much lower performance software only method. The system log
will still show the messages as above and the backup performance will be seriously (2x)
degraded in performance.
Known Workarounds:
1. Disable distributed segment processing for Sparc.
2. An upgrade to Solaris 11 may correct the problem.
Note
DSP is enabled by default on Solaris SPARC T5 clients running on Solaris 11 (with SRU2
or later) or Solaris 11.1 or later.
NetBackup
l
NetBackup 7.x accelerator requires an external types file to enable accelerator. The
external types file requires a Data Domain specific entry to enable accelerator on a
Data Domain system.
The resolution for this issue is to apply the updated external types file available from
Symantec:
UNIX/Linux: http://www.symantec.com/docs/TECH203427
Windows: http://www.symantec.com/docs/TECH203428
In versions of NetBackup prior to 7.5.0.4, jobs may fail with a message such as:
Automatic Image Replication (AIR) jobs may fail in the case where the target Data
Domain system has insufficient inbound opt-dupe streams. NetBackup starts the AIR
process for each file of an image set in parallel. The plug-in has no control or visibility
into how many. In the case where the source Data Domain system has insufficient
outbound opt-dupe streams, the plug-in is able to retry each file as resources become
Known Issues and Workarounds
RELEASE NOTES
available. However, in the case that the target Data Domain system has insufficient
inbound opt-dupe streams, the opt-dupe job fails with no retry. This problem can
happen in two general cases:
n
In the case of one source Data Domain system to one target Data Domain
system, the target opt-dupe target stream count is less than the source optdupe source stream count. This can happen when a large Data Domain system
(DD890, for example) is the source, and a small Data Domain system (DD640, for
example) is the target.
In the case of two or more source Data Domain systems to one target Data
Domain system, the target opt-dupe target stream count is less than the sum of
all source opt-dupe source stream counts. This can happen in the case of
multiple Data Domain systems (three DD670s, for example) opt-duping to a single
Data Domain system (DD670, for example).
If AIR imports begin failing after upgrade, destroy the association then re-create it.
For NetBackup customers using the AIR feature with a large number of policies
associated with a single LSU, a feature is available that may improve performance.
For more information, contact EMC Online Support at https://support.emc.com.
Backup Exec
l
Backup Exec can only initiate managed file replication from a Single Node Data
Domain system. It cannot initiate managed file replication from an Extended
Retention Data Domain system due to a problem with fast-copy making the phantom
file.
details. EMC Data Domain will be enabled in the latest external_types file
upon the completion of our qualification with the Symantec HCL.
RELEASE NOTES
Copyright 2016 EMC Corporation. All rights reserved. Published in the USA.
Published March, 2016
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
8