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

Transcription

1 EMC NetWorker Module for Databases and Applications Release number 8.2 and Service Packs Release Notes 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 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: Revision history... 2 Product description...2 New features and changes... 5 Fixed problems Environment and system requirements Known problems and limitations...12 Technical notes...22 Documentation Software media, organization, and files Installation Troubleshooting and getting help...32 Compatibility matrix...33

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: Fixed problems on page 10 - Added the following bugs to the table of fixed problems: NW (186596), NW (186399), NW (191984), NW (193052). Updated the NW problem summary. Table 5 on page 12 - Updated the list of supported MEB versions in the table. 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: NetWorker Module for DB2 (NMDB2) NetWorker Module for Informix (NMI) NetWorker Module for Lotus (NML) NetWorker Module for Oracle (NMO) 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. 2 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

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: On UNIX and Linux: /nsr/apps/config 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. Restore through the db2 commands. DB2_PSWD parameter. DB2_USR parameter. NSR_DB2_BACKUP_INFO parameter. NSR_DB2_CONFIG_FILE parameter. No change. No change. Replaced by USER_PSWD parameter. Set the password value in the parameter through the nsrdaadmin -P command. Replaced by DB2_USER 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). Replaced by NSR_DR_FILE_LIST parameter. Major configuration changes from legacy NetWorker modules to NMDA 3

4 Table 1 Configuration changes from legacy NetWorker modules to NMDA (continued) Feature or parameter in legacy NetWorker module NSR_*_DEBUG* parameters. Corresponding feature or parameter in NMDA Replaced by NSR_DEBUG_LEVEL parameter. NetWorker Module for Informix (NMI): Scheduled backup performed through the nsrdbmi shell/batch script. Manual backup performed through the onbar commands. Restore performed through the onbar commands. BOOTFILE parameter. DO_BOOTFILE_BACKUPS parameter. Replaced by scheduled backup performed through the nsrdasv -z configuration_file command. No change. No change. Replaced by NSR_DR_FILE_LIST 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. Manual backup or restore performed through the NetWorker User for Lotus GUI (nwbml.exe) on Windows only. Document-level recovery performed through the nsrdocrc -z configuration_file command. Document-level recovery performed through the Notes client GUI on Windows only. LOTUSUSER parameter. No change. No change. No change. No change. Replaced by LOTUS_USER parameter. NetWorker Module for Oracle (NMO): Scheduled backup (configured without the wizard) performed through the nsrnmo shell/batch script. Manual backup performed through the Oracle RMAN interface. Restore performed through the Oracle RMAN interface. NSR_SB_DEBUG_FILE parameter. Replaced by scheduled backup (configured without wizard) performed through the nsrdasv -z configuration_file command. No change. No change. Replaced by NSR_DEBUG_LEVEL=1 parameter. NetWorker Module for Sybase (NMS): Scheduled backup performed through the nsrsyb shell/batch script. Manual backup performed through the nsrsybsv command_line_options command. Replaced by scheduled backup performed through the nsrdasv -z configuration_file command. Replaced by manual backup performed through the nsrdasv -z configuration_file command. 4 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

5 Table 1 Configuration changes from legacy NetWorker modules to NMDA (continued) Feature or parameter in legacy NetWorker module Database consistency check performed through the nsrsybcc command_line_options command. Restore performed through the nsrsybrc command_line_options command. Manual backup or restore performed through the NetWorker User for Sybase GUI (nwbms.exe) on Windows only. BACKUP_OPT parameter. -G, -R, and -T options of nsrsybsv command. Corresponding feature or parameter in NMDA No change. No change. No change. Parameter is dropped. 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: Data Domain IPv6 support on page 6 DB2 HADR support on page 6 DB2 load with copy yes option support on page 6 Sybase listonly option support on page 6 Sybase restore parameter support on page 7 Updated NMDA 8.2 SP1 parameters on page 8 New features and changes 5

6 Data Domain IPv6 support 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. 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: Multiple standby mode is available only with DB and later. DB2 load with copy yes option support Sybase listonly option support HADR is not available in partitioned database environments. DB2 does not support backups on the standby host, even if the Reads on Standby (ROS) feature is enabled. 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: 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. 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. 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. NMDA 8.2 SP1 supports the use of the Sybase restore command, nsrsybrc, with the listonly option for obtaining structure information from the latest backup of a Sybase instance or databases, without restoring the backup. Sybase ASE 15.7 ESD#2 and later provides the listonly option support. 6 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

