EMC® NetWorker®

Module for Databases and

Applications
Release 1.5

Installation Guide
P/N 300-014-206
REV 01
Copyright © 2009 - 2013 EMC Corporation. All rights reserved. Published in the USA.

Published July, 2013

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect
to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular
purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

2 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
CONTENTS

Preface

Chapter 1 Getting Started

NMDA software requirements...................................................................... 12
Database or application server software................................................ 12
NetWorker server software .................................................................... 13
NMC server software ............................................................................. 14
NetWorker storage node software.......................................................... 14
NetWorker client software ..................................................................... 14
NMDA software ..................................................................................... 14
PowerSnap software ............................................................................. 15
Replication Manager software ............................................................... 15
Installation checklists ................................................................................. 15
Documents............................................................................................ 15
Installation media ................................................................................. 16
License enablers ................................................................................... 16
Accessing the NMDA software ..................................................................... 16
Accessing NMDA from the DVD media ................................................... 16
Accessing NMDA from the EMC website................................................. 17
Installation road maps ................................................................................ 18
Road map to install or update NMDA on a local host ............................. 18
Road map to update NMDA remotely by push install ............................. 20
Road map to post-installation procedures ............................................. 21
Converting legacy scheduled backup configurations to NMDA ..................... 22
Converting legacy backup configurations to NMDA with nsrdaadmin ..... 23
Converting legacy backup configurations to NMDA manually................. 25

Chapter 2 UNIX and Linux Installation

Installing NMDA on AIX systems .................................................................. 30
Installing NMDA on HP-UX systems ............................................................. 31
Installing NMDA on Linux systems............................................................... 31
Installing NMDA on Solaris systems ............................................................ 32
Linking and unlinking NMDA in the environment on UNIX or Linux ............... 34
Linking NMDA in a DB2 environment ..................................................... 34
Linking and unlinking NMDA in an Informix environment ....................... 35
Linking and unlinking NMDA in an Oracle environment.......................... 36
Linking and unlinking NMDA in a Sybase environment .......................... 37
Uninstalling NMDA on UNIX or Linux systems .............................................. 39
Uninstalling NMDA on AIX systems........................................................ 39
Uninstalling NMDA on HP-UX systems ................................................... 40
Uninstalling NMDA on Linux systems..................................................... 40
Uninstalling NMDA on Solaris systems .................................................. 40

Chapter 3 Microsoft Windows Installation

Installing NMDA on Microsoft Windows ....................................................... 44
Linking and unlinking NMDA in the environment on Windows...................... 45
Linking NMDA in a DB2 environment ..................................................... 45

EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide 3
Contents

Linking and unlinking NMDA in an Informix environment ....................... 46

Linking and unlinking NMDA in a Lotus Notes environment (optional) ... 47
Linking and unlinking NMDA in a Sybase environment .......................... 48
Maintaining the installation on Microsoft Windows ..................................... 49
Running the Setup program in maintenance mode ................................ 49
Repairing an NMDA installation............................................................. 49
Uninstalling NMDA on Microsoft Windows................................................... 50

Chapter 4 NMDA with Mixed 32-bit and 64-bit Databases and Applications
Coexistence of 32-bit and 64-bit databases and applications ...................... 52
Installing NMDA on a 32-bit/64-bit system .................................................. 52
Uninstalling 32-bit NMDA on a 32-bit/64-bit system ................................... 55

Appendix A Uninstalling ISM on an Informix Server

ISM software on an Informix server ............................................................. 58
Uninstalling ISM on UNIX or Linux ............................................................... 58
Uninstalling ISM on Microsoft Windows....................................................... 59
Uninstalling ISM on Windows with the Setup program........................... 59
Unstalling ISM on Windows manually.................................................... 59

4 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
TABLES

Title Page

1 Typical hosts and software in the NMDA backup and recovery environment................. 12
2 Software directory on the DVD ..................................................................................... 17
3 Zipped download file and software directory for install................................................ 18
4 Command to register the wizard .................................................................................. 22
5 Options of the nsrdaadmin command ......................................................................... 24
6 Resultant configuration file pathname after NMDA conversion..................................... 25
7 Legacy NetWorker module parameters to change for NMDA......................................... 28
8 Linking and unlinking commands for Oracle library file on UNIX or Linux ..................... 36
9 Linking and unlinking commands for Sybase library file on UNIX or Linux .................... 37
10 Additional steps to enable NMDA for a 32-bit application............................................ 53

EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide 5
Tableses

6 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
PREFACE

As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly or
does not function as described in this document.

Note: This document was accurate at publication time. Go to EMC Online Support
(https://support.emc.com) to ensure that you are using the latest version of this
document.

Purpose
This document describes how to install, update, and remove the EMC NetWorker Module
for Databases and Applications (NMDA) release 1.5.

Audience
This document is intended for system administrators or database administrators (DBAs)
who are responsible for installing software and maintaining backup and recovery systems
for databases or applications.
Users of this guide must be familiar with these topics:
◆ Backup, recovery, database, applications, and network terminology
◆ Backup and recovery procedures
◆ Disaster recovery procedures

Related documentation
You can find additional EMC publications for this product release and related NetWorker
products at EMC Online Support.
The EMC NetWorker Software Compatibility Guide at EMC Online Support provides a full
list of supported environments and platforms.
The following additional documentation might be useful:
◆ Database or application server documentation
◆ Database or application backup and recovery documentation

Conventions used in this document

EMC uses the following conventions for special notices:



NOTICE is used to address practices not related to personal injury.

Note: A note presents information that is important, but not hazard-related.

EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide 7
Preface

Typographical conventions
EMC uses the following type style conventions in this document:
Normal Used in running (nonprocedural) text for:
• Names of interface elements, such as names of windows, dialog boxes,
buttons, fields, and menus
• Names of resources, attributes, pools, Boolean expressions, buttons,
DQL statements, keywords, clauses, environment variables, functions,
and utilities
• URLs, pathnames, file names, directory names, computer names, links,
groups, service keys, file systems, and notifications
Bold Used in running (nonprocedural) text for names of commands, daemons,
options, programs, processes, services, applications, utilities, kernels,
notifications, system calls, and man pages
Used in procedures for:
• Names of interface elements, such as names of windows, dialog boxes,
buttons, fields, and menus
• What the user specifically selects, clicks, presses, or types
Italic Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis, for example, a new term
• Variables
Courier Used for:
• System output, such as an error message or script
• URLs, complete paths, file names, prompts, and syntax when shown
outside of running text
Courier bold Used for specific user input, such as commands
Courier italic Used in procedures for:
• Variables on the command line
• User input variables
<> Angle brackets enclose parameter or variable values supplied by the user
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections—the bar means “or”
{} Braces enclose content that the user must specify, such as x or y or z
... Ellipses indicate nonessential information omitted from the example

Where to get help

EMC support, product, and licensing information can be obtained as follows:
Product information — For documentation, release notes, software updates, or
information about EMC products, go to EMC Online Support at:
https://support.emc.com
Technical support — Go to EMC Online Support and click Service Center. You will see
several options for contacting EMC Technical Support. Note that to open a service request,
you must have a valid support agreement. Contact your EMC sales representative for
details about obtaining a valid support agreement or with questions about your account.
Online communities — Visit EMC Community Network at https://community.EMC.com for
peer contacts, conversations, and content on product support and solutions. Interactively
engage online with customers, partners, and certified professionals for all EMC products.

8 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Preface

Your comments
Your suggestions will help to improve the accuracy, organization, and overall quality of the
user publications. Send your opinions of this document to:
[email protected]

EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide 9
Preface

10 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
CHAPTER 1
Getting Started

This chapter includes the following topics:

◆ NMDA software requirements.................................................................................. 12
◆ Installation checklists ............................................................................................. 15
◆ Accessing the NMDA software ................................................................................. 16
◆ Installation road maps ............................................................................................ 18
◆ Converting legacy scheduled backup configurations to NMDA ................................. 22

Getting Started 11
Getting Started

NMDA software requirements

EMC® NetWorker® Module for Databases and Applications (NMDA) is an add-on module
for the NetWorker client software to provide backup and recovery services for the
supported DB2, Informix, Lotus Domino/Notes, MySQL, Oracle, and Sybase data.
NMDA replaces all the following NetWorker modules:
◆ 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)
You must uninstall any legacy NetWorker modules from the system before you install
NMDA.
Table 1 on page 12 lists the hosts and software you might need for NMDA services.

Table 1 Typical hosts and software in the NMDA backup and recovery environment

Host Required software

NetWorker server • NetWorker client

• NetWorker storage node
• NetWorker server

NetWorker storage node • NetWorker client

• NetWorker storage node

NetWorker Management Console (NMC) server • NetWorker client

• NMC server

Each supported database server (NMDA host) • Supported database or application server
• NetWorker client
• NMDA
• For DB2 and Oracle snapshot operations with
NetWorker client 8.0.x or earlier, EMC
NetWorker Module for PowerSnap™ software
• For snapshot operations with Oracle ASM,
EMC Replication Manager software

Review the following software descriptions to plan your installation requirements.

The EMC NetWorker Software Compatibility Guide at EMC Online Support and the EMC
NetWorker Module for Databases and Applications Release 1.5 Release Notes describe
the operating systems and the software versions required for NMDA services.
The Support link at EMC Online Support describes patches required for a particular
system.
The EMC NetWorker Installation Guide describes how to install the NetWorker server,
storage node, client, and NMC software.

Database or application server software

Ensure that the supported DB2, Informix, Lotus Domino/Notes, MySQL, Oracle, or Sybase
database or application server is installed on an operating system that supports the
NetWorker client and NMDA versions to be installed on that host.

12 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

If you install NMDA in a non-English environment, ensure that the host operating system
supports internationalization (I18N). Also ensure that the database or the application
software provides the required National Language Support (NLS) or globalization support,
and is configured with the required non-ASCII character set.

MySQL software
If you install NMDA on a MySQL database server host, you must meet the following
requirements for MySQL support:
◆ MEB version 3.6 or 3.7 is installed on the MySQL server host. Any other MEB version is
not supported.
◆ 32-bit MEB is installed for 32-bit MySQL support, and 64-bit MEB is installed for 64-bit
MySQL support.
◆ MySQL client library libmysqlclient.so version 18 is installed on the MySQL server
host, and the corresponding symbolic link is created.
You can use the following steps to install the MySQL client library libmysqlclient.so
version 18 on the MySQL host and create the corresponding symbolic link.
1. Install MySQL libmysqlclient.so.18 by downloading and installing
MySQL-shared-version.rpm or MySQL-shared-compat-version.rpm from MySQL,
where version depends on the Linux operating system and MySQL version in use.
2. Create a symbolic link to libmysqlclient.so.18:
– To create the link on 32-bit Linux, type the following command:
ln –s /usr/lib/libmysqlclient.so.18
/usr/lib/nsr/apps/libmysqlclient.so

– To create the link on 64-bit Linux, type the following command:

ln –s /usr/lib64/libmysqlclient.so.18
/usr/lib/nsr/apps/lib64/libmysqlclient.so

