NetWorker Module For Databases and Applications 8.2 and Service Packs Releas

Release Notes
® ®
EMC NetWorker Module for Databases and
Applications
Release number 8.2 and Service Packs
Release Notes
302-000-386
REV 06
July 13, 2015
These release notes contain supplemental information about EMC NetWorker Module for
Databases and Applications (NMDA) release 8.2 and Service Packs.
NOTICE
Before you install NMDA and periodically after the installation, refer to the latest revision of
this document on EMC Online Support at https://support.emc.com. On the Support by
Product page, search for NMDA by typing the full product name in the Find a Product field.
The product page provides the product-specific downloads, documentation, and additional
content and tools.
Topics include:
l Revision history......................................................................................................... 2
l Product description....................................................................................................3
l New features and changes......................................................................................... 6
l Fixed problems........................................................................................................ 11
l Environment and system requirements.................................................................... 12
l Known problems and limitations..............................................................................13
l Technical notes........................................................................................................24
l Documentation........................................................................................................ 33
l Software media, organization, and files................................................................... 34
l Installation.............................................................................................................. 34
l Troubleshooting and getting help.............................................................................35
l Compatibility matrix.................................................................................................36
Release Notes
Revision history
The following table presents the revision history of this document.
Revision Date Description

06 July 13, 2015 Updated the following information:
l Added the escalation number in the following
topic headings:
n 227747 (ESC 23153) on page 17
n 228292 (ESC 23260) on page 17
n 234458, 235572 (ESC 23787) on page 18
n 233072, 233552 (ESC 23496) on page 19
n 234431 (ESC 23780) on page 20
l Updated information in the following topics:
n 234458, 235572 (ESC 23787) on page 18
n 233072, 233552 (ESC 23496) on page 19
l Compatibility matrix on page 36 - Updated
details in the compatibility matrix.
05 June 30, 2015 Added to Known problems and limitations:

l 227747 on page 17, "DB2 backups might
continue to fail after a network disconnection
causes a backup failure"
l 228292 on page 17, "DB2 rollforward might
appear to become suspended"
l 234458, 235572 on page 18, "DB2 backups and
restores might fail due to DB2 10.5 and 10.1
issues"
l 233072, 233552 on page 19, "Notes database
restore might fail after scanner re-creates the
backup index"
l 234431 on page 20, "Lotus transaction log
backup fails if NSR_CATALOGFILE is set"
Updated the following information:
04 May 6, 2015 Updated the following information:

l MySQL and MEB support on page 13 - Added
information about the support of MEB 3.11.
Added to Known problems and limitations:
l 227400 on page 23, "Oracle backup with
postcommand script might fail"
03 January 28, 2015 Updated for the release of NMDA 8.2 SP1.
2 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
Revision Date Description

02 August 29, 2014 Updated the following information:
l Fixed problems on page 11 - Added the
following bugs to the table of fixed problems:
NW159657 (186596), NW160571 (186399),
NW161178 (191984), NW161337 (193052).
Updated the NW158246 problem summary.
l Table 5 on page 13 - Updated the list of
supported MEB versions in the table.
01 June 18, 2014 Initial release of NMDA 8.2.
Product description
EMC® NetWorker® Module for Databases and Applications (NMDA) is an add-on module
for the NetWorker server and client that provides backup and recovery services for DB2,
Informix, Lotus Domino/Notes, MySQL, Oracle, and Sybase ASE data.
NMDA replaces all the following legacy NetWorker modules on the supported UNIX, Linux,
or Windows operating systems:
l NetWorker Module for DB2 (NMDB2)
l NetWorker Module for Informix (NMI)
l NetWorker Module for Lotus (NML)
l NetWorker Module for Oracle (NMO)
l NetWorker Module for Sybase (NMS)
NOTICE
You can use NMDA to restore backups that were performed with the legacy NetWorker
modules.
You can use the existing legacy NetWorker module enabler to perform NMDA backups
after the upgrade.
Major configuration changes from legacy NetWorker modules to NMDA on page 4

describes major configuration differences between the legacy modules and NMDA.
New features and changes on page 6 describes the major new features and
enhancements in NMDA 8.2 and Service Packs. The appropriate release of the EMC
NetWorker Module for Databases and Applications Administration Guide describes all the
features that NMDA supports in the corresponding software release.
Environment and system requirements on page 12 provides information about the
supported versions of the NetWorker software.
Known problems and limitations on page 13 describes the known problems and
limitations in NMDA 8.2 and Service Packs.
Technical notes on page 24 describes existing NMDA features that require special
considerations or require a later version of the NetWorker software.
Product description 3
Release Notes
Documentation on page 33 describes the NMDA 8.2 and Service Packs documentation
and related documents. Installation on page 34 provides details about installing
NMDA.
Before you install NMDA, review the compatibility matrix at the end of this document and
the NMDA installation guide, administration guide, and other documentation at EMC
Online Support.
Major configuration changes from legacy NetWorker modules to NMDA

The following table compares the major configurations in the legacy NetWorker modules
and NMDA, and outlines any changes in those configurations.
You must set most NMDA parameters in the NMDA configuration file. The NMDA
configuration file templates are in the following directories:
l On UNIX and Linux: /nsr/apps/config
l On Windows: NetWorker_install_path\apps\config
Table 1 Configuration changes from legacy NetWorker modules to NMDA
Feature or parameter in legacy NetWorker module Corresponding feature or parameter in NMDA

NSR_DEBUG_FILE = debug_file_full_path. Replaced by NSR_DIAGNOSTIC_DEST =
debug_directory_full_path.
NSR_ENCRYPTION parameter. Parameter is dropped. Specify backup encryption through the

NSR_AES_ENCRYPTION parameter.
NetWorker Module for DB2 (NMDB2):
Scheduled backup (configured without the wizard) performed Replaced by scheduled backup (configured without the wizard)
through the nsrdb2sv -f configuration_file command. performed through the nsrdasv -z configuration_file
command.
Note
The NMDA configuration_file supports the NMDB2

configuration_file format.
Manual backup through the db2 commands. No change.
Restore through the db2 commands. No change.
DB2_PSWD parameter. Replaced by USER_PSWD parameter. Set the password value in

the parameter through the nsrdaadmin -P command.
DB2_USR parameter. Replaced by DB2_USER parameter.
NSR_DB2_BACKUP_INFO parameter. Replaced by NSR_DR_BACKUP_INFO parameter.

If NSR_DB2_BACKUP_INFO was not set,
NSR_DR_BACKUP_INFO is set to TRUE (default).
NSR_DB2_CONFIG_FILE parameter. Replaced by NSR_DR_FILE_LIST parameter.
NSR_*_DEBUG* parameters. Replaced by NSR_DEBUG_LEVEL parameter.
NetWorker Module for Informix (NMI):
Scheduled backup performed through the nsrdbmi shell/batch Replaced by scheduled backup performed through the
script. nsrdasv -z configuration_file command.
Release Notes
Table 1 Configuration changes from legacy NetWorker modules to NMDA (continued)

Manual backup performed through the onbar commands. No change.
Restore performed through the onbar commands. No change.
BOOTFILE parameter. Replaced by NSR_DR_FILE_LIST parameter.
DO_BOOTFILE_BACKUPS parameter. Replaced by NSR_DR_BACKUP_INFO parameter.
NetWorker Module for Lotus (NML):
Scheduled backup (configured without the wizard) or manual Replaced by scheduled backup (configured without the wizard)
backup performed through the nsrnotesv -z or manual backup performed through the nsrdasv -z
configuration_file command. configuration_file command.
Note
The NMDA configuration_file supports the NML configuration_file

format.
Restore performed through the nsrnotesrc -z No change.

configuration_file command.
Manual backup or restore performed through the NetWorker No change.

User for Lotus GUI (nwbml.exe) on Windows only.
Document-level recovery performed through the nsrdocrc -z No change.

configuration_file command.
Document-level recovery performed through the Notes client GUI No change.

on Windows only.
LOTUSUSER parameter. Replaced by LOTUS_USER parameter.
NetWorker Module for Oracle (NMO):
Scheduled backup (configured without the wizard) performed Replaced by scheduled backup (configured without wizard)
through the nsrnmo shell/batch script. performed through the nsrdasv -z configuration_file
command.
Manual backup performed through the Oracle RMAN interface. No change.
Restore performed through the Oracle RMAN interface. No change.
NSR_SB_DEBUG_FILE parameter. Replaced by NSR_DEBUG_LEVEL=1 parameter.
NetWorker Module for Sybase (NMS):
Scheduled backup performed through the nsrsyb shell/batch Replaced by scheduled backup performed through the
script. nsrdasv -z configuration_file command.
Manual backup performed through the nsrsybsv Replaced by manual backup performed through the nsrdasv
command_line_options command. -z configuration_file command.
Database consistency check performed through the nsrsybcc No change.

command_line_options command.
Restore performed through the nsrsybrc No change.

command_line_options command.
Major configuration changes from legacy NetWorker modules to NMDA 5

Release Notes
Table 1 Configuration changes from legacy NetWorker modules to NMDA (continued)

Manual backup or restore performed through the NetWorker No change.
User for Sybase GUI (nwbms.exe) on Windows only.
BACKUP_OPT parameter. Parameter is dropped.
-G, -R, and -T options of nsrsybsv command. Replaced by NSR_DUMP_LOG_OPT parameter.
-l option of nsrsybsv command. Replaced by NSR_BACKUP_LEVEL parameter.
-p option of nsrsybsv command. Replaced by NSR_PROMOTE_FULL parameter.
-P option of nsrsybsv command, or password setting in the Replaced by USER_PSWD parameter. Set the password value in
Client resource. the parameter through the nsrdaadmin -P command.
-r option of nsrsybsv command. Replaced by NSR_ASE_PASSWORD parameter.
-U option of nsrsybsv command, or remote user setting in the Replaced by SYBASE_USER parameter.
Client resource.
-V option of nsrsybsv command. Replaced by NSR_ASE_VERIFY parameter.
New features and changes

The following topics describe the new features and changes in NMDA 8.2 and the related
Service Packs.
NMDA 8.2 and Service Packs replace the previous NMDA releases on the supported
Linux, UNIX, and Windows operating systems. You can use NMDA 8.2 and Service Packs
to restore any backups performed with previous NMDA releases.
Note
Deprecated features are features supported in this NMDA release that will be removed
and unsupported in a future NMDA release.
NMDA 8.2 SP1

The following topics describe the major new or enhanced features of NMDA 8.2 SP1:
l Data Domain IPv6 support on page 7
l DB2 HADR support on page 7
l DB2 load with copy yes option support on page 7
l Sybase listonly option support on page 7
l Sybase restore parameter support on page 8
l Updated NMDA 8.2 SP1 parameters on page 9
The EMC NetWorker Module for Databases and Applications Release 8.2 SP1 Administration
Guide provides complete configuration details for the new features. The compatibility
matrix at the end of this document provides details about the supported environments.
Release Notes
Data Domain IPv6 support