7 Sybase restore parameter support 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. 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: nmda_sybase_backup.cfg Template for Sybase backup parameters 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 NSR_DEBUG_LEVEL NSR_DIAGNOSTIC_DEST (new parameter) NSR_DPRINTF (new debug parameter) NSR_ENCRYPTION_PHRASES NSR_NWPATH NSR_RECOVER_POOL NSR_RELOCATION_DEST (new parameter) nsrsybrc -c client_name nsrsybrc -D debug_level Not applicable Not applicable nsrsybrc -e AES_pass_phrase Not applicable nsrsybrc -w recover_pool nsrsybrc -d SYBASE:/ASE_server_name[/ database_name] NMDA 8.2 SP1 7

8 Table 2 NMDA Sybase restore parameters and nsrsybrc command line options (continued) Sybase restore parameters in NMDA 8.2 SP1 NSR_SERVER NSR_XBSA_DEBUG (new debug parameter) RECOVER_LISTONLY (new parameter) Corresponding command line options nsrsybrc -s server_name Not applicable 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) SYBASE_USER nsrsybrc -L temporary_file_pathname nsrsybrc -U username USE_CONSISTENCY_CHECK nsrsybrc -k USER_PSWD nsrsybrc -P password Updated NMDA 8.2 SP1 parameters NMDA 8.2 DB2 data recovery with the HPU utility 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. The following topics describe the major new or enhanced features of NMDA 8.2: DB2 data recovery with the HPU utility on page 8 Lotus transaction logs backup with multiple concurrent streams on page 9 Oracle recovery wizard support of TNS_ADMIN environment variable on page 9 Sybase network password encryption on page 9 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. 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 8 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

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 Sybase network password encryption Updated NMDA 8.2 parameters 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. 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 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. 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: NMDA 8.2 9

10 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. 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 The 32-bit NMDA software files are missing in the 64-bit NMDA zipped download file on Windows. All NW NW NW For DB2 NSM backups, the DB2 metadata save set is not removed when a point-in-time save set is removed or released. A misleading message "Unknown error category 211" might cause confusion with a Domino backup failure. An Oracle backup might fail with the following error message when the nsrmmd process is busy: DB2 Lotus Oracle Volume ID 'volume_id' is not in media database. (2:3:73) NW The nsrdasv program fails to correctly process the NLS_DATE_FORMAT parameter value that contains spaces. Oracle NW NSR_ORACLE_RETENTION is not honored if the parameter is set by the wizard. Oracle NW 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 NW The nsrsybrc command does not permit spaces between the -P option and the password. Sybase NW An NMDA Sybase restore cannot find a backup performed during Standard Time when the restore is performed during Daylight Saving Time. Sybase 10 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

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, DB2 backup on Windows fails due to a db2sysc.exe process crash. DB2 NW The restore of a DB2 NSM snapshot backup might fail with a crash of the db2vend process. DB2 NW161337, NW NW NW160571, NW161178, NW NW NW159657, DB2 redirected recovery with the db2 "rollforward db" command fails to recover the transaction logs from the backup media. 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 recovery of a Domino.nsf file with many transaction logs does not stop when End restore is selected, and the recovery continues to completion. On Linux, a Lotus scheduled backup fails with a crash of the nsrdasv program when the checkpoint restart option (CPR) is enabled. 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. Oracle recovery configuration wizard fails if the Oracle TNS_ADMIN environment variable specifies a nondefault location for the Oracle Net service files. NSR_RMAN_OUTPUT=SHELL setting on Windows does not generate the expected names for the RMAN output log files. The nsrdasv program always returns a zero exit code for an Oracle backup failure. DB2 Lotus Domino Lotus Domino Lotus Domino Lotus Domino Oracle Oracle 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. Fixed problems in 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 , 3.7, 3.8, 3.9, , 3.7, 3.8, 3.9, , 3.7, 3.8, 3.9, 3.10 The following considerations apply to NMDA MySQL operations and MEB dependencies: 32-bit MEB must be installed for 32-bit MySQL support, and 64-bit MEB must be installed for 64-bit MySQL support. 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 or later to be installed on the MySQL server host. For a list of the new features supported only with MEB or later, refer to the topic Compatibility Note for MySQL Version in the MySQL Enterprise Backup User s Guide for version 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: Limitations in NMDA 8.2 and Service Packs on page 13 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. 12 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