To verify the version of the installed MySQL client library, use the ls -lart command.
For example:
• On 32-bit Linux:
ls -lart /usr/lib/libmysqlclient*

• On 64-bit Linux:
ls -lart /usr/lib64/libmysqlclient*

NetWorker server software

You must install a supported version of the NetWorker server software (with all applicable
patches) on the NetWorker server host. The NetWorker server host is usually a separate
host, but the server host can also be the NMDA host.
You might require specific NetWorker server versions to support specific NMDA features as
described in the EMC NetWorker Module for Databases and Applications Release 1.5
Release Notes.

NMDA software requirements 13

Getting Started

You must use a certified version of the NetWorker server that works with the NetWorker
client version installed on the NMDA host. The operating systems used must support the
NetWorker server version.

NMC server software

You must install a supported version of the NMC software on a network host to provide a
user interface with the NetWorker software and NMDA.

NetWorker storage node software

You must install a supported version of the NetWorker storage node software on the host
that manages the backup storage devices. You can install the NetWorker storage node on
the same host as the NetWorker server, on the same host as NMDA (to support backups to
a local device), or on a separate host.
You must use a certified version of the NetWorker storage node that works with the
NetWorker client version installed on the NMDA host and the NetWorker server. The
operating systems used must support the NetWorker storage node version.

NetWorker client software

You must install a supported version of the NetWorker client software on the supported
database server host or application server host before you install NMDA on that host.
Additional requirements are as follows:
◆ Only the more recent NetWorker client versions support some NMDA features as
described in the EMC NetWorker Module for Databases and Applications Release 1.5
Release Notes.
◆ On Linux systems except Linux s390x (zLinux), the bitness of NMDA must match the
bitness of the NetWorker client software.
◆ You must use a certified version of the NetWorker client that runs on the host
operating system.

Note: NetWorker client release 8.1 or later includes the NetWorker Snapshot Management
(NSM) feature that integrates and replaces the previous stand-alone NetWorker
PowerSnap Module. NMDA can use PowerSnap or NSM to provide a high-availability
storage environment for snapshot backup and restore operations.

NMDA software
You must install NMDA on a supported database server or application server. You must
use a certified version of NMDA to run on the host operating system with the installed
database version or application software version.
For Oracle ASM snapshot backups and restores with EMC Replication Manager, you must
also install NMDA on the proxy host (data mover).

14 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

PowerSnap software
To enable PowerSnap snapshot backup features for DB2 and Oracle with NetWorker client
release 8.0.x or earlier, you must install the NetWorker PowerSnap Module designed for
the primary storage system on both of the following hosts:
◆ NMDA host
◆ A proxy client host, also called the data mover, which can be a NetWorker storage
node
The proxy client host can be either of the following hosts:
• A separate host (to offload the data transfer from the database host)
• The same host as the database host
The NetWorker PowerSnap Module documentation provides details.

Note: NetWorker client release 8.1 or later includes the NetWorker Snapshot Management
(NSM) feature that integrates and replaces the previous stand-alone NetWorker
PowerSnap Module.

Replication Manager software

You cannot back up Oracle ASM by using NetWorker PowerSnap Module or NSM. To enable
snapshot backups with Oracle ASM, EMC Replication Manager server software must work
with Replication Manager agent software installed on both of the following hosts:
◆ Oracle server
◆ A mount host (data mover), which can be a NetWorker storage node
The EMC Replication Manager documentation provides installation information.

Installation checklists
Review the following checklists to ensure that you have the required materials for the
installation procedures.

Documents
You can find the required information in the following documents:
◆ EMC NetWorker Module for Databases and Applications Installation Guide
(appropriate version to uninstall a previous NMDA release, if required)
◆ EMC NetWorker Module for Databases and Applications Release 1.5 Release Notes
◆ EMC NetWorker Module for Databases and Applications Release 1.5 Administration
Guide
◆ EMC NetWorker Administration Guide for the supported NetWorker release
◆ The latest EMC NetWorker Software Compatibility Guide

Installation checklists 15
Getting Started

Installation media
You must use one of the following installation media:
◆ DVD from the EMC Information Protection and Availability Product Families Media Kit
◆ Link to the EMC website if you download the software

License enablers
You must use the following license enablers:
◆ Evaluation enabler
◆ Enabler certificate
NMDA release 1.5 has separate license enablers for UNIX systems and for Microsoft
Windows/Linux systems.

Note: Without an enabler code, you can only evaluate the software obtained from the DVD
or the EMC website.

The EMC NetWorker Licensing Guide describes licensing.

The EMC Price Guide describes the licensing requirements for NetWorker modules.

Accessing the NMDA software

The NMDA software is distributed on DVD media and on the EMC website.

Accessing NMDA from the DVD media

The DVD is in the EMC Information Protection and Availability Product Families Media Kit.
The kit contains the software and online documentation for related products.
You can access the NMDA software files from the NetWorker Module DVD on a host with a
local DVD drive.
1. Log in as the root user (UNIX or Linux) or system administrator (Windows) on the host.
2. Insert and mount the NetWorker Module DVD in the DVD drive:
• On UNIX or Linux, mount the DVD drive:
mount /dev/DVD_drive_name /mount_point

• On Windows, select the DVD drive in Windows Explorer.

3. Go to the directory that contains the software as shown in Table 2 on page 17.
The EMC NetWorker Software Compatibility Guide describes the operating systems,
database software, and application software that NMDA supports.

16 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

Table 2 Software directory on the DVD

Operating system (NMDA bitness) Software directory

AIX (32-bit) /mount_point/nmda/aix_32

AIX (64-bit) /mount_point/nmda/aix_64
HP Itanium (64-bit) /mount_point/nmda/hpux11_ia64
HP PA-RISC (64-bit) /mount_point/nmda/hpux11_64
Linux s390x (64-bit) /mount_point/nmda/linuxs390x
Linux x64 (64-bit) /mount_point/nmda/linux_x86_64
Linux x86 (32-bit) /mount_point/nmda/linux_x86
Solaris x64 (64-bit) /mount_point/volume_label/nmda/solaris_amd64
Sun SPARC (32-bit) /mount_point/volume_label/nmda/solaris_32
Sun SPARC (64-bit) /mount_point/volume_label/nmda/solaris_64
Windows x64 (64-bit) DVD_drive_letter:\nmda\win_x64
Windows x86 (32-bit) DVD_drive_letter:\nmda\win_x86

Accessing NMDA from the EMC website

You can download the NMDA software files from the EMC Online Support website.
1. Log in as the root user (UNIX or Linux) or system administrator (Windows) on the host.
2. Create a temporary installation download directory in a local file system with sufficient
free disk space to contain both the downloaded software package and the software
installation files extracted from the package. For example:
• On UNIX or Linux:
mkdir /usr/nsr_extract_nmda

• On Windows:
mkdir C:\Downloads\nmda

3. Go to EMC Online Support at https://support.emc.com.

4. Go to the Downloads for NetWorker Module for Databases and Applications page.
The EMC NetWorker Software Compatibility Guide describes the operating systems,
database software, and application software that NMDA supports.
5. Download the NMDA release 1.5 software file to the temporary directory that you
created.

Accessing the NMDA software 17

Getting Started

6. Extract the installation files from the downloaded software package:

• On UNIX or Linux:
a. Uncompress the downloaded package by typing the gunzip command with the
file_name.tar.gz name for the specific download file name:
gunzip file_name.tar.gz

b. Extract the software from the uncompressed, tarred file:

tar -xvpBf file_name.tar

The extraction lists the distribution software files on the screen.

c. Remain in the directory for the installation.
• On Windows:
a. Unzip the downloaded software package as shown in Table 3 on page 18.
b. Go to the correct directory as shown in Table 3 on page 18.

Table 3 Zipped download file and software directory for install

Downloaded software file Directory for install

nmda15_win_x64.zip win_x64

nmda15_win_x86.zip win_x86

Installation road maps

Follow the appropriate road map to install NMDA:
◆ “Road map to install or update NMDA on a local host” on page 18
◆ “Road map to update NMDA remotely by push install” on page 20
◆ “Road map to post-installation procedures” on page 21

Road map to install or update NMDA on a local host

Follow these instructions to install or update NMDA locally on a host in any of the
following configurations:
◆ Single host
◆ Active-passive cluster
◆ Active-active application cluster, 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.

You must install NMDA on each node host in a cluster that will perform backup and
recovery operations.

18 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

The EMC NetWorker Software Compatibility Guide at EMC Online Support describes
the supported versions and cluster environments.
1. Review the “Installation checklists” on page 15 and verify that you have the required
documentation, installation media, pathnames, and license information.
2. If you installed Informix Storage Manager (ISM) on the host, uninstall ISM according to
the instructions in Appendix A, “Uninstalling ISM on an Informix Server.”
3. Ensure that you have installed the NetWorker client software on the host. The client
version must support the NMDA version to be installed.
The EMC NetWorker Module for Databases and Applications Release 1.5 Release
Notes describes the supported NetWorker software.
4. Access the NMDA software as described in “Accessing the NMDA software” on
page 16 and ensure that you are in the correct directory.

Note: If you do not start the installation from the correct directory, the installation
might fail.

5. Ensure that no backups or restores are running on the database server or application
server. You do not need to shut down a supported database or application during the
installation.
6. If any of the following NetWorker modules exist on the host, uninstall the modules by
using the following substeps before you install NMDA release 1.5:
• Previous version of NMDA
• 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)



Do not use an upgrade option on the platform, for example, the rpm -U command on
Linux.

Perform the following steps to uninstall an existing NetWorker module:

a. If you are updating from NMI, NMO, or NMS and you modified the script nsrdbmi,
nsrnmo, or nsrsyb, respectively, originally installed with the module instead of
modifying a copy of the script, perform these steps before you uninstall the
module:
1. Copy the script file (nsrdbmi, nsrnmo, or nsrsyb) to a new file with a different
name, for example, to the file nsrdbmi2, nsrnmo2, or nsrsyb2, respectively.
2. Change the script name in the Backup Command attribute of the Client
resource from the original name (nsrdbmi, nsrnmo, or nsrsyb) to the new file
name.
b. Uninstall the NetWorker module according to the instructions in the installation
guide for the module version.

Installation road maps 19

Getting Started

Note: You can use NMDA to restore backups performed with any of the legacy
NetWorker modules that NMDA supports.

7. Start the NetWorker client service before the NMDA installation.

Note: If you do not start the NetWorker client before the NMDA installation, then
automatic registration of the NMDA configuration wizard might not occur and the
wizard might fail to run after the installation. “Road map to post-installation
procedures” on page 21 describes the manual wizard registration.

8. If you want to install NMDA on a system that runs both a 32-bit and 64-bit database or
application supported by NMDA, follow the instructions in Chapter 4, “NMDA with
Mixed 32-bit and 64-bit Databases and Applications.”

