Dell EMC NetWorker Module for Databases

and Applications
Installation Guide
Version 19.3

Dell Inc.

June 2020
Rev. 01
Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2009 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.
 Contents

List of Tables........................................................................................................................................................... 5

Preface..........................................................................................................................................6

1 Getting Started............................................................................................................................ 9
NMDA software requirements.............................................................................................................................................9
Database or application server software.....................................................................................................................10
NetWorker server software.......................................................................................................................................... 10
NMC server software.................................................................................................................................................... 10
NetWorker Authentication Service.............................................................................................................................. 10
NetWorker storage node software.............................................................................................................................. 10
NetWorker client software............................................................................................................................................ 11
NMDA software.............................................................................................................................................................. 11
Data Domain BoostFS software....................................................................................................................................11
Installation checklists............................................................................................................................................................ 11
Documents....................................................................................................................................................................... 11
Installation media............................................................................................................................................................ 12
License enablers............................................................................................................................................................. 12
Accessing the NMDA software.......................................................................................................................................... 12
Accessing NMDA from the DVD media.......................................................................................................................12
Accessing NMDA from the website.............................................................................................................................13
Accessing the Data Domain BoostFS software............................................................................................................... 13
Installation road maps.......................................................................................................................................................... 14
Road map to install or update NMDA on a database or application host................................................................14
Road map to update NMDA with the Package Manager......................................................................................... 16
Road map to post-installation procedures.................................................................................................................. 16

2 UNIX and Linux Installation.......................................................................................................... 18

Installing NMDA on AIX systems........................................................................................................................................ 18
Installing NMDA on HP-UX systems................................................................................................................................. 19
Installing NMDA on Linux systems.................................................................................................................................... 20
Enabling Data Domain BoostFS for Orchestrated Application Protection.............................................................20
Installing NMDA on Solaris systems...................................................................................................................................21
Linking and unlinking NMDA in the environment on UNIX or Linux.............................................................................. 22
Linking NMDA in a DB2 environment..........................................................................................................................22
Linking and unlinking NMDA in an Informix environment......................................................................................... 23
Linking and unlinking NMDA in a MySQL environment............................................................................................ 23
Linking and unlinking NMDA in an Oracle environment............................................................................................ 26
Linking and unlinking NMDA in an SAP IQ environment........................................................................................... 27
Linking and unlinking NMDA in a Sybase ASE environment.................................................................................... 28
Uninstalling NMDA on UNIX or Linux systems................................................................................................................ 30
Uninstalling NMDA on AIX systems............................................................................................................................ 30
Uninstalling NMDA on HP-UX systems.......................................................................................................................31
Uninstalling NMDA on Linux systems.......................................................................................................................... 31

Contents 3
 Uninstalling NMDA on Solaris systems........................................................................................................................ 31

3 Microsoft Windows Installation....................................................................................................32

Installing NMDA on Microsoft Windows...........................................................................................................................32
Linking and unlinking NMDA in the environment on Windows...................................................................................... 33
Linking NMDA in a DB2 environment..........................................................................................................................33
Linking and unlinking NMDA in an Informix environment......................................................................................... 34
Linking and unlinking NMDA in a Lotus Notes environment.................................................................................... 35
Linking and unlinking NMDA in a Sybase ASE environment.................................................................................... 36
Repairing the installation on Microsoft Windows............................................................................................................ 36
Uninstalling NMDA on Microsoft Windows......................................................................................................................36

4 NMDA with Mixed 32-bit and 64-bit Databases and Applications.................................................... 38

Coexistence of 32-bit and 64-bit databases and applications.......................................................................................38
Installing NMDA to enable 32-bit and 64-bit coexistence..............................................................................................38
Uninstalling 32-bit NMDA on a 32-bit/64-bit system.................................................................................................... 40

A Uninstalling ISM on an Informix Server.........................................................................................42

ISM software on an Informix server..................................................................................................................................42
Uninstalling ISM on UNIX or Linux.....................................................................................................................................42
Uninstalling ISM on Microsoft Windows...........................................................................................................................43
Uninstalling ISM on Windows with the Setup program............................................................................................ 43
Uninstalling ISM on Windows manually.......................................................................................................................43

4 Contents
List of Tables
Table 1. Revision history.........................................................................................................................................6

Table 2. Style conventions.....................................................................................................................................7

Table 3. Typical hosts and software in the NMDA environment......................................................................9

Table 4. Software directory on the DVD............................................................................................................12

Table 5. Zipped download file and software directory for install.................................................................... 13

Table 6. NetWorker startup commands on UNIX and Linux........................................................................... 15

Table 7. Command to register the wizard..........................................................................................................17

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

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

Table 10. Additional steps to enable NMDA for a 32-bit application..............................................................39

List of Tables 5
 Preface
Preface
As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the
software or hardware currently in use might not support some functions that are described in this document. The product release notes
provide the most up-to-date information on product features.
If a product does not function correctly or does not function as described in this document, contact a technical support professional.
NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this
document, go to the Support website https://www.dell.com/support.

Purpose
This document describes how to install, update, and uninstall the NetWorker Module for Databases and Applications (NMDA) version 19.3.
NOTE: Any references to Data Domain systems or Data Domain devices in the product also apply to the PowerProtect
DD systems.

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 the following topics:
• Backup, recovery, databases, applications, and network terminology
• Backup and recovery procedures
• Disaster recovery procedures

Revision history
The following table presents the revision history of this document.

Table 1. Revision history

Revision Date Description
01 June 15, 2020 Initial release of this document for NMDA version 19.3.

Related documentation
You can find additional publications for this product release and related NetWorker products at the Support website.
The NetWorker E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome provides details about supported environments and
platforms.
The following additional documentation might be useful:
• Database or application server documentation
• Database or application backup and recovery documentation

Special notice conventions that are used in this

document
The following conventions are used for special notices:

6 Preface
 CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.

NOTE: A Note indicates important information that helps you make better use of your product.

Typographical conventions
The following type style conventions are used in this document:

Table 2. Style conventions

Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons,
fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area
with title, table label, and window.
Italic Used for full titles of publications that are referenced in text.
Monospace Used for:
• System code
• System output, such as an error message or script
• Pathnames, file names, file name extensions, prompts, and syntax
• Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.
[] Square brackets enclose optional values.
| Vertical line indicates alternate selections. The vertical line means or for the alternate selections.
{} Braces enclose content that the user must specify, such as x, y, or z.
... Ellipses indicate non-essential information that is omitted from the example.

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation

• https://www.dell.com/support
• https://www.dell.com/community

Where to get support

The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories, downloads, and
how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Support.
To access a product-specific page:
1. Go to https://www.dell.com/support.
2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by
keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Knowledge Base.
3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by typing a
product name in the search box, and then selecting the product from the list that appears.

Preface 7
Live chat
To participate in a live interactive chat with a support agent:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Contact Support.
3. On the Contact Information page, click the relevant support, and then proceed.

Service requests
To obtain in-depth help from Licensing, submit a service request. To submit a service request:
1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests.
NOTE: To create a service request, you must have a valid support agreement. For details about either an account or
obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the
Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests.
3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities
For peer contacts, conversations, and content on product support and solutions, go to the Community Network https://www.dell.com/
community. Interactively engage with customers, partners, and certified professionals online.

How to provide feedback

Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to
DPAD.Doc.Feedback@emc.com.

8 Preface
 1
Getting Started
Topics:
• NMDA software requirements
• Installation checklists
• Accessing the NMDA software
• Accessing the Data Domain BoostFS software
• Installation road maps

NMDA software requirements

NetWorker Module for Databases and Applications (NMDA) is a NetWorker add-on module that provides data protection services for the
supported DB2, Informix, Lotus Domino/Notes, MySQL, Oracle, SAP IQ, and Sybase ASE databases.
The following table lists the hosts and software that you might require for NMDA services.
NOTE:

Before you install NMDA, install both the NetWorker base client and extended client software packages on the database
server host.

The product name Sybase ASE is synonymous with the name SAP ASE.

Table 3. Typical hosts and software in the NMDA environment

Host Required software
NetWorker server • NetWorker base client
• NetWorker extended client
• NetWorker storage node
• NetWorker server
• NetWorker Authentication Service

NetWorker storage node • NetWorker base client

• NetWorker extended client
• NetWorker storage node

NetWorker Management Console (NMC) server • NetWorker base client

• NetWorker extended client
• NMC server

Each supported database server (NMDA host) • Supported database or application server
• NetWorker base client
• NetWorker extended client
• NMDA
• For snapshot operations with Oracle ASM: Replication
management software
• For Orchestrated Application Protection: Data Domain Boost -
File System software

Review the following software descriptions to plan the installation requirements.

The bitness (32-bit or 64-bit) of NMDA software that is required depends on the bitness of the database or application server being
protected:

Getting Started 9
• With one exception, you require 32-bit NMDA to support a 32-bit database or application server and 64-bit NMDA to support a 64-bit
database or application server, regardless of the operating system bitness. The exception applies to Sybase ASE releases earlier than
16.0 SP02. For those Sybase ASE releases, 32-bit NMDA supports both 32-bit and 64-bit Sybase ASE on AIX and Solaris SPARC.
• If only 32-bit database or application servers are installed on a 64-bit system, then you only need to install 32-bit NMDA on the system.
• With 32-bit NMDA on Linux, ensure that the 32-bit NetWorker client is installed. With 64-bit NMDA on Linux, ensure that the 64-bit
NetWorker client is installed. NMDA does not support 32-bit and 64-bit coexistence on Linux.
• If both 32-bit and 64-bit database or application servers are installed on the same system, refer to the sections in this guide about
NMDA with mixed 32-bit and 64-bit databases and applications.
The NetWorker E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome provides details about the operating systems and
software versions that are required for NMDA services.
The 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, SAP IQ, or Sybase ASE database or application server is
installed on an operating system that supports the NetWorker client and NMDA version to be installed on that host.
If you install NMDA in a non-English environment, ensure that you meet the following requirements:
• The host operating system supports internationalization (I18N).
• The database or application software provides the required National Language Support (NLS) or globalization support.
• The database or application software is configured with the required non-ASCII character set.

NetWorker server software

Install a supported version of the NetWorker server software 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 NetWorker Module for
Databases and Applications Release Notes.
Use a supported version of the NetWorker server that works with the NetWorker client version installed on the NMDA host. The
operating systems that are used must support the NetWorker server version that is used.

NMC server software

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

NetWorker Authentication Service

The NetWorker Authentication Service provides centralized token-based authentication to components in the NetWorker environment.
NetWorker uses the NetWorker Authentication Service to authenticate NMC and CLI users. You can configure the NetWorker
Authentication Service to use a local user database or external identity providers (LDAP and AD) for authentication.
The NetWorker Installation Guide provides details on the installation and configuration requirements for the NetWorker Authentication
Service software.

NetWorker storage node software

Install a supported version of the NetWorker storage node software on the host that manages the backup storage devices. You can
configure a 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.
Use a supported version of the NetWorker storage node that works with the NetWorker client version that is installed on the NMDA host
and the NetWorker server. The operating systems that are used must support the NetWorker storage node version.

10 Getting Started
NetWorker client software
Install a supported version of the NetWorker client software on the supported database or application server host before you install NMDA
on that host. Install both the NetWorker base client and extended client software packages.
With 32-bit NMDA on Linux, ensure that the 32-bit NetWorker client is installed. With 64-bit NMDA on Linux, ensure that the 64-bit
NetWorker client is installed. NMDA does not support 32-bit and 64-bit coexistence on Linux.
NMDA can use the NetWorker Snapshot Management (NSM) feature to provide a high-availability storage environment for snapshot
backups and restores of DB2 and Oracle data. To enable the snapshot-based operations, install the NetWorker base client and extended
client software packages on both of the following hosts:
• NMDA host
• A mount host
The mount 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 or application host
NOTE: Some operating systems and volume managers require that you configure a mount host on a separate host
from the database or application host. For example, Veritas Volume Manager (VxVM) and Linux Logical Volume
Manager (LVM) do not support the use of the database or application host as the mount host. The NetWorker
Snapshot Management Integration Guide provides a full list of restrictions and details.
The NetWorker extended client package must be installed to enable the following functionality on the host:
• NSM
• CLI utilities for server reporting and administration, such as mminfo, nsradmin, and nsrinfo
• Cluster integration scripts
• Custom script integration tools (pre/post save)
• Audit log
• Cloning and staging
• ProtectPoint for VMAX
• ProtectPoint for RecoverPoint
The NetWorker Installation Guide provides details about the NetWorker base and extended client packages.

NMDA software
Install NMDA on a supported database server or application server.
For Oracle ASM snapshot backups and restores with replication management software, also install NMDA on the mount host.

Data Domain BoostFS software

For Orchestrated Application Protection, install the Data Domain BoostFS on the supported database server or application server.

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

Documents
You can find the required information in the following documents:
• NetWorker Module for Databases and Applications Installation Guide for the existing version, if you are updating from a previous
NMDA version to NMDA 19.3
• NetWorker Module for Databases and Applications Version 19.3 Release Notes
• NetWorker Module for Databases and Applications Version 19.3 Administration Guide
• NetWorker Administration Guide for the supported NetWorker release
• NetWorker E-LAB Navigator
• Data Domain BoostFS Configuration Guide

Getting Started 11
Installation media
Use one of the following installation media:
• The DVD from the Information Protection and Availability Product Families Media Kit
• If you download the software, use the Support website

License enablers
Enabler codes or licenses activate the functionality of the NMDA software and are sold separately.

NOTE: Without an enabler code, you can only evaluate the software that is obtained from the DVD or the website.

The NetWorker Licensing Guide describes licensing.

Accessing the NMDA software

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

Accessing NMDA from the DVD media

The DVD is in the Information Protection and Availability Product Families Media Kit. The kit contains the software and online
documentation for related products.

About this task

You can access the NMDA software files from the NetWorker Module DVD on a host with a local DVD drive.

Steps
1. Log in to the host as the root user on UNIX or Linux, or as the local administrator user on Windows.
2. Insert and then 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 the following table.
The NetWorker E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome provides details about the operating systems and
the database and application software that NMDA supports.

Table 4. Software directory on the DVD

Operating system (NMDA bitness) Software directory
AIX (32-bit) /mount_point/nmda/aixpower_32

AIX (64-bit) /mount_point/nmda/aixpower_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

Linux Power PC (64-bit little-endian) /mount_point/nmda/linuxppc64le_64

Solaris AMD (64-bit) /mount_point/volume_label/nmda/solaris_amd64

Solaris SPARC (32-bit) /mount_point/volume_label/nmda/solaris_32

12 Getting Started
 Table 4. Software directory on the DVD(continued)
Operating system (NMDA bitness) Software directory
Solaris 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 website

You can download the NMDA software files from the Support website.

Steps
1. Log in to the host as the root user on UNIX or Linux, or as the local administrator user on Windows.
2. Create a temporary installation download directory in a local file system with sufficient free disk space. The directory must contain
both the downloaded software package and the software installation files that are extracted from the package.
3. Review the details in the NetWorker E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome about the operating systems
and the database and application software that NMDA supports.
4. Complete the following steps on the Support website at https://www.dell.com/support:
a. Select Drivers & Downloads.
The Drivers & Downloads page appears.
b. In the search box, type NetWorker Module for Databases and Applications.
5. Download the NMDA release 19.3 software file to the temporary directory that you created.
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. Go to the directory that contains the NMDA installation files.
• On Windows:
a. Extract the downloaded software package as shown in the following table.
b. Go to the correct directory as shown in the following table.

Table 5. Zipped download file and software directory for install