NMDA 8.2 SP1 provides support for both the EMC® Data Domain® IPv6 and mixed IPv4
and IPv6 networks.
The EMC NetWorker Release 8.2 SP1 Release Notes provides information about the new
support of Data Domain IPv6 networks with NetWorker software.
DB2 HADR support

NMDA 8.2 SP1 supports DB2 backups and restores in a DB2 High Availability Disaster
Recovery (HADR) environment. The NetWorker scheduled backups always run on the
active node in the HADR environment.
IBM DB2 has the following restrictions with HADR support that impact NMDA
functionality:
l Multiple standby mode is available only with DB2 10.1 and later.
l HADR is not available in partitioned database environments.
l DB2 does not support backups on the standby host, even if the Reads on Standby
(ROS) feature is enabled.
l Tablespace-level restore or rollforward is not supported on either a primary or
standby database.
NMDA supports DB2 HADR configuration with and without Virtual IP (VIP).
NMDA has the following limitations with DB2 HADR support:
l You cannot use the NMDA wizard to configure an HADR backup in a VIP environment.
You must use the client-side manual configuration procedure through NMC.
l NMDA does not support DB2 HADR in a DB2 pureScale environment.
Guide provides details about how to configure and perform DB2 HADR backups and
restores.
DB2 load with copy yes option support

NMDA supports the use of the DB2 load command with the copy yes option to save a
copy of DB2 database changes during the load operation to NetWorker for later use in
the database recovery. Rollforward recovery must be enabled for the database before you
can use the copy yes option with the load command.
Guide provides details about how to use a load operation with the copy yes option to
save a load-copy file and use a rollforward operation to recover the file into a database.
Sybase listonly option support

NMDA 8.2 SP1 supports the use of the Sybase restore command, nsrsybrc, with the
listonly option for obtaining structure information from the latest backup of a Sybase
instance or databases, without restoring the backup.
Sybase ASE 15.7 ESD#2 and later provides the listonly option support.
Guide provides details about how to obtain the structure information from an NMDA
Sybase backup by using the Sybase listonly option.
NMDA 8.2 SP1 7

Release Notes
Sybase restore parameter support

In previous NMDA releases, the Sybase restore parameters were set as nsrsybrc
command line options, described in the EMC NetWorker Module for Databases and
Applications Command Reference Guide. These command line options are deprecated in
NMDA 8.2 SP1, and support of the command line options will be removed in the future.
NMDA 8.2 SP1 provides new support for Sybase restore parameters in the NMDA
configuration file. After setting the required restore parameters in the configuration file,
you can perform a Sybase restore/recovery with the nsrsybrc -z
configuration_file_path command.
This NMDA release provides separate configuration file templates for the Sybase backup
and restore parameters:
l nmda_sybase_backup.cfg—Template for Sybase backup parameters
l nmda_sybase_restore.cfg—Template for Sybase restore parameters
The following table lists the parameters that you can set in the NMDA 8.2 SP1
configuration file for a Sybase restore/recovery. The table also lists the corresponding
nsrsybrc command line options. The EMC NetWorker Module for Databases and
Applications Release 8.2 SP1 Administration Guide provides details about how to set the
Sybase parameters.
Table 2 NMDA Sybase restore parameters and nsrsybrc command line options
Sybase restore parameters in NMDA 8.2 Corresponding command line options

SP1
DATABASE_ONLINE (new parameter) nsrsybrc -p
NSR_ASE_PASSWORD nsrsybrc -r backup_password
NSR_ASE_VERIFY nsrsybrc -V {header | full |

verifyonly}
NSR_BACKUP_PATHS nsrsybrc { SYBASE:/ASE_server_name |

SYBASE:/ASE_server_name/database_name
[ SYBASE:/ASE_server_name/
database_name...] }
NSR_CLIENT nsrsybrc -c client_name
NSR_DEBUG_LEVEL nsrsybrc -D debug_level
NSR_DIAGNOSTIC_DEST (new parameter) Not applicable
NSR_DPRINTF (new debug parameter) Not applicable
NSR_ENCRYPTION_PHRASES nsrsybrc -e AES_pass_phrase
NSR_NWPATH Not applicable

NSR_RECOVER_POOL nsrsybrc -w recover_pool
NSR_RELOCATION_DEST (new parameter) nsrsybrc -d SYBASE:/ASE_server_name[/

database_name]
NSR_SERVER nsrsybrc -s server_name
NSR_XBSA_DEBUG (new debug parameter) Not applicable
Release Notes
Table 2 NMDA Sybase restore parameters and nsrsybrc command line options (continued)
Sybase restore parameters in NMDA 8.2 Corresponding command line options

SP1
RECOVER_LISTONLY (new parameter) nsrsybrc -l {load_sql | create_sql}
RECOVER_UNTIL (new parameter) nsrsybrc -m {up_to_min |

up_to_min_noskip} -t backup_time
STRIPE_DEVICE_DEST (new parameter) nsrsybrc -L temporary_file_pathname
SYBASE_USER nsrsybrc -U username
USE_CONSISTENCY_CHECK nsrsybrc -k
USER_PSWD nsrsybrc -P password
Updated NMDA 8.2 SP1 parameters

NMDA 8.2 SP1 supports the new parameter DB2_ACS_METADATA_DELETION_FORCE.
You can use this parameter to enforce the deletion of the DB2 snapshot metadata save
sets of a snapshot backup. You can enforce this deletion after a deletion of the
corresponding NSM snapshot backup succeeded in removing the snapshot save sets but
failed to remove the associated metadata save sets.
NMDA 8.2 SP1 also provides new support for the Sybase restore parameters described in
the preceding topic.
Guide provides complete details about all the supported NMDA parameters.
NMDA 8.2
The following topics describe the major new or enhanced features of NMDA 8.2:
l DB2 data recovery with the HPU utility on page 9
l Lotus transaction logs backup with multiple concurrent streams on page 10
l Oracle recovery wizard support of TNS_ADMIN environment variable on page 10
l Sybase network password encryption on page 10
l Updated NMDA 8.2 parameters on page 10
The EMC NetWorker Module for Databases and Applications Release 8.2 Administration Guide
provides complete configuration details for the new features. The compatibility matrix at
the end of this document provides details about the supported environments.
DB2 data recovery with the HPU utility

NMDA 8.2 introduces support for the IBM Optim High Performance Unload (HPU) utility,
which is a high-speed stand-alone utility that unloads, extracts, and repartitions backup
data into DB2 databases.
The HPU utility unloads data directly from an NMDA DB2 full, incremental, or delta
backup to staging files and then writes the data to output files for use with the DB2 load
utility. By reading the data directly from a backup image instead of through the DB2
software layer or database engine, the utility provides quick and efficient recovery of
discrete volumes of data.
NMDA 8.2 9
Release Notes
The IBM DB2 documentation provides details about HPU and how to create the control
file for HPU operations.
NMDA support of the HPU utility requires HPU 4.2 Fixpack 1 or later.
Lotus transaction logs backup with multiple concurrent streams

NMDA 8.2 introduces support for the backup of Lotus archived transaction logs through
multiple concurrent (parallel) streams during a full, incremental, or logs only backup. You
can improve the backup performance by specifying that multiple concurrent data streams
are sent to the NetWorker server for the backup.
For a logs only backup, you must set the NSR_PARALLELISM parameter or
corresponding wizard option to specify the maximum number of concurrent streams to
send to the NetWorker server. During a full or incremental backup, the parameter or
option that you set for the data backup is automatically used for the logs backup.
Oracle recovery wizard support of TNS_ADMIN environment variable

NMDA 8.2 enables you to set the Oracle TNS_ADMIN environment variable in the Oracle
recovery configuration wizard to specify a nondefault location for the tnsnames.ora
file. You need to set the parameter only if the file is not in the default location. The
tnsnames.ora file is required to enable the proper database connections during an
NMDA Oracle recovery.
Sybase network password encryption

NMDA 8.2 supports the Sybase network password encryption feature. This feature
encrypts login passwords for secure password transmission between the Sybase server
and client.
The Sybase network password encryption was introduced in Sybase ASE 15.0.2 ESD #2,
with support of a value from 0 to 2. A value of 1 restricts clients to use either the RSA
public key encryption algorithms or the Sybase proprietary algorithms. A value of 2
restricts clients to use only the RSA encryption algorithms.
Starting with Sybase ASE 15.7 ESD #2, the network password encryption also supports a
value of 3, which indicates that the server allows only incoming clients that use the EPEP
login protocol. The Sybase documentation provides more details about network
password encryption.
NMDA automatically encrypts the Sybase login passwords by using the algorithms
configured on the Sybase ASE server. No additional configuration is needed in NMDA.
Updated NMDA 8.2 parameters

NMDA 8.2 provides support for the new DB2 parameter SOURCE_DBNAME, which
specifies the name of the DB2 database used for a backup of the archived logs. The
parameter is mandatory for a rollforward recovery of the destination database after a
restore to a different database.
NMDA 8.2 no longer supports the NSR_NO_BUSY_ERRORS parameter. Use the
NSR_MAX_START_RETRIES parameter instead. You do not need to use this parameter
for regular operations, but only in the case of connectivity issues with the NetWorker
server.
The NMDA Oracle parameter NSR_RETENTION_DISABLED is unsupported. The
following results occurred if you used the parameter in a prior NMDA release:
Release Notes
l Backups remained on the backup device forever unless the DBA ran the delete
obsolete command on a regular basis with permissions to delete the backup
entries.
l Clone operations failed.
If you set the NSR_RETENTION_DISABLED parameter in an RMAN backup script, the
NMDA Oracle backup fails with an error message. Instead of using this parameter, either
you must use the NSR_ORACLE_RETENTION parameter if you use Oracle window-based
policies or you must set the NetWorker retention policies correctly going forward. The EMC
NetWorker Module for Databases and Applications Release 8.2 Administration Guide
provides details.
Fixed problems
The following topics provide details about the major fixes implemented in NMDA 8.2 and
the related Service Packs.
Fixed problems in NMDA 8.2 SP1

The following table lists the major fixes implemented in NMDA 8.2 SP1.
Table 3 Problems fixed in NMDA 8.2 SP1
Issue number Problem summary Application

203697 The 32-bit NMDA software files are missing in the 64-bit NMDA zipped download file on All
Windows.
NW161970 For DB2 NSM backups, the DB2 metadata save set is not removed when a point-in-time save DB2
set is removed or released.
NW161515 A misleading message "Unknown error category 211" might cause confusion with a Domino Lotus
backup failure.
NW161419 An Oracle backup might fail with the following error message when the nsrmmd process is Oracle
busy:
Volume ID 'volume_ID' is not in media database. (2:3:73)
NW161762 The nsrdasv program fails to correctly process the NLS_DATE_FORMAT parameter value that Oracle
contains spaces.
NW161809 NSR_ORACLE_RETENTION is not honored if the parameter is set by the wizard. Oracle
NW161962 Oracle backups complete successfully but do not release the FIPS140 resource correctly at the Oracle
end, which might cause Oracle to dump a core file.
NW160422 The nsrsybrc command does not permit spaces between the -P option and the password. Sybase
NW161343 An NMDA Sybase restore cannot find a backup performed during Standard Time when the Sybase
restore is performed during Daylight Saving Time.
Fixed problems 11
Release Notes
Fixed problems in NMDA 8.2