Note: On HP Itanium, if you installed Sybase ASE 15.5 or later and Sybase ASE 15.0.x
on the same system, you must follow the instructions in Chapter 4, “NMDA with Mixed
32-bit and 64-bit Databases and Applications,” because the ASE Backup Server is
64-bit in the 15.5 and later releases and the server is 32-bit in earlier releases.

If the system runs a single database or application or if the system runs multiple
databases or applications that are all supported by a single NMDA package, then skip
this step.
9. If you performed step 8, then skip this step. Otherwise, install NMDA by following the
instructions for the operating system in the appropriate chapter:
• Chapter 2, “UNIX and Linux Installation”
• Chapter 3, “Microsoft Windows Installation”
After the software installation completes, a message appears about how to start the
NMDA scheduled backup configuration wizard. The EMC NetWorker Module for
Databases and Applications Release 1.5 Administration Guide describes the wizard.
10. Perform all the required post-installation procedures. “Road map to post-installation
procedures” on page 21 provides details.

Road map to update NMDA remotely by push install

You can update NMDA on one or more remote NMDA hosts with the software distribution
(push install) feature from a centralized NetWorker server. You can perform a push
installation with the Software Administration Wizard or the nsrpush command.

Note: Cluster environments do not support push installation.

The EMC NetWorker Installation Guide describes the software distribution feature,
including these procedures:
◆ Viewing software installed on NetWorker clients
◆ Performing and monitoring push installations
◆ Managing the repository of software to push install from the NetWorker server

20 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

Note: To add a new version of NMDA to the NetWorker server repository, follow the
NetWorker installation guide instructions for the nsrpush command. For the Product
Name variable, type the complete name “NetWorker Module for Databases and
Applications” with the quotation marks.

You can use the following steps to update NMDA remotely by push install.
1. Review the “Installation checklists” on page 15.
2. Ensure that you meet the following requirements:
• The remote NMDA clients contain a previous release of NMDA, and the client
operating systems support push install.
The EMC NetWorker Module for Databases and Applications Release 1.5 Release
Notes describes the operating systems that support push installation on NMDA
hosts.
• The NMDA software version to be push installed exists in the software distribution
repository of the NetWorker server that will perform the push install.
• The NetWorker Console server includes administrative privileges for the user who
performs the update.
3. Ensure that all NetWorker backups are stopped before you start any push install
updates.

Note: The software distribution program might stop and restart the NetWorker client
nsrexecd daemon during the installation.

4. On the NetWorker server, perform the push installation to update the NMDA clients by
using either the Software Administration wizard or the nsrpush command.
The EMC NetWorker Installation Guide describes the different methods of push
installation with the NetWorker software distribution feature.
5. Perform all the required post-installation procedures on each host. “Road map to
post-installation procedures” on page 21 provides details.

Road map to post-installation procedures

After you have installed or updated NMDA, either directly on a local host or by remote
installation (push install), you must complete the installation by performing any required
post-installation procedures.
1. If you are installing NMDA for the first time on the host, register and enable NMDA to
work with the NetWorker software.
The EMC NetWorker Licensing Guide describes licensing and enabling of software.
The EMC Price Guide describes the licensing requirements for NetWorker modules.
If you are updating from a previous NMDA release or from a legacy NetWorker module
(NMDB2, NMI, NML, NMO, or NMS), you do not need to reenable the software.

Installation road maps 21

Getting Started

2. If you are updating from a legacy NetWorker module, convert the existing scheduled
backup configuration to NMDA. “Converting legacy scheduled backup configurations
to NMDA” on page 22 provides details.
3. If you will perform PowerSnap snapshot backups and restores on the host (DB2 and
Oracle only) with NetWorker client 8.0.x or earlier, install and enable the required
PowerSnap Module on the NMDA host and the proxy client (data mover) host.
The NetWorker PowerSnap Module documentation and the EMC NetWorker Module for
Databases and Applications Release 1.5 Administration Guide provide details.
4. If you will perform snapshot backups for Oracle ASM on the host, install and enable
the required Replication Manager agent software on the NMDA host and the proxy
client (data mover) host.
The Replication Manager server software must exist on a separate host.
5. If automatic wizard registration did not occur during the NMDA installation and the
NMDA configuration wizard fails to run, manually register the wizard:
a. Log in as the root user (UNIX or Linux) or system administrator (Windows).
b. At a command prompt, type the appropriate command as listed in Table 4 on
page 22.

Note: To manually unregister the wizard, use the command from the table but
replace the -i option with -u.

Table 4 Command to register the wizard

Database or application Wizard registration command

DB2 nsrdb2ra(.exe) -i

Informix nsrifmxra(.exe) -i

Lotus nsrlotusra(.exe) -i

MySQL nsrmysqlra(.exe) -i

Oracle nsrorara(.exe) -i

Sybase nsrsybra(.exe) -i

6. Configure the NMDA software.

The EMC NetWorker Module for Databases and Applications Release 1.5
Administration Guide provides details.

Converting legacy scheduled backup configurations to NMDA

If you upgrade to NMDA from a supported legacy NetWorker module (NMDB2, NMI, NML,
NMO, or NMS), you must convert the existing (original) scheduled backup configurations
to NMDA configurations. Otherwise, the scheduled backup will fail after the upgrade.
The two methods of conversion, in order of recommendation, are as follows:
◆ “Converting legacy backup configurations to NMDA with nsrdaadmin” on page 23
◆ “Converting legacy backup configurations to NMDA manually” on page 25

22 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

Converting legacy backup configurations to NMDA with nsrdaadmin

The recommended method to convert the supported legacy (original) NetWorker module
backup configurations to new configurations supported by NMDA is to use the
nsrdaadmin command.
The nsrdaadmin command finds and converts scheduled backup configurations of
supported legacy NetWorker modules, no matter which method was originally used to
create the configuration:
◆ If you created the original configuration with the NMDB2 or NMO wizard, the
conversion creates a new NMDA wizard (server-side) configuration.
◆ If the original configuration used a configuration file (NMDB2 or NML) or a backup
script (NMI, NMO, or NMS), the conversion creates a new client-side NMDA
configuration that uses the NMDA configuration file.
“Results of the nsrdaadmin conversion” on page 24 describes the changes that the
system makes during the conversion.
You must meet the following requirements for the nsrdaadmin conversion:
◆ Backup shell or batch scripts for NMI (nsrdbmi), NMO (nsrnmo), or NMS (nsrsyb) must
conform to the templates supplied with the legacy NetWorker module.
◆ NML backups must use the nsrnotesv -z option in the Backup Command field of the
NML Client resource.
If you cannot meet these requirements, perform the conversion manually according to the
steps in “Converting legacy backup configurations to NMDA manually” on page 25.
To convert legacy configurations with the nsrdaadmin command:
1. Log in as the root user (UNIX or Linux) or system administrator (Windows) on the
NMDA client host to be converted.
2. Ensure that you have the Configure NetWorker user group privilege. The NetWorker
documentation provides details.
3. If you are upgrading from NMS on UNIX or Linux, run the SYBASE.sh script to set any
required environment variables.
4. At an operating system prompt, type the following command:
nsrdaadmin -M -s server_name [-c client_name] [-g group_name]
[-N save_set_name] [-Y]

Table 5 on page 24 lists the nsrdaadmin command options. The EMC NetWorker
Module for Databases and Applications Release 1.5 Command Reference Guide
provides details.

Converting legacy scheduled backup configurations to NMDA 23

Getting Started

Table 5 Options of the nsrdaadmin command

Option Description

-M Mandatory. Specifies the conversion from the legacy NetWorker module

to NMDA.

-c client_name Optional. Specifies the hostname of the NetWorker client to be

converted. The default value is the name of the local physical host. In a
cluster, you must set this option to a virtual client.

-g group_name Optional. Converts only the configurations of the client (either the
default or set through the -c option) associated with this group_name.

-N save_set_name Optional. Converts only the configurations of the client (either the
default or set through the -c option) associated with this
save_set_name.
-s server_name Mandatory. Specifies the hostname of the NetWorker server that backs
up the client that is being converted.

-Y Optional. Specifies that the conversion does not issue prompts for
confirmation. If you do not specify this option, nsrdaadmin asks for user
confirmation before proceeding with the conversion.

Results of the nsrdaadmin conversion

During the conversion of supported legacy configurations, the nsrdaadmin command sets
the following values in the NetWorker Client resource:
◆ Sets the Backup Command attribute to:
nsrdasv [-z config_file] [-T app] [-c client]

where:
• config_file is the pathname of the new NMDA configuration file created by the
conversion on the NMDA host. This option is set only when converting to a
client-side NMDA configuration.
The settings in this new configuration file are based on the original Client resource
Backup Command attribute and the original configuration file or script. The original
configuration file or script might be renamed but it is not modified and is not used
by NMDA. Table 6 on page 25 describes the names and locations of the NMDA
configuration file and the original file or script.
• app is db2, informix, lotus, oracle, or sybase, depending on the database or
application.
• client is the client name found in the old value of the Backup Command attribute.

Note: The conversion also sets the same value in the NSR_CLIENT parameter in the
NMDA configuration file for a client-side NMDA configuration.

◆ Sets the Comment attribute to indicate that this resource is an NMDA Client resource.
◆ If converting from NMS, sets the Remote User attribute and Password attribute to
empty values. The conversion sets these options in the NMDA configuration file
instead.

24 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

The Save Set attribute remains unchanged from its original value in the NetWorker module
Client resource.

Table 6 Resultant configuration file pathname after NMDA conversion

Type of
configuration
converted NMDA configuration file pathname

NMDB2 Same as the original NMDB2 configuration file pathname.

The original NMDB2 configuration file is saved as
original_NMDB2_config_file_path.orig.
NMI • UNIX or Linux:
/nsr/apps/config/original_nsrdbmi_script_name.cfg
• Windows:
NetWorker_install_dir\apps\config\original_nsrdbmi_script_name.cfg
The original NMI script is unchanged.

NML Same as the original NML configuration file pathname.

The original NML configuration file is saved as
original_NML_config_file_path.orig.
NMO • UNIX or Linux:
/nsr/apps/config/original_nsrnmo_script_name.cfg
• Windows:
NetWorker_install_dir\apps\config\original_nsrnmo_script_name.cfg
The original NMO script is unchanged.

NMS • UNIX or Linux:

/nsr/apps/config/original_nsrsyb_script_name.cfg
• Windows:
NetWorker_install_dir\apps\config\original_nsrsyb_script_name.cfg
The original NMS script is unchanged.

Converting legacy backup configurations to NMDA manually

If you cannot use the nsrdaadmin command to convert an existing supported legacy
NetWorker module backup configuration to the NMDA backup configuration, you can
convert manually by following the appropriate instructions:
◆ “Converting a wizard-based NMDB2 or NMO backup configuration manually” on
page 26
◆ “Converting a file-based NMDB2 backup configuration manually” on page 26
◆ “Converting a script-based NMI, NMO, or NMS backup configuration manually” on
page 26
◆ “Converting a legacy NML backup configuration manually” on page 27

Converting legacy scheduled backup configurations to NMDA 25

Getting Started

Converting a wizard-based NMDB2 or NMO backup configuration manually