Downloaded software file Directory for install
nmda193_win_x64.zip win_x64

nmda193_win_x86.zip win_x86

Accessing the Data Domain BoostFS software

If you want to enable and leverage the Orchestrated Application Protection feature, you can download the Data Domain BoostFS software
files from the Support website.

Steps
1. Log in to the host as the root user on UNIX or Linux, or as the local administrator user on Windows.

Getting Started 13
2. Create a temporary installation download directory in a local file system with sufficient free disk space. The file system must contain
both the downloaded software package and the software installation files that are extracted from the package.
3. Download the required Data Domain BoostFS software:
a. On the Support website at https://www.dell.com/support, select Drivers & Downloads.
The Drivers & Downloads page appears.
b. In the search box, type Data Domain Boost and then select Data Domain Boost – File System.
c. Select the Data Domain BoostFS 1.1.0.1 or later version, and download the Data Domain BoostFS software file to the temporary
directory that you created in step 2.
4. Review the required documentation:
a. Go to https://www.dell.com/support.
b. In the search box, type Data Domain Boost and then select Data Domain Boost – File System.
c. Click Documentation.
d. Download the Data Domain BoostFS Configuration Guide, and review the "Supported Environments" section about the operating
system and FUSE that Data Domain BoostFS supports.

Installation road maps

Follow the proper road map to install NMDA:
• Road map to install or update NMDA on a database or application host
• Road map to update NMDA remotely with the Package Manager
• Road map to perform the post-installation procedures

Road map to install or update NMDA on a database or

application host
To install or update NMDA on a database or application host in any of the supported configurations, complete the procedure as follows.

About this task

You can install or update NMDA in any of the following configurations:
• Single host
• Active-passive cluster
• Active-active application cluster, such as one of the following types of cluster:
○ DB2 Database Partitioning Feature (DPF)
○ DB2 pureScale
○ Informix Multi-node Active Clusters for High Availability or High Availability Clusters (MACH)
○ Oracle Real Application Clusters (RAC)
○ Sybase ASE Cluster Edition

NOTE: Install NMDA on each node host in a cluster that performs backup and recovery operations.

The NetWorker E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome provides details about the supported software
versions and cluster environments.

Steps
1. Review the Installation checklists on page 11 and verify that you have the required documentation, installation media, and license
information.
2. If you installed Informix Storage Manager (ISM) on the host, uninstall ISM according to the instructions in Uninstalling ISM on an
Informix Server on page 42.
3. Ensure that you have installed the NetWorker client software on the host. The client version must support the NMDA version that will
be installed.
4. Access the NMDA software as described in Accessing the NMDA software on page 12, and then ensure that you are in the correct
directory.

14 Getting Started
 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 the
database or application during the installation.
6. Uninstall any previous version of NMDA according to the instructions in the installation guide for the module version.
NOTE: Do not use an upgrade option on the platform, for example, the rpm -U command on Linux.

7. Before the NMDA installation, ensure that the NetWorker Remote Exec daemon, nsrexecd, is running on UNIX or Linux, or the
NetWorker Remote Exec service, nsrexecd.exe, is running on Windows.
To verify that the NetWorker Remote Exec daemon or service is running:
• On UNIX or Linux, type the following command:

ps -ef | grep nsrexecd

• On Windows, use either Component Services or Task Manager.

If the NetWorker Remote Exec daemon or service is not running:
• To start the NetWorker Remote Exec daemon on UNIX or Linux, log in as root, and type the appropriate startup command from
the following table.

Table 6. NetWorker startup commands on UNIX and Linux

Operating system Startup command
Linux service networker start

Solaris /etc/init.d/networker start

HP-UX /sbin/init.d/networker start

AIX /etc/rc.nsr
• To start the NetWorker Remote Exec service on Windows, perform the following steps:
a. Log in as a Windows Administrator.
b. Right-click My Computer, and select Manage.
c. Expand Configuration, and select Services.
d. Right-click the NetWorker Remote Exec Service, and select Start.
NOTE: If you do not start the NetWorker Remote Exec daemon or service before the NMDA installation, then the
automatic registration of the NMDA configuration wizard might not occur and the wizard might fail to detect if
NMDA is installed. Road map to post-installation procedures on page 16 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 that NMDA supports, follow the
instructions in NMDA with Mixed 32-bit and 64-bit Databases and Applications on page 38.
For example, follow the instructions for a mixed 32-bit/64-bit system if the same host runs both 32-bit and 64-bit Lotus Domino or
runs both 32-bit Sybase ASE and 64-bit DB2.
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
correct chapter:
• UNIX and Linux Installation on page 18
• Microsoft Windows Installation on page 32
NOTE: If only 32-bit database or application servers are installed on a 64-bit system, then you must only install 32-
bit NMDA on the system.
After the software installation completes, a message appears about how to start the NMDA scheduled backup configuration wizard.
The NetWorker Module for Databases and Applications Version 19.3 Administration Guide describes the wizard.

10. Perform all the required post-installation procedures. Road map to post-installation procedures on page 16 provides details.

Getting Started 15
Road map to update NMDA with the Package Manager
You can update NMDA on one or more NMDA hosts by using the Package Manager feature from a centralized NetWorker server. You can
perform the update with the Package Manager or the nsrpush command. When you use the Package Manager, NMDA must not be
installed on the NetWorker server.

About this task

NOTE: Cluster environments do not support updates with the Package Manager. You cannot use the Package Manager
to update 32-bit NMDA on a 64-bit operating system.
The NetWorker Updating from a Previous Release Guide describes the Package Manager, including the following procedures:
• Viewing software that is installed on NetWorker clients.
• Performing and monitoring the updates.
• Managing the repository of media kits that the Package Manager uses to install the software from the NetWorker server.
NOTE: To add an NMDA release to the Package Manager repository, follow the instructions in the NetWorker
Updating from a Previous Release Guide. If you use the nsrpush command, type the complete product name as
“NetWorker Module for Databases and Applications” with the quotation marks.
Complete the following steps to update NMDA with the Package Manager.

Steps
1. Review the Installation checklists on page 11.
2. Ensure that you meet the following requirements:
• NMDA 1.5 or later is installed on the NMDA host, and the operating systems support the Package Manager. You cannot perform
an update of earlier NMDA releases.
The NetWorker Updating from a Previous Release Guide at the Support website describes the operating systems that support the
Package Manager feature on the NMDA host.
• The NMDA client host contains a supported version of the NetWorker client software.
• The user that performs the update is both an NMC administrator and a member of the application administrator's user group on
the NetWorker server.
3. Before you start an update, ensure that all backups and restores are stopped on the client to be updated.
NOTE: The Package Manager might stop and restart the NetWorker client nsrexecd daemon or service during the
installation.

4. On the NetWorker server, perform the update of the NMDA client by using the Package Manager feature or the nsrpush command.
The NetWorker Updating from a Previous Release Guide provides more information.

5. Perform all the required post-installation procedures on the client host. Road map to post-installation procedures on page 16 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 with Package Manager, complete the
following post-installation procedures.

Steps
1. If you are installing NMDA for the first time on the host, register and enable NMDA to work with the NetWorker software.
The NetWorker Licensing Guide describes licensing and enabling of software.

2. If you perform snapshot backups for Oracle ASM on the host, install and enable the required replication management software on the
NMDA host and the mount host.
3. Review the following information about the wizard registration:
• If you installed the NMDA package when the NetWorker Remote Exec service (the nsrexecd or nsrexecd.exe program) was
running, the automatic wizard registration occurred during the installation.
• If you installed the NMDA package when the NetWorker Remote Exec service (the nsrexecd or nsrexecd.exe program) was
not running:

16 Getting Started
 ○ With NetWorker version 18.2 or later, the automatic wizard registration occurs after the NetWorker Remote Exec service (the
nsrexecd or nsrexecd.exe program) is started.
○ With NetWorker version pre-18.2, after the NetWorker Remote Exec service (the nsrexecd or nsrexecd.exe program) is
started, register the wizard manually by typing the appropriate command as described in the next step.

