Академический Документы
Профессиональный Документы
Культура Документы
® ®
EMC NetWorker Module for Databases and
Applications
Release number 8.2 and Service Packs
Release Notes
302-000-386
REV 06
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.
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
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.
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.
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
Scheduled backup performed through the nsrdbmi shell/batch Replaced by scheduled backup performed through the
script. nsrdasv -z configuration_file command.
4 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
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
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.
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.
-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.
-U option of nsrsybsv command, or remote user setting in the Replaced by SYBASE_USER parameter.
Client resource.
Note
Deprecated features are features supported in this NMDA release that will be removed
and unsupported in a future NMDA release.
6 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
Table 2 NMDA Sybase restore parameters and nsrsybrc command line options
8 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
Table 2 NMDA Sybase restore parameters and nsrsybrc command line options (continued)
USE_CONSISTENCY_CHECK nsrsybrc -k
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.
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.
10 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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.
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:
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
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
12 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
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.
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:
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.
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.
14 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
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
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.
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:
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.
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/
16 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
libmysqlapiwrap.so
# ln -s /relocation_path/lib/libnsrmysql.so /usr/lib/libnsrmysql.so
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 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
Contact EMC Technical Support for a hotfix.
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 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.
18 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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:
You can run the following db2 update history command to update the
Comment field with a valid configuration file pathname:
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.
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
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.
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
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:
20 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
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 used to query MySQL backup information displays the following
error message:
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:
The backup is successful and fully recoverable, but the save set bundling or policy
uniformity feature fails.
As a workaround:
22 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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;
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;
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.
24 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
Release Notes
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.
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
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
26 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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
The Oracle recovery configuration wizard does not support the configuration of Oracle
RMAN scripts in a cluster environment.
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.
Probe-based backups
NMDA supports probe-based (event-based) backups.
NMDA does not support probe-based backups for snapshot backups with NSM.
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.
28 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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.
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.
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.
Note
NMDA Lotus restartable backups do not support Client Direct backups to Data Domain,
described in Client Direct backups and restores on page 25.
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:
30 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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
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;
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.
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.
32 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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
Installation
The EMC NetWorker Module for Databases and Applications Installation Guide describes how
to install, update, uninstall, and license 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.
Note
You can perform a push installation of NMDA on the following NMDA platforms (NMDA
bitness in parentheses):
34 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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.
36 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes
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
SuSE Linux Enterprise Server (SLES) 9, 10, 11
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
SuSE Linux Enterprise Server (SLES) 9, 10, 11
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
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