To manually convert a scheduled backup configuration created with the NMDB2 4.0 or
NMO 5.0 wizard to an NMDA configuration:
1. In the existing NetWorker Client resource for the NMDB2 or NMO client, clear the group
attribute.
2. Run the NMDA configuration wizard to configure a new DB2 or Oracle backup. The EMC
NetWorker Module for Databases and Applications Release 1.5 Administration Guide
provides details.
3. Ensure that the new NMDA configuration works and then delete the original NMDB2 or
NMO Client resource.

Converting a file-based NMDB2 backup configuration manually

To manually convert a NMDB2 scheduled backup configuration that uses a configuration
file to an NMDA configuration:
1. Use the existing NMDB2 backup configuration file to create a configuration file that
contains valid values for NMDA. “Creating the NMDA configuration file manually” on
page 27 provides details.
2. Use the NMC program to update the NetWorker Client resource that you used for the
NMDB2 backups. The Backup Command attribute for the client must contain the
following value:
nsrdasv [-T db2] –z config_file

where config_file is the complete pathname of the valid NMDA configuration file from
step 1.

Converting a script-based NMI, NMO, or NMS backup configuration manually

Follow the appropriate instructions to manually convert an existing NMI, NMO, or NMS
scheduled backup script to NMDA.

Converting a script that conforms to the supplied template

If the scheduled backup script conforms to the template provided by the NetWorker
module, convert the configuration files as follows:
1. Copy only the environment variable settings from the script file specified in the
Backup Command attribute of the NetWorker Client resource and create a
configuration file that contains the valid values of those variable settings for NMDA.
“Creating the NMDA configuration file manually” on page 27 provides details.
2. Use the NMC program to update the NetWorker Client resource that you used for the
NMI, NMO, or NMS backups. The Backup Command attribute must contain the
following value:
nsrdasv [-T app] –z config_file

where:
• app is informix, oracle, or sybase.
• config_file is the complete pathname of the valid NMDA configuration file.

26 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Getting Started

3. For Sybase backups only, delete any existing values in the Remote User attribute and
Password attribute of the NetWorker Client resource.
You must set the Sybase username and password with the nsrdaadmin -P command in
the NMDA configuration file. The EMC NetWorker Module for Databases and
Applications Release 1.5 Administration Guide provides details.

Converting a script that does not conform to the supplied template

If the legacy backup script does not conform to the template provided by the NetWorker
module, and you want to preserve the backup preprocessing or postprocessing that you
added to the script, you can continue to use the existing script for NMDA backups if you
modify the script as follows:
1. Use the NMDA parameters described in Table 7 on page 28 to replace obsolete
parameters with the correct NMDA parameters.
2. Replace the original backup command, such as nsrifmx (NMI), nsrnmostart (NMO), or
nsrsybsv (NMS) with the nsrdasv command and the correct options.

Converting a legacy NML backup configuration manually

To manually convert an NML scheduled backup configuration to an NMDA configuration:
1. Ensure the valid parameter settings in the configuration file for NMDA backups:
• If the NML backups did not use a configuration file (the Backup Command attribute
in the Client resource did not contain nsrnotesv -z config_file), create a
configuration file for NMDA that includes the required parameter settings.
• If the NML backups did use a configuration file, modify any required parameter
settings in the file to create a configuration file that contains valid parameter
names and values for NMDA. “Creating the NMDA configuration file manually” on
page 27 provides details.
2. Use the NMC program to update the NetWorker Client resource that you used for the
NML backups. The Backup Command attribute must contain the following value:
nsrdasv [-T lotus] –z config_file

where config_file is the complete pathname of the valid NMDA configuration file from
step 1.

Creating the NMDA configuration file manually

If you upgrade from a supported legacy NetWorker module to NMDA and you cannot use
the nsrdaadmin command, you must manually create the NMDA configuration file.
The EMC NetWorker Module for Databases and Applications Release 1.5 Administration
Guide provides details about the NMDA configuration file format and all the supported
NMDA parameters.
Table 7 on page 28 lists the legacy parameters that you must change to valid NMDA
parameters.

Converting legacy scheduled backup configurations to NMDA 27

Getting Started

Table 7 Legacy NetWorker module parameters to change for NMDA

NetWorker
module Legacy parameters Parameter changes in NMDA

All NSR_DEBUG_FILE Dropped. Use NSR_DIAGNOSTIC_DEST instead.

NSR_ENCRYPTION Dropped. Use NSR_AES_ENCRYPTION instead.

NMDB2 DB2_PSWD Replaced by USER_PSWD.

Note: The password remains unchanged and

the encryption procedure remains unchanged.

DB2_USR Replaced by DB2_USER.

NSR_DB2_BACKUP_INFO Replaced by NSR_DR_BACKUP_INFO.

If NSR_DB2_BACKUP_INFO was not set,
NSR_DR_BACKUP_INFO is set to TRUE
(default).

NSR_DB2_CONFIG_FILE Replaced by NSR_DR_FILE_LIST.

NSR_*_DEBUG* Replaced by NSR_DEBUG_LEVEL.

NMI BOOTFILE Replaced by NSR_DR_FILE_LIST.

DO_BOOTFILE_BACKUPS Replaced by NSR_DR_BACKUP_INFO.

NML LOTUSUSER Replaced by LOTUS_USER.

NMO NSR_SB_DEBUG_FILE Replaced by NSR_DEBUG_LEVEL=1.

NMS BACKUP_OPT Replaced by new NMDA parameters (SYBASE

and LD_LIBRARY_PATH, LIBPATH, or
SHLIB_PATH) described in the EMC NetWorker
Module for Databases and Applications
Release 1.5 Administration Guide.

28 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
CHAPTER 2
UNIX and Linux Installation

This chapter includes the following topics:

◆ Installing NMDA on AIX systems .............................................................................. 30
◆ Installing NMDA on HP-UX systems ......................................................................... 31
◆ Installing NMDA on Linux systems........................................................................... 31
◆ Installing NMDA on Solaris systems ........................................................................ 32
◆ Linking and unlinking NMDA in the environment on UNIX or Linux ........................... 34
◆ Uninstalling NMDA on UNIX or Linux systems .......................................................... 39

UNIX and Linux Installation 29

UNIX and Linux Installation

Installing NMDA on AIX systems

You can install NMDA on an AIX system by running the installp command-line interface
(CLI) program or the AIX System Management Interface Tool (SMIT), which is a graphical
user interface (GUI) program.
1. Complete the initial steps in “Installation road maps” on page 18. Ensure that you log
in as the root user, no database or application backups are running, and you are in the
correct directory, which contains the NMDA installation files.
2. Run either the installp CLI program or the SMIT GUI program:
• To run the CLI program, type the following command:
installp -a -d /dir_pathname LGTOnmda.rte

where /dir_pathname is the complete pathname of the correct directory that

contains the installation software as described in “Accessing the NMDA software”
on page 16.
To verify that the installation succeeded, type the following command:
lslpp -L all | grep -i lgtonmda

If the lslpp command output includes LGTOnmda.rte 1.5.0.0, then the installation
succeeded.
• To run the SMIT GUI program, perform the following steps:
a. Type the following command:
smitty install_latest

b. In the Entry Field, type the location of the NMDA installation software as the
complete pathname of the directory described in “Accessing the NMDA
software” on page 16.
c. Select the option SOFTWARE to install .
d. Type yes in response to the following prompts:
Accept new license agreements?
Preview new license agreements?

e. Select F4=List to display the list of the NMDA software packages.

f. Select LGTOnmda.rte to install the NMDA software.
g. Select Install and Update Software.
h. Press Enter to begin the installation.
3. Link NMDA to the database server environment by completing the steps in “Linking
and unlinking NMDA in the environment on UNIX or Linux” on page 34.
4. When the NMDA installation is complete, return to the installation road map to
perform any post-installation procedures. “Road map to post-installation procedures”
on page 21 provides details.

30 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 UNIX and Linux Installation

Installing NMDA on HP-UX systems

You can install NMDA on an HP-UX system by using the swinstall command to run the
command-line interface (CLI) or the graphical user interface (GUI) program.
1. Complete the initial steps in “Installation road maps” on page 18. Ensure that you log
in as the root user, no database or application backups are running, and you are in the
correct directory, which contains the NMDA installation files.
2. Type the swinstall command to run either the CLI or GUI program:
• To run the swinstall CLI program, type the following command:
swinstall -x mount_all_filesystems=false
-s /dir_pathname/LGTOnmda.pkg NMDA

where /dir_pathname is the complete pathname of the directory that contains the
software installation files as described in “Accessing the NMDA software” on
page 16.
• To run the swinstall GUI program, type the following command:
swinstall -x mount_all_filesystems=false -i
-s /dir_pathname/LGTOnmda.pkg NMDA

where /dir_pathname is the complete pathname of the directory that contains the
software installation files as described in “Accessing the NMDA software” on
page 16. Perform the following steps in the GUI program:
a. From the Actions menu, select Install (analysis).
When the analysis is complete, a “Ready with Warnings” message appears. The
message is normal.
b. Click OK to continue the installation.
The NMDA installation on HP-UX stores informational messages including installation
errors in the /var/adm/sw/swagent.log file. If an error occurs during the installation,
check this file to obtain details about the error.
3. Link NMDA to the database server environment by completing the steps in “Linking
and unlinking NMDA in the environment on UNIX or Linux” on page 34.
4. When the NMDA software installation is complete, return to the installation road map
to perform any post-installation procedures. “Road map to post-installation
procedures” on page 21 provides details.

Installing NMDA on Linux systems

You can install NMDA on a Linux system by running the rpm command. You can optionally
install NMDA in a non-default directory on Linux.
1. Complete the initial steps in “Installation road maps” on page 18. Ensure that you log
in as the root user, no database or application backups are running, and you are in the
correct directory, which contains the NMDA installation files.
2. To install NMDA, type the appropriate rpm command.

Installing NMDA on HP-UX systems 31

UNIX and Linux Installation

Note: You must install NMDA in the same directory as the NetWorker client software.

If you installed the NetWorker client software in a non-default directory, add this
option to the rpm commands that follow:
--relocate /usr=NetWorker_base_dir

where NetWorker_base_dir is the directory where the NetWorker client software

resides.
To install NMDA in the default directory, type the rpm command:
• On Linux s390x (zLinux) 64-bit:
rpm -i lgtonmda-1.5.0.0-1.s390x.rpm

• On Linux x64:
rpm -i lgtonmda-1.5.0.0-1.x86_64.rpm

• On Linux x86:
rpm -i lgtonmda-1.5.0.0-1.i686.rpm

3. To verify that the installation was successful, type the rpm -aq command:
rpm -aq | grep -i lgto

The command output must include the appropriate lines, for example:
lgtoclnt-8.0.0.5-1
lgtonmda-1.5.0.0-1

4. Link NMDA to the database server environment by completing the steps in “Linking
and unlinking NMDA in the environment on UNIX or Linux” on page 34.
5. When the NMDA installation is complete, return to the installation road map to
perform any post-installation procedures. “Road map to post-installation procedures”
on page 21 provides details.