4. Ensure that the wizard registration succeeded:

a. Log in as the root user (UNIX or Linux) or system administrator (Windows).
b. Ensure that the NetWorker Remote Exec service (the nsrexecd or nsrexecd.exe program) is running.
c. At a new command prompt, type the appropriate command:
• On UNIX or Linux, type the following command:

nsradmin -p nsrexecd

• On Windows, type the following command:

nsradmin.exe -p nsrexecd

d. At the nsradmin> prompt, type the following command:

print type: NSR remote agent

Check that the command output includes the correct values for "backup type" (database or application type that you want to
protect) and "product version" (version of NMDA that you installed). You can run the exit command to return to the original
console.
If the command output is missing or does not contain the correct values, then the NetWorker Remote Exec service (the
nsrexecd or nsrexecd.exe program) was not running during the NMDA installation. Perform one of the following corrective
actions:
• Start the NetWorker Remote Exec service, and then reinstall NMDA.
• Register the wizard manually by typing the appropriate command from the following table.

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

Table 7. 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 ASE nsrsybra(.exe) -i

5. On UNIX or Linux, to ensure the success of backups and restores, check that the /nsr/apps directory and its subdirectories have
the 01777 permissions.
The NMDA installation sets the permissions to 01777 for /nsr/apps and its subdirectories. These permissions are required for non-
root database users to create temporary files and logs during backups and restores. The sticky bit is also set to ensure that the files
can be removed only by the file owners. For example, the permissions appear as follows:
drwxrwxrwt 6 root root 4096 Dec 22 12:17 /nsr/apps

6. On Windows, to ensure the success of backups and restores, completed the following tasks:
• Restart the database services.
• Close and reopen any command prompt window or console that will be used to run backups or restores.

7. Configure the NMDA software.

The NetWorker Module for Databases and Applications Version 19.3 Administration Guide provides details.

Getting Started 17
 2
UNIX and Linux Installation
Topics:
• Installing NMDA on AIX systems
• Installing NMDA on HP-UX systems
• Installing NMDA on Linux systems
• Installing NMDA on Solaris systems
• Linking and unlinking NMDA in the environment on UNIX or Linux
• Uninstalling NMDA on UNIX or Linux systems

Installing NMDA on AIX systems

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.

Steps
1. Complete the initial steps in Installation road maps on page 14. Ensure that you meet the following requirements:
• You are logged in as the root user.
• No backups or restores are running.
• The nsrexecd daemon is running. You can check the daemon status by running the ps -ef | grep nsrexecd command.
• You are in the correct directory that 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 12.
To verify that the installation succeeded, type the following command:

lslpp -L all | grep -i lgtonmda

If the lslpp command output includes LGTOnmda.rte, the installation was successful.
• 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 that is
described in Accessing the NMDA software on page 12.
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. To display the list of the NMDA software packages, select F4=List.
f. To install the NMDA software, select LGTOnmda.rte.
g. Set the Preview Only option to No.
h. Select Install and Update Software.
i. To begin the installation, press Enter.

18 UNIX and Linux 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 22.
4. Return to the installation road map to perform any post-installation procedures. As part of these procedures, ensure that the NMDA
automatic wizard registration succeeded by using the following commands:

nsradmin -p nsrexecd
nsradmin> print type: NSR remote agent

Road map to post-installation procedures on page 16 provides complete details.

Installing NMDA on HP-UX systems

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.

Steps
1. Complete the initial steps in Installation road maps on page 14. Ensure that you meet the following requirements:
• You are logged in as the root user.
• No backups or restores are running.
• The nsrexecd daemon is running. You can check the daemon status by running the ps -ef | grep nsrexecd command.
• You are in the correct directory that contains the NMDA installation files.

2. To run either the CLI or GUI program, type the swinstall command:
• 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 12.
• 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 12.
Complete the installation 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 displays as normal.
b. To continue the installation, click OK.
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 22.
4. Return to the installation road map to perform any post-installation procedures. As part of these procedures, ensure that the NMDA
automatic wizard registration succeeded by using the following commands:

nsradmin -p nsrexecd
nsradmin> print type: NSR remote agent

Road map to post-installation procedures on page 16 provides complete details.

UNIX and Linux Installation 19

Installing NMDA on Linux systems
Install NMDA on a Linux system by running the rpm command. Install NMDA in the same directory as the NetWorker client software.

Steps
1. Complete the initial steps in Installation road maps on page 14. Ensure that you meet the following requirements:
• You are logged in as the root user.
• No backups or restores are running.
• The nsrexecd daemon is running. You can check the daemon status by running the ps -ef | grep nsrexecd command.
• You are in the correct directory that contains the NMDA installation files.

2. To install NMDA, type the required rpm command, for example:

• On Linux s390x (zLinux) 64-bit:

rpm -ivh lgtonmda-19.3.0.0-1.s390x.rpm

• On Linux x64:

rpm -ivh lgtonmda-19.3.0.0-1.x86_64.rpm

• On Linux x86:

rpm -ivh lgtonmda-19.3.0.0-1.i686.rpm

• On Linux Power PC 64-bit little-endian:

rpm -ivh lgtonmda-19.3.0.0-1.ppc64le.rpm

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

rpm -aq | grep lgto

The command output must include the proper lines, for example:
lgtoclnt-19.3.0.0-1
lgtonmda-19.3.0.0-1
lgtoxtdclnt-19.3.0.0-1

4. To enable support of the Orchestrated Application Protection feature on Linux x64, complete the steps in Enabling Data Domain
BoostFS for Orchestrated Application Protection on page 20.
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 22.
6. Return to the installation road map to perform any post-installation procedures. As part of these procedures, ensure that the NMDA
automatic wizard registration succeeded by using the following commands:

nsradmin -p nsrexecd
nsradmin> print type: NSR remote agent

Road map to post-installation procedures on page 16 provides complete details.

Enabling Data Domain BoostFS for Orchestrated

Application Protection
To enable the Orchestrated Application Protection feature on Linux x64, install the Data Domain BoostFS version 1.1 or later client package
in the default location. Data Domain BoostFS user documentation describes the Data Domain OS version requirements. Ensure that you
also complete the required post-installation settings.

About this task

NOTE: If you have an existing Data Domain BoostFS installation, perform only the following steps 3 to 5 to enable
Orchestrated Application Protection with the existing installation.

20 UNIX and Linux Installation

Steps
1. Log in as the root user on the Linux x64 system.
2. To install the Data Domain BoostFS 1.1 or later package in the default location, run the appropriate rpm -i command. For example:
• On Linux RHEL:

# rpm -i DDBoostFS-1.1.0.1-565598.rhel.x86_64.rpm

• On Linux SuSE:

# rpm -i DDBoostFS-1.1.0.1-565598.sles.x86_64.rpm

NOTE: The Orchestrated Application Protection feature does not support the relocated installation of the Data
Domain BoostFS package in a nondefault location.

3. Create an initial entry in the lockbox by using dummy information, such as the string aaaa as a dummy password. Ensure that you set
the permissions to enable only the root user to read and write the lockbox and log files. For example:

# /opt/emc/boostfs/bin/boostfs lockbox set -d aaaa -s aaaa -u aaaa

Enter storage unit user password:

Enter storage unit user password again to confirm:
Lockbox entry set

# chmod 0700 /opt/emc/boostfs/lockbox/*

# chmod 1700 /opt/emc/boostfs/lockbox
# chmod 1700 /opt/emc/boostfs/log

4. Assign the ACL permissions to the OS users that will run the Orchestrated Application Protection backups and restores, including the
application daemon that runs with the user accounts of these OS users. For example, the following commands set the ACL
permissions for the OS user with username mysql:

# setfacl -m u:mysql:rwx /opt/emc/boostfs/lockbox