The following table lists the major fixes implemented in NMDA 8.2.
Table 4 Problems fixed in NMDA 8.2
Issue number Problem summary Application

NW154527, DB2 backup on Windows fails due to a db2sysc.exe process crash. DB2
186742
NW158246 The restore of a DB2 NSM snapshot backup might fail with a crash of the db2vend process. DB2
NW161337, DB2 redirected recovery with the db2 "rollforward db" command fails to recover the DB2
193052 transaction logs from the backup media.
NW155418 With the NSR_PREFETCH_LOGS parameter set to a nonzero value, a Lotus restore with the Lotus Domino
nsrdocrc command does not prefetch any transaction logs.
NW157119 Lotus recovery of a Domino .nsf file with many transaction logs does not stop when End Lotus Domino
restore is selected, and the recovery continues to completion.
NW160571, On Linux, a Lotus scheduled backup fails with a crash of the nsrdasv program when the Lotus Domino
186399 checkpoint restart option (CPR) is enabled.
NW161178, When you run the NetWorker User for Lotus GUI to recover a Lotus backup, the GUI might not Lotus Domino
191984 display all the backed-up files included in the backup.
NW154716 Oracle recovery configuration wizard fails if the Oracle TNS_ADMIN environment variable Oracle
specifies a nondefault location for the Oracle Net service files.
NW157752 NSR_RMAN_OUTPUT=SHELL setting on Windows does not generate the expected names for the Oracle
RMAN output log files.
NW159657, The nsrdasv program always returns a zero exit code for an Oracle backup failure. Oracle
186596
Environment and system requirements

As client-side products, NMDA and the NetWorker client must reside on each database or
application server that participates in the backup or restore. The NetWorker server and
storage node can reside on either the same system or separate systems.
Unless otherwise specified, NMDA requires the NetWorker server, storage node, and
client release 8.0 or later.
The compatibility matrix at the end of this document provides the current details on the
software that NMDA 8.2 and related Service Packs require, such as supported operating
systems and versions, database servers or application servers, NetWorker, and other
supporting software.
The EMC NetWorker Module for Databases and Applications Administration Guide for the
corresponding NMDA release provides details about the environment and system
configurations required to operate NMDA.
Release Notes
MySQL and MEB support

NMDA interacts with the MySQL Enterprise Backup (MEB) software to perform MySQL
backups and restores. You must install a supported version of MEB with the proper
version of MySQL as shown in the following table.
Table 5 MySQL and MEB version dependencies
MySQL version Supported MEB versions

5.1 3.6, 3.7, 3.8, 3.9, 3.10
5.5 3.6, 3.7, 3.8, 3.9, 3.10, 3.11
5.6 3.6, 3.7, 3.8, 3.9, 3.10, 3.11
The following considerations apply to NMDA MySQL operations and MEB dependencies:
l 32-bit MEB must be installed for 32-bit MySQL support, and 64-bit MEB must be
installed for 64-bit MySQL support.
l NMDA does not support the MEB 3.9 “copy-back-and-apply-log” operation.
l With MEB 3.11, NMDA does not support wizard configurations of the partial MySQL
backups of non-InnoDB databases. However, you can use the NMDA wizard to
configure the partial MySQL backups of InnoDB databases.
l With MEB 3.11, NMDA supports MySQL binary log backups only if you disable the
MEB log file backups by setting MYSQL_MEB_OPTIONS=--skip-binlog.
MySQL 5.6 support

NMDA supports MySQL release 5.6, including the new features except for the use of an
encrypted login file, mylogin.cnf, for setting the backup credentials.
NMDA support of new features in MySQL 5.6 requires MEB version 3.8.1 or later to be
installed on the MySQL server host. For a list of the new features supported only with MEB
3.8.1 or later, refer to the topic “Compatibility Note for MySQL Version” in the MySQL
Enterprise Backup User’s Guide for version 3.8.1 or later.
Known problems and limitations

The following tables list the known problems and limitations that apply to NMDA 8.2 and
the related Service Packs:
l Limitations in NMDA 8.2 and Service Packs on page 14
l Limitations in other products that affect NMDA 8.2 and Service Packs on page 15
The issues are grouped according to the specific application to which they apply. The first
group includes the common issues that apply to multiple applications.
When you contact Customer Service about an issue, use the listed issue number.
Unless the entry for a known limitation indicates that it is resolved for a specific release,
the limitation applies to NMDA 8.2 and all the Service Packs.
A resolved limitation is listed in the fixed problems table for the release in which it is
resolved.
MySQL and MEB support 13

Release Notes
Table 6 Limitations in NMDA 8.2 and Service Packs
Issue Description Operating Product feature Application

number system
224226 on On Linux, NMDA installations and operations fail if the Linux Installation, All
page 16 NetWorker client package is installed in a nondefault backup,
location.
restore
227747 (ESC After a DB2 backup fails due to a network disconnection All Backup, DB2
23153) on with the NetWorker server, subsequent DB2 backups archive
page 17 might continue to fail in certain cases.
228292 (ESC A DB2 rollforward operation might appear to become All Restore DB2
23260) on suspended if the NetWorker client file index includes
page 17 many entries for non-DB2 backups.
NW151464 on The savegroup report for a DB2 snapshot and rollover Linux Backup, DB2
page 18 backup does not include any save set information from NSM
the rollover part of the backup.
NW158881 on With 32-bit NMDA on AIX, an Informix backup fails with AIX Backup Informix
page 19 the following error message:
Dependent module /usr/lib/liblocktbl.so

could not be loaded.
233072, After the NetWorker backup index is re-created by using All Restore Lotus Domino
233552 (ESC the scanner program, a restore of a Lotus Domino
23496) on database backup might fail.
page 19
234431 (ESC If the NSR_CATALOGFILE parameter value is set in the All Backup Lotus Domino
23780) on configuration file or in the backup configuration wizard,
page 20 then a Lotus transaction log backup fails.
NW101758, A Lotus backup of 64-bit Domino on AIX might cause the AIX Backup Lotus Domino
NW113768 on Domino server to crash or become suspended or the
page 20 backup might fail with a specific error message.
NW121290 on A Lotus full database backup might expire before the All Backup Lotus Domino
page 21 dependent transaction log backups because NMDA
Lotus does not create dependencies between the
backups.
NW143964 on Conversion of a MySQL client-side to server-side Linux Configuration MySQL

page 21 configuration with the nsrdaadmin -W command conversion
fails.
NW148580 on When you run the nsrinfo command to obtain Linux Backup MySQL
page 21 information about MySQL backups, the command
displays an error message.
LGTsc06110 o Japanese Oracle backup information might be displayed All Backup, Oracle
n page 22 incorrectly in the NMC program. internationalization
NW150321 on NMDA Oracle save set bundling or policy uniformity fails All Backup Oracle
page 22 for a multinode Oracle RAC backup, but the backup is
successful and fully recoverable.
Release Notes
Table 6 Limitations in NMDA 8.2 and Service Packs (continued)

number system
227400 on An Oracle scheduled backup with a postcommand All Backup Oracle
page 23 script might fail if the script name starts with nsrnmodr.
NW105216 on If a Sybase manual or scheduled backup attempts to All Backup Sybase ASE
page 24 back up more than 200 databases, the backup might
fail.
NW146800 on A Sybase scheduled backup might fail if the Sybase All Backup Sybase ASE
page 24 server and NetWorker client run in different locales.
Table 7 Limitations in other products that affect NMDA 8.2 and Service Packs

number system
NW007000 on Due to a NetWorker limitation in non-English locales, All Configuration wizard, All
page 17 backup configuration with the wizard fails. internationalization
181210 on Due to a DB2 bug, if you use the HPU utility to unload All Restore DB2
page 17 and restore an NMDA DB2 incremental backup, then the
operation might fail with an error.
234458, Due to issues in DB2 10.5 and 10.1, such as APAR All Backup, DB2
235572 (ESC IT05079, a DB2 backup configuration in the wizard or a restore
23787) on scheduled backup might fail. A restore of tablespaces in
page 18 a DPF environment might fail.
NW152810 on Due to a DB2 bug, if you run a multisession DB2 backup All Backup DB2
page 18 and use the db2 prune command to delete backup
entries from the DB2 history file, the command might
leave some entries in the file.
NW154550 on Due to a DB2 limitation, NMDA does not delete the logs All Backup DB2
page 18 from the NetWorker server during a db2 prune
operation if the NMDA configuration file pathname in
the LOGARCHOPTn parameter exceeds 30 ASCII
characters.
NW019057 on Due to an Oracle limitation, Oracle backup problems All Backup, Oracle
page 22 might occur when the RMAN script contains non-ASCII internationalization
data.
NW152664 on Due to Oracle bug 17080042, a point-in-time recovery All Restore Oracle
page 23 of an Oracle 12c table, table partition, or pluggable
database (PDB) might fail if you use manual channel
allocation.
NW154492 on Due to Oracle bug 17770652, an Oracle 12cR1 Windows Backup, Oracle
page 23 container or pluggable database snapshot backup with NSM
NSM fails on Windows if some of the datafiles are not
located on a snapshotable device.
Known problems and limitations 15

Release Notes
Common NMDA problems and limitations

This section contains the NMDA problems and limitations that apply to all the
applications (DB2, Informix, Lotus Domino/Notes, MySQL, Oracle, Sybase) that NMDA
supports.
Installations and operations fail on Linux with NetWorker client installed in nondefault location
224226
On Linux, if the NetWorker client package is installed in a nondefault location, then
NMDA operations cannot load the FIPS140 shared libraries. As a result, the following
issues occur:
l The NMDA installation fails with the following error message:
Unable to load FIPS-140 module: The FIPS140 shared library could

not be found
The NMDA binaries are installed correctly, but the automated wizard registration fails
with the error.
l All other NMDA operations fail with the same error message, including backups,
restores, and backup deletions.
As a workaround, perform the following steps:
1. Run the following command as the root user to create the required symbolic link:
# ln -s /relocation_path/lib/nsr /usr/lib/nsr
2. If you want to use the NMDA wizard, then run the appropriate command from the
following table as the root user to register the wizard.
Note
To manually unregister the wizard, use the command from the table but replace the
option -i with -u.
Table 8 Command to register the wizard
Database or application Wizard registration command