Installing NMDA on Solaris systems

You can install NMDA on a Solaris system by running the pkgadd command. You can
optionally install NMDA in a non-default directory on Solaris.
1. Complete the initial steps in “Installation road maps” on page 18. Ensure that you log
in as the root user, no database or application backups are running, and you are in the
correct directory, which contains the NMDA installation files.

Note: If the Solaris system has Solaris zones (containers) and NMDA is to run on a
sparse root zone, install NMDA on the global zone and on each required sparse root
zone.

32 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 UNIX and Linux Installation

2. Verify the basedir variable setting in the /var/sadm/install/admin/default file.

You must install NMDA in the same base directory as the NetWorker client software.
You can set the basedir variable in this file to one of three possible values:
• If basedir=default, the system installs the software in the same directory as the
NetWorker client software.
• If basedir=ask, the system prompts you for the name of the base directory where
the software will be installed.
• If basedir=/dirpath, the system installs the software in the /dirpath directory. The
/dirpath must be the pathname of the NetWorker client software base directory as
determined by this pkgparam command:
pkgparam LGTOclnt BASEDIR

3. Type the appropriate pkgadd command:

pkgadd -d /dir_pathname LGTOnmda

where /dir_pathname is the complete pathname of the directory that contains the
LGTOnmda package.
4. Complete the NMDA installation, depending on the basedir variable setting in the
/var/sadm/install/admin/default file:
• If basedir=default in the file, type y when prompted whether to continue the
installation.
The system installs the software in the same directory as the NetWorker client
software.
• If basedir=ask in the file, perform the following steps:
a. When prompted for the pathname of the base directory, type the result of the
pkgparam LGTOclnt BASEDIR command that provides the path of the NetWorker
client software.
b. Type y when prompted whether to continue the installation.
The system installs the software in the specified base directory.

Note: If you type an incorrect pathname, where the NetWorker client is not located,
the installation displays an error, and the software is installed in the incorrect
directory. In this case:
a. Uninstall the software by typing the pkgrm LGTOnmda command.
b. Reinstall the software by typing the correct pathname at the first pkgadd
prompt.

• If basedir=/dirpath in the file, type y when prompted whether to continue the

installation.
The system installs the software in the specified /dirpath directory.

Installing NMDA on Solaris systems 33

UNIX and Linux Installation

Note: If /dirpath is not the base directory where the NetWorker client software is
installed, the installation displays an error and the software is installed in the
incorrect directory. In this case:
a. Uninstall the software by typing the pkgrm LGTOnmda command.
b. Correct basedir=/dirpath in the /var/sadm/install/admin/default file.
c. Reinstall the software.

5. Link NMDA to the database server environment by completing the steps in “Linking
and unlinking NMDA in the environment on UNIX or Linux” on page 34.
6. When the NMDA installation is complete, return to the installation road map to
perform any post-installation procedures. “Road map to post-installation procedures”
on page 21 provides details.

Linking and unlinking NMDA in the environment on UNIX or Linux

After you install NMDA on UNIX or Linux as described in the first part of this chapter, you
must perform an additional procedure to link NMDA to the database environment. Before
you uninstall NMDA, you must also remove the link.
Perform the appropriate procedure for the database:
◆ “Linking NMDA in a DB2 environment” on page 34
◆ “Linking and unlinking NMDA in an Informix environment” on page 35
◆ “Linking and unlinking NMDA in an Oracle environment” on page 36
◆ “Linking and unlinking NMDA in a Sybase environment” on page 37

Note: In a Lotus Domino environment, you do not require the linking or unlinking
procedure to install or uninstall NMDA.

Linking NMDA in a DB2 environment



You must not set the DB2_VENDOR_INI registry variable. Also, if the
$INSTHOME/sqllib/cfg/vendor.cfg file exists, either remove the file or remove all the
NMDA parameter settings from the file.

After you install NMDA on a DB2 server, use the db2set command to check if the
DB2_VENDOR_INI registry variable is set. The db2set command displays all the variable
settings.
Use the required steps to implement the changes on the DB2 server.
1. Log in as the DB2 DBA user.
2. Remove the $INSTHOME/sqllib/cfg/vendor.cfg file, or edit the file and remove all the
NMDA parameter settings.

34 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 UNIX and Linux Installation

3. Unset the DB2_VENDOR_INI variable.

a. Stop the database instance with the db2stop command.
b. Unset the DB2_VENDOR_INI registry variable with the db2set command:
db2set DB2_VENDOR_INI=

c. Restart the database instance with the db2start command.

Note: You do not require unlinking steps to uninstall NMDA in a DB2 environment.

Linking and unlinking NMDA in an Informix environment

Perform the required link procedure or unlink procedure in an Informix environment:
◆ After you install NMDA, perform the procedure to link NMDA.
◆ Before you uninstall NMDA, perform the procedure to unlink NMDA.

Linking NMDA to the Informix server environment

After you install NMDA, link NMDA to the Informix server environment.
1. Log in as the Informix user.
2. Edit the Informix $ONCONFIG file and set the BAR_BSALIB_PATH variable to the full
pathname of the NMDA libnsrifmx (XBSA) library.
The default library pathname is /usr/lib/libnsrifmx.xx where xx is the platform-specific
extension:
• sl on HP-UX 64-bit systems
• so on AIX, Linux, and other UNIX systems
3. Update the sm_versions file (Informix user password required) by typing the following
command:
echo "1|1.0.1|nwbsa|1">> $INFORMIXDIR/etc/sm_versions

This action updates the NMDA Informix library links. Without the required values,
ON-Bar commands fail and the following message appears:
ERROR: Version 1.0.1 of the XBSA shared library is not compatible
with version 1 of ON-Bar.

4. Restart the IDS server to apply the $ONCONFIG file changes.

Unlinking NMDA from the Informix server environment

Before you uninstall NMDA, unlink NMDA from the Informix server environment.
1. Log in as the Informix user.
2. Edit the Informix $ONCONFIG file and remove the setting from the BAR_BSALIB_PATH
variable.
3. Restore the copy of the sm_versions file, stored by Informix in
$INFORMXIDIR/etc/sm_versions.std.
4. Restart the IDS server to apply the $ONCONFIG file changes.

Linking and unlinking NMDA in the environment on UNIX or Linux 35

UNIX and Linux Installation

Linking and unlinking NMDA in an Oracle environment

Perform the required link or unlink procedure in an Oracle environment:
◆ After you install NMDA, perform the procedure to link NMDA.
◆ Before you uninstall NMDA, perform the procedure to unlink NMDA.

Linking NMDA to the Oracle server environment

Note: You do not need to shut down and restart Oracle instances to perform this
procedure.

After you install NMDA, link NMDA to the Oracle server environment.
1. Log in as the $ORACLE_HOME owner.
2. Create the symbolic link by using one of the following options:
• If you installed NMDA in the default directory, type the appropriate commands
listed in Table 8 on page 36.
• If you installed NMDA in a non-default directory, perform one of the following
actions:
– Copy the libnsrora.xx library file to the default directory /usr/lib, and type the
appropriate linking commands listed in Table 8 on page 36.
– Type the linking commands listed in Table 8 on page 36 except replace the
default installation pathname /usr/lib with the non-default installation
pathname /relocation_path.

Note: The commands apply only to Oracle base releases. The commands might vary
for patched releases of the Oracle server.

Table 8 Linking and unlinking commands for Oracle library file on UNIX or Linux

Operating Create or Install: create the symbolic link

system remove link Uninstall: remove the symbolic link

AIX Create link % cd $ORACLE_HOME/lib

% ln -s /usr/lib/libnsrora.a libobk.a

Remove link % cd $ORACLE_HOME/lib

% rm libobk.a

HP PA-RISC Create link % cd $ORACLE_HOME/lib

% ln -s /usr/lib/libnsrora.sl libobk.sl

Remove link % cd $ORACLE_HOME/lib

% rm libobk.sl

HP Itanium Create link % cd $ORACLE_HOME/lib

Linux s390x % ln -s /usr/lib/libnsrora.so libobk.so
Linux x64
Remove link % cd $ORACLE_HOME/lib
Linux x86
% rm libobk.so
Sun SPARC
Sun x64

36 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 UNIX and Linux Installation

Unlinking NMDA from the Oracle server environment

Before you uninstall NMDA, unlink NMDA from the Oracle server environment.
1. Log in as the $ORACLE_HOME owner.
2. Type the appropriate commands listed in Table 8 on page 36 to remove the link.
3. If you copied the libnsrora.xx library file from the installation location to the default
directory /usr/lib, remove the library from the default directory.

Linking and unlinking NMDA in a Sybase environment

Perform the required link or unlink procedure in a Sybase ASE Backup Server environment:
◆ After you install NMDA, perform the procedure to link NMDA.
◆ Before you uninstall NMDA, perform the procedure to unlink NMDA.

Linking NMDA to the Sybase server environment

After you install NMDA on a Sybase server, link NMDA to the server environment.

Note: To link Sybase on HP Itanium, follow the instructions in “Linking NMDA to Sybase on
HP Itanium” on page 38.

1. Log in as the Sybase user.

2. Create the symbolic link by using one of the following options:
• If you installed NMDA in the default directory, type the appropriate commands
listed in Table 9 on page 37.
• If you installed NMDA in a non-default directory, perform one of the following
actions:
– Copy the libnsrsyb.xx library file to the default directory, and type the
appropriate linking commands listed in Table 9 on page 37.
– Type the linking commands listed in Table 9 on page 37 except replace the
default installation pathname with the non-default installation pathname
/relocation_path.

Table 9 Linking and unlinking commands for Sybase library file on UNIX or Linux

Operating Createor Install: create the symbolic link

system remove link Uninstall: remove the symbolic link

AIX Create link % cd $SYBASE/$SYBASE_ASE/lib

Linux x64 % ln -s /usr/lib/libnsrsyb.so libnsrsyb.so
Linux x86
Remove link % cd $SYBASE/$SYBASE_ASE/lib
Sun SPARC
% rm libnsrsyb.so
Sun x64

HP PA-RISC Create link % cd $SYBASE/$SYBASE_ASE/lib

% ln -s /opt/networker/lib/pa11_32/libnsrsyb.sl libnsrsyb.sl

Remove link % cd $SYBASE/$SYBASE_ASE/lib

% rm libnsrsyb.sl

Linking and unlinking NMDA in the environment on UNIX or Linux 37

UNIX and Linux Installation

Linking NMDA to Sybase on HP Itanium

Sybase changed the bitness of the ASE Backup Server for HP Itanium processors between
ASE releases 15.0.x and 15.5:
◆ ASE 15.0.x has a 32-bit server and requires the NMDA 32-bit libnsrsyb.so library.
◆ ASE 15.5 or later has a 64-bit server and requires the NMDA 64-bit libnsrsyb.so library.

Note: Regardless of the Sybase ASE version, the NMDA installation on HP Itanium places
only the libnsrsyb.so (64-bit) library file in the NMDA installation directory. To ensure that
you link the correct library, perform the appropriate procedure for the ASE version.

