Pages From DP 9 Installation 2017 03

Installation Guide
Chapter 3: Installing Data Protector clients
components" on page 58.

Selecting components
If you selected more than one client and you want to install different components on each client,
click Specify components for each client individually and then click Next. Select the
components for each client independently.
Click Finish to start the installation.
Local installation on UNIX and Mac OS X

systems
If you do not have an Installation Server for UNIX installed on your network, or if for some reason you
cannot remotely install a client system, Data Protector clients can be installed locally from the UNIX
installation DVD-ROM or ISO image (for HP-UX or Linux).
Before starting the installation procedure, decide which components you need to install on your client
system. For the list of the Data Protector software components and their descriptions, see "Data
Protector components" on page 58.
Note: Windows XP Home Edition and HP OpenVMS clients can be installed locally. Remote
installation is not supported.
Prerequisites
l For system requirements, disk space requirements, supported platforms, processors, and Data
Protector components, see the HPE Data Protector Product Announcements, Software Notes, and
References.
HPE Data Protector (9.09) Page 98 of 426

Installation Guide
l You must have root permissions on every target system.

l A POSIX shell (sh) must be used for the installation.
Note: You can also use the following procedure to upgrade the UNIX clients locally. The script will
detect a previous installation and will prompt you to perform the upgrade.
Installation Procedure
To install UNIX and Mac OS X clients locally
1. Insert and mount the UNIX installation DVD-ROM or ISO image (for HP-UX or Linux).
Note that the DVD-ROM filesystem uses the Rock Ridge extensions.
2. From the MountPoint/LOCAL_INSTALL directory execute the omnisetup.sh command.
The syntax of the command is as follows:
omnisetup.sh [-source directory] [-server name] [-install component_list]
where:
l directory is the location where the installation DVD-ROM or ISO image is mounted. If not
specified, the current directory is used.
l name is a full hostname of the Cell Manager of the cell to which you want to import the client. If
not specified, the client will not be automatically imported to the cell.
Note: In case of upgrading the client that resides on the Cell Manager or Installation
Server, you do not need to specify -install component_list. In this case, the setup will
select the same components that were installed on the system before the upgrade without
issuing a prompt.
l component_list is a comma-separated list of component codes to be installed. No spaces are

allowed. If the -install parameter is not specified, Setup will prompt you separately about
installing each available component on the system.
Note: In case of upgrading the client, the setup will select the same components that were
installed on the system before the upgrade started, without issuing a prompt.
The list of the components is presented in the table below. The exact list of the components is
subject to the availability on the particular system. For the description of the components, see
"Data Protector components" on page 58.
Data Protector component codes
Component code Component
cc User Interface
da Disk Agent

Installation Guide
ma General Media Agent
ndmp NDMP Media Agent
informix Informix Integration
lotus Lotus Integration
oracle8 Oracle Integration
mysql MySQL Integration
postgresql PostgreSQL Integration
vmware VMware Integration (Legacy)
vepa Virtual Environment Integration
sybase Sybase Integration
sap SAP R/3 Integration
sapdb SAP MaxDB Integration
saphana SA HANA Integration
db2 DB2 Integration
emc EMC Symmetrix Agent
smisa HPE P6000 / HPE 3PAR SMI-S Agent
ssea HPEP9000 XP Agent
emcvnx EMC VNX Storage Provider
emcvmax EMC VMAX Storage Provider
netapp NetApp Storage Provider
StoreOnceSoftware StoreOnce Software Deduplication
autodr Automatic Disaster Recovery

Installation Guide
docs English Documentation (Guides, Help)
Example
The example below shows how you can install the Disk Agent, General Media Agent, User
Interface, and Informix Integration components on a client that will be automatically
imported to the cell with the Cell Managercomputer.company.com:
./omnisetup.sh -server computer.company.com -installda,ma,cc,informix
3. Setup informs you if the installation was completed and if the client was imported to the Data
Protector cell.
The CORE component is installed the first time any software component is selected for installation.
The CORE-INTEG component is installed the first time any integration software component is
selected for installation or reinstallation.
Running the installation from the hard disk