DB2 nsrdb2ra -i
Informix nsrifmxra -i
Lotus nsrlotusra -i
MySQL nsrmysqlra -i
Oracle nsrorara -i
Sybase nsrsybra -i
3. To enable NMDA MySQL operations, run the following commands as the root user to
create the required symbolic links:
# ln -s /relocation_path/lib64/libmysqlapi.so.2 /usr/lib64/
libmysqlapi.so.2
# ln -s /relocation_path/lib64/libmysqlapiwrap.so /usr/lib64/
Release Notes
libmysqlapiwrap.so
# ln -s /relocation_path/lib/libnsrmysql.so /usr/lib/libnsrmysql.so
Backup configuration with the wizard fails in non-English locale

NW007000
Due to a NetWorker limitation in non-English locales, if the NetWorker server is installed
in a nondefault path that includes any non-ASCII characters, the configuration of a
backup with the wizard fails with the following error message:
Failed to open lockbox non-ASCII_dir_name\nsr\lockbox\client_name

\clb.lb
As a workaround, perform either of the following actions:

l Configure the backup manually with the NMC method, without the wizard.
l Ensure that the installation path of the NetWorker server does not include any non-
ASCII characters.
DB2 problems and limitations

This section contains NMDA problems and limitations specific to DB2 operations.
DB2 HPU restore might fail with an incremental backup

181210
Due to a DB2 bug, if you use the IBM Optim High Performance Unload (HPU) utility to
unload and restore an NMDA DB2 incremental backup, then the unload and restore
operation might fail with the INZU366I HPU return code 8 (reason code 0x283a001).
The DB2 bug is resolved in the following IBM HPU versions:
l HPU v4.2.1 FP1 with IF11 or later
l HPU v5.1 with IF8 or later
l HPU v5.1.0.1
DB2 backups might continue to fail after a network disconnection causes a backup failure
227747 (ESC 23153)
After a DB2 backup fails due to a network disconnection with the NetWorker server,
subsequent DB2 backups might continue to fail in certain cases because the libnsrdb2
shared library blocks the subsequent backups even when the network connection is
resumed.
Contact EMC Technical Support for a hotfix.
DB2 rollforward might appear to become suspended

228292 (ESC 23260)
A DB2 rollforward operation might appear to become suspended if the NetWorker client
file index includes many entries for non-DB2 backups. The rollforward operation
incorrectly searches index entries in all namespaces instead of searching only the
backup entries in the DB2 namespace, which might take an extended period of time.
DB2 problems and limitations 17

Release Notes
DB2 backups and restores might fail due to DB2 10.5 and 10.1 issues
234458, 235572 (ESC 23787)
Due to issues in DB2 10.5 and DB2 10.1, such as APAR IT05079, the following NMDA
operations might fail:
l The configuration of a DB2 scheduled backup in the wizard might fail.
l A DB2 scheduled backup might fail.
l A restore of tablespaces in a DPF environment might fail due to a change in the
vendor context input from DB2 with respect to the type of restore. The restore failure
produces the following error message:
No match for a database image file was found based on the source
database alias "database_name" and timestamp "backup_timestamp"
provided
DB2 snapshot and rollover backup does not report the rollover save set details
NW151464
When you use NMDA with NSM to perform a DB2 snapshot and rollover backup, the
savegroup report does not include any save set information from the rollover part of the
backup. The savegroup report includes information from the snapshot backup only.
DB2 prune operation might fail to delete all entries from DB2 history file
NW152810
Due to a DB2 bug, if you run a multisession DB2 backup and then use the db2 prune
command to delete the backup entries from the DB2 history file, the command deletes
the index entries on the NetWorker server but might leave some of the entries in the DB2
history file.
The DB2 bug is fixed in DB2 9.7fp4.
As a workaround, run the db2 prune command again without the and delete option
to delete the remaining entries in the DB2 history file. For example:
db2 prune history 20130605180753 with force option and delete

db2 prune history 20130605180753 with force option
DB2 prune operation does not delete the logs from the NetWorker server in certain cases
NW154550
NMDA does not delete the DB2 transaction logs from the NetWorker server during a DB2
prune operation if the NMDA configuration file pathname specified in the LOGARCHOPTn
parameter exceeds 30 ASCII characters. This character length limitation is a DB2
limitation. The LOGARCHOPTn parameter is set when configuring an automatic backup of
DB2 transaction logs.
The issue is a result of DB2 not setting the NMDA configuration file pathname correctly in
the Comment field of the corresponding DB2 history file record when the pathname
exceeds 30 ASCII characters.
As a workaround, you can perform the following steps.
1. Run the db2 update history command to update the Comment field in the DB2
history file to point to an NMDA configuration file pathname that does not exceed 30
ASCII characters.
Release Notes
For example, the following db2 list history command output shows that the
Comment field in the history file does not contain a valid NMDA configuration file
pathname:
db2 list history archive log all for db hat
List History File for hat
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID

-- --- ------------------ ---- --- ------------ ----------- ---------
X D 20130920133146 1 O S0000017.LOG C0000000
--------------------------------------------------------------------
Comment:
Start Time: 20130920133146
End Time: 20130920133155
Status: P
--------------------------------------------------------------------
EID: 25 Location: /usr/lib/libnsrdb2.so
You can run the following db2 update history command to update the
Comment field with a valid configuration file pathname:
db2 update history eid 25 with comment \"@/space/db2inst1/nmda.cfg

\"
2. Rerun the db2 prune command.

To prevent this issue in future archive log backups, use an NMDA configuration file
pathname that does not exceed 30 ASCII characters in the LOGARCHOPTn parameter.
Informix problems and limitations

This section contains NMDA problems and limitations specific to Informix operations.
Informix backup fails with 32-bit NMDA on AIX

NW158881
With 32-bit NMDA on AIX, an Informix backup fails with the following error message:
Dependent module /usr/lib/liblocktbl.so could not be loaded.
As a workaround, run the following command as root, to remove the following symbolic
link before you perform any Informix backups:
rm /usr/lib/liblocktbl.so
This link removal ensures that the 32-bit NMDA Informix library can locate the correct 32-
bit libraries.
Lotus Domino/Notes problems and limitations

This section contains NMDA problems and limitations specific to Lotus Domino/Notes
operations.
Notes database restore might fail after scanner re-creates the backup index
233072, 233552 (ESC 23496)
After the NetWorker backup index is re-created by using the scanner program, a restore
of a Lotus Domino database backup might fail. The failure is caused when the backup
index is not rebuilt correctly by the scanner program. The scanner program stops
Informix problems and limitations 19

Release Notes
rebuilding the backup index if a backup save set includes a file that was skipped during
the backup, for example, due to errors in opening the file.
Contact EMC Technical Support for a hotfix of the scanner and nsrdasv programs.
Lotus transaction log backup fails if NSR_CATALOGFILE is set

234431 (ESC 23780)
If the NSR_CATALOGFILE parameter value is set in the configuration file or in the backup
configuration wizard, then a Lotus transaction log backup fails.
Backup of 64-bit Domino on AIX might fail

NW101758, NW113768
An NMDA Lotus backup of 64-bit Domino on AIX might cause the Domino server to crash
or become suspended or the backup might fail with the following error message:
notes_sess_open: Exiting with error:

The call to NotesInitExtended failed: 433
To prevent the issues NW101758 and NW113768, perform the following steps on the AIX
Domino host after the NMDA software is installed:
1. Log in as the Notes user, run the following commands, and record the command
output:
> ulimit -a
> echo $LDR_CNTRL
2. Log in as the root user, and run the following commands:
# ulimit -a
# echo $LDR_CNTRL
# dump -o /usr/bin/nsrexecd
If any of the following conditions is true, perform step 3 on page 20 to step 5 on

page 21:
a. The data limit reported by the ulimit command for the root user is lower than for
the Notes user.
b. The LDR_CNTRL value for the root user is different than for the Notes user.
c. The output from the dump nsrexecd command contains the following
information:
maxDATA
0x80000000
3. Shut down the NetWorker client that is running on the Domino host by using the
nsr_shutdown command.
4. Perform the appropriate action, depending on the issues found:
a. Set the data limit for the root user to the same value as for the Notes user.
b. Set the LDR_CNTRL parameter for the root user to the same value as for the Notes
user.
c. Run the following ldedit command on the nsrexecd executable to decrease
the amount of memory that it uses:
# /usr/ccs/bin/ldedit -bmaxdata:0x00000000 /usr/bin/nsrexecd
Release Notes
5. Restart the NetWorker client.

If the issue occurs on the AIX Domino host before you have performed the preceding
steps:
1. Shut down the Domino server.
2. Reboot the whole machine.
3. Perform the preceding step 1 on page 20 to step 5 on page 21.
Lotus full backups might expire before dependent transaction logs

NW121290
NMDA Lotus does not create dependencies between any transaction log backups
(performed during an incremental backup or transaction log only backup) and full
database backups. As a result, a database backup might expire before the corresponding
transaction log backups. You cannot use the transaction log backups to restore and
recover the data without the full backup.
If you have encountered this issue with your backups, the backups expired from the
NetWorker online indexes might not be deleted immediately from the backup media. As a
workaround, run the scanner –i command or the nsrck –L7 command to rebuild
the online indexes so that you can still use full backups for restore operations.
To reduce the possibility of encountering this issue, set the browse policy and retention
policy of the Domino and Notes backups to a much longer time than the recovery point
objective (RPO). For example, if the RPO is 1 week and you perform full backups on
Sundays and incremental backups for the rest of the week, set the browse policy and
retention policy to 2 weeks for both full backups and incremental backups. This setting
ensures that the software retains the backups on the media to achieve the RPO of 1
week.
MySQL problems and limitations

This section contains NMDA problems and limitations specific to MySQL operations.
Conversion of MySQL client-side to server-side configuration fails

NW143964
When you use the nsrdaadmin -W command to convert a MySQL client-side
configuration to a server-side configuration, the conversion fails with the following error
message:
75525:nsrdaadmin: NMDA wizard conversion is not supported for

application type specified: 7.
As a workaround, use the wizard and select your existing client-side configuration file on
the Specify the NMDA configuration file template page to create a new configuration. You
can delete the old client-side configuration when the wizard configuration has completed
successfully.
The nsrinfo command does not display MySQL backup information

NW148580
When you run the nsrinfo command to obtain information about MySQL backups from
the NetWorker client file index, the command does not provide the backup information.
You need to use the nsrinfo command to obtain specific types of information about
MySQL backups, such as the binary log start number and log position information.
MySQL problems and limitations 21

Release Notes
The nsrinfo command used to query MySQL backup information displays the following
error message:
90955:nsrinfo: The MySQL client attributes could not be decoded.
As a workaround, update the NetWorker client software to release 8.0.1.3 or later.
Oracle problems and limitations

This section contains NMDA problems and limitations specific to Oracle operations.
Japanese Oracle backup information might be displayed incorrectly in NMC program