Linking NMDA to ASE 15.0.x on HP Itanium

The NMDA installation does not place the required 32-bit libnsrsyb32.so library file in the
installation directory.
Copy the libnsrsyb32.so library file to the installation directory and link the library file to
the Sybase server.
1. As the root user, go to the directory that contains the NMDA installation files as
described in “Accessing the NMDA software” on page 16.
2. Copy the 32-bit NMDA Sybase library file to the installation directory:
cp 32-bit/sybase/libnsrsyb32.so /usr/lib/libnsrsyb32.so

Note: When you uninstall NMDA, you must first remove this library manually.

3. As the Sybase user, type these commands to link the library file to the Sybase server:
cd $SYBASE/$SYBASE_ASE/lib
ln -s /usr/lib/libnsrsyb32.so libnsrsyb.so

Linking NMDA to ASE 15.5 or later on HP Itanium

The NMDA installation places the required 64-bit libnsrysb.so file in the installation
directory.
As the Sybase user, type these commands to link the library to the Sybase server:
cd $SYBASE/$SYBASE_ASE/lib
ln -s /usr/lib/libnsrsyb.so libnsrsyb.so

Unlinking NMDA from the Sybase server environment

Before you uninstall NMDA, unlink NMDA from the Sybase server environment.
1. Log in as the Sybase user.
2. For Sybase ASE 15.0.x on HP Itanium, remove the libnsrsyb32.so file from the
installation directory.
3. Type the appropriate commands from Table 9 on page 37 to remove the link.

38 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 UNIX and Linux Installation

Uninstalling NMDA on UNIX or Linux systems

Note: If you installed NMDA to support the coexistence of 32-bit and 64-bit databases and
applications on the same host, perform the procedure for “Uninstalling 32-bit NMDA on a
32-bit/64-bit system” on page 55.

Follow these instructions to uninstall NMDA in any of the following configurations:

◆ Single host
◆ Active-passive cluster
◆ Active-active application cluster, such as DB2 DPF, Informix MACH, Oracle RAC, or
Sybase ASE Cluster Edition
When you uninstall NMDA in a cluster, perform the uninstall procedure on each node of
the cluster that contains the NMDA software.
1. Ensure that no database or application backups are running.
2. Unlink NMDA from the database environment according to the instructions in “Linking
and unlinking NMDA in the environment on UNIX or Linux” on page 34.
3. As the root user, uninstall NMDA by using the instructions for the operating system:

Note: You do not need to shut down a database to uninstall NMDA.

• “Uninstalling NMDA on AIX systems” on page 39

• “Uninstalling NMDA on HP-UX systems” on page 40
• “Uninstalling NMDA on Linux systems” on page 40
• “Uninstalling NMDA on Solaris systems” on page 40

Uninstalling NMDA on AIX systems

You can uninstall NMDA on an AIX system by running the installp command or the SMIT
GUI program.
1. Ensure that you have completed the steps in “Uninstalling NMDA on UNIX or Linux
systems” on page 39 for the initial part of the uninstall procedure.
2. Use one of the following methods to uninstall NMDA.
• Use the command-line interface by typing the following command:
installp -u LGTOnmda.rte

• Use the SMIT GUI program:

a. Type the following smitty command:
smitty remove

b. Select F4=List to display a list of the installed software packages.

c. Select the package to uninstall:
LGTOnmda.rte

Uninstalling NMDA on UNIX or Linux systems 39

UNIX and Linux Installation

d. Set the PREVIEW Only option to No.

e. Press Enter to uninstall NMDA.
f. Exit the SMIT GUI program.

Uninstalling NMDA on HP-UX systems

You can uninstall NMDA on an HP-UX system by running the swremove command or GUI
program.
1. Ensure that you have completed the steps in “Uninstalling NMDA on UNIX or Linux
systems” on page 39 for the initial part of the uninstall procedure.
2. Use one of the following methods to uninstall NMDA.
• Use the command-line interface by typing the following command:
swremove NMDA

• Use the swremove GUI program:

a. Type the following swremove command:
swremove -i NMDA

b. Select Actions > Remove (analysis).

c. When the system analysis is complete, click OK to complete the uninstall.
d. To confirm the uninstall, click Yes.

Uninstalling NMDA on Linux systems

You can install NMDA on a Linux system by running the rpm command.
1. Ensure that you have completed the steps in “Uninstalling NMDA on UNIX or Linux
systems” on page 39 for the initial part of the uninstall procedure.
2. Type the following command:
rpm -e lgtonmda-1.5.0.0-1

Note: On Linux, you must uninstall NMDA before you uninstall the NetWorker client
software.

Uninstalling NMDA on Solaris systems

You can install NMDA on a Solaris system by running the pkgrm command.
1. Ensure that you have completed the steps in “Uninstalling NMDA on UNIX or Linux
systems” on page 39 for the initial part of the uninstall procedure.

Note: To uninstall NMDA on Solaris zones, first uninstall NMDA on the global zone and
then uninstall NMDA on each required sparse root zone.

40 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 UNIX and Linux Installation

2. Type the following command:

pkgrm LGTOnmda

3. Perform the appropriate action according to the basedir variable setting in the
/var/sadm/install/admin/default file:
• If basedir=default in the file, type y when prompted.
The software is uninstalled from the directory that contains the NetWorker client
software.
• If basedir=ask in the file, type the result of the pkgparam LGTOnmda BASEDIR
command when prompted for the pathname of the base directory.
The software is uninstalled from the specified base directory.
• If basedir=/dirpath in the file, type y when prompted.
The software is uninstalled from the specified /dirpath directory.

Uninstalling NMDA on UNIX or Linux systems 41

UNIX and Linux Installation

42 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
CHAPTER 3
Microsoft Windows Installation

This chapter includes the following topics:

◆ Installing NMDA on Microsoft Windows ................................................................... 44
◆ Linking and unlinking NMDA in the environment on Windows.................................. 45
◆ Maintaining the installation on Microsoft Windows ................................................. 49
◆ Uninstalling NMDA on Microsoft Windows ............................................................... 50

Microsoft Windows Installation 43

Microsoft Windows Installation

Installing NMDA on Microsoft Windows

You can install NMDA on a Windows system by running the NMDA Setup program,
networkr\setup.exe.
1. Complete the initial steps in “Installation road maps” on page 18. Ensure that you log
in as an administrator, no database or application backups are running, and you are in
the correct directory, which contains the NMDA installation files.
2. Run the NMDA Setup program, networkr\setup.exe, and follow the instructions
provided by the installation wizard.
When the NMDA package has the same bitness as the NetWorker client package
installed on the system, the NMDA program files are installed in the same directory as
the NetWorker client program files, NetWorker_install_path\bin.
When you install a 32-bit NMDA package on 64-bit Windows with a 64-bit NetWorker
client package, the NMDA program files are installed in
%SystemDrive%\Program Files (x86)\Legato\nsr\bin, regardless of where the
NetWorker client program files are installed.

Note: If the Setup program detects no NetWorker client program files, the program
displays an error message and exits without installing NMDA.

When the installation completes, a message appears about how to start the NMDA
scheduled backup configuration wizard. The EMC NetWorker Module for Databases
and Applications Release 1.5 Administration Guide describes the wizard.
3. Click Finish to exit the Setup program.
4. Verify that the system %PATH% environment variable includes the required
directories, including the NetWorker client installation directory and NMDA
installation directory. For example:
a. Right-click My Computer and select Manage.
b. Click Properties.
c. On the Advanced tab under Environment Variables, click Settings.
d. In System Variables, verify the Path variable. The Path variable must include the
following directories:
– NetWorker client installation directory, for example, NetWorker_install_dir\bin.
– NMDA installation directory, as described in step 2.

Note: The directory pathname can include spaces, but there cannot be spaces
before or after the pathname.

e. If you modified the %PATH% variable, restart the NetWorker Remote Exec Service
(the program nsrexecd.exe).

44 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Microsoft Windows Installation

5. Restart the database server, if required:

• If you installed the NetWorker client software for the first time in a particular
directory on a DB2, Oracle, or a Sybase server before you installed NMDA, then
restart the DB2, Oracle, or Sybase server instance.
• If you installed 32-bit NMDA for the first time with a 64-bit NetWorker client on a
Sybase server and you will perform Client Direct backups to a Data Domain device,
restart the Sybase server.
6. Link NMDA to the database or the application server environment by completing the
steps in “Linking and unlinking NMDA in the environment on Windows.”
7. When the NMDA installation is complete, return to the installation road map to
perform any post-installation procedures. “Road map to post-installation procedures”
on page 21 provides details.

Linking and unlinking NMDA in the environment on Windows

After you install NMDA on Windows as described in the first part of this chapter, you must
perform an additional procedure to link NMDA to the database or application
environment. Before you uninstall NMDA, you must also remove the link.
Perform the appropriate procedures for the database or application:
◆ “Linking NMDA in a DB2 environment” on page 45
◆ “Linking and unlinking NMDA in an Informix environment” on page 46
◆ “Linking and unlinking NMDA in a Lotus Notes environment (optional)” on page 47
◆ “Linking and unlinking NMDA in a Sybase environment” on page 48

Note: In an Oracle environment, you do not require the linking or unlinking procedure to
install or uninstall NMDA.

Linking NMDA in a DB2 environment



You must not set the DB2_VENDOR_INI registry variable. Also, if the
%INSTHOME%\sqllib\cfg\vendor.cfg file exists, either remove the file or remove all the
NMDA parameter settings from the file.

After you install NMDA on a DB2 server, use the db2set command to check if the
DB2_VENDOR_INI registry variable is set. The db2set command displays all the variable
settings. For example:
C:\Program Files\IBM\SQLLIB\BIN>db2set
DB2ACCOUNTNAME=CORP\brownr1
DB2INSTOWNER=CA-RBROWN-4
DB2PORTRANGE=60000:60003
DB2INSTPROF=C:\PROGRAMDATA\IBM\DB2\DB2COPY1
DB2COMM=TCPIP

Linking and unlinking NMDA in the environment on Windows 45

Microsoft Windows Installation

Use the required steps to implement the changes on the DB2 server.
1. Log in as the DB2 DBA user.
2. Remove the %INSTHOME%\sqllib\cfg\vendor.cfg file, or edit the file and remove all
the NMDA parameter settings.
3. Stop the database engine with the db2stop command.
4. Unset the DB2_VENDOR_INI variable with the db2set command:
db2set DB2_VENDOR_INI=

5. If the stack size for the db2syscs.exe file is less than 1024, use the db2hdr.exe utility
to increase the stack size to a minimum of 1024. For example:
C:\Program Files\IBM\SQLLIB\BIN> ..\misc\db2hdr db2syscs.exe
/s 1024,32

Note: Insufficient stack size can cause backup failure with the error SQL2079N return
code 30.

6. Restart the database engine with the db2start command.

Note: You do not require unlinking steps to uninstall NMDA in a DB2 environment.

Linking and unlinking NMDA in an Informix environment

