Release Notes. EMC NetWorker Module for Databases and Applications. Release Notes. Release number 8.2 and Service Packs REV 03

(1)

EMC

®

NetWorker

®

Module for Databases and

Applications

Release number 8.2 and Service Packs

Release Notes

302-000-386 REV 03

January 28, 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...2

l New features and changes... 5

l Fixed problems... 10

l Environment and system requirements... 11

l Known problems and limitations...12

l Technical notes...22

l Documentation... 30

l Software media, organization, and files... 31

l Installation... 31

l Troubleshooting and getting help...32

(2)

Revision history

The following table presents the revision history of this document.

Revision Date Description

03 January 28, 2015 Updated for the release of NMDA 8.2 SP1. 02 August 29, 2014 Updated the following information:

l _{Fixed problems on page 10 - 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 12 - Updated the list of

supported MEB versions in the table. l _{Compatibility matrix on page 33 - Updated}

details in the compability matrix.

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 3

describes major configuration differences between the legacy modules and NMDA.

New features and changes on page 5 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 11 provides information about the supported versions of the NetWorker software.

(3)

Known problems and limitations on page 12 describes the known problems and limitations in NMDA 8.2 and Service Packs.

Technical notes on page 22 describes existing NMDA features that require special considerations or require a later version of the NetWorker software.

Documentation on page 30 describes the NMDA 8.2 and Service Packs documentation and related documents. Installation on page 31 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 through the nsrdb2sv -f configuration_file command.

Replaced by scheduled backup (configured without the wizard) 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.

(4)

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

NSR_*_DEBUG* parameters. Replaced by NSR_DEBUG_LEVEL parameter.

NetWorker Module for Informix (NMI):

Scheduled backup performed through the nsrdbmi shell/batch script.

Replaced by scheduled backup performed through the nsrdasv -z configuration_file command.

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 backup performed through the nsrnotesv -z

configuration_file command.

Replaced by scheduled backup (configured without the wizard) or manual backup performed through the nsrdasv -z configuration_file command.

Note

The NMDA configuration_file supports the NML configuration_file format.

Restore performed through the nsrnotesrc -z configuration_file command.

No change. Manual backup or restore performed through the NetWorker

User for Lotus GUI (nwbml.exe) on Windows only.

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

configuration_file command.

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

on Windows only.

No change.

LOTUSUSER parameter. Replaced by LOTUS_USER parameter.

NetWorker Module for Oracle (NMO):

Scheduled backup (configured without the wizard) performed through the nsrnmo shell/batch script.

Replaced by scheduled backup (configured without wizard) 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 script.

Replaced by scheduled backup performed through the nsrdasv -z configuration_file command.

Manual backup performed through the nsrsybsv command_line_options command.

Replaced by manual backup performed through the nsrdasv -z configuration_file command.

(5)

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

Database consistency check performed through the nsrsybcc command_line_options command.

No change. Restore performed through the nsrsybrc

command_line_options command.

No change. Manual backup or restore performed through the NetWorker

User for Sybase GUI (nwbms.exe) on Windows only.

No change.

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 Client resource.

Replaced by USER_PSWD parameter. Set the password value in 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 Client resource.

Replaced by SYBASE_USER parameter.

-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 6 l DB2 HADR support on page 6

l DB2 load with copy yes option support on page 6 l Sybase listonly option support on page 6

l Sybase restore parameter support on page 7 l Updated NMDA 8.2 SP1 parameters on page 8

(6)

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.

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.

The EMC NetWorker Module for Databases and Applications Release 8.2 SP1 Administration 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.

The EMC NetWorker Module for Databases and Applications Release 8.2 SP1 Administration 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.

(7)

The EMC NetWorker Module for Databases and Applications Release 8.2 SP1 Administration Guide provides details about how to obtain the structure information from an NMDA Sybase backup by using the Sybase listonly option.

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

SP1 Corresponding command line options

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]

(8)

Table 2 NMDA Sybase restore parameters and nsrsybrc command line options (continued)

Sybase restore parameters in NMDA 8.2

SP1 Corresponding command line options

NSR_SERVER nsrsybrc -s server_name

NSR_XBSA_DEBUG (new debug parameter) Not applicable

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.

The EMC NetWorker Module for Databases and Applications Release 8.2 SP1 Administration 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 8

l Lotus transaction logs backup with multiple concurrent streams on page 9 l Oracle recovery wizard support of TNS_ADMIN environment variable on page 9 l Sybase network password encryption on page 9

l Updated NMDA 8.2 parameters on page 9

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

(9)

software layer or database engine, the utility provides quick and efficient recovery of discrete volumes of data.

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:

(10)

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

All NW161970 For DB2 NSM backups, the DB2 metadata save set is not removed when a point-in-time save

set is removed or released.

DB2 NW161515 A misleading message "Unknown error category 211" might cause confusion with a Domino

backup failure.

Lotus NW161419 An Oracle backup might fail with the following error message when the nsrmmd process is

busy:

Volume ID 'volume_ID' is not in media database. (2:3:73)

Oracle

NW161762 The nsrdasv program fails to correctly process the NLS_DATE_FORMAT parameter value that contains spaces.

Oracle 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

end, which might cause Oracle to dump a core file.

Oracle 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

restore is performed during Daylight Saving Time.

(11)

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, 186742