LGTsc06110
When a scheduled NMDA Oracle backup is run in a Japanese environment and the output
from RMAN or from a preprocessing or postprocessing script (used for the backup) is not
UTF8 text, the Japanese backup information displayed in the NMC program might appear
incorrectly as box or question mark characters.
As a workaround, perform the following actions:
l Use the NSR_RMAN_ARGUMENTS parameter to redirect the RMAN output to a
specified log file.
l Specify "echo off" in any preprocessing and postprocessing scripts used for the
scheduled NMDA Oracle backup.
Backup problems might occur due to non-ASCII data in RMAN script

NW019057
Due to Oracle bug 3627132, an NMDA Oracle backup might fail or some parameters
might be ignored in a non-English locale when the following conditions exist:
l NMDA internationalization is set up.
l The character sets of the RMAN script and Oracle database are different.
l A non-ASCII character is included in the parms option or send command in the
RMAN script.
For example, if the database uses the UTF8 character set and the RMAN script uses the
EUC-JP character set, an NMDA Oracle backup fails when the parms option or send
command in the RMAN script contains any non-ASCII data.
As a result, the NMDA software does not support non-ASCII data in the RMAN script when
the character set of the RMAN script (set through the NLS_LANG environment variable)
differs from the character set of the Oracle database in a non-English locale.
NMDA Oracle save set bundling or policy uniformity fails for multinode RAC backups
NW150321
If you configure the NMDA Oracle save set bundling or policy uniformity feature, then a
multinode Oracle RAC backup generates the following warning:
No information could be obtained from the backup piece file.
The backup is successful and fully recoverable, but the save set bundling or policy
uniformity feature fails.
As a workaround:
Release Notes
l On UNIX or Linux, create a symbolic link that points the /nsr/apps directory on
every RAC node to a file system pathname on a shared disk, which is accessible from
all the nodes.
l On Windows, set NSR_TMPDIR in the nwora.res file on every RAC node to a file
system pathname on a shared disk, which is accessible from all the nodes.
Oracle 12c point-in-time recovery might fail with manual channel allocation
NW152664
Due to Oracle bug 17080042, a point-in-time recovery of an Oracle 12c table, table
partition, or pluggable database (PDB) might fail if you use manual channel allocation
with the allocate channel command.
As a workaround, use automatic channel allocation with the configure channel
command for a point-in-time recovery of an Oracle 12c table, table partition, or PDB.
Oracle 12cR1 container or pluggable database snapshot backup fails on Windows if some datafiles
are not on a snapshotable device
NW154492
Due to Oracle bug 17770652, an Oracle 12cR1 snapshot backup of a container or
pluggable database on Windows fails when some of the datafiles are not located on a
snapshotable device.
For example, you run the following RMAN command to back up a database that consists
of datafiles 1 to 5, but datafiles 3 and 4 are not on a snapshotable device:
backup proxy
full
format '%d_%U'
database;
The backup fails with the following error message:
ORA-00600: internal error code, arguments:

[krbbbdr_inconsistent_pdbid]
As a workaround, exclude from the proxy backup any datafiles that are not on a
snapshotable device, and back up those datafiles in a separate backup command
without the proxy option.
For example, in the previous example where datafiles 3 and 4 are not on a snapshotable
device, run two separate backups by using the following separate RMAN commands:
backup proxy
full
format '%d_%U'
datafile 1,2,5;
backup
full
format '%d_%U'
datafile 3,4;
Oracle backup with postcommand script might fail

227400
You can use a postcommand script during an Oracle scheduled backup to back up files to
prepare an Oracle server for disaster recovery. The backup with the postcommand script
might fail if the script name starts with nsrnmodr.
Oracle problems and limitations 23

Release Notes
Sybase ASE problems and limitations

This section contains NMDA problems and limitations specific to Sybase ASE operations.
Backup of more than 200 databases might fail

NW105216
If a Sybase manual or scheduled backup attempts to back up more than 200 databases,
the backup might fail.
Note
The limit of 200 databases is based on a maximum size of 30 bytes for a Sybase
database name. The database limit might be higher for a backup of databases with
names of smaller sizes.
As a workaround, perform two or more smaller Sybase backups instead of one large
Sybase backup, where each smaller backup backs up fewer than 200 databases. For
example, perform one of the following operations:
l Perform two or more Sybase manual backups with the nsrdasv command, with
each nsrdasv command backing up fewer than 200 databases.
l Perform two or more Sybase scheduled backups that each back up fewer than 200
databases. For each backup, create a separate Client resource and separate
configuration file with each configuration file specifying a difference set of databases
for the backup.
Sybase scheduled backup might fail if Sybase server and NetWorker client run in different locales
NW146800
A Sybase scheduled backup might fail if the Sybase server and NetWorker client run in
different locales.
As described in the EMC NetWorker Module for Databases and Applications Release 8.2
Administration Guide, you must set the NSR_LOCALE parameter to the required locale in
the NMDA configuration file for a Sybase manual backup configuration or a client-side
scheduled backup configuration. However, NSR_LOCALE is not supported for a server-
side scheduled backup or a probe-based backup.
As a workaround for a server-side scheduled backup or a probe-based backup, you can
set the LANG environment variable in the NetWorker start script that is installed with the
NetWorker client software on the Sybase server host. For example on Linux, insert the
LANG setting lines at the beginning of the start script after the "#! /bin/sh" line:
#! /bin/sh
LANG=en_US.UTF-8
export LANG
Technical notes
This section provides supplementary technical notes for implementing NMDA 8.2 and the
related Service Packs. Some of these notes describe issues that are dependent on the
functionality of other products used with NMDA.
Release Notes
Client Direct backups and restores

NMDA supports Client Direct backups to an AFTD or DD Boost device. NMDA also
supports the Client Direct feature for NSM snapshot backups of DB2 or Oracle data to
these types of devices.
Client Direct operations with an AFTD
NMDA supports Client Direct backups to and restores from an AFTD. This support requires
specific NetWorker software, depending on the operating system:
l For an AFTD on UNIX or Linux, NetWorker server and storage node release 8.1 or later
l For an AFTD on Windows, NetWorker server and storage node release 8.0 or later
Client Direct operations with a DD Boost device
NMDA supports Client Direct backups to and restores from a DD Boost device over an IP
or Fibre Channel (FC) connection. NMDA supports the FC connection on all the platforms
where NetWorker 8.1 or later provides the same support.
NMDA support of Client Direct operations with DD Boost devices over FC requires the
following software:
l NetWorker server, storage node, and client release 8.1 or later
l Data Domain DD OS release 5.3 or later
Note
The latest versions of the EMC NetWorker Release Notes and the EMC NetWorker and EMC
Data Domain Boost Deduplication Devices Integration Guide provide details about
supported platforms and any limitations for the DD Boost over FC support.
For DD Boost over IP only, Client Direct backups require ONCplus version B.11.31.06 or
later installed on HP-UX 11.31.
Consider the following limitations for Client Direct backups:
l NMDA does not support Client Direct Lotus backups that are checkpoint restart
enabled due to the dependence of the checkpoint restart feature on the storage node
nsrmmd process to ensure that data is written to a device.
l NMDA does not support Client Direct backups to DD Boost devices for 64-bit Sybase
ASE 15.0.x on HP Itanium.
NMDA does not require any additional licenses to perform deduplication operations with
a DD Boost device, provided that the NetWorker server and Data Domain system are
configured and licensed for distributed segment processing through the DD Boost
license.
Client Direct snapshot operations for DB2 or Oracle data
NMDA supports Client Direct backups and restores with an AFTD or DD Boost device for a
DB2 or Oracle snapshot backup performed with NSM. By default, NMDA with NSM tries to
use the Client Direct feature for both of the following operations:
l Rolling over the snapshot to secondary storage during a snapshot and rollover
backup or a rollover-only backup
l Restoring from secondary storage during a restore from rollover
If a proxy host (mount host) is used, Client Direct operations occur between the proxy
host and the device. If a Client Direct operation is not possible, then the backup or
restore is automatically routed through the storage node.
Client Direct backups and restores 25

Release Notes
NMDA support of Client Direct snapshot backups and restores with NSM requires the
NetWorker server, storage node, and client release 8.1 or later.
Note
With NetWorker release 8.1 or later, the NSM feature integrates and replaces the previous
stand-alone EMC NetWorker PowerSnap™ Modules. NSM is available as part of the
NetWorker client software.
Configuration wizards
NMDA supports the following configuration wizards:
l Scheduled backup configuration wizards for all NMDA applications (DB2, Informix,
Lotus Domino/Notes, MySQL, Oracle, Sybase)
l Recovery configuration wizard for Oracle
Features supported with the Oracle wizards

NMDA includes wizards for configuring Oracle scheduled backups and Oracle recovery.
The configuration wizard also provides the recommended method to create and modify
an NMDA configuration for an Oracle snapshot backup with NSM. The wizard ensures the
correct sequence of configuration steps and the verification of configuration
dependencies.
NMDA support of the Oracle snapshot configuration wizard requires NMC release 8.1 SP1
or later. The NetWorker client release 8.1 or later with the NSM feature must be installed
on the NMDA host.
NMDA supports database authentication with an Oracle wallet (Oracle Secure External
Password Store) in the Oracle configuration wizard. When the wallet feature is set up for
the database connection on the NMDA host, you do not need to specify a database
username and password for the database credentials in the wizard.
NMDA also provides full support in the Oracle configuration wizard for operating system
authentication on UNIX and Linux systems. In the wizard, you can specify only the OS
username to use operating system authentication, which enables you to configure the
backup of any objects, such as an entire database, individual tablespaces and datafiles,
or archived redo logs only.
Features not supported with the wizards

The scheduled backup configuration wizards do not support the following features:
l Configuration of probe-based (event-based) backups
Note
When you create a NetWorker Client resource with the wizard, you can associate the
resource with a probe by selecting the Probe attribute in the Client resource in NMC,
outside of the wizard.
l Configuration of backups in active-active application clusters, such as DB2 Database
Partitioning Feature (DPF), Informix Multi-node Active Clusters for High Availability or
High Availability Clusters, Oracle Real Application Cluster (RAC), and Sybase ASE
Cluster Edition
Release Notes
Note
NMDA documentation uses the MACH acronym for both Informix technologies:
Informix Multi-node Active Clusters for High Availability and High Availability Clusters.
l Configuration of DB2 snapshot backups with NSM.
l Configuration of split-mirror-based backups of Oracle ASM data with EMC Replication
Manager
l Configuration of two different database backups in the same Client resource
l Modification of a backup configuration that was created with the wizard from a legacy
NetWorker module
l Modification of a client-side NMDA configuration that was created with the NMC
method (without a wizard)
Note
You must convert a client-side configuration to a server-side (wizard) configuration

before you can use the wizard to modify the configuration.
The Oracle recovery configuration wizard does not support the configuration of Oracle
RMAN scripts in a cluster environment.
Conversion of backup configurations