Perform the required link procedure or unlink procedure in an Informix environment:
◆ After you install NMDA, perform the procedure to link NMDA.
◆ Before you uninstall NMDA, perform the procedure to unlink NMDA.

Linking NMDA to the Informix server environment

After you install NMDA, link NMDA to the Informix server environment.
1. Log in as the Informix user.
2. Edit the Informix %ONCONFIG% file and set the BAR_BSALIB_PATH variable to the full
pathname of the NMDA libxbsa.dll (XBSA) library.
The default library pathname is NetWorker_install_path\bin\libxbsa.dll.
3. Use the type command to ensure that the sm_versions file in the %INFORMIXDIR%\etc
directory includes the following line, and if it does not, change it:
type sm_versions
1|1.0.1|nwbsa|1

This action updates the NMDA Informix library links. Without the required values,
ON-Bar commands fail and the following message appears:
ERROR: Version 1.0.1 of the XBSA shared library is not compatible
with version 1 of ON-Bar.

4. Restart the IDS server to apply the %ONCONFIG% file changes.

46 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Microsoft Windows Installation

Unlinking NMDA from the Informix server environment

Before you uninstall NMDA, unlink NMDA from the Informix server environment.
1. Log in as the Informix user.
2. Edit the Informix %ONCONFIG% file and unset the BAR_BSALIB_PATH variable.
3. Restore the copy of the sm_versions file, stored by Informix in
%INFORMXIDIR%\etc\sm_versions.std.
4. Restart the IDS server to apply the %ONCONFIG% file changes.

Linking and unlinking NMDA in a Lotus Notes environment (optional)

Perform the required link or unlink procedure in a Lotus Notes environment:
◆ After you install NMDA, perform the procedure to link NMDA.
◆ Before you uninstall NMDA, perform the procedure to unlink NMDA.
You require these procedures on Windows only when you want to use the NMDA Lotus
document-level restore through the Lotus Notes client GUI to restore deleted or modified
Notes documents.

Note: The 32-bit NMDA Windows package must be installed on the Notes client host.

Linking NMDA to Lotus Notes

After you install NMDA, you can add the document-level recovery feature to the Lotus
Notes client software. The EMC NetWorker Module for Databases and Applications Release
1.5 Administration Guide describes the feature.
Complete the following steps to add the document-level recovery feature.
1. Exit the Lotus Notes client or administrator GUI.
2. Copy the nsrdoclb.dll file from the NMDA software directory to the Notes directory that
contains the notes.ini file, which is typically %SystemDrive%\Lotus\Notes.
3. In the Notes directory, add the following line to the notes.ini file:
AddInMenus=nsrdoclb.dll

If an AddInMenus item already exists, you can place a comma after it and add your
item as follows:
AddInMenus=command.dll, nsrdoclb.dll

4. Start the Lotus Notes client software.

The Lotus Notes client Actions menu must display the following choices:
• NMDA Lotus - Restore Selected Documents
• NMDA Lotus - Restore Deleted Documents

Linking and unlinking NMDA in the environment on Windows 47

Microsoft Windows Installation

Unlinking NMDA from Lotus Notes

Before you uninstall NMDA, remove the NMDA document-level recovery feature from the
Notes Client software:
1. Exit the Lotus Notes client or administrator GUI.
2. In the Notes directory, remove the following line from the notes.ini file:
AddInMenus=nsrdoclb.dll

3. Delete the nsrdoclb.dll file from the Notes directory, which is typically
%SystemDrive%\Lotus\Notes.
4. Start the Lotus Notes client software.
The recovery items previously added to the Lotus Notes client Actions menu are removed.

Linking and unlinking NMDA in a Sybase environment

Perform the required link procedure or unlink procedure in a Sybase ASE Backup Server
environment:
◆ After you install NMDA, perform the procedure to link NMDA.
◆ Before you uninstall NMDA, perform the procedure to unlink NMDA.

Linking NMDA to a Windows x64 Sybase server environment

On a Windows x64 Sybase server host, the NMDA installation does not install the
libnsrsyb64.dll file.
Copy and rename the libnsrsyb64.dll file:
1. Go to the win_x86 directory that contains the NMDA installation files as described in
“Accessing the NMDA software” on page 16.
2. Copy and rename the libnsrsyb64.dll file from the win_x86 directory to
%SYBASE%\%SYBASE_ASE%\lib\libnsrsyb.dll.

Linking NMDA to a Windows x86 Sybase server environment

On a Windows x86 Sybase server host, the NMDA installation installs the libnsrsyb.dll file.
Copy the libnsrsyb.dll file from the NetWorker location to the Sybase location:
1. Go to the directory that contains the NMDA installed files,
NetWorker_install_path\bin.
2. Copy the libnsrsyb.dll file to the %SYBASE%\%SYBASE_ASE%\lib directory.

Unlinking NMDA from the Sybase server environment

Before you uninstall NMDA, remove the link to the Sybase server environment.
1. Open the %SYBASE%\%SYBASE_ASE%\lib directory.
2. Delete the libnsrsyb.dll entry.

48 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Microsoft Windows Installation

Maintaining the installation on Microsoft Windows

You can modify, repair, or remove an existing NMDA installation on a Microsoft Windows
system.

Running the Setup program in maintenance mode

1. Log in as the Windows system administrator.
2. Ensure that no database or application backups are running.
3. Go to the directory that contains the NMDA installation files as described in
“Accessing the NMDA software” on page 16.
4. Run the networkr\setup.exe program.
5. In the Welcome dialog box, click Next.
6. In the Program Maintenance dialog box, select the maintenance task to perform:
• Repair—Enables you to replace missing files or corrupted files in the NMDA
installation. “Repairing an NMDA installation” on page 49 provides details.
• Remove—Enables you to remove the NMDA software.
You can also use Add or Remove Programs in the Windows Control Panel to remove
the components. “Uninstalling NMDA on Microsoft Windows” on page 50 provides
details.
7. Click Next.

Repairing an NMDA installation

1. Log in as the Windows system administrator.
2. Ensure that no database or application backups are running.
3. Start the Setup program in maintenance mode. “Running the Setup program in
maintenance mode” on page 49 provides details.
4. In the Program Maintenance dialog box, select Repair and click Next.
5. In the Ready to Repair the Program dialog box, click Install to begin the installation.
The Setup program reinstalls the NMDA files as required.
At the end of the install, the InstallShield Wizard Completed dialog box displays a
message about how to start the NetWorker Client Backup Configuration wizard. The
EMC NetWorker Module for Databases and Applications Release 1.5 Administration
Guide describes the configuration wizard.
6. In the InstallShield Wizard Completed dialog box, click Finish to exit the wizard.
7. If you changed the system Path variable, restart the Windows system and verify that
any required database instances and services are restarted.

Maintaining the installation on Microsoft Windows 49

Microsoft Windows Installation

Uninstalling NMDA on Microsoft Windows

Note: If you installed NMDA to support the coexistence of 32-bit and 64-bit databases and
applications on the same host, perform the procedure for “Uninstalling 32-bit NMDA on a
32-bit/64-bit system” on page 55.

Follow these instructions to uninstall NMDA in any of the following configurations:

◆ Single host
◆ Active-passive cluster
◆ Active-active application cluster, such as DB2 DPF, Informix MACH, Oracle RAC, or
Sybase ASE Cluster Edition
When you uninstall NMDA in a cluster, perform the uninstall procedure on each node of
the cluster that contains the NMDA software.
1. Log in as the Windows system administrator on the NMDA host.
2. Ensure that no database or application backups are running.
3. Unlink NMDA from the database or application environment according to the
instructions in “Linking and unlinking NMDA in the environment on Windows” on
page 45.
4. Uninstall NMDA by using one of the following methods:

Note: You do not need to shut down a database to uninstall NMDA.

• Setup program method:

a. Run the networkr\setup.exe program as described in “Running the Setup
program in maintenance mode” on page 49.
b. In the Program Maintenance dialog box, select Remove and click Next.
c. In the Remove the Program dialog box, click Remove to uninstall NMDA.
• Windows Control Panel method:
a. In the Windows Control Panel window, select Add or Remove Programs or
Programs and Features, depending on the Microsoft Windows version.
b. In the Add or Remove Programs window, select NetWorker Module for
Databases and Applications and click Remove.

50 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
CHAPTER 4
NMDA with Mixed 32-bit and 64-bit Databases
and Applications

This chapter includes the following topics:

◆ Coexistence of 32-bit and 64-bit databases and applications .................................. 52
◆ Installing NMDA on a 32-bit/64-bit system .............................................................. 52
◆ Uninstalling 32-bit NMDA on a 32-bit/64-bit system................................................ 55

NMDA with Mixed 32-bit and 64-bit Databases and Applications 51

NMDA with Mixed 32-bit and 64-bit Databases and Applications

Coexistence of 32-bit and 64-bit databases and applications

NMDA supports combinations of 32-bit and 64-bit database and application software
installed on the same 64-bit system. For example:
◆ 32-bit Lotus Domino and 64-bit DB2 servers on a 64-bit Sun SPARC system
◆ 32-bit Informix IDS and 64-bit IDS servers on a 64-bit HP PA-RISC system
◆ 32-bit Informix and 64-bit Oracle servers on a 64-bit Windows system
Refer to the documentation for the database or application that you are using for details
about the versions of 32-bit and 64-bit application software that can coexist on the same
system.



NMDA does not support the coexistence of either 32-bit or 64-bit Sybase with 64-bit DB2,
Informix, Lotus, or Oracle on the same 64-bit Windows system.

The EMC NetWorker Module for Databases and Applications Release 1.5 Release Notes
describes additional support limitations.
The following topics describe how to install and uninstall NMDA on a system with both
32-bit and 64-bit databases or applications, which are supported by two separate NMDA
packages:
◆ “Installing NMDA on a 32-bit/64-bit system” on page 52
◆ “Uninstalling 32-bit NMDA on a 32-bit/64-bit system” on page 55
The EMC NetWorker Module for Databases and Applications Release 1.5 Administration
Guide provides configuration instructions and special considerations for NMDA in an
environment with both 32-bit and 64-bit databases and applications.

Installing NMDA on a 32-bit/64-bit system

To install NMDA on a 64-bit operating system where both 32-bit and 64-bit databases or
applications are running, you must install 64-bit NMDA and enable NMDA for 32-bit use.
1. If you install 32-bit NMDA on the system, uninstall NMDA with the appropriate
procedure:
• “Uninstalling NMDA on UNIX or Linux systems” on page 39
• “Uninstalling NMDA on Microsoft Windows” on page 50
2. Install 64-bit NMDA for the operating system. The following chapters provide details
for each operating system:
• Chapter 2, “UNIX and Linux Installation”
• Chapter 3, “Microsoft Windows Installation”
After the software installation completes, a message appears about how to start the
NMDA scheduled backup configuration wizard. The EMC NetWorker Module for
Databases and Applications Release 1.5 Administration Guide describes the wizard.
3. Go to the 32-bit directory under the directory that contains the NMDA installation
package for the operating system as described in “Accessing the NMDA software” on
page 16.

52 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 NMDA with Mixed 32-bit and 64-bit Databases and Applications