# setfacl -m u:mysql:rw /opt/emc/boostfs/lockbox/*
# setfacl -m u:mysql:rwx /opt/emc/boostfs/log

5. Check the fusermount binary permissions. When possible, limit the number of OS users that have read and execute permissions for
the fusermount command.
Ensure that the OS users that will run the Orchestrated Application Protection backups and restores have the read and execute
permissions for the fusermount command. For example, this OS user has the username mysql as follows:

# which fusermount

/bin/fusermount

# ls -l /bin/fusermount

-rwsr-xr-x 1 root fuse 32336 Dec 7 2011 /bin/fusermount

# chmod o-rx /bin/fusermount

# ls -l /bin/fusermount

-rwsr-x--- 1 root fuse 32336 Dec 7 2011 /bin/fusermount

# setfacl -m u:mysql:rx /bin/fusermount

Installing NMDA on Solaris systems

Install NMDA on a Solaris system by running the pkgadd command.

Steps
1. Complete the initial steps in Installation road maps on page 14. Ensure that you meet the following requirements:

UNIX and Linux Installation 21

 • You are logged in as the root user.
• No backups or restores are running.
• The nsrexecd daemon is running. You can check the daemon status by running the ps -ef | grep nsrexecd command.
• You are in the correct directory that 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.

2. Type the required pkgadd command:

pkgadd -d /dir_pathname LGTOnmda

where /dir_pathname is the complete pathname of the directory that contains the LGTOnmda package.

3. When prompted to continue the installation, type y.

The system installs the software in the same directory as the NetWorker client software.
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 22.
5. Return to the installation road map to perform any post-installation procedures. As part of these procedures, ensure that the NMDA
automatic wizard registration succeeded by using the following commands:

nsradmin -p nsrexecd
nsradmin> print type: NSR remote agent

Road map to post-installation procedures on page 16 provides complete details.

Linking and unlinking NMDA in the environment on

UNIX or Linux
After you install NMDA on UNIX or Linux as described in the preceding topics of this chapter, perform an additional procedure to link
NMDA to the database environment. Before you uninstall NMDA, perform the procedure to unlink NMDA.
Use the correct instructions that follow to perform the linking or unlinking procedure for the database:
• Linking NMDA in a DB2 environment
• Linking and unlinking NMDA in an Informix environment
• Linking and unlinking NMDA in an Oracle environment
• Linking and unlinking NMDA in a Sybase ASE environment
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

About this task
NOTE:

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.

DB2_VENDOR_INI is deprecated in DB2 9.5 and discontinued in DB2 10.1, as announced by IBM. However,
DB2_VENDOR_INI might still be in effect in some DB2 versions, such as a DB2 version later than 10.1.

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

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.
You must complete the required steps to implement the changes on the DB2 server.

22 UNIX and Linux Installation

Steps
1. Log in as the DB2 user.
2. Remove the $INSTHOME/sqllib/cfg/vendor.cfg file, or edit the file and remove all the NMDA parameter settings.
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.

Linking and unlinking NMDA in an Informix environment

Perform the required link 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.

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

Steps
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 that Informix stored in $INFORMXIDIR/etc/sm_versions.std.
4. Restart the IDS server to apply the $ONCONFIG file changes.

Linking and unlinking NMDA in a MySQL environment

Perform the required link or unlink procedure in a MySQL environment:
• After you install NMDA, perform the procedure to link NMDA.
• Before you uninstall NMDA, perform the procedure to unlink NMDA.

UNIX and Linux Installation 23

Linking NMDA in a MySQL environment
About this task
Ensure that you meet the following requirements for MySQL support with NMDA on a MySQL database server host:
• A supported version of MySQL Enterprise Backup (MEB) software is installed on the MySQL server host, as detailed in the NetWorker
Module for Databases and Applications Version 19.3 Release Notes.
• MySQL client library libmysqlclient.so.version is installed on the MySQL server host, and the corresponding symbolic link is
created.
NOTE: If the symbolic link /usr/lib/libmysqlclient.so or /usr/lib/nsr/apps/libmysqlclient.so (32-bit)
or /usr/lib64/libmysqlclient.so or /usr/lib/nsr/apps/lib64/libmysqlclient.so (64-bit) does not exist
on the MySQL host, use the following steps to install the MySQL client library and create the symbolic link. If the
symbolic link already exists, ignore the following steps.

Steps
1. To install the MySQL libmysqlclient.so.version library that is included with the corresponding MySQL server, download and
unpack the appropriate MySQL server package from Oracle and then install the package on the MySQL server host:
• For MySQL version 5.5 or 5.6, install MySQL-shared-advanced-version.rpm, where version depends on the Linux
operating system and MySQL version in use.
NOTE: The MySQL-shared-advanced-version.rpm installation script creates the /usr/lib/
libmysqlclient.so (32-bit) or /usr/lib64/libmysqlclient.so (64-bit) symbolic link. If the symbolic link
is not created automatically, then you must create the symbolic link manually.
• For MySQL version 5.7 or later, install mysql-commercial-libs-version.rpm, where version depends on the Linux
operating system and MySQL version in use.
The libmysqlclient.so.version libraries are installed in /usr/lib/mysql (32-bit) or /usr/lib64/mysql (64-bit).

2. For MySQL version 5.7 or later, create a symbolic link from the file named libmysqlclient.so to the actual library file. For MySQL
5.5 and 5.6, this step is required only if you installed the MySQL library in a nondefault location:
NOTE: On 32-bit Linux, NMDA searches for the library in the /usr/lib/nsr/apps/ directory first, before
the /usr/lib/ directory. On 64-bit Linux, NMDA searches for the library in the /usr/lib/nsr/apps/lib64/
directory first, before the /usr/lib64/ directory.

• If you installed the MySQL 5.5 or 5.6 library in a nondefault location:

○ On 32-bit Linux, type one of the following commands:

ln –s <install_pathname>/libmysqlclient.so.18
/usr/lib/nsr/apps/libmysqlclient.so

or

ln –s <install_pathname>/libmysqlclient.so.18
/usr/lib/libmysqlclient.so

○ On 64-bit Linux, type one of the following commands:

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

or

ln –s <install_pathname>/libmysqlclient.so.18
/usr/lib64/libmysqlclient.so

• If you installed the MySQL 5.7 or later library in the default location:

NOTE:

24 UNIX and Linux Installation

 You can run the following command to determine the correct library file name and version number:

ls -l /usr/lib/mysql/libmysqlclient.so.*

In the following commands, replace the file name and version number as needed. For example, if the correct
version number is 20, then use the file name libmysqlclient.so.20 instead of
libmysqlclient.so.version.

○ On 32-bit Linux, type one of the following commands:

ln –s /usr/lib/mysql/libmysqlclient.so.version
/usr/lib/nsr/apps/libmysqlclient.so

or

ln –s /usr/lib/mysql/libmysqlclient.so.version
/usr/lib/libmysqlclient.so

○ On 64-bit Linux, type one of the following commands:

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

or

ln –s /usr/lib64/mysql/libmysqlclient.so.version
/usr/lib64/libmysqlclient.so

• If you installed the MySQL 5.7 or later library in a nondefault location:

NOTE:

You can run the following command to determine the correct library file name with version number:

ls -l <install_pathname>/libmysqlclient.so.*

In the following commands, replace the file name and version number as needed. For example, if the correct
version number is 20, then use the file name libmysqlclient.so.20 instead of
libmysqlclient.so.version.

○ On 32-bit Linux, type one of the following commands:

ln –s <install_pathname>/libmysqlclient.so.version
/usr/lib/nsr/apps/libmysqlclient.so

or

ln –s <install_pathname>/libmysqlclient.so.version
/usr/lib/libmysqlclient.so

○ On 64-bit Linux, type one of the following commands:

ln –s <install_pathname>/libmysqlclient.so.version
/usr/lib/nsr/apps/lib64/libmysqlclient.so

or