You must convert an existing legacy NetWorker module configuration, created with or
without a configuration wizard, to an NMDA configuration before you can use the
configuration with NMDA.
Major configuration changes from legacy NetWorker modules to NMDA on page 4
describes the configuration changes that occurred between the legacy NetWorker
modules and NMDA.
NOTICE
During the conversion of an NMDB2 4.0 or NMO 5.0 probe-based backup configuration,
the nsrdaadmin -M command does not update the NetWorker Probe resource
associated with the backup. You must update the Probe resource manually.
If you want to use the NMDA configuration wizard to modify an NMDA configuration that
was created without the wizard, you must convert the NMDA client-side (nonwizard)
configuration to an NMDA server-side (wizard) configuration.
Immediate cloning support

NMDA provides support of automatic cloning for an NMDA scheduled backup. You can set
a clone operation to start immediately after each save set in the group is backed up
(immediate cloning) or start only after all save sets in the group are backed up.
To enable immediate cloning in the Group resource, you can select the Clones attribute
and set the Clone Mode attribute to “Start on each save set completion”. The EMC
NetWorker Administration Guide provides details.
NMDA support of immediate cloning requires the NetWorker server release 8.1 SP1 or
later.
Conversion of backup configurations 27

Release Notes
Probe-based backups
NMDA supports probe-based (event-based) backups.
NMDA does not support probe-based backups for snapshot backups with NSM.
Backups and restores in cloud configurations

NMDA provides support for backups and restores in private or public cloud configurations
for all supported databases and applications.
NMDA provides the same cloud support as NetWorker, including an option to send the
application backup directly to a cloud device, if required.
The NMDA support of cloud backups and restores requires the NetWorker server and
client release 8.0 or later.
The EMC NetWorker documentation provides details about how to configure and perform
cloud operations.
Backup operations that Avamar deduplication does not support

EMC Avamar® deduplication operations do not support the following features:
l AES encryption, checksumming, or compression of deduplicated data through the
NSR_AES_ENCRYPTION, NSR_CHECKSUM, or NSR_COMPRESSION parameter,
respectively
If NSR_AES_ENCRYPTION, NSR_CHECKSUM, or NSR_COMPRESSION is set for a
deduplication backup, the NMDA software applies the AES encryption,
checksumming, or compression, respectively, to only the metadata that is stored on
the NetWorker storage node.
l Cloning or staging of deduplicated data on the Avamar server
Only the metadata (hash information) stored on the NetWorker backup volumes can
be cloned or staged. However, deduplicated data on the Avamar server can be
replicated to another Avamar server that has been configured as a replication node
by EMC Professional Services. Avamar documentation and the EMC NetWorker
Administration Guide provide details on replication of deduplicated data.
Avamar deduplication backups with NSM do not support the following operations:
l Backup of data in instant (PIT) backups
Note
NSM deduplication backups support only the backup of data that is rolled over to
secondary storage.
l Backup of raw devices or volumes
The NSM documentation provides details on any additional requirements and limitations
of the NSM deduplication backups and restores.
Support for multiple installations of multiple databases on the same host

Specific combinations of 32-bit and 64-bit application software can coexist on the same
64-bit AIX, HP-UX PA-RISC, Linux, Solaris SPARC, or Windows system. For example:
l 32-bit and 64-bit Lotus Domino server might be installed on the same 64-bit AIX
system.
Release Notes
l 32-bit Informix and 64-bit DB2 server might be installed on the same 64-bit Windows
system.
The appropriate application documentation provides details on the versions of 32-bit and
64-bit application software that can coexist on the same 64-bit system.
The NMDA support for 32-bit and 64-bit application coexistence on 64-bit systems
includes the following limitations:
l You cannot use the NMDA wizard to configure backups of 32-bit DB2 or 32-bit Lotus
on a 64-bit Windows system where 32-bit and 64-bit applications coexist.
l You cannot use the NMDA wizard to configure backups of 32-bit Lotus on a 64-bit AIX
system where 32-bit and 64-bit applications coexist.
l You cannot use the NetWorker User for Lotus program for backups or restores of 32-
bit Notes on a 64-bit Windows system where 32-bit and 64-bit applications coexist.
l 32-bit or 64-bit Sybase cannot coexist with DB2, Informix, Lotus Domino/Notes, or
Oracle on a 64-bit Windows system.
l You cannot relocate the software on a 64-bit Linux or Solaris SPARC system where 32-
bit and 64-bit applications coexist.
The EMC NetWorker Module for Databases and Applications Installation Guide describes how
to install and configure NMDA for 32-bit and 64-bit application coexistence on a 64-bit
system.
DB2 pureScale support

NMDA supports DB2 pureScale, which is an active-active application cluster with a
shared-disk architecture.
You can configure pureScale to automatically back up logs generated by each member
node, to the NetWorker backup device.
NMDA supports all the features of a DB2 pureScale system except the following features:
l Automatic failover during scheduled backups
l Backup configuration with the wizard
l Snapshot-based backups, due to DB2 limitations
NMDA support of DB2 pureScale requires DB2 release 10.1 or later on the operating
systems that support DB2 pureScale. Support of delta and incremental pureScale
backups requires DB2 10.5fp4 or later as required by DB2.
The IBM documentation and the compatibility matrix at the end of this document provide
details and requirements of the operating systems for DB2 pureScale.
Backup and recovery of Domino server fails with secured console

If a Lotus Domino server is configured with a secured (password-protected) console,
NMDA cannot back up or recover the Lotus databases.
Under these conditions, backups and recoveries fail and report the following error:
Notes Library initialization failed, error = 417
For backups and recoveries to succeed, you must remove the password protection for the
Domino server console by using the Domino Administrator program or the Set Secure
command. The Domino Administrator online help provides instructions on removing
password protection.
DB2 pureScale support 29

Release Notes
Lotus backup features

NOTICE
To use NMDA backups with 64-bit Domino on AIX, follow the steps in Backup of 64-bit
Domino on AIX might fail on page 20 before you perform the first backup.
Note
If DAOS backups were performed with the NetWorker save command, as required for the
NW112719 issue workaround in NMDA 1.0, then you must restore the DAOS backups
with the NetWorker recover command.
Lotus restartable backups

NMDA supports Lotus restartable scheduled backups through the NetWorker checkpoint
restart feature. This feature enables you to restart an NMDA Lotus backup from a known
good point called a checkpoint, avoiding the backup of any files that were successfully
backed up during the failed backup. The backup is restarted only within the restart
window of the backup group.
NMDA Lotus checkpoint granularity is always at the file level. The checkpoint option is
disabled for browselist save sets.
Note
NMDA Lotus restartable backups do not support Client Direct backups to Data Domain,
described in Client Direct backups and restores on page 25.
Child process termination for cancelled Lotus backups

If a Lotus manual or scheduled backup is cancelled while child processes are waiting for
writable volumes on the NetWorker server, the child processes might not be terminated.
To terminate the child processes, make available the writable volumes on the NetWorker
server, as requested by the Lotus backup. When the volumes become available, the
backup resumes and immediately fails, and the processes are then terminated.
Prevent memory allocation failure with 32-bit Lotus Domino restores on AIX
If an NMDA Lotus restore with 32-bit Lotus Domino on AIX involves multiple parallel
processes (for example, NSR_PARALLELISM is set to a value greater
than 1) and produces a memory allocation failure, set the environment variable value
EXTSHM=ON and rerun the restore, based on IBM recommendations.
For example, with 32-bit Domino on AIX:
l If an NMDA Lotus restore fails with a memory allocation error, set EXTSHM=ON on the
command line where you run the nsrnotesrc program.
l If an NMDA Lotus directed recovery through the NetWorker User for Lotus program
fails with a memory allocation error, uncomment the following line in the
nsrlotus_remrecov script:
EXTSHM=ON; export EXTSHM
Release Notes
Recovery report from NetWorker User for Lotus contains unexpected characters
When NetWorker User for Lotus is used to recover a Domino database that has non-ASCII
characters in its name, the file name might be displayed incorrectly in the GUI.
Note
On Windows, if the non-ASCII characters in the nsrnotesrc command line output are
not readable, ensure that you use the proper code page for the language. For example, if
the language is Spanish, type the following command to set the proper code page before
you use the nsrnotesrc command for recovery:
chcp 1251
Multiplexing for Oracle11g multisection backups is supported with AFTDs only

Due to Oracle11g and NetWorker limitations, NetWorker multiplexing for multisection
backups (a new feature with Oracle11g) is supported with AFTDs only, not with tape or
regular file type devices.
If you have tape or regular file type devices, you should configure a separate NetWorker
device for each RMAN channel to avoid multiplexing in NetWorker.
If you multiplex the Oracle11g multisection backups on a tape or regular file type device
and then experience a hang at restore time, use a single RMAN channel to restore the
multisection Oracle backups.
Prevent possible degradation of NMDA restore performance with Oracle

Due to an Oracle limitation, degradation of NMDA restore performance might occur if
NetWorker multiplexing is used with NMDA for Oracle backups. If NetWorker multiplexing
is enabled, you can prevent the restore performance degradation by including the set
parallelmediarestore off command in the RMAN restore script that is used for
the Oracle restore.
For example, the following RMAN restore script contains the required Oracle command to
disable the multiplexing during the Oracle restore:
set parallelmediarestore off;

run {
allocate channel c1 type ’SBT_TAPE’;
restore database;
release channel c1;
}
Prevent possible performance issues with Oracle Exadata backups

If an Oracle Exadata database server is running on Linux and the backup data is sent over
an Infiniband connection, you can prevent any backup performance issues by setting the
following parameter with the parms option for each backup channel in the RMAN script:
NSR_SOCK_BUF_UNSET=YES
Recovery report from NetWorker User for Lotus contains unexpected characters 31
Release Notes
The following RMAN script includes the parameter setting for each channel:
run {
allocate channel c1 type SBT parms ’ENV=(NSR_SOCK_BUF_UNSET=YES)’;
allocate channel c2 type SBT parms ’ENV=(NSR_SOCK_BUF_UNSET=YES)’;
backup database;
release channel c1;

release channel c2;
}
The same environment variable, NSR_SOCK_BUF_UNSET=YES, must also be set on the

NetWorker storage node host where the backup will be sent. You can set the environment
variable in the NetWorker startup script (for example, /etc/init.d/networker) on
UNIX and Linux systems, and in the system environment variables on Microsoft Windows.
The storage node must be restarted in order for the environment variables to take effect.
The NetWorker documentation provides details on setting environment variables.
This environment variable setting causes the NMDA and NetWorker software to not tune
the socket buffer size, which results in better performance with an Infiniband connection.
Raw devices are not supported with Oracle NSM operations on 64-bit Linux
Due to NSM limitations, NMDA does not support Oracle proxy operations with raw
devices that use NSM on 64-bit Linux.
Rollback restore fails for Oracle NSM backup in FRA