4. Manually copy the 32-bit files listed in Table 10 on page 53 to the specified location
for each 32-bit database or application on the system.
5. Complete the software linking and post-installation procedures for the 32-bit NMDA
software components if required:
• “Linking and unlinking NMDA in the environment on UNIX or Linux” on page 34
• “Linking and unlinking NMDA in the environment on Windows” on page 45
• “Road map to post-installation procedures” on page 21
Use the appropriate program file name as listed in Table 10 on page 53 when
performing these steps. For example, to link the 32-bit NMDA Sybase component to
the Sybase server on AIX:
cd $SYBASE/$SYBASE_ASE/lib
ln -s /usr/lib/libnsrsyb32.so libnsrsyb.so

Note:
- IBM does not support 32-bit DB2 software on 64-bit UNIX or Linux.
- Oracle does not support 32-bit Oracle software on 64-bit UNIX, Linux, or Windows.

Table 10 Additional steps to enable NMDA for a 32-bit application (page 1 of 3)

On this 64-bit operating Copy these 32-bit files from

system For this 32-bit application the 32-bit directory To this directory

AIX Informix informix/libnsrifmx32.so /usr/lib

nsrdasv32 /usr/bin
nsrdaprobe32

Lotus nsrdasv32 /usr/bin

nsrdaprobe32
lotus/nsrdocrc32
lotus/nsrnotesrc32

Sybase sybase/libnsrsyb32.so /usr/lib

nsrdasv32 /usr/bin
nsrdaprobe32
sybase/nsrsybcc32
sybase/nsrsybrc32
sybase/threshold.sql

HP Itanium Sybase sybase/libnsrsyb32.so /usr/lib

HP PA-RISC Informix informix/libnsrifmx32.sl /usr/lib

nsrdasv32 /opt/networker/bin
nsrdaprobe32

Sybase sybase/libnsrsyb32.sl /usr/lib

nsrdasv32 /opt/networker/bin
nsrdaprobe32
sybase/nsrsybcc32
sybase/nsrsybrc32
sybase/threshold.sql

Installing NMDA on a 32-bit/64-bit system 53

NMDA with Mixed 32-bit and 64-bit Databases and Applications

Table 10 Additional steps to enable NMDA for a 32-bit application (page 2 of 3)

On this 64-bit operating Copy these 32-bit files from

system For this 32-bit application the 32-bit directory To this directory

Linux x64 Informix informix/libnsrifmx32.so /usr/lib

nsrdasv32 /usr/sbin1
nsrdaprobe32

Lotus nsrdasv32 /usr/sbin1

nsrdaprobe32
lotus/nsrdocrc32
lotus/nsrnotesrc32
lotus/nsrlotusra
lotus/nmlra.jar
lotus/nmlra_res.jar

MySQL nsrdasv32 /usr/sbin1

nsrmysqlrc32

libnsrmysql32.so /usr/lib

libmysqlapi32.so /usr/lib

Note: Rename libmysqlapi32.so in

this directory to libmysqlapi.so.

libmysqlapiwrap32.so /usr/lib

Note: Rename
libmysqlapiwrap32.so in this
directory to libmysqlapiwrap.so.

Sybase sybase/libnsrsyb32.so /usr/lib

nsrdasv32 /usr/sbin1
nsrdaprobe32
sybase/nsrsybcc32
sybase/nsrsybrc32

Sun SPARC Informix informix/libnsrifmx32.so /usr/lib

nsrdasv32 /usr/sbin1
nsrdaprobe32

Lotus nsrdasv32 /usr/sbin1

nsrdaprobe32
lotus/nsrdocrc32
lotus/nsrnotesrc32
lotus/nsrlotusra
lotus/nmlra.jar
lotus/nmlra_res.jar

Sybase sybase/libnsrsyb32.so /usr/lib

nsrdasv32 /usr/sbin1
nsrdaprobe32
sybase/nsrsybcc32
sybase/nsrsybrc32

54 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 NMDA with Mixed 32-bit and 64-bit Databases and Applications

Table 10 Additional steps to enable NMDA for a 32-bit application (page 3 of 3)

On this 64-bit operating Copy these 32-bit files from

system For this 32-bit application the 32-bit directory To this directory

Windows x64 DB2 32-bit\nsrdasv32.exe NetWorker_install_path\bin

32-bit\nsrdaprobe32.exe
32-bit\db2\libnsrdb232.dll
32-bit\db2\nsrdb2rlog32.exe

Informix 32-bit\nsrdasv32.exe NetWorker_install_path\bin

32-bit\nsrdaprobe32.exe
32-bit\informix\libxbsa32.dll

Lotus 32-bit\nsrdasv32.exe NetWorker_install_path\bin

32-bit\nsrdaprobe32.exe
32-bit\lotus\nsrdocrc32.exe
32-bit\lotus\nsrnotesrc32.exe

Sybase Not applicable. 32-bit or 64-bit Sybase cannot coexist with another
application on 64-bit Windows.
1 Copy the 32-bit file to /usr/sbin or to the same location where 64-bit NMDA was relocated.

Uninstalling 32-bit NMDA on a 32-bit/64-bit system

On a system where both 32-bit and 64-bit databases or applications coexist, uninstall
NMDA as follows.
1. Ensure that no database or application backups are running on the NMDA host.
2. Unlink the NMDA 32-bit components that you manually installed according to the
following instructions:
• “Linking and unlinking NMDA in the environment on UNIX or Linux” on page 34
• “Linking and unlinking NMDA in the environment on Windows” on page 45
3. Log in as the root user (UNIX or Linux) or system administrator (Microsoft Windows).
4. Manually delete the appropriate files for the 32-bit database or applications that you
manually copied during installation as shown in Table 10 on page 53
5. Uninstall 64-bit NMDA according to the appropriate instructions:
• “Uninstalling NMDA on UNIX or Linux systems” on page 39
• “Uninstalling NMDA on Microsoft Windows” on page 50

Uninstalling 32-bit NMDA on a 32-bit/64-bit system 55

NMDA with Mixed 32-bit and 64-bit Databases and Applications

56 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
APPENDIX A
Uninstalling ISM on an Informix Server

This appendix contains the following topics:

◆ ISM software on an Informix server.......................................................................... 58
◆ Uninstalling ISM on UNIX or Linux ........................................................................... 58
◆ Uninstalling ISM on Microsoft Windows................................................................... 59

Uninstalling ISM on an Informix Server 57

Uninstalling ISM on an Informix Server

ISM software on an Informix server

Informix Storage Manager (ISM) is a storage management software, packaged and
installed with Informix Dynamic Server (IDS).
For Informix servers only, if you installed ISM software, you must uninstall the software
before you install NMDA by following the instructions for the operating system:
◆ “Uninstalling ISM on UNIX or Linux” on page 58
◆ “Uninstalling ISM on Microsoft Windows” on page 59

Note: Starting with Informix 12.10, Informix Primary Storage Manager (PSM) replaces ISM.
When you install NMDA with IDS 12.10, you do not need to uninstall PSM. Just follow the
linking instructions in the appropriate linking section of this guide.

Uninstalling ISM on UNIX or Linux

Completed the required steps to uninstall ISM on an Informix server on a UNIX or Linux
host.
1. Log in as the root user on the NMDA host.
2. Change to the Informix directory:
# cd $INFORMIXDIR/bin

3. Shut down the ISM daemons:

# ./ism_shutdown

Note: The ism_shutdown command does not uninstall ISM. You must complete the
following steps.

4. Verify that the daemons are shut down:

# ps -ef | grep nsr

5. Move the ISM executables to a temporary directory. For example:

# mkdir ISM.TMP
# mv ism* ISM.TMP
# mv nsr* ISM.TMP
# mv mm* ISM.TMP
# mv save* ISM.TMP
# mv scanner ISM.TMP
# mv uasm ISM.TMP
# mv recover ISM.TMP
# mv ansrd ISM.TMP

6. Move the ISM catalogs to a temporary directory:

# cd $INFORMIXDIR
# mv ism ism.bak

7. Remove the symbolic link to the ISM catalogs:

# rm /nsr

58 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide
 Uninstalling ISM on an Informix Server

8. Remove the call to ism_catalog from the $INFORMIXDIR/bin/onbar script.

9. Remove any references to ISM in the environment variable PATH.
10. Edit the $INFORMIXDIR/etc/$ONCONFIG file, and comment out the following line if it
exists:
#BAR_BSALIB_PATH ISM_library

Also, comment out any references to the following parameters:

ISM_DATA_POOL
ISM_LOG_POOL

Uninstalling ISM on Microsoft Windows

There are two methods to uninstall the ISM software on an Informix server installed on a
Windows host. You can use the IDS Server Setup program or the manual method.

Uninstalling ISM on Windows with the Setup program

The recommended method to uninstall ISM on an Informix server on Windows is to use the
IDS Server Setup program, if available.
1. Launch the IDS Server Setup program.
2. Select Modify the Installation.
3. Clear the selection Informix Storage Manager.
4. Complete the Setup program to uninstall ISM.

Unstalling ISM on Windows manually

If the IDS Server Setup program is not available, manually uninstall ISM on an Informix
server on Windows.
1. Log in as user informix.
2. Type the following command to set the Informix Database server environment
variables:
database-servername.cmd

3. Change to the ISM directory. For example:

cd C:\ism\2.2\bin

4. Set the ISM path variable. For example:

set ISMDIR=C:\ism\2.2

5. Shut down the ISM services:

ism_shutdown -deinstall

6. Shut down ISM and verify that there are no services listed for ISM in Control Panel >
Administrative Tools > Services.

Uninstalling ISM on Microsoft Windows 59

Uninstalling ISM on an Informix Server

7. Rename the directory that contains ISM:

rename ism ism.bak

8. Remove the call to ism_catalog from the %INFORMIXDIR%\bin\onbar.bat file.

9. Remove any references to ISM in the environment variable PATH.
Delete the %ISMDIR%\bin directory entry from the user environment variable PATH.
For example, change the following PATH setting:
PATH=C:\installdir;D:\ISM\2.20\bin;C:\msdev

The changed PATH setting will be as follows:

PATH=C:\installdir;C:\msdev

10. Edit the %INFORMIXDIR%\%ONCONFIG% file, and comment out the following line, if it
exists:
#BAR_BSALIB_PATH ISM_library

Also comment out any references to the following parameters:

ISM_DATA_POOL
ISM_LOG_POOL

11. Remove the ISM portmapper:

a. Stop the ISM portmapper service.
b. Type Regedit, and delete the following entry:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\PORTMAP

Confirm that the Displayname is ISM Portmapper before deleting the entry.
12. Edit the registry to delete any of the following keys, if present:



Edit the registry with caution. Errors can corrupt the Windows system.

• Hkey_Local_Machine\Software\XBSA
• Hkey_Local_Machine\Software\Informix\ISM
• Hkey_Local_Machine\Software\Informix\Informix Storage Manager
13. Restart the computer.

60 EMC NetWorker Module for Databases and Applications Release 1.5 Installation Guide