ln –s <install_pathname>/libmysqlclient.so.version
/usr/lib64/libmysqlclient.so

To verify the version of the installed MySQL client library, use the ls -lart command. For example:
• On 32-bit Linux, type the appropriate command:

ls -lart /usr/lib/nsr/apps/libmysqlclient*

UNIX and Linux Installation 25

 or

ls -lart /usr/lib/libmysqlclient*

• On 64-bit Linux, type the appropriate command:

ls -lart /usr/lib/nsr/apps/lib64/libmysqlclient*

or

ls -lart /usr/lib64/libmysqlclient*

Unlinking NMDA in a MySQL environment

Before you uninstall NMDA, unlink NMDA from the MySQL environment. Use the rm command to remove any libmysqlclient.so
symbolic link that you created manually for the NMDA installation.
Use the appropriate rm command to remove the symbolic link:
• For 32-bit NMDA, run the appropriate command:

rm /usr/lib/nsr/apps/libmysqlclient.so

or

rm /usr/lib/libmysqlclient.so

• For 64-bit NMDA, run the appropriate command:

rm /usr/nsr/apps/lib64/libmysqlclient.so

or

rm /usr/lib64/libmysqlclient.so

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

About this task

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.

Steps
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 required commands that are listed in the following table.
• If you installed NMDA in a nondefault directory, perform one of the following actions:
○ Copy the libnsrora.xx library file to the default directory /usr/lib, and type the required linking commands that are
listed in the following table.
○ Without copying the libnsrora.xx library file to the default directory /usr/lib, type the linking commands that are listed
in the following table to link the libnsrora.xx file in the nondefault installation directory /relocation_path/lib.

26 UNIX and Linux Installation

 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 system Create or remove Install: create the symbolic link Uninstall: remove the symbolic link
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 If not relocated:
• Linux x64 ln -s /usr/lib/libnsrora.so libobk.so
• Linux x86
• Solaris SPARC If relocated:
ln -s /relocation_path/lib/libnsrora.so libobk.so
• Solaris x64
Remove link cd $ORACLE_HOME/lib

rm libobk.so

Unlinking NMDA from the Oracle server environment

Before you uninstall NMDA, unlink NMDA from the Oracle server environment.

Steps
1. Log in as the $ORACLE_HOME owner.
2. Type the required commands that are listed in Table 8. Linking and unlinking commands for Oracle library file on UNIX or Linux on page
27 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 an SAP IQ environment

Perform the required link or unlink procedure in an SAP IQ 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 SAP IQ server

After you install NMDA on an SAP IQ server, link NMDA to the server environment.

Steps
1. Log in as the SAP IQ user on the Linux system.

UNIX and Linux Installation 27

2. Create the symbolic link by typing the following commands:

cd <SAP_IQ_installation_directory>/IQ-16_0/lib64
ln -s /usr/lib/libnsriqbr.so libnsriqbr.so

Unlinking NMDA from the SAP IQ server

Before you uninstall NMDA, unlink NMDA from the SAP IQ server environment.

Steps
1. Log in as the SAP IQ user on the Linux system.
2. Remove the symbolic link by typing the following commands:

cd <SAP_IQ_installation_directory>/IQ-16_0/lib64
rm libnsriqbr.so

Linking and unlinking NMDA in a Sybase ASE 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 ASE server

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

Steps
1. Log in as the Sybase ASE user.
2. Create the symbolic link by using one of the following options:
• If you installed NMDA in the default directory, type the required commands that are listed in the following table.
• If you installed NMDA in a nondefault directory, perform one of the following actions:
○ Copy the libnsrsyb.xx library file to the default directory, and type the required linking commands that are listed in the
following table.
○ Without copying the libnsrsyb.xx library file to the default directory, type the linking commands that are listed in the
following table to link the libnsrsyb.xx file in the nondefault installation directory /relocation_path/lib.

Table 9. Linking and unlinking commands for Sybase ASE library file on UNIX or Linux
Operating system Create or remove Install: create the symbolic link
link
Uninstall: remove the symbolic link

AIX Create link cd $SYBASE/$SYBASE_ASE/lib

HP-UX Itanium If not relocated:
Linux x64 ln -s /usr/lib/libnsrsyb.so libnsrsyb.so
Linux x86 If relocated:
Solaris SPARC ln -s /relocation_path/lib/libnsrsyb.so libnsrsyb.so
Solaris x64
Remove link cd $SYBASE/$SYBASE_ASE/lib

rm libnsrsyb.so

28 UNIX and Linux Installation

3. On SuSE Linux, if the LANG environment variable is set to POSIX, then create the /nsr/nsrrc file if it does not exist. Also set LANG
in the file to one of the locales that the Sybase server supports. If you do not have a preferred locale value, set LANG to C:

# cat /nsr/nsrrc

LANG=C
export LANG

After you set the environment variable, restart the NetWorker client. The NetWorker Administration Guide provides details about the
NetWorker software.

4. With 64-bit Sybase ASE 16.0 SP02, Sybase delivers a 64-bit backup server in addition to a 32-bit backup server on AIX and Solaris.
The ASE backup server script points to the 64-bit backup server by default.
NMDA 9.1 introduced support for the 64-bit backup server in Sybase ASE 16.0 SP02 or later for AIX and Solaris. You should use the
64-bit NMDA Sybase package on AIX and Solaris with Sybase ASE 16.0 SP02 or later.
If a 32-bit backup server is being used, then a DBA can change the ASE backup server script to start the 64-bit backup server. This
script change may be necessary when you upgrade from a previous version of NMDA where the 64-bit backup server is not supported
and the 32-bit backup server is used.
The following example shows a backup server run script for a 32-bit backup server:

#!/bin/sh
#
# Error log path: /space2/sybase/ASE-16_0/install/sybase160_BS.log
# Maximum number of network connections: 25
# Maximum number of server connections: 20
# Interfaces file path: /space2/sybase/interfaces
# Multibuf executable path: /space2/sybase/ASE-16_0/bin/sybmultbuf
# Backup Server name: sybase160_BS
#
/space2/sybase/ASE-16_0/bin/backupserver32 \
-e/space2/sybase/ASE-16_0/install/sybase160_BS.log \
-N25 \
-C20 \
-I/space2/sybase/interfaces \
-M/space2/sybase/ASE-16_0/bin/sybmultbuf32 \
-Ssybase160_BS \

If you remove the "32" suffix from "backupserver32" and "sybmultbuf32" in the script, then the script starts the 64-bit backup server.
Change the two lines in the script to point to the 64-bit backup server:
• Change the following line:
/space2/sybase/ASE-16_0/bin/backupserver32 \
Change the line to appear as follows:
/space2/sybase/ASE-16_0/bin/backupserver \
• Change the following line:
-M/space2/sybase/ASE-16_0/bin/sybmultbuf32 \
Change the line to appear as follows:
-M/space2/sybase/ASE-16_0/bin/sybmultbuf \

Unlinking NMDA from the Sybase ASE server

Before you uninstall NMDA, unlink NMDA from the Sybase ASE server environment.

Steps
1. Log in as the Sybase ASE user.
2. Type the required commands from Table 9. Linking and unlinking commands for Sybase ASE library file on UNIX or Linux on page 28 to
remove the link.

UNIX and Linux Installation 29

Uninstalling NMDA on UNIX or Linux systems
About this task
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 40.
To uninstall NMDA in any of these configurations, complete the steps in the following procedure:
• Single host
• Active-passive cluster
• Active-active application cluster, such as DB2 DPF, DB2 pureScale, 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.

Steps
1. Ensure that no backups or restores are running.
2. Ensure that the NetWorker Remote Exec daemon, nsrexecd, is running.
NOTE: If the NetWorker Remote Exec daemon is not running during the uninstallation, the NMDA wizard information
(not the binary) is left on the local host.