If you create a copy of an Oracle datafile or archived log to the FRA, and then perform a
successful NSM snapshot backup of that copy in the recovery area, a rollback restore of
the backup fails to restore the Oracle datafile or archived log to its original location
outside the recovery area. The rollback restore produces the following RMAN error:
ORA-27037: unable to obtain file status
Note
The FRA is a directory where RMAN places all of the disk type backups it creates (backups
not created with NMDA). The NMDA software can back up the backups from the recovery
area.
For example, you create a datafile copy and an NSM snapshot backup as follows:
1. Use the backup as copy datafile command to create a datafile copy of the
file /fs1/test1.dbf to the recovery area located at /fs2. The datafile copy is
created as /fs2/datafile/o1_mf_test1_2nnplt1z_.dbf.
2. Use the backup proxy recovery area command to perform an Oracle NSM
backup of the datafile copy in the recovery area.
Then if you perform a rollback restore of this snapshot backup, the restore occurs to /
fs2. The restore produces the RMAN error because RMAN expects the backed-up file to
be restored to /fs1, the original file location.
As a workaround, use the additional command restore...from datafilecopy to
restore from the datafile copy in the recovery area to the original datafile location.
Release Notes
Documentation
The following sections describe related documentation and any corrections or additions
for the NMDA documentation.
Related documentation
The compatibility matrix at the end of this document provides the latest details about the
platforms, operating systems, database servers, application servers, and other software
components that NMDA supports.
The following documentation provides information about NMDA and is available at EMC
Online Support:
l The NetWorker Module for Databases and Applications documentation set:
n Administration guide—Information on how to configure and use NMDA
n Installation guide—Information on how to install or update NMDA in stand-alone
and cluster environments
n Release notes—Information on new NMDA features and changes, fixed problems,
and known limitations
n Command reference guide—Reference information on NMDA commands and
options
l The NetWorker client, storage node, and server documentation set, including (but not
limited to) the following documents:
n Administration guide—Information on how to configure and maintain the
NetWorker software
n Installation guide—Information on how to install or update the NetWorker
software on supported platforms
n Release notes—Information on new NetWorker features and changes, fixed
problems, and known limitations
n Command reference guide—Reference information on NetWorker commands and
options
n Data Domain deduplication devices integration guide—Information on how to
configure and use Data Domain device systems
n Disaster recovery guide—Information on how to prepare for and perform disaster
recovery with NetWorker
n Licensing guide—Information on how to enable and license the NetWorker
software
n NetWorker Snapshot Management integration guide—Information on the NSM
requirements for snapshot backups and restores
l Other EMC documentation:
n Replication Manager documentation—Information on the Replication Manager
releases and requirements for snapshot backups and restores of Oracle ASM
The following additional documentation might be useful:
l Database or application server documentation
l Database or application database backup and recovery documentation
Documentation 33
Release Notes
Software media, organization, and files

The EMC NetWorker Module for Databases and Applications Installation Guide for NMDA 8.2
or the related Service Pack describes the NMDA software media, organization, and files.
Installation
The EMC NetWorker Module for Databases and Applications Installation Guide describes how
to install, update, uninstall, and license NMDA.
Coexistence of NMDA software

NMDA does not support the coexistence of NMDA with any other legacy NetWorker
module release on the same system.
NMDA does not support the coexistence of different NMDA releases on the same system.
NMDA reinstall after NetWorker software update

If you relocate the NetWorker client installation directory, for example, during a
NetWorker software update on the database or application server host where NMDA is
installed, you must uninstall and reinstall NMDA.
Licensing
To enable NMDA operations after the end of an evaluation period, obtain and install an
NMDA license enabler.
If you updated from a legacy NetWorker module to the NMDA software, you can continue
to use the legacy enabler for NMDA operations.
To enable NSM snapshot operations, obtain and install a separate NSM license enabler.
NMDA wizard and GUI installations on supported platforms

NMDA installs the configuration wizard for all the applications or databases that the
wizard supports on the given platform, regardless of which database or application is
actually installed on the system. The wizard also displays all the supported applications
accordingly as the available choices of applications for which backups can be configured.
If Lotus or Sybase is not installed on a Windows system, NMDA still installs the
NetWorker User for Lotus and NetWorker User for Sybase GUI programs on the system.
The programs are displayed under the Start menu.
Remote update of NMDA by push installation

You can update NMDA on one or more remote NMDA hosts with the software distribution
(push installation) feature from a centralized NetWorker server. You can perform a push
installation with either the Software Administration wizard or the nsrpush command.
Note
You cannot perform a push installation in a cluster environment.
You can perform a push installation of NMDA on the following NMDA platforms (NMDA
bitness in parentheses):
Release Notes
l AIX (32-bit, 64-bit)

l HP PA-RISC (32-bit, 64-bit)
l HP Itanium (64-bit)
l Linux x86 (32-bit)
l Linux x64 (64-bit)
l Solaris AMD (64-bit)
l Solaris SPARC (32-bit, 64-bit)
l Windows x86 (32-bit)
l Windows x64 (64-bit)
The EMC NetWorker Module for Databases and Applications Installation Guide describes the
push installation requirements and procedures.
Troubleshooting and getting help

The EMC support page provides access to licensing information, product documentation,
advisories, and downloads, as well as how-to and troubleshooting information. This
information may enable you to resolve a product issue before you contact EMC Customer
Support.
Support page
To access the support page:
1. Go to https://support.emc.com/products.
2. Type a product name in the Find a Product box.
3. Select the product from the list that appears.
4. Click the arrow next to the Find a Product box.
5. (Optional) Add the product to the My Saved Products list by clicking Add to My Saved
Products in the top right corner of the Support by Product page.
Knowledgebase
The EMC Knowledgebase contains applicable solutions that you can search for either by
solution number (for example, esgxxxxxx) or by keyword.
To search the EMC Knowledgebase:
1. Click the Search link at the top of the page.
2. Type either the solution number or keywords in the search box.
3. (Optional) Limit the search to specific products by typing a product name in the
Scope by product box and then selecting the product from the list that appears.
4. Select Knowledgebase from the Scope by resource list.
5. (Optional) Specify advanced options by clicking Advanced options and specifying
values in the available fields.
6. Click the Search button.
Online communities
Visit EMC Community Network at https://community.emc.com for peer contacts,
conversations, and content on product support and solutions. Interactively engage online
with customers, partners and certified professionals for all EMC products.
Troubleshooting and getting help 35

Release Notes
Live chat
To engage EMC Customer Support by using live interactive chat, click Join Live Chat on
the Service Center panel of the support page.
Service requests
For in-depth help from EMC Customer Support, submit a service request by clicking
Create Service Request on the Service Center panel of the support page.
Note
To open a service request, you must have a valid support agreement. Contact your EMC
sales representative for details about obtaining a valid support agreement or with
questions about your account.
To review an open service request, click the Service Center link on the Service Center
panel, and then click View and manage service requests.
Compatibility matrix
The following compatibility matrix provides the latest details about the platforms,
operating systems and versions, database servers or application servers, and other
software components supported by NMDA 8.2 and Service Packs.
EMC NetWorker Module for Databases and Applications (NMDA) − without EMC NetWorker
Snapshot Management (NSM); stand-alone configurations
Supported Supported Supported Supported Supported Supported Supported
Module Module Platform
Supported OS OS IBM DB2 Informix IDS Lotus Domino/Notes MySQL Oracle Sybase ASE
Version (Module bit-ness)
Version Version Version Version Version Version Version
IMPORTANT: Notes are provided at the end of the table
6
NMDA Linux x86 (32-bit) Red Hat Enterprise Linux AS, ES, WS 4, 5, 6, 7 9.5, 9.7, 10.1 11.50, 11.70, Domino Server 8.0.x, 5.1, 5.5, 5.6 11gR1, 11gR2 15.0.3, 15.5
8.2.x (RHEL) 12.10 8.5.x, 9.0.x
SuSE Linux Enterprise Server (SLES) 9, 10, 11
CentOS Linux 4 5, 6
Redflag Asianux Server 3
Oracle Linux 1 4, 5, 6
6
Linux x64 (64-bit) Red Hat Enterprise Linux AS, ES, WS 4, 5, 6, 7 9.5, 9.7, 10.1, 10.5 11.50, 11.70, Domino Server 9.0.x 5.1, 5.5, 5.6 11gR1,11gR2,12cR1 15.0.3, 15.5, 15.7, 16.0
(RHEL) 12.10
CentOS Linux 4 5, 6
Redflag Asianux Server 3
Oracle Linux 1 4, 5, 6
IBM System Z (64-bit) Red Hat Enterprise Linux AS, ES, WS 4, 5, 6 9.5, 9.7, 10.1, 10.5 11gR2, 12cR1
IBM Power AIX (32-bit) IBM AIX 6.1, 7.1 11.50 Domino Server 8.0.x, 15.0.3, 15.5, 15.7, 16.0
8.5.x, 9.0.x
IBM Power AIX (64-bit) IBM AIX 6.1, 7.1 9.5, 9.7, 10.1, 10.5 11.50, 11.70, Domino Server 8.0.x, 11gR1, 11gR2,
12.10 8.5.x, 9.0.x 12cR1
HP PA-RISC (64-bit) HP-UX 11iv2, 11iv3 11.50, 11.70 11gR1, 11gR2