To copy the installation DVD-ROM image to your computer and run the installation or upgrade of UNIX
and Mac OS X clients from the hard disk, copy at least the hpux/DP_DEPOT and the LOCAL_INSTALL
directories.
Note: The Linux depot does not support local installation. You must copy the HP-UX depot, even
on Linux systems.
For example, if you copy installation packages to /var/dp80, the directories must be a subdirectory of
/var/dp62:
# pwd
/var/dp80
# ls
DP_DEPOT
LOCAL_INSTALL
After you have copied this to the hard disk, change to the LOCAL_INSTALL directory and execute the
following command:
omnisetup.sh [-server name] [-install component_list]
For example:
./omnisetup.sh -install da
Note, that if you copied the DP_DEPOT directory to a different directory (for example due to disk space
constraints), the -source option is also required.

Installation Guide
Next steps
If you did not specify the name of the Cell Manager during the installation, the client will not be imported
to the cell. In this case, you should import it using the Data Protector graphical user interface. For the
procedure, see "Importing clients to a cell " on page 187. For information on additional configuration
tasks, see the HPE Data Protector Help.
Installing a Media Agent to use the ADIC/GRAU

Library or the StorageTek Library
Data Protector provides a dedicated ADIC/GRAU and StorageTek ACS library policies used to
configure an ADIC/GRAU library or StorageTek ACS library as a Data Protector backup device. You
need to install a Data Protector Media Agent (the General Media Agent or the NDMP Media Agent) on
every system that will be physically connected to a drive in an ADIC/GRAU or StorageTek library.
Also, for multihost configurations, you must install a Data Protector Media Agent on the systems that
control the ADIC/GRAU or StorageTek library robotics. Note that multihost configuration is a
configuration where the library and drive are not connected to the same computer.
For the ADIC/GRAU library, each system on which you install a Media Agent software and it accesses
the library robotics through the GRAU/ADIC DAS Server is called a DAS Client. For the STK ACS
integration, each system on which you install a Media Agent software and it accesses the library
robotics through the STK ACS Server is called an ACS Client.
Note: You need special licenses that depend on the number of drives and slots used in the
StorageTek library. For more information, see "Data Protector Licensing" on page 306.
Connecting library drives

Physically connect the library drives to the systems where you intend to install a Media Agent
software.
For details about supported ADIC/GRAU or STK libraries, see https://softwaresupport.hpe.com/.
For information about how to physically attach a backup device to the system, see "Installing Data
Protector clients" on page 55 and the documentation that comes with the ADIC/GRAU or StorageTek
library.
For information on how to physically attach a backup device to a supported Windows system, see
"Installing Data Protector clients" on page 55 and the documentation that comes with the ADIC/GRAU
or StorageTek library.

Pages From DP 9 Installation 2017 03

Uploaded by

Copyright:

Available Formats

Pages From DP 9 Installation 2017 03

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pages From DP 9 Installation 2017 03

Uploaded by

Copyright:

Available Formats

Installation Guide

Chapter 3: Installing Data Protector clients

components" on page 58.

Local installation on UNIX and Mac OS X

HPE Data Protector (9.09) Page 98 of 426

l You must have root permissions on every target system.

l component_list is a comma-separated list of component codes to be installed. No spaces are

Data Protector component codes

Component code Component

HPE Data Protector (9.09) Page 99 of 426

Component code Component

ma General Media Agent

ndmp NDMP Media Agent

informix Informix Integration

lotus Lotus Integration

oracle8 Oracle Integration

mysql MySQL Integration

postgresql PostgreSQL Integration

vmware VMware Integration (Legacy)

vepa Virtual Environment Integration

sybase Sybase Integration

sap SAP R/3 Integration

sapdb SAP MaxDB Integration

saphana SA HANA Integration

db2 DB2 Integration

emc EMC Symmetrix Agent

smisa HPE P6000 / HPE 3PAR SMI-S Agent

ssea HPEP9000 XP Agent

emcvnx EMC VNX Storage Provider

emcvmax EMC VMAX Storage Provider

netapp NetApp Storage Provider

StoreOnceSoftware StoreOnce Software Deduplication

autodr Automatic Disaster Recovery

HPE Data Protector (9.09) Page 100 of 426

Component code Component

docs English Documentation (Guides, Help)

Running the installation from the hard disk

HPE Data Protector (9.09) Page 101 of 426

Installing a Media Agent to use the ADIC/GRAU

Connecting library drives

HPE Data Protector (9.09) Page 102 of 426

You might also like