3. Unlink NMDA from the database environment according to the instructions in Linking and unlinking NMDA in the environment on UNIX
or Linux on page 22.
4. As the root user, uninstall NMDA according to the following uninstall instructions for the AIX, HP-UX, Linux, or Solaris operating
system.
NOTE: You do not need to shut down a database to uninstall NMDA.

Uninstalling NMDA on AIX systems

Uninstall NMDA on an AIX system by running the installp command or the SMIT GUI program.

Steps
1. Ensure that you have completed the steps in Uninstalling NMDA on UNIX or Linux systems on page 30 for the initial part of the
uninstall procedure.
2. To uninstall NMDA, use one of the following methods:
• 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. To display a list of the installed software packages, select F4=List.

c. Select the package to uninstall:

LGTOnmda.rte

d. Set the PREVIEW Only option to No.

e. To uninstall NMDA, press Enter.
f. Exit the SMIT GUI program.

30 UNIX and Linux Installation

Uninstalling NMDA on HP-UX systems
Uninstall 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.

Steps
1. Ensure that you have completed the steps in Uninstalling NMDA on UNIX or Linux systems on page 30 for the initial part of the
uninstall procedure.
2. To uninstall NMDA, use one of the following methods:
• Use the CLI program 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. To complete the uninstall when the system analysis is complete, click OK.
d. To confirm the uninstall, click Yes.

Uninstalling NMDA on Linux systems

Uninstall NMDA on a Linux system by running the rpm command.

Steps
1. Ensure that you have completed the steps in Uninstalling NMDA on UNIX or Linux systems on page 30 for the initial part of the
uninstall procedure.
2. Type the following command:

rpm -e lgtonmda

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

Uninstalling NMDA on Solaris systems

Uninstall NMDA on a Solaris system by running the pkgrm command.

Steps
1. Ensure that you have completed the steps in Uninstalling NMDA on UNIX or Linux systems on page 30 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.

2. Type the following command:

pkgrm LGTOnmda

3. When prompted, type y.

The software is uninstalled from the directory that contains the NetWorker client software.

UNIX and Linux Installation 31

 3
Microsoft Windows Installation
Topics:
• Installing NMDA on Microsoft Windows
• Linking and unlinking NMDA in the environment on Windows
• Repairing the installation on Microsoft Windows
• Uninstalling NMDA on Microsoft Windows

Installing NMDA on Microsoft Windows

Install NMDA on a Windows system by running the NMDA Setup program, win_x64\networkr\NMDA.exe.

Steps
1. Complete the initial steps in Installation road maps on page 14. Ensure that you meet the following requirements:
• You are logged in as an administrator.
• No backups or restores are running.
• The nsrexecd.exe service is running. You can check the service status by running either Component Services or Task Manager.
• You are in the correct directory that contains the NMDA installation files.

2. Install NMDA by using one of the following methods:

• Setup program method with installation wizard:
a. Run the NMDA Setup program, win_x64\networkr\NMDA.exe, and follow the instructions that the installation wizard
provides.
NOTE: If the NMDA 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 NetWorker Module for Databases and Applications Version 19.3 Administration Guide describes the wizard.
b. To exit the Setup program, click Finish.
• Silent installation method:
Run the NMDA.exe command with the appropriate command options:

NMDA.exe <installation_options>

where <installation_options> includes the following options:

○ /s /q suppresses all the UI output.
○ /passive displays the progress bar only during the installation.
○ /repair runs a repair or (if the software is not installed) an installation.
○ /l <pathname> specifies the log file pathname. Enclose <pathname> in double quotes if it includes a space. The default
directory for the log file is C:\users\username\AppData\Local\temp.
For example, the following command performs a silent NMDA installation that logs messages in the C:\Program Files\EMC
NetWorker\nsr\logs\nmda_installation.log file:

NMDA.exe /s /q /l "C:\Program Files\EMC NetWorker\nsr\logs\nmda_installation.log"

When the NMDA package has the same bitness as the NetWorker client package that is installed on the system, the NMDA program
files are installed in the same directory as the NetWorker client program files, NetWorker_install_path\bin.

32 Microsoft Windows Installation

 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.

3. Verify that the system Path environment variable includes the required directories, including the NetWorker client installation directory
and NMDA installation directory. For example:
a. Browse to Control Panel > System > Advanced System Settings.
b. On the Advanced tab, click Environment Variables.
c. In the System Variables section, 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.

d. If you modified the Path variable, restart the NetWorker Remote Exec Service (the program nsrexecd.exe).
4. 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 ASE server
before you installed NMDA, then restart the DB2, Oracle, or Sybase ASE server instance.
• If you installed 32-bit NMDA for the first time with a 64-bit NetWorker client on a Sybase ASE server and you will perform Client
Direct backups to a Data Domain device, restart the Sybase ASE server.
5. If you installed a 32-bit NMDA package on 64-bit Windows with a 64-bit NetWorker client package, then restart the NetWorker
Remote Exec Service (the program nsrexecd.exe).
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 on page 33.
7. Return to the installation road map to perform any post-installation procedures. As part of these procedures, ensure that the NMDA
automatic wizard registration succeeded by using the following commands:

nsradmin.exe -p nsrexecd
nsradmin> print type: NSR remote agent

Road map to post-installation procedures on page 16 provides complete details.

Linking and unlinking NMDA in the environment on

Windows
After you install NMDA on Windows as described in the preceding part of this chapter, perform an additional procedure to link NMDA to
the database or application environment. Before you uninstall NMDA, perform the procedure to unlink NMDA.
Use the correct instructions that follow to perform the linking or unlinking procedure for the database or application:
• Linking NMDA in a DB2 environment
• Linking and unlinking NMDA in an Informix environment
• Linking and unlinking NMDA in a Lotus Notes environment (optional)
• Linking and unlinking NMDA in a Sybase ASE environment

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

About this task
NOTE:

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.

DB2_VENDOR_INI is deprecated in DB2 9.5 and discontinued in DB2 10.1, as announced by IBM. However,
DB2_VENDOR_INI might still be in effect in some DB2 versions, such as a DB2 version later than 10.1.

Microsoft Windows Installation 33

 You do not require unlinking steps to uninstall NMDA in a DB2 environment.
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
Complete the following steps to implement the changes on the DB2 server.

Steps
1. Log in as the DB2 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.

Linking and unlinking NMDA in an Informix environment

Perform the required link 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.

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

34 Microsoft Windows Installation

Unlinking NMDA from the Informix server environment
Before you uninstall NMDA, unlink NMDA from the Informix server environment.

Steps
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 that Informix stored 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

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

About this task
After you install NMDA, you can add the document-level recovery feature to the Lotus Notes client software. The NetWorker Module for
Databases and Applications Version 19.3 Administration Guide describes the feature.
Complete the following steps to add the document-level recovery feature.

Steps
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 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 displays the following choices:
• NMDA Lotus - Restore Selected Documents
• NMDA Lotus - Restore Deleted Documents

Unlinking NMDA from Lotus Notes

Before you uninstall NMDA, remove the NMDA document-level recovery feature from the Notes Client software.

Steps
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

Microsoft Windows Installation 35

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 ASE 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 ASE server environment

Copy the libnsrsyb.dll file from the NetWorker location to the Sybase ASE location.

Steps
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 ASE server environment

Before you uninstall NMDA, remove the link to the Sybase ASE server environment.

Steps
1. Open the %SYBASE%\%SYBASE_ASE%\lib directory.
2. Delete the libnsrsyb.dll entry.

Repairing the installation on Microsoft Windows

To repair an NMDA installation on a Microsoft Windows system, complete the following steps.

Steps
1. Log in as the Windows system local administrator user on the NMDA host.
2. Ensure that no backups or restores are running.
3. Go to the directory that contains the NMDA installation files as described in Accessing the NMDA software on page 12.
4. Run the win_x64\networkr\NMDA.exe program.
5. In the Welcome dialog box, click Next.
6. In the Program Maintenance dialog box, select Repair, and then click Next.
7. To begin the installation, in the Ready to Repair the Program dialog box, click Install. The Setup program reinstalls the NMDA files
as required.
8. To exit the wizard, in the Installation Wizard Completed dialog box, click Finish.
The Installation Wizard Completed dialog box displays a message about how to start the NetWorker Client Configuration Wizard.
The NetWorker Module for Databases and Applications Version 19.3 Administration Guide describes the configuration wizard.