HP Itanium (64-bit) HP-UX 11iv2, 11iv3 9.5, 9.7, 10.1, 10.5 11.50, 11.70, 11gR1, 11gR2, 15.0.3, 15.5, 15.7, 16.0
12.10 12cR1
Oracle SPARC (32-bit) Oracle Solaris 10 11.50 Domino Server 8.0.x, 15.0.3, 15.5, 15.7, 16.0
8.5.x
Oracle SPARC (64-bit) Oracle Solaris 10, 11 9.5, 9.7, 10.1, 10.5 11.50, 11.70, 11gR1, 11gR2,
12.10 12cR1
Oracle x64 (64-bit) Oracle Solaris 10, 11 2 9.5, 9.7, 10.1, 10.5 11.50, 11.70, 11gR1, 11gR2, 15.0.3, 15.5, 15.7, 16.0
12.10 12cR1
Windows x86 (32-bit) Windows 2003 R2, Vista, 9.5, 9.7, 10.1 11.50, 11.70, Notes & Domino Server 11gR1, 11gR2 15.0.3, 15.5, 15.7
2008, 2008 R2, 12.10 8.0.x, 8.5.x, 9.0.x
7, 8, 2012
Snapshot Management (NSM); stand-alone configurations
Supported Supported Supported Supported Supported Supported Supported
Module Module Platform
Supported OS OS IBM DB2 Informix IDS Lotus Domino/Notes MySQL Oracle Sybase ASE
Version (Module bit-ness)
Version Version Version Version Version Version Version
Windows x64 (64-bit) Windows 2003 R2, Vista, 9.5, 9.7, 10.1, 10.5 11.50, 11.70, Domino Server 8.0.x, 11gR1, 11gR2, 15.0.3, 15.5, 15.7, 16.0
2008, 2008 R2, 12.10 8.5.x, 9.0.x 12cR1
7, 8, 2012, 2012
R2
Notes
Consult the latest NMDA Release Notes for limitations, required patches, and more information.
NMDA supports NetWorker (Server, Client and Storage Node) versions 8.0 and up
NMDA supports
o all combinations of OS’s and databases (i.e. DB2, Informix, Lotus, MySQL, Oracle, Sybase) versions in this table, provided that the OS is supported by both database and the NetWorker Client installed on the NMDA
host
o raw devices, and all file systems supported by both the application and the NetWorker Client installed on the NMDA host; if the database is Oracle, ASM and ACFS are supported, too
o all FixPacks/PatchSets for all database releases in this table (e.g. stated support for Oracle 11.2 implies support for Oracle 11.2.0.2 too; stated support for IDS 12.10 implies support for 12.10.FC3 too, etc.)
o all Service Packs, Updates, patches, etc, of all OS’s listed in this table (e.g. stated support for Oracle Linux 5 implies support for Oracle Linux 5 Update 4 too, stated support for Asianux Server 3 implies support for
Asianux Server 3 SP 3 too, stated support for AIX 6.1 implies support for AIX 6.1 TL06 too, etc.)
Supported and required bitnesses of involved components:
For hosts having a single application installed:
For support of Sybase ASE installed on an AIX, HP-UX PA- RISC, or Oracle SPARC host: 32-bit NMDA 8.2 supports both 32-bit and 64-bit Sybase ASE, regardless of whether the OS or the CPU is 32-bit or 64-
bit; See the latest NMDA Release Notes for required bitness of the NetWorker Client installed on the NMDA host
For support of all other applications and/or OS’s: 32-bit NMDA supports 32-bit versions of the installed application, and 64-bit NMDA supports 64-bit versions of the installed application, regardless of whether the
OS or the CPU is 32-bit or 64-bit. See the latest NMDA Release Notes for required bitness of the NetWorker Client installed on the NMDA host
For hosts having multiple applications installed: see the latest NMDA Release Notes for supported environments and procedures.
Deduplication support:
o NMDA supports client direct deduplication to Data Domain device on most (see Release Notes for details) environments for which the NetWorker Client installed on the NMDA host supports file system client direct
restores.
o NMDA supports deduplication to Avamar on most (see Release Notes for details) environments for which the NetWorker Client installed on the NMDA host supports file system deduplication to Avamar.
NMDA supports all virtualization environments (such as VMware, Hyper-V, Solaris zone and LDOM, AIX LPAR and WPAR, HP nPar and vPar, HP IVM etc,) at the guest-level, provided that the application, NMDA, and the
NetWorker Client running on this guest-OS support natively this OS.
1 Linuxsupported with or without UEK (Unbreakable Enterprise Kernel)

2 Solaris
11 (x64) supported for Informix, Oracle and Sybase ASE
4 CentOS supported for MySQL
6 RHEL 7 supported for DB2, Lotus Domino, MySQL, Oracle, Sybase ASE
Snapshot Management (NSM); cluster configurations
IBM DB2 Informix IDS Lotus Domino/Notes MySQL Oracle
Module Version Sybase ASE Support
Support Support Support Support Support
NMDA NMDA supports NMDA supports NMDA supports NMDA supports: NMDA supports
active-passive cluster configurations: active-passive cluster active-passive cluster active-passive cluster configurations: active-passive cluster
o on all clusters supported by both DB2 configurations: configurations: o on all clusters supported by both configurations:
and the NetWorker Client installed o on all clusters supported o on all clusters Oracle and the NetWorker Client o on all clusters supported by
on the NMDA host by both IDS and the supported by both installed on the NMDA host both ASE and the
NetWorker Client installed
active-active application cluster NetWorker Client installed Lotus Domino and active-active application cluster
on the NMDA host
configurations (DPF and pureScale): on the NMDA host the NetWorker Client configurations (RAC)
active-active application
o on all environments supported by active-active application installed on the o on all clusters supported by both
cluster configurations (ASE
both DB2 and NetWorker Client cluster configurations (MACH NMDA host Oracle and the NetWorker Client
Cluster Edition):
installed on the NMDA host 11) installed on the NMDA host o on all environments
o on all environments o on all Oracle OSD clusterware supported by both ASE and
NMDA 8.2.1 and up supports: supported by both IDS and versions supported by Oracle the NetWorker Client
DB2 HADR: the NetWorker Client o on raw devices, ASM and all installed on the NMDA host
o on all environments supported by installed on the NMDA Cluster File Systems supported by
both DB2 and NetWorker Client host Oracle
installed on the NMDA host
EMC NetWorker Module for Databases and Applications (NMDA) −
with EMC NetWorker Snapshot Management (NSM)
NSM NSM NSM Platform NMDA 8.2 NMDA 8.2
Version Product (NSM bit-ness) Oracle Support DB2 Support
IMPORTANT: Notes are provided at the end of the table
NSM NSM for Symmetrix DMX / Linux x64 (64-bit) √ √
8.2.x VMAX HP Itanium (64-bit) √
8.1.x IBM Power AIX (64-bit) √ √
Oracle SPARC (64-bit) √
Windows x64 (64-bit) √
NSM for CLARiiON / VNX Linux x64 (64-bit) √ √
IBM Power AIX (64-bit) √ √
Oracle SPARC (64-bit) √
Windows x64 (64-bit) √
Notes
Consult the latest NMDA Release Notes for limitations, required patches, etc.
For DB2 and Oracle single-instance, un-clustered, or active-passive cluster configurations:
o A check-marked NMDA/NSM combination in this table denotes that this combination is supported
provided that all NSM requirements (e.g. homogeneous/heterogeneous configurations, multi-path software, etc.) have been met
provided that the bit-nesses of NSM and NMDA are the same
for all single-instance, un-clustered or clustered, Oracle and DB2 versions supported by NMDA without NSM
on all OS’s supported by both NMDA and NSM
on raw devices, and on all file systems supported by both NMDA and NSM
with all versions of NetWorker (Client, Server and Storage Node) supported by both NMDA and NSM
For Oracle active-active application cluster configurations (RAC)
o NMDA supports all environments supported by NMDA and NSM for single-instance Oracle (in this table), with the additional limitations
support only for NSM for CLARiiON, and for NSM for Symmetrix in homogeneous environment
support for raw devices, only on
o Oracle SPARC and either Oracle SunCluster or Veritas Cluster Server
o HP-UX Itanium 64-bit and Veritas Cluster Server
support for cluster file systems, only on
o Oracle SPARC and Veritas Cluster Server and Veritas Cluster File System
o HP-UX Itanium 64-bit and Veritas Cluster Server and Veritas Cluster File System
o Linux x64 and Oracle OSD Cluster and Oracle Cluster File System 2 (OCFS2)
Release Notes
Copyright © 2009-2015 EMC Corporation. All rights reserved. Published in USA.
Published July 13, 2015
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).
Compatibility matrix 37

NetWorker Module For Databases and Applications 8.2 and Service Packs Releas

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetWorker Module For Databases and Applications 8.2 and Service Packs Releas

Uploaded by

Copyright:

Available Formats

Release Notes

July 13, 2015

Revision Date Description

05 June 30, 2015 Added to Known problems and limitations:

04 May 6, 2015 Updated the following information:

Revision Date Description

01 June 18, 2014 Initial release of NMDA 8.2.

Major configuration changes from legacy NetWorker modules to NMDA on page 4

Major configuration changes from legacy NetWorker modules to NMDA

Table 1 Configuration changes from legacy NetWorker modules to NMDA

Feature or parameter in legacy NetWorker module Corresponding feature or parameter in NMDA

NSR_ENCRYPTION parameter. Parameter is dropped. Specify backup encryption through the

NetWorker Module for DB2 (NMDB2):

The NMDA configuration_file supports the NMDB2

Manual backup through the db2 commands. No change.

Restore through the db2 commands. No change.

DB2_PSWD parameter. Replaced by USER_PSWD parameter. Set the password value in

DB2_USR parameter. Replaced by DB2_USER parameter.

NSR_DB2_BACKUP_INFO parameter. Replaced by NSR_DR_BACKUP_INFO parameter.

NSR_DB2_CONFIG_FILE parameter. Replaced by NSR_DR_FILE_LIST parameter.

NSR_*_DEBUG* parameters. Replaced by NSR_DEBUG_LEVEL parameter.

NetWorker Module for Informix (NMI):

Table 1 Configuration changes from legacy NetWorker modules to NMDA (continued)

Feature or parameter in legacy NetWorker module Corresponding feature or parameter in NMDA

Restore performed through the onbar commands. No change.

BOOTFILE parameter. Replaced by NSR_DR_FILE_LIST parameter.

DO_BOOTFILE_BACKUPS parameter. Replaced by NSR_DR_BACKUP_INFO parameter.

NetWorker Module for Lotus (NML):

The NMDA configuration_file supports the NML configuration_file

Restore performed through the nsrnotesrc -z No change.

Manual backup or restore performed through the NetWorker No change.

Document-level recovery performed through the nsrdocrc -z No change.

Document-level recovery performed through the Notes client GUI No change.

LOTUSUSER parameter. Replaced by LOTUS_USER parameter.

NetWorker Module for Oracle (NMO):

Manual backup performed through the Oracle RMAN interface. No change.

Restore performed through the Oracle RMAN interface. No change.

NSR_SB_DEBUG_FILE parameter. Replaced by NSR_DEBUG_LEVEL=1 parameter.

NetWorker Module for Sybase (NMS):

Database consistency check performed through the nsrsybcc No change.

Restore performed through the nsrsybrc No change.

Major configuration changes from legacy NetWorker modules to NMDA 5

Table 1 Configuration changes from legacy NetWorker modules to NMDA (continued)

Feature or parameter in legacy NetWorker module Corresponding feature or parameter in NMDA

BACKUP_OPT parameter. Parameter is dropped.

-G, -R, and -T options of nsrsybsv command. Replaced by NSR_DUMP_LOG_OPT parameter.

-l option of nsrsybsv command. Replaced by NSR_BACKUP_LEVEL parameter.

-p option of nsrsybsv command. Replaced by NSR_PROMOTE_FULL parameter.

-r option of nsrsybsv command. Replaced by NSR_ASE_PASSWORD parameter.

-V option of nsrsybsv command. Replaced by NSR_ASE_VERIFY parameter.

New features and changes

NMDA 8.2 SP1

Data Domain IPv6 support

DB2 HADR support

DB2 load with copy yes option support

Sybase listonly option support

NMDA 8.2 SP1 7

Sybase restore parameter support

Sybase restore parameters in NMDA 8.2 Corresponding command line options

NSR_ASE_PASSWORD nsrsybrc -r backup_password

NSR_ASE_VERIFY nsrsybrc -V {header | full |

NSR_BACKUP_PATHS nsrsybrc { SYBASE:/ASE_server_name |

NSR_DEBUG_LEVEL nsrsybrc -D debug_level

NSR__DEBUG parameters. Replaced by NSR_DEBUG_LEVEL parameter.