DB2 backup on Windows fails due to a db2sysc.exe process crash. DB2 NW158246 The restore of a DB2 NSM snapshot backup might fail with a crash of the db2vend process. DB2 NW161337,

193052

DB2 redirected recovery with the db2 "rollforward db" command fails to recover the transaction logs from the backup media.

DB2 NW155418 With the NSR_PREFETCH_LOGS parameter set to a nonzero value, a Lotus restore with the

nsrdocrc command does not prefetch any transaction logs.

Lotus Domino NW157119 Lotus recovery of a Domino .nsf file with many transaction logs does not stop when End

restore is selected, and the recovery continues to completion.

Lotus Domino NW160571,

186399

On Linux, a Lotus scheduled backup fails with a crash of the nsrdasv program when the checkpoint restart option (CPR) is enabled.

Lotus Domino NW161178,

191984

When you run the NetWorker User for Lotus GUI to recover a Lotus backup, the GUI might not display all the backed-up files included in the backup.

Lotus Domino NW154716 Oracle recovery configuration wizard fails if the Oracle TNS_ADMIN environment variable

specifies a nondefault location for the Oracle Net service files.

Oracle NW157752 NSR_RMAN_OUTPUT=SHELL setting on Windows does not generate the expected names for the

RMAN output log files.

Oracle NW159657,

186596

The nsrdasv program always returns a zero exit code for an Oracle backup failure. Oracle

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.

(12)

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

5.6 3.6, 3.7, 3.8, 3.9, 3.10

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.

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 13

l Limitations in other products that affect NMDA 8.2 and Service Packs on page 13

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.

(13)

Table 6 Limitations in NMDA 8.2 and Service Packs

Issue

number Description Operatingsystem Product feature Application

224226 on page 14

On Linux, NMDA installations and operations fail if the NetWorker client package is installed in a nondefault location. Linux Installation, backup, restore All NW151464 on page 16

The savegroup report for a DB2 snapshot and rollover backup does not include any save set information from the rollover part of the backup.

Linux Backup,

NSM

DB2

NW158881 on page 17

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.

AIX Backup Informix

NW101758, NW113768 on page 18

A Lotus backup of 64-bit Domino on AIX might cause the Domino server to crash or become suspended or the backup might fail with a specific error message.

AIX Backup Lotus Domino

NW121290 on page 19

A Lotus full database backup might expire before the dependent transaction log backups because NMDA Lotus does not create dependencies between the backups.

All Backup Lotus Domino

NW143964 on page 19

Conversion of a MySQL client-side to server-side configuration with the nsrdaadmin -W command fails. Linux Configuration conversion MySQL NW148580 on page 19

When you run the nsrinfo command to obtain information about MySQL backups, the command displays an error message.

Linux Backup MySQL

LGTsc06110 o n page 20

Japanese Oracle backup information might be displayed incorrectly in the NMC program.

All Backup,

internationalization

Oracle NW150321 on

page 20

NMDA Oracle save set bundling or policy uniformity fails for a multinode Oracle RAC backup, but the backup is successful and fully recoverable.

All Backup Oracle

NW105216 on page 21

If a Sybase manual or scheduled backup attempts to back up more than 200 databases, the backup might fail.

All Backup Sybase ASE

NW146800 on page 22

A Sybase scheduled backup might fail if the Sybase server and NetWorker client run in different locales.

All Backup Sybase ASE

Table 7 Limitations in other products that affect NMDA 8.2 and Service Packs

Issue

NW007000 on page 15

Due to a NetWorker limitation in non-English locales, backup configuration with the wizard fails.

All Configuration wizard, internationalization

All

(14)

Table 7 Limitations in other products that affect NMDA 8.2 and Service Packs (continued)

Issue

181210 on page 16

Due to a DB2 bug, if you use the HPU utility to unload and restore an NMDA DB2 incremental backup, then the operation might fail with an error.

All Restore DB2

NW152810 on page 16

Due to a DB2 bug, if you run a multisession DB2 backup and use the db2 prune command to delete backup entries from the DB2 history file, the command might leave some entries in the file.

All Backup DB2

NW154550 on page 16

Due to a DB2 limitation, NMDA does not delete the logs from the NetWorker server during a db2 prune operation if the NMDA configuration file pathname in the LOGARCHOPTn parameter exceeds 30 ASCII characters.

All Backup DB2

NW019057 on page 20

Due to an Oracle limitation, Oracle backup problems might occur when the RMAN script contains non-ASCII data. All Backup, internationalization Oracle NW152664 on page 21

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.

All Restore Oracle

NW154492 on page 21

Due to Oracle bug 17770652, an Oracle 12cR1 container or pluggable database snapshot backup with NSM fails on Windows if some of the datafiles are not located on a snapshotable device.

Windows Backup,

NSM

Oracle

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.

(15)

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

(16)

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

(17)

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

(18)

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 18 to step 5 on page 18:

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

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.

(19)

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

(20)

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:

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

(21)

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;

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.

(22)

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.

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

(23)

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.

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)

(24)

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

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

(25)

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 3

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.

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.

(26)

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.

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-32-bit Windows system where 32-32-bit and 64-32-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

(27)

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.

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 18 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

(28)

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

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

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.

(29)

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

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.

(30)

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.

Documentation

The following sections describe related documentation and any corrections or additions for the NMDA documentation.