9. If you changed the system Path variable, restart the Windows system, and then verify that any required database instances and
services are restarted.

Uninstalling NMDA on Microsoft Windows

About this task
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 40.
To uninstall NMDA in any of the following configurations, complete the procedure as follows:
• Single host

36 Microsoft Windows Installation

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

Steps
1. Log in as the Windows system local administrator user on the NMDA host.
2. Ensure that no backups or restores are running.
3. Ensure that the NetWorker Remote Exec service, nsrexecd.exe, is running.
NOTE: If the NetWorker Remote Exec service is not running during the uninstallation, the NMDA wizard information
(not the binary) is left on the local host.

4. Unlink NMDA from the database or application environment according to the instructions in Linking and unlinking NMDA in the
environment on Windows on page 33.
5. 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 with installation wizard:

a. Go to the directory that contains the NMDA installation files as described in Accessing the NMDA software on page 12, and
then run the win_x64\networkr\NMDA.exe program.
b. In the Program Maintenance dialog box, select Remove, and then click Next.
c. In the Remove the Program dialog box, click Remove.
• Silent uninstallation method:
Run the NMDA.exe command with the appropriate command options:

NMDA.exe /uninstall <uninstallation_options>

where <uninstallation_options> includes the following options:

○ /s /q suppresses all the UI output.
○ /l <pathname> specifies the log file pathname. Enclose <pathname> in double quotes if it includes a space. The default
directory for the log file is C:\users\username\AppData\Local\temp.
For example, the following command performs a silent NMDA uninstallation that logs messages in the C:\Program Files\EMC
NetWorker\nsr\logs\nmda_uninstallation.log file:

NMDA.exe /uninstall /s /q /l "C:\Program Files\EMC NetWorker\nsr\logs

\nmda_uninstallation.log"

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

Microsoft Windows Installation 37

 4
NMDA with Mixed 32-bit and 64-bit Databases
and Applications
Topics:
• Coexistence of 32-bit and 64-bit databases and applications
• Installing NMDA to enable 32-bit and 64-bit coexistence
• Uninstalling 32-bit NMDA on a 32-bit/64-bit system

Coexistence of 32-bit and 64-bit databases and

applications
NMDA supports specific combinations of 32-bit and 64-bit database and application software that are installed on the same 64-bit
operating system.
For example, NMDA supports the combination of 32-bit Informix and 64-bit Oracle servers on the same 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 64-bit system.
The NMDA support for 32-bit and 64-bit application coexistence on 64-bit systems includes the following limitations:
• You cannot use the NMDA wizard to configure backups of 32-bit DB2 or 32-bit Lotus on a 64-bit Windows system where 32-bit and
64-bit applications coexist.
• You cannot use the NMDA wizard to configure backups of 32-bit Lotus on a 64-bit AIX system where 32-bit and 64-bit applications
coexist.
• You cannot use the NetWorker User for Lotus program for backups or restores of 32-bit Notes on a 64-bit Windows system where
32-bit and 64-bit applications coexist.
• 32-bit or 64-bit Sybase cannot coexist with DB2, Informix, Lotus Domino/Notes, or Oracle on a 64-bit Windows system.
• You cannot relocate the software on a 64-bit Solaris SPARC system where 32-bit and 64-bit applications coexist.
• NMDA does not support 32-bit and 64-bit application coexistence on a 64-bit Linux system.
The following topics describe how to install and uninstall NMDA on a system with both 32-bit and 64-bit databases or applications:
• Installing NMDA to enable 32-bit and 64-bit coexistence
• Uninstalling 32-bit NMDA on a 32-bit/64-bit system
The NetWorker Module for Databases and Applications Version 19.3 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 to enable 32-bit and 64-bit

coexistence
To install NMDA on a 64-bit operating system where both 32-bit and 64-bit databases or applications are running, install 64-bit NMDA and
enable NMDA for 32-bit use.

About this task

NOTE: NMDA does not support 32-bit and 64-bit application coexistence on a 64-bit Linux system.

Steps
1. If you install 32-bit NMDA on the system, uninstall NMDA with the required procedure:

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

 • Uninstalling NMDA on UNIX or Linux systems on page 30
• Uninstalling NMDA on Microsoft Windows on page 36

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 NetWorker Module for Databases and Applications Version 19.3 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 12.
4. Manually copy the 32-bit files that are listed in the following table 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 22
• Linking and unlinking NMDA in the environment on Windows on page 33
• Road map to post-installation procedures on page 16

Use the program file name that is listed in the following table when performing these steps. For example, to link the 32-bit NMDA
Sybase component to the Sybase ASE 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

On this 64- For this 32- Copy these 32-bit files from the 32-bit To this directory
bit operating bit directory
system application
AIX Informix informix/libnsrifmx32.so /usr/lib

• nsrdasv32 /usr/bin
• nsrdaprobe32

Lotus • nsrdasv32 /usr/bin

• nsrdaprobe32
• lotus/nsrdocrc32
• lotus/nsrnotesrc32

Sybase ASE sybase/libnsrsyb32.so /usr/lib

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

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

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

• nsrdasv32 /usr/sbin1
• nsrdaprobe32

Lotus • nsrdasv32 /usr/sbin1

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

 Table 10. Additional steps to enable NMDA for a 32-bit application(continued)
On this 64- For this 32- Copy these 32-bit files from the 32-bit To this directory
bit operating bit directory
system application

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

Sybase ASE sybase/libnsrsyb32.so /usr/lib

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

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 ASE Not applicable. 32-bit or 64-bit Sybase ASE 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
Complete the required steps to uninstall NMDA on a system where the 32-bit and 64-bit databases or applications coexist.

Steps
1. Ensure that no backups or restores 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 22
• Linking and unlinking NMDA in the environment on Windows on page 33

3. Log in as the root user (UNIX) or system administrator (Windows).

4. Manually delete the files for the 32-bit database or application that you manually copied during installation as shown in Table 10.
Additional steps to enable NMDA for a 32-bit application on page 39.
5. Uninstall 64-bit NMDA according to the required instructions:
• Uninstalling NMDA on UNIX or Linux systems on page 30

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

• Uninstalling NMDA on Microsoft Windows on page 36

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

 A
Uninstalling ISM on an Informix Server
Topics:
• ISM software on an Informix server
• Uninstalling ISM on UNIX or Linux
• Uninstalling ISM on Microsoft Windows

ISM software on an Informix server

Informix Storage Manager (ISM) is a storage management software that is packaged and installed with Informix Dynamic Server (IDS).
For Informix servers only, if you installed ISM software, uninstall the software before you install NMDA by using the OS-specific
instructions in the following topics:
• Uninstalling ISM on UNIX or Linux
• Uninstalling ISM on Microsoft Windows
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. Follow the linking instructions in the correct linking section of this
guide.

Uninstalling ISM on UNIX or Linux

Complete the required steps to uninstall ISM on an Informix server on a UNIX or Linux host.

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

42 Uninstalling ISM on an Informix Server

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

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

About this task

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

Uninstalling ISM on Windows manually

If the IDS Server Setup program is not available, manually uninstall ISM on an Informix server on Windows.

Steps
1. Log in as user informix.
2. To set the Informix Database server environment variables, type the following command:

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

Uninstalling ISM on an Informix Server 43

5. Shut down the ISM services:

ism_shutdown -deinstall

6. Shut down ISM, and then verify that there are no services listed for ISM in Control Panel > Administrative Tools > Services.
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 is 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 then 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:
CAUTION: 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.

44 Uninstalling ISM on an Informix Server