13 Table 6 Limitations in NMDA 8.2 and Service Packs Issue number Description Operating system Product feature Application 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 NW 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 NW on page 17 With 32-bit NMDA on AIX, an Informix backup fails with the following error message: AIX Backup Informix Dependent module /usr/lib/liblocktbl.so could not be loaded. NW101758, NW on page 18 NW on page 19 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. A Lotus full database backup might expire before the dependent transaction log backups because NMDA Lotus does not create dependencies between the backups. AIX Backup Lotus Domino All Backup Lotus Domino NW on page 19 Conversion of a MySQL client-side to server-side configuration with the nsrdaadmin -W command Linux Configuration conversion MySQL fails. NW 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 NW on page 20 NW on page 21 NW on page 22 NMDA Oracle save set bundling or policy uniformity fails for a multinode Oracle RAC backup, but the backup is successful and fully recoverable. If a Sybase manual or scheduled backup attempts to back up more than 200 databases, the backup might fail. A Sybase scheduled backup might fail if the Sybase server and NetWorker client run in different locales. All Backup Oracle All Backup Sybase ASE All Backup Sybase ASE Table 7 Limitations in other products that affect NMDA 8.2 and Service Packs Issue number Description Operating system Product feature Application NW on page 15 Due to a NetWorker limitation in non-english locales, backup configuration with the wizard fails. All Configuration wizard, internationalization All Known problems and limitations 13

14 Table 7 Limitations in other products that affect NMDA 8.2 and Service Packs (continued) Issue number Description Operating system Product feature Application on page 16 NW on page 16 NW 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. 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. 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 Restore DB2 All Backup DB2 All Backup DB2 NW 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 NW on page 21 Due to Oracle bug , 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 NW on page 21 Due to Oracle bug , 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 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: 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. All other NMDA operations fail with the same error message, including backups, restores, and backup deletions. As a workaround, perform the following steps: 14 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

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 NW 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: Configure the backup manually with the NMC method, without the wizard. Ensure that the installation path of the NetWorker server does not include any non- ASCII characters. Common NMDA problems and limitations 15

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 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: HPU v4.2.1 FP1 with IF11 or later HPU v5.1 with IF8 or later HPU v DB2 snapshot and rollover backup does not report the rollover save set details NW 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 NW 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 with force option and delete db2 prune history with force option DB2 prune operation does not delete the logs from the NetWorker server in certain cases NW 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. 16 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

17 db2 list history archive log all for db hat List History File for hat 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: Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID X D O S LOG C Comment: Start Time: End Time: Status: P EID: 25 Location: /usr/lib/libnsrdb2.so Informix problems and limitations 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. Informix backup fails with 32-bit NMDA on AIX 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. This section contains NMDA problems and limitations specific to Informix operations. NW With 32-bit NMDA on AIX, an Informix backup fails with the following error message: Dependent module /usr/lib/liblocktbl.so could not be loaded. As a workaround, run the following command as root, to remove the following symbolic link before you perform any Informix backups: rm /usr/lib/liblocktbl.so This link removal ensures that the 32-bit NMDA Informix library can locate the correct 32- bit libraries. Lotus Domino/Notes problems and limitations This section contains NMDA problems and limitations specific to Lotus Domino/Notes operations. Informix problems and limitations 17

18 Backup of 64-bit Domino on AIX might fail NW101758, NW 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 NW 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 0x 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:0x /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. 3. Perform the preceding step 1 on page 18 to step 5 on page EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes

19 Lotus full backups might expire before dependent transaction logs MySQL problems and limitations NW 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. This section contains NMDA problems and limitations specific to MySQL operations. Conversion of MySQL client-side to server-side configuration fails NW 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 NW 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 or later. MySQL problems and limitations 19

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: Use the NSR_RMAN_ARGUMENTS parameter to redirect the RMAN output to a specified log file. 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 NW Due to Oracle bug , an NMDA Oracle backup might fail or some parameters might be ignored in a non-english locale when the following conditions exist: NMDA internationalization is set up. The character sets of the RMAN script and Oracle database are different. 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 NW 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: 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. 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. 20 EMC NetWorker Module for Databases and Applications 8.2 and Service Packs Release Notes