2 - 1 DP - Install - L300

HP Data Protector 6.
2 – Installation
HP Data Protector 6.2 software
Installation
Essentials Training
for Support and Services
1
©2011©2011
HP Restricted
HP Restricted
Version: 6.2
Date: December 15, 2011
Contact: HP Software
IM R&D Technology Intelligence Center
HP Data Protector Team
Hewlett-Packard Co.
-- HP Restricted -- -1-
HP Data Protector 6.2 – Installation
Notice
The information contained in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this manual,
including but not limited to, the implied warranties of merchantability and fitness
for a particular purpose. Hewlett-Packard shall not be liable for errors contained
herein or direct, indirect, special, incidental or consequential damages in
connection with the furnishing, performance, or use of this material.
Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard
product and replacement parts can be obtained from your local Sales and
Service Office.
Copyright
© Copyright 2011 Hewlett-Packard Company. This document contains
information, which is protected by copyright. All rights are reserved.
Reproduction, adoption, or translation without prior written permission is
prohibited, except as allowed under the copyright laws.
Restricted Rights Legend

Use, duplication or disclosure by the U.S. Government is subject to restrictions as
set forth in subparagraph (c)(I)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 for DOD agencies, Computer
Software Restricted Rights clause at FAR 52.227-19 for other agencies.
Document history
Version Date Description
1.0 December 2011
-2- -- HP Restricted --
Please use this Page as a reference, while working with this training.
Logical Example path Explanation

Name
$DP_HOME C:\Program Files\Omniback DP Home directory on all Windows

versions
/opt/omni DP Home directory on HP-UX, Linux and

Sun Solaris
$DP_CONFIG C:\Program Files DP configuration directory on

\Omniback\config\server Windows 2000/2003/XP
C:\ProgramData DP configuration directory on

\Omniback\config\server Windows Vista/2008/7
/etc/opt/omni/server/ DP configuration directory on HP-UX,

Linux and Sun Solaris
$DP_VAR C:\Program Files\Omniback DP Internal Database, Log and

temporary files directory on Windows
2000/2003/XP
C:\ProgramData\Omniback DP Internal Database, Log and

temporary files directory on Windows
Vista/2008/7
/var/opt/omni DP Internal Database, Log and

temporary files directory on HP-UX, Linux
and Sun Solaris
Note: In customer visible Data Protector documentation the above variables are
not used, instead only two variables are used:
• DP_Home: On Windows Vista, Windows 7, and Windows Server
2008,the directory containing Data Protector program files. On other
Windows operating systems, the directory containing Data Protector
program files and data files. Its default path is
%ProgramFiles%\OmniBack
• Data_Protector_program_data: On Windows Vista, Windows 7, and
Windows Server 2008, the directory containing Data Protector data files. Its
default path is %ProgramData%\OmniBack
Table of Contents
Objective .......................................................................................... 6
Overall Installation Sequence ................................................................. 7
Plan the layout of the cell ......................................................................... 9
Installation Planning ........................................................................... 10
Example of a heterogeneous Data Protector Cell ...................................... 12
Hardware and Software requirements check .............................................. 13
Windows Installation Requirements ........................................................ 14
Installation Requirements – Unix ............................................................ 15
Product Media / DVD Contents............................................................ 16
Product Download ............................................................................ 16
Electronic Delivery Program ................................................................. 17
Cell Manager (CM) and Installation Server (IS) Installation ............................. 18
Install Cell Manager on Windows ........................................................ 19
The Installation on Windows ................................................................ 21
Cell Manager installation on Windows 1/3 ........................................... 22
Installation Status Page ....................................................................... 26
Installation Server (IS) installation on Windows ......................................... 28
Windows Services ............................................................................ 29
Installation on Unix ............................................................................ 31
Setting kernel parameters ................................................................... 32
The omnisetup.sh command ................................................................. 33
Adding DP user manually ................................................................... 33
The installed directory structure on UNIX ................................................ 34
Unix Services ................................................................................... 35
Client Installation ................................................................................. 37
Client Installation Overview ................................................................. 38
Remote Push Installation 1/3 ............................................................... 39
Windows Firewall ............................................................................. 44
Enabling Data Protector port 5555 ...................................................... 44
Check that outbound connections are allowed........................................ 46
Inbound rules created by Data Protector ................................................ 47
Push Installation with Secure Shell ......................................................... 48
Local Client Installation – Windows 1/2 ................................................ 49
Local Client Installation – Windows 2/2 ................................................ 51
Local Client Installation – Unix .............................................................. 53
Omnisetup.sh ................................................................................... 53
Notive OS installation tools................................................................. 54
xinetd handling ................................................................................ 54

Port 5555 handling .......................................................................... 54
Local Client Installation Others.............................................................. 56
Installation of the OpenVMS Client ....................................................... 56
Installing Netware Clients ................................................................... 56
Maintenance ...................................................................................... 58
Patches 1/2 .................................................................................... 59
Patches 2/2 .................................................................................... 62
Ex – and import of clients .................................................................... 63
Export ............................................................................................. 63
Import ............................................................................................. 64
Installation Server & MS Cluster ........................................................... 64
Export of clients ................................................................................ 65
Importing Clients ............................................................................... 66
Adding Components to clients .............................................................. 67
Uninstallation ................................................................................... 68
Uninstallation of DP clients using the DP GUI............................................ 69
Local Uninstallation ............................................................................ 70
Local Uninstallation: windows .............................................................. 71
The Upgrade Procedure ...................................................................... 72
Upgrade Cell Manager and Installation Server ....................................... 72
Upgrade using omnisetup.sh ............................................................... 73
Upgrade/Migration Paths - Windows.................................................... 74
Upgrade/Migration Paths - HP-UX ........................................................ 75
Appendix........................................................................................... 76
Omnisetup.sh description .................................................................... 76
Installation examples .......................................................................... 80
Example for a Cell Manager installation on HP-UX .................................. 80
Example for a local client installation on HP-UX ....................................... 81
Example for a Cell Manager and Installation Server installation on Linux ...... 82
Objective
Upon completion of this module, the student will know how to install the
HP Data Protector product. This includes to:
• plan an installation of Data Protector
• understand the installation sequence
• install the Data Protector Cell Manager
• install and import Installation Servers
• distribute Data Protector agent components to client systems
• alternatively install the clients locally and then import them in the cell
• understand how to upgrade an existing DP environment to a newer product
version
• maintain an existing cell
OVERALL INSTALLATION SEQUENCE

Plan the layout of the Cell
Check hardware and software requirements

Installation
Cell Manager Installation
Installation Server Installation
Client Installation
add clients / add components on existing clients

Maintenance
Upgrade to a new version / patch installation
Uninstallation
3 ©2011 HP Restricted
Overall Installation Sequence

This slide gives an overview about the sequence of the installation steps:
• Before you start to install the Data Protector software, make a plan how your
cell should look like. If you have a huge environment, consider to create
several cells and to use them either independently of each other or to
manage them through one central Cell Manager using the MoM (Manager
of Managers) concept.
• Hardware and Software Requirements
o Installation Servers and Cell Managers have certain hardware and
software requirements, which you should check and verify before you
start installing the software.
• Install Cell Manager and Installation Servers
o Cell Manager and Installation Servers are installed directly from the
product release media (electronic or DVD).
o If you have additional Installation Servers they must be imported at
the Cell Manager.
• Install Clients
o After you have installed the Cell Manager and Installation Servers,
the Data Protector client systems may be installed remotely, using the
DP GUI to push the respective agent components from the depot on
the Installation Server through the network to the clients, or the clients
can be installed manually from the local DVD media.
Clients that are manually installed from the media must be imported
into the cell after their installation completed.
• Licensing
o An Instant-On license is automatically created when the product is
first installed. This gives you usage for 60 days, during which time
you must apply for and install a permanent license
• Maintenance
o Once on all systems the DP client software is installed, backups can
be performed. However the existing installation must be maintained
(installing patches) and modified.
PLAN THE LAYOUT

OF THE CELL
DP 6.2 Installation
Essential Training for Support
and Services
Plan the layout of the cell
INSTALLATION PLANNING
plan the layout of the cell
– which platforms will be backed up?

– which applications will be integrated with Data Protector?
– which system will be the Cell Manager?
– is remote installation possible for the clients?
– are there several Installation Servers needed?
– which systems will be Installation Servers?
– where will the Cell Console be installed?
– how many clients will be in the Cell?
– is there more than one cell needed?
– will the clients all be on the same LAN?
– is this a new installation or an upgrade?
Installation Planning
This slide lists the questions that must be answered during the installation
planning.
For the first 2 questions
• Which platforms will be backed up?
• Which applications will be integrated with Data Protector?
you must check the Data Protector Platform and Integration Support Matrix to see
whether DP does support your systems.
• Which system will be the Cell Manager?
The Cell Manager must be one of the following: HP-UX 11.x,
Solaris 8/9/10, SLES 9/10/11(64-Bit ), RHEL 4/5/6(64-Bit) or a
Windows XP Pro(32-Bit)/Win-7(32-Bit) /2003/2008/2008-R2 system.
The Cell Manager system should be reliable and ideally configured with high
availability characteristics (RAID, Disk Mirroring, etc). Permanent availability of
the Cell Manager with its DP Internal Database is essential for Data Protector to
be operational. Consider size and growth of the IDB
• Which system will be the Installation Server(s)?
• Are there several Installation Servers needed?
Any system that is supported as a Cell Manager can also be used as Installation
Server. About 1 GB is needed for the depot directory that stores the DP client
agent components. In a heterogeneous (Windows/Unix) environment, allocate
one system to be the Installation Server for UNIX platforms and one for Windows
platforms.
- 10 - -- HP Restricted --
An Installation Server can be imported into more than one cells. Similarly more
than one Installation Server (per platform) can be configured (and imported) for a
large environment in one cell. This can help to distribute the installation load
during updates or patches to the Data Protector clients, and might be helpful in
firewall environments.
• Is remote installation possible for the clients?
Remote installation and update is possible for all Unix and Linux flavors and for
Windows. For Novell and OpenVMS it is not possible. Clients on those
platforms must be installed locally.
• Where will the Cell Console be installed?
The Cell Console is just the GUI of DP. It can be installed on many client
platforms and on several clients. It is up to you whether you want restrict the
number of GUI clients and therewith access to Data Protector to a few systems
only, or you want install a large number of GUIs. Here it is worthwhile to know
that users can restore their own files if they have a GUI on their local system
• How many clients will be in the Cell?
• Is there more than one cell needed?
The answer to these questions depends on the size of your environment.
Theoretically there can be more than1000 clients in one cell. However,
depending on the frequency of backups, the numbers of files to backup, their
sizes and how often their contents changes, the number of entries in the DP
internal database can grow quickly and reach their limit. The fnames file is the
part of the internal database (IDB) which stores the names of backed up files.
The size limit of the fnames file is 48GB.
To avoid reaching this limit, a rule of thumb is not to have more than 100 clients
in a cell. If you reach the number of 300 to 500 clients in a cell, performance
degradations may be seen because system resources reach their limits.
• Will the clients all be on the same LAN subnet?
Even if they are on different subnets, this should be no issue for DP as it is a
product to perform LAN backups.
• Will the clients all be on the same domain?
DP is able to include clients in a cell from different domains. However it is very
sensible to an absolutely correct network setup. Meaning that the respective
other domain must be reachable for the CM to contact the client and vice versa
the client must be able to easily reach the CM in the other domain.
• Is this a new installation or an upgrade?
Maybe this question should be on top of the list as you need not care about the
cell setup if it is already available. However the steps to perform an upgrade
from a currently installed DP version to a newer one are pretty similar to an initial
installation. In both cases the CM and IS must be installed/upgraded and then
the agent components be distributed (pushed) to the clients.
-- HP Restricted -- - 11 -
EXAMPLE OF A DATA PROTECTOR CELL

plan the layout of the cell
– Cell Manager (CM) including Installation Server (IS) on Windows

– Installation Servers (IS) on Unix/Linux
– Client systems on various supported platforms
HP--UX Windows Windows HP--UX

Client Client Client Client
Windows CM (IS) Windows Unix/Linux

Client Agent
Client Agent
Installation
IDB Windows Component Component
Depot Depot Server
Solaris AIX Linux Windows

Client Client Client Client
Example of a heterogeneous Data Protector Cell

This slide shows an example for a heterogeneous Data Protector cell.
Only one of the systems in the Cell must be the Cell Manager. It can be an HP-
UX, Solaris, Linux or Windows system. If you are running Data Protector in a
mixed environment, you need at least two installation servers, one for Windows
and one for UNIX.
The Cell Manager is typically used also as an installation server; this is a
configurable option during the Cell Manager installation. However the
installation servers can also run stand alone on different systems than the Cell
Manager.
The Data Protector agent components can be installed locally on the various
client systems. Usually they are distributed from the installation servers to the
clients, using the DP GUI. This process is also called the remote installation.
CHECK
HARDWARE AND
SOFTWARE
REQUIREMENTS
DP 6.2 Installation
and Services
Hardware and Software requirements check
WINDOWS INSTALLATION REQUIREMENTS

check hardware and software requirements
• Windows XP Pro 32-bit

• Windows 2003 32- and 64-bit
• Windows Server 2008 32- and 64-bit
• Windows Server 2008 R2 64-bit
• Windows 7 32-bit
Module RAM [MB] Disk space [MB]
Cell Manager (CM) 256, recommended 512 190 + IDB
Installation Server (IS) 64 1 GB
Original GUI 256 150
Java GUI 512 , recommended 1 GB 40, recommended 60
Disk Agent 64, recommended 128 10
Media Agent 64, recommended 128 20
Integration modules
8 ©2011 HP Restricted 64, recommended 128 20
Windows Installation Requirements

The Cell Manager must meet the following minimum requirements:
• 256 MB of RAM (512 MB recommended)
For each parallel backup session 40 MB of RAM are required. For
example, if you want to run 60 parallel backup sessions 3 GB of RAM are
needed.
• 190 MB of disk space + approximately up to 2% of planned data to be
backed up (for use by the IDB).
• On Windows Server 2008 systems, administrative privileges are required to
install Data Protector 6.20.
The Installation Server must meet the following minimum requirements:
• 64 MB of RAM
• 1 GB of disk space
For the English Documentation (Guides and Help) you need about 85MB disk
space.
For more details about the software and hardware requirements, refer to the
DP Product Announcements, Software Notes, and References guide.
UNIX INSTALLATION REQUIREMENTS

• HP-UX 11.11, 11.23, 11.31 on PA-Risc and IA

• Solaris 8, 9, 10
• Linux SLES 9, 10, 11
• Linux RHEL 4, 5, 6 64-bit
Module RAM [MB] Disk space [MB]
Cell Manager (CM) 256, recommended 512 350-550 + IDB
Installation Server 64 1,5 GB
(IS)
Java GUI 512, recommended 1GB 40, recommended
60
Disk Agent 64, recommended 128 10
Media Agent 64, recommended 128 20
Integration modules 64, recommended 128 20
Installation Requirements – Unix

The Cell Manager must meet the following minimum requirements:
• 256 MB of RAM (512 MB recommended)
For each parallel backup session 40 MB of RAM are required and 5–8 MB
per data segment size. This means that, for example, if you want to run 60
parallel backup sessions 3 GB of RAM plus 512 MB for data segments are
needed.
• 350–550 MB of disk space + approximately up to 2% of planned data to
be backed up (for use by the IDB).
The Installation Server must meet the following minimum requirements:
• 64 MB of RAM
• 1.5 GB of disk space
• The inetd daemon must be installed and running.
For the English Documentation (Guides and Help) you need about 80MB disk
space.
For more details about the software and hardware requirements, refer to the
DP Product Announcements, Software Notes, and References guide.
PRODUCT MEDIA / DVD CONTENTS

– the DP 6.2 product case contains 3 DVDs:
DVD 1: DVD 2: DVD 3:
HP Data Protector for HP Data Protector for HP Data Protector for
Windows Solaris
HP-UX
• Windows • Solaris depot
(CM and IS for 32/64-bit) • HP-UX depot (covering CM and IS on
• Open VMS (Alpha, IA64) (covering all PA-RISC, IA64, SPARC Platforms)
• Novell Netware CM and IS in one)
HP Data Protector for
• manuals in PDF format • manuals in PDF format Linux
• product demo for • HP Operations Manager • Linux Depot
Windows platforms Integrations (CM, IS for RHEL, SLES
• HP Operations Manager – DP-OMU (Unix) (x64)
Integrations – DP-OMW (Windows)
• product information – DP-OML (Linux) Miscellaneous
• Media Operations • AutoPass • manuals in PDF format
− HP-UX, Solaris, Windows, • HP Operations Manager
Linux • Citrix Xen scripts
− Documentation Integrations
• AutoPass
Evaluation bits are downloadable from:
www.hp.com/go/dataprotector
Product Media / DVD Contents

The DP product can be ordered as electronic delivery or on physical media. The
physical media are three DVDs:
• one for installing the product on Windows Systems
• one for HP-UX systems
• the third one covers the bits for Solaris and Linux
The customer will receive a case containing all 3 DVDs. The detailed contents of
the DVDs are shown on the slide.
Since DP version 6.2, the manuals - Learning Products - are no longer available
as printed books - and therefore cannot be ordered. They are however available
as PDF files on the product media (and on the web as well).
The DVDs also contain the Media Operations product. Note that its version is
always the same as for the corresponding Data Protector.
Product Download
Data Protector can also be downloaded in .zip files from the WEB. Go to
www.hp.com/go/dataprotector, click on Trials and Demos then select the HP
Data Protector 6.20 Evaluation.
The layout of the packages for download is a bit different from the DVDs. You
can download a package respectively for the installation on HP-UX, Linux,
Solaris and Windows. The Windows package includes the Media Operation
product. And the fifth package is for the installation of Netware and OVMS
clients and the HP Software integrations.
Electronic Delivery Program

Customers who do not need the product on DVD media can order it also via E-
Delivery. The product numbers for the E-Delivery are similar as for the DVD
media, just append the letter "E" to the number of the physical media.
For example, TD586AA is the product number for the English DVDs. The
respective product number for E-Delivery is TD586AAE.
For more information, refer to the QuickSpecs document. It is available on
www.hp.com/go/dataprotector. Click on the Resources tab, expand Quick
Specs and then select the document for your region.
Note that customers should always order 24x7 support in addition as the
product is complex and needs support for large customer installations.
The support contract is attached to the order of the product media. A customer
should always order both, the media and the LTU (License to use).
It is not supported to only order the LTU and then to use it with the downloaded
evaluation bits.
CELL MANAGER
AND
INSTALLATION
SERVER
INSTALLATION
DP 6.2 Installation
and Services
Cell Manager (CM) and Installation Server (IS) Installation
PREPARATION ON WINDOWS
Install Cell Manager and Installation Server
Logon as Domain Administrator
Verify that Microsoft TCP/IP is installed and running
Verify that host name resolution is enabled (DNS)
Make sure the Cell Manager (and Installation Server) have static IP addresses
Verify that port number 5555 is free on all systems in the cell
Verify that sufficient disk space is available for IDB growth on CM
Install HP Data Protector from DVD
Install Cell Manager on Windows

To install a Windows Cell Manager, you must have Administrator rights. The
Windows system that will become your Cell Manager must meet the following
requirements:
• Have the Microsoft implementation of the TCP/IP protocol installed and
running.
• The host name resolution must be enabled and work consistently on all
systems where Data Protector is supposed to be installed. The computer
name and the hostname must be the same.
• Have a static IP address for the system on which the Cell Manager will be
installed. If the system is configured as a DHCP client, its IP address
changes; therefore, it is required to either assign a permanent DNS entry for
the system (and reconfigure it), or to configure a DHCP server to reserve a
static IP address for the system (IP address is bound to the system's MAC
address).
• Have the port number 5555 (default) free. If this is not the case, refer to
Changing the Data Protector default port number inside the Installation and
Licensing manual. Have the port number 5556 free to install Java GUI
Server or Java GUI Client.
• Have sufficient disk space (about 2% of the backed up data) for the IDB.
Refer to the HP Data Protector Product Announcements, Software Notes, and
References for details.
• Have access to a DVD-ROM drive and start the installation (see the next
slides for a detailed description). If the Cell Manager has to be installed
cluster aware, additional steps have to be considered. Please check the HP
Data Protector MS Cluster training for Support and Services for further
details.
Please note that Data Protector Cell Manager does not support the IDB on a file
system that is mounted as NFS type.
INSTALLATION WIZARD ON WINDOWS

– insert product DVD

• autorun starts either automatically or you click on autorun.exe to start the HP Data
Protector software 6.2 splash screen
– select Install Data Protector

– alternatively open the product media in Explorer and run
~\WINDOWS_OTHER\<platform>\setup.exe
where <platform> is one of
i386, x8664 or ia64
– after a successful installation a 60 days
trial license is installed
• during that time all required licenses
must be purchased and installed
The Installation on Windows

The installation procedure consists of the following steps:
Insert the DVD-ROM; this should execute the Windows Autorun. If the so called
HP Data Protector software 6.2 installation splash screen does not come up
automatically, open the installation media in the Windows Explorer and click
autorun.exe.
Click on the Install Data Protector selection to start the installation.
If you do not install from the DVD directly but have the product software on some
installation folder, for example on a network share, then navigate to that folder
and select folder WINDOWS_OTHER. Then choose the i386, x8664 or the
IA64 folder as appropriate according to the platform on which you are installing
and run the setup.exe installer program.
The Data Protector Setup Wizard window will come up.
CM INSTALLATION ON WINDOWS 1/3

1.
• Welcome screen
1.
2. 3. 2.
• license agreement
3.
• installation type
4.
• user credentials
5.
• installation directories
4. 5.
Cell Manager installation on Windows 1/3

The installation wizard guides you thru the following windows:
1. The first windows is a welcome screen, click Next
The Advanced options.. button allows to change the following
behavior:
2. Read and accept the License Agreement. Click Next.

3. The Installation Type windows allows to start three different types of
clients:
• Cell Manager
Installs the Cell Manager including the default agents DA,
MA, CC, the Learning Products and the Installation Server.
The component selection can be changed on one of the next

windows.
• Installation Server
Installs a Windows stand alone Installation Server that is used
by a Cell Manager (that runs for example on HP-UX) to
remotely install DP clients on Windows.
• Data Protector client
This is the selection for the local client installation. This is for
example used to install the DP client software cluster aware,
as this cannot be achieved via the remote push installation.
For cluster installation see the HP Data Protector MS Cluster
integration training for Support and Services.
4. Provide the username and password for the account under which the
Data Protector services CRS (Cell Request Server) and UIPROXY (User
Interface Proxy for Java) will run. The services Inet and RDS will always
be started under the local system account. The processes MMD and
KMS process are started by the CRS and takes over the user
credentials.
5. This window allows changing the default install folder.

6.
• Component Selection
6.
• Firewall Configuration
7.
• Lists the configuration and

8. • Starts the installation
By default Installation
Server will be installed
together with CM
7. 8.

6. In the Component Selection page, the components that should be
installed can be selected. For a list and descriptions of all components,
see the Data Protector Installation and Licensing Guide.
Disk Agent, General Media Agent, User Interface, Documentation
(English) and Installation Server are selected by default.
7. If Data Protector detects a Windows Firewall on your system, the
Windows Firewall configuration page is displayed. By default, the
option Initially, enable newly registered Data Protector binaries to
open ports as needed is selected and Data Protector executables are
registered for the inbound rules (see screenshot below). If you do not
want to enable Data Protector to open ports at the moment, deselect
the option. However, note that for proper functioning of Data
Protector, the executables must be enabled.
Note that only inbound firewall rules are automatically created and
outbound firewall rules, if required, have to be created manually. See
also the online help index firewall support.
8. On this screen, the component summary list is displayed. Check your
selection. Going back allows changing the list of agents that are
supposed to be installed. Clicking Install starts the installation of the
selected components. This may take several minutes.
Inbound rules created during the DP Cell Manager installation:

9.
9.
• Progress Update
10.
• Installation Result
11.
• End Message
10. 11.
Installation Status Page

9. While the installation is running Data Protector shows a progress
update and is mentioning the current installation operation.
10. At the end of the installation a status page is shown. Check whether it
shows any irregularities. During the installation, a number of Data
Protector registry entries were added to the Windows registry, and
Data Protector services are configured and started:
• Cell Request Server - CRS
• Raima Database Server - RDS
• Data Protector omniinet
• Data Protector UIProxy
For a detailed description of these services see chapter Windows
Services on page 29
In addition to these Windows services there are two application
processes started on a Windows Cell Manager:
• Media Management Daemon – MMD
• Key Management Server - KMS
11. The Setup Wizard enables you to install or upgrade the HP AutoPass
utility if you want to download and install passwords for the purchased
licenses directly through the internet from the HP password delivery
center web server. For more information on the AutoPass utility, refer to
the Data Protector Installation and Licensing Guide.
By default, the Start AutoPass installation or the Upgrade AutoPass

installation option is selected. It is recommended to install the HP
AutoPass utility. If you do not want to install or upgrade AutoPass,
deselect the option. On Windows Server 2003 x64, Windows Vista
x64, and Windows Server 2008 x64 systems, HP AutoPass is not
supported. To start using Data Protector immediately after setup, select
Start the Data Protector Manager. To view the HP Data Protector
Product Announcements, Software Notes, and References, select
Open the Product Announcements.
IS INSTALLATION ON WINDOWS
Install Cell Manager and Installation Server •Welcome screen
1.
•license agreement
– If only the Installation Server (IS) should be 2.
installed 3. •installation type

3.
• similar wizard as for
•user credentials
CM installation 4.
• example use case: •installation directories
5.
Cell Manager (with IS)
exists on Unix and an •firewall configuration
6.
IS is required for the
remote installation of •List the configuration and
7. •Starts the installation
windows clients
10.
8. •Installation Result
7.
•End Message
9.
•Import the IS on the CM

10.
Installation Server (IS) installation on Windows

The installation of an Installation Server on Windows is similar to the installation
of a Cell Manager; actually some of the windows used by the installation
wizard are the same. This slide only indicates the windows that are different:
• Step 3
When selecting the installation type the option Installation Server must be
selected. If the system should be used besides the Installation Server also
as DP client (for example files should be backed up) then the option
Client must be selected that allows also to select the Installation Server as
a component.
• Step 7
This windows lists all components that are going to be installed, in case
of an Installation Server installation only the Installation Server and Core
component will be installed.
• Step9
After the installation is completed the Installation Server must be imported
into the cell. This must be done within the Clients context as indicated in
the screenshot above.
IMPORTANT:
If you do not install the Installation Server for Windows on your network, you will
have to install every Windows client locally from the DVD-ROM.
Limitation
Due to the security restrictions imposed by the Windows operating system,
Installation Server can be used to remotely install clients only in the same
domain.
WINDOWS SERVICES / PROCESSES

Windows description
services
CRS The Cell Request Server (CRS) service starts and controls backup and
restore sessions in the cell.
RDS The Raima Database Server (RDS) service manages the IDB.
Inet The Data Protector client service that enables the Cell Manager to start
agents on other systems.
UIProxy The Data Protector Java GUI Server (UIProxy service) is responsible for
communication between the Java GUI Client and the Cell Manager.
Windows description
processes
MMD The Media Management Daemon (MMD) service manages the device
and media management operations.
KMS The Data Protector Key Management Server (KMS) service provides key
management for the Data Protector encryption functionality.
Windows Services
A successful Cell Manager installation on Windows configures and starts the
following Windows Services:
• crs.exe
The Data Protector Cell Request Server (CRS) service runs on the Cell
Manager system and is started when the Cell Manager software is installed
on the system. The CRS starts and controls backup and restore sessions in
the cell. It runs in the DP_Home\bin directory.
• rds.exe
The Data Protector Raima Database Server (RDS) service runs on the Cell
on the system. The RDS manages the IDB. It runs in the DP_Home\bin
directory.
• omniinet.exe
The Data Protector client service that enables the Cell Manager to start
agents on other systems. The Data Protector Inet service must run on all
systems in the Data Protector cell. It runs in the DP_Home\bin directory.
• uiproxy.exe
The Data Protector Java GUI Server (UIProxy service) runs on the Cell
Manager system in the DP_Home\java\server\bin directory. The UIProxy
service is responsible for communication between the Java GUI Client and
the Cell Manager.
Besides these four Windows Services there are two processes that are also
permanent up and running:
• mmd.exe
The Data Protector Media Management Daemon (MMD) process runs on
the Cell Manager system and is started when the Cell Manager software is
installed on the system. The MMD manages the device and media
management operations. It runs in the DP_Home\bin directory.
• kms.exe
The Data Protector Key Management Server (KMS) process runs on the Cell
on the system. The KMS provides key management for the Data Protector
encryption functionality. It runs in the DP_Home\bin directory.
You can check the status of these services with the Control Panel. They should be
set to start automatically. You may also use the $DP_HOME\bin\omnisv –status
command to verify their status.
Example:
C:\Users\administrator.TIC>omnisv -status
ProcName Status [PID]
===============================
rds : Active [5224]
crs : Active [1564]
mmd : Active [6764]
kms : Active [7108]
uiproxy : Active [8892]
omniinet: Active [848]
Sending of traps disabled.
===============================
Status: All Data Protector relevant processes/services up and
running.
PREPARATION ON UNIX
Logon as root
Verify that sufficient disk space is available
inetd or xinetd daemon up and running
Make sure the Cell Manager (and Installation Server) have static IP addresses.
Verify that port number 5555 is free on all systems in the cell
(and 5556 for Java GUI installation)
Verify that host name resolution is enabled (DNS)
Install HP Data Protector from DVD
Installation on Unix
There are three Unix flavors on which the Data Protector Cell Manager (and
Installation Server) is supported: HP-UX, Solaris and Linux.
To install a Unix Cell Manager on these platforms, root permissions are required.
The system that will become your Cell Manager must meet the following
requirements:
• Sufficient disk space for the Data Protector software and for the IDB (about
2% of the planned data to be backed up). Refer to the HP Data Protector
Product Announcements, Software Notes, and References for details. Note
that the current IDB design allows the database binary files to be relocated if
growth in database size makes it necessary. See the online Help index:
“IDB, calculating the size of”.
To overcome a shortage of space linked directories can be used. Refer to

the chapter The installed directory structure on HP-UX, Solaris, and Linux o
and Allocating more disk space for the Cell Manager installation on within
the Data Protector Installation and Licensing Guide.
• Have the inetd or xinetd daemon up and running. Please check the
paragraph Error! Reference source not found. further down for detailed
information.
• Have a static IP address for the system on which the Cell Manager will be
installed.
• Have the port number 5555 (default) free. If this is not the case, refer to
Changing the Data Protector default port number within the Data Protector
Installation and Licensing Guide. See also the chapter Error! Reference
source not found. on page Error! Bookmark not defined..
• Have the port number 5556 free to install Java GUI Server or Java GUI
Client.
• Have the TCP/IP protocol installed and running. The protocol must be able
to resolve hostnames.
• Support long filenames. To find out if your filesystem supports long filenames
use the getconf NAME_MAX directory command.
• It is recommended to use Large file support (LFS). The recommendation
applies to the file systems which hold an internal database, including DC
binary files that are expected to grow larger than 2 GB.
• For the Java GUI Client, a supported version of Java runtime environment is
required. See the HP Data Protector Product Announcements, Software
Notes, and References or the latest support matrices at
http://www.hp.com/support/
Setting kernel parameters

On HP-UX, it is recommended to set the kernel parameter maxdsiz (Max Data
Segment Size) or maxdsiz_64 (for 64bit systems) to at least 134217728 bytes
(128 MB), and the kernel parameter semmnu (Number of Semaphore Undo
Structures) to at least 256. After committing these changes, recompile the kernel
and reboot the machine. On Solaris, it is recommended to set the kernel
parameter shmsys:shminfo_shmmax (maximum shared memory segment size
(SHMMAX)) in /etc/system to at least 67108864 bytes (64 MB). After
committing this change, reboot the machine.
OMNISETUP.SH
– Omnisetup.sh is used to install Cell Manager and Installation Server on all

Unix platforms
• HP-UX, Solaris and Linux
– can also to be used for local client installation on most supported

platforms
– synopsis
omnisetup.sh [-source directory] [-server name] [-CM] [-IS]
[-install Component_list] [-autopass]
– Examples
• installs a Cell Manager and Installation Server on Linux:
omnisetup.sh -source /DP62/linux_x86_64/dp_depot/ -CM -IS
The omnisetup.sh command

The omnisetup.sh is a shell script used to install or upgrade a Data Protector
UNIX Cell Manager, Installation Server, or client systems locally. The script is
located on the UNIX product media for HP-UX, Linux or Solaris, inside the
subdirectory LOCAL_INSTALL.
The usage of the script is very similar for all UNIX servers. Please check the
Appendix for a description of the omnisetup.sh command.
Adding DP user manually

The installation of a Cell Manager adds the user under which the installation
was executed to the user list, hence allows this user to connect to the Cell
Manager. If a connection from another DP GUI client should be possible, such a
user must be specified before. This can be done with the CLI utility omniusers:
/opt/omni/bin/omniusers
Usage synopsis:
omniusers -version | -help
omniusers -add -type {U | W} -usergroup DPUserGroup -name
UserName
-group GroupOrDomainName -client ClientName
[-desc Description]
omniusers -remove -name UserName -group GroupOrDomainName
-client ClientName
omniusers –list
Example: Adding the user Administrator of the system tpc101 to the admin
group:
/opt/omni/bin/omniusers -add -type W -usergroup admin -name

administrator -group TIC -client tpc101
User 'ADMINISTRATOR' successfully added to 'admin' group.
The installed directory structure on UNIX

The following list is an excerpt of the most interesting Data Protector installation
directories on a Cell Manger:
/opt/omni/bin All commands
/opt/omni/lbin Data Protector internal commands
/opt/omni/sbin Superuser commands
/opt/omni/lib Shared libraries for compression, data
encoding, and device handling
/opt/omni/lib/nls/C Message catalog files
/opt/omni/lib/man Man pages
/opt/omni/help/C Online Help files
/opt/omni/doc/C Guides in the electronic PDF format
/opt/omni/databases Installation Server packets
/etc/opt/omni/IS Installation Server configuration information

/etc/opt/omni/server Cell Manager configuration information
/etc/opt/omni/server/datalists
filesystem backup specifications
/etc/opt/omni/server/barlists
integration backup specifications
/etc/opt/omni/server/cell Cell layout information
/etc/opt/omni/client Client configuration information
/var/opt/omni/log Log files

/var/opt/omni/tmp Temporary files
/var/opt/omni/server/log Log files

/var/opt/omni/server/db40 Internal Database (IDB) files
/opt/omni/java/server Directory containing Java GUI Server

executables
/opt/omni/java/client Directory containing Java GUI Client
executables
UNIX SERVICES
name location description
CRS /opt/omni/ The Cell Request Server (CRS) service starts and controls
lbin/crs backup and restore sessions in the cell.
RDS /opt/omni/ The Raima Database Server (RDS) service manages the IDB
lbin/rds
Inet /opt/omni/ The Data Protector client service that enables the Cell
lbin/inetd Manager to start agents on other systems. Is started by
(x)initd on demand.
UIProxy /opt/omni/ The Data Protector Java GUI Server (UIProxy service) is
java/serve responsible for communication between the Java GUI Client
r/bin/uipr and the Cell Manager.
oxyd
MMD /opt/omni/ The Media Management Daemon (MMD) service manages
lbin/mmd the device and media management operations.
KMS /opt/omni/ The Data Protector Key Management Server (KMS) service
lbin/kms provides key management for the Data Protector encryption
21 ©2011 HP Restricted functionality.
Unix Services
When the installation is finished, the following processes are running on the Cell
Manager:
• Data Protector Cell Request Server (CRS)
This service runs on the Cell Manager system and is started when the Cell
Manager software is installed on the system. The CRS starts and controls
backup and restore sessions in the cell. The binary is located under
/opt/omni/lbin/crs.
• Data Protector Raima Database Server (RDS)
This service runs on the Cell Manager system and is started when the Cell
Manager software is installed on the system. The RDS manages the IDB and
is located under /opt/omni/lbin/rds.
• Data Protector Media Management Daemon (MMD)
This service runs on the Cell Manager and is started when the Cell
Manager software is installed on the system. The MMD manages the device
and media management operations and is located under
/opt/omni/lbin/mmd.
• Inet service
The Data Protector resident service that allows communication with Data
Protector services on other systems on the network. The Inet service must run
on all systems in the Data Protector cell and is located under
/opt/omni/lbin/inetd.
• Data Protector Key Management Server (KMS)
Manager software is installed on the system. The KMS provides key
management for the Data Protector encryption functionality and is located

under /opt/omni/lbin/kms.
• Data Protector Java GUI Server (UIProxy service)
Manager software is installed on the system. The UIProxy service is
responsible for communication between the Java GUI Client and the Cell
Manager and is located under/opt/omni/java/server/bin/uiproxyd.
Data Protector configures during the installation the required files in order to ensure
that these processes are started, whenever the system is booted (inside
/sbin/init.d). Please check the Data Protector Installation and Licensing Guide for
detailed description.
./omnisv -status
ProcName Status [PID]
===============================
rds : Active [19979]
crs : Active [19994]
mmd : Active [19992]
kms : Active [19993]
omnitrig: Active
uiproxy : Active [19998]
Sending of traps disabled.
===============================
Status: All Data Protector relevant processes/services up and
running.
Note that the omnitrig is a process that is started by cron (daemon to execute
scheduled commands).
Example (Linux):
# crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Fri Nov 11 17:37:49 2011)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
# omnitrig entry was automatically added by
0,15,30,45 * * * * /opt/omni/sbin/omnitrig
CLIENT
INSTALLATION
DP 6.2 Installation
and Services
Client Installation
CLIENT INSTALLATION OVERVIEW

Client Installation
– clients can be installed locally or remotely using the push mechanism of

the Installation Server
• local installation
− available for all supported client platforms
• remote installation (using the push mechanism of the Installation Server)

− available for: Windows, HP-UX, Solaris, Linux, MacOS, AIX, Tru64, SCO, DAS Client, ACS Client
– remote installation
• to a Unix system
− requires at least one Installation Server either on HP-UX, Solaris, or Linux
− methods: secure shell (recommended), rsh and rexec
• to a Windows system
− requires at least one Installation Server on Windows
− requires certain firewall configuration on the client
• see slide Windows firewall - Push Installation
• not supported on
− Windows XP Home Edition, Novell NetWare, and HP OpenVMS clients
Client Installation Overview

After the Cell Manager and Installation Server (optionally but strongly
recommend) is installed, it is time to install the Data Protector agent software on
all systems that should be backed up. Those systems become then DP clients
belonging to this cell. The installation can be performed via two mechanisms:
• Local installation
With a local installation it is required to log into the system and start the
installation on the corresponding system. A local installation is available for
all supported platforms.
• Remote installation
The Installation Server (IS) offers the possibility to push the software to the
corresponding systems. There are two different Installation Servers, one for
Windows and one for Unix. That means that if the software has to be
pushed to Windows and Unix clients, both Installation Servers must be
installed.
The remote installation is not available for all platforms. It can be used for
Windows, HP-UX, Solaris, Linux, MacOS, AIX, Tru64, SCO, DAS Client,
ACS Client. On certain platform there are also some requirements to be
considered. They are explained in detail in the following slides. Remote
installation is not possible for Windows XP Home Edition, Novell NetWare,
and HP OpenVMS clients. These have to be installed locally.
REMOTE PUSH INSTALLATION 1/3

Client Installation
1.
2.
define which Installation
Server platform should
be used
3.
• select Add Clients

1.
• select the target platform

2.
4.
• select the Installation
3. Server
• press Next
4.
Remote Push Installation 1/3

If a new Data Protector client should be added to the cell, Data Protector agents
software must be installed for the first time on that system. This can be achieved
vi a local installation or via a remote pushing mechanism offered by the
Installation Server. This and the following slides show how the remote push
mechanism works.
1. Start the Data Protector GUI (on any system) and right mouse click
Clients within the Clients context
2. Select the correct platform of the remote system (either Windows or Unix)
3. Select the Installation Server that should be used for the installation. Note
that only those Installation Servers are listed that belong to the platform
as selected during step 2.
4. Select Next.

Client Installation •specify system
name
5.
5. 6. •press Add
6.
•select all required

when pressing Add DP components
7.
checks whether the
name can be resolved
•press Finish
8.
7.
8.

5. Enter the remote system on which the Data Protector software should
be installed. It is also possible to browse or search for the client
system:
6. Press the Add button. Data Protector checks whether the name can be
resolved, hence Data Protector detects typos. In case of resolve issues
DP pops the window:
7. Select which Data Protector component or agent software should be

installed. For some dedicated components, like MS SharePoint
Granular Recovery Extension, it is required to specify dedicated user
credentials. If more than one client is selected and it is required to
install different components on each client, select the option I want to
customize these options for client systems independently.
Example:
8. Press Finish to start the installation.

Client Installation
9.
10.
• Session starts
9.
• if required DP asks for

10. user credentials
• Installation finishes
11.

9. The session starts and lists all important operation in the session output
window.
10. Data Protector tries to connect to the system and requests for user
credentials if required.
11. The installation continues and installs all selected components on the
system.
Example session output:

[Normal] Starting installation session on Tuesday, November 15,
2011, 10:16:31 AM...
[Normal] Getting list of clients for installation...
[Normal] Done.
[Normal] Expanding and checking clients to be installed...
[Normal] Connecting to client vmw39150.tic.dp...
[Normal] Done.
[Normal] Installing the Data Protector bootstrap service on

client vmw39150.tic.dp...
[Normal] Starting installation on client vmw39150.tic.dp at

Tuesday, November 15, 2011, 10:16:35 AM...
[Normal] <vmw39150.tic.dp> Installing Core...
[Normal] <vmw39150.tic.dp> Installation of Core succeeded.
[Normal] <vmw39150.tic.dp> Installing User Interface...
[Normal] <vmw39150.tic.dp> Installation of User Interface

succeeded.
[Normal] <vmw39150.tic.dp> Installing Disk Agent...
[Normal] <vmw39150.tic.dp> Installation of Disk Agent succeeded.
[Normal] <vmw39150.tic.dp> Installing General Media Agent...
[Normal] <vmw39150.tic.dp> Installation of General Media Agent

succeeded.
[Normal] Importing client vmw39150.tic.dp to Cell Manager

vmw39151.tic.dp configuration...
[Normal] Import successful.
[Normal] Installation session finished on Tuesday, November 15,

2011, 10:17:51 AM.
==================================================================
Session completed successfully!
==================================================================
The client is also imported automatically into the Cell:
WINDOWS FIREWALL - PUSH INSTALLATION

Client Installation
– push installation requires certain firewall configurations

• port 5555 must be enabled
• outbound connections are allowed
– for local installation no manual firewall configuration are necessary

• DP is doing necessary changes on its own
− see slides Local Client installation - Windows
Windows Firewall
If the firewall is enabled on the remote system the firewall must be configured
such as
• port 5555 is enabled
• Outbound connections are allowed
Enabling Data Protector port 5555
The port 5555 must be opened for incoming connections:
Within the Firewall with Advanced Security utility right mouse click Inbound Rules
and select New Rule …
Within the next window specify Port, press Next
Specify 5555, press Next
TCP is enough, UDP is not necessary.
Specify Allow the connection, press Next
and continue and save the rule.
Check that outbound connections are allowed

Run firewall properties (right click on Windows Firewall with Advanced Security
on the left) and verify that Inbound connections are blocked (default) and
Outbound connections are allowed (default):
If the firewall configuration is not configured correctly the push installation might
fail with the following messages:
[Critical] [110:1022] Cannot connect to the SCM (Service Control

Manager) on client vmw39150.tic.dp:
[5] Access is denied.
[Normal] Starting installation on client vmw39150.tic.dp at

Tuesday, November 15, 2011, 11:50:10 AM...
[Critical] [110:1025] Cannot connect the Data Protector bootstrap

service on client vmw39150.tic.dp:
IPC Cannot Connect
System error: [10060] Connection timed out
[Normal] Installation session finished on Tuesday, November 15,

2011, 11:52:20 AM.
In case the Cell Manager is Windows 2003 and the clients 2008 the user that
starts remote installation must have Administrator privileges on remote host and
the Remote Administration (NP-In) inbound rule must be enabled on the remote
system.
Inbound rules created by Data Protector

Note that the rule for port 5555 is only required for the push installation. The
installation will create for all required Data Protector binaries a corresponding
inbound rule: Hence after the installation the rule for port 5555 can be removed
again.
PUSH INSTALLATION WITH SECURE SHELL

Client Installation
– push installation on Unix can be perform using secure shell (SSH)

• omnirc variable OB2_SSH_ENABLED must be set on the Installation Server
• if secure shell is not available the legacy Unix tools rsh and rexec are used
• secure shell protocol ensures that data including password/passphrase is send encrypted
over the network
• based on public-private keys
– if configured correctly no password must be specified

– secure shell installation is supported only on Unix systems only
Push Installation with Secure Shell

For security reasons, it is recommended to use secure shell for the Data Protector
remote installation. If secure shell is not available, the legacy UNIX tools rsh and
rexec are automatically used by the Data Protector remote installation.
To use secure shell, install and set up OpenSSH on both, the client and
installation Server. If your private key is encrypted, install and set up keychain on
the Installation Server.
Secure shell installation helps you to protect your client and Installation Server by
installing Data Protector components in a secure way. High level of protection is
achieved by:
• Authenticating the Installation Server user to the client in a secure way
through the public-private key pair mechanism.
• Sending encrypted installation packages over the network.
NOTE: Secure shell installation is supported on UNIX systems only and requires
the omnirc variable OB2_SSH_ENABLED set on the Installation Server:
# OB2_SSH_ENABLED=0|1
# Default: 0
# Allows SSH protocol to be used for remote installation of DP agents.
# This secures the remote connections while distributing the agents.
# Set this variable on Installation Server host. Applicable only on UNIX
# platforms.
For a detailed description how to configure and use the Secure Shell for the push
installation see the Installation and Licensing manual.
LOCAL CLIENT INSTALLATION - WINDOWS

Client Installation • Welcome screen
1.
1.
2.
2.
• License agreement
3.
3.
• Choose Installation type
4.
• Specify Cell Manager
5.
• Installation directories
4.
5.
Local Client Installation – Windows 1/2

The installation of a client is started like the installation of the Cell Manager.
Either by using the DVD_ROM, that will open the HP Data Protector software
6.2 installation splash screen, or by starting the setup.exe within the appropriate
folder (i386, x8664 or the IA64).
In both ways the installation wizard is started:

1. The first window is a welcome screen, click Next
2. Read and accept the License Agreement. Click Next.
3. The Installation Type windows allows to start the installation of:
• Cell Manager
• Data Protector client
• Installation Server
Select the second option Client. This is for example used to install the DP
client software cluster aware, as this cannot be achieved via the remote
push installation. For cluster installation see the HP Data Protector MS
Cluster integration training for Support and Services.
4. Provide, if available, the name of the Cell Manager. If specified the
client will be after a successful installation automatically imported to
this cell.
With the button Check response… it is possible to verify whether the
cell manager can be reached from this client system.
Example where the Cell Manager could not be reached:
Example where the Cell Manager could be reached:
5. This window allows changing the default install folder.
LOCAL CLIENT INSTALLATION - WINDOWS

Client Installation • Component Selection
6.
6.
7.
• Firewall Configuration
8.
• Lists the configuration and starts the installation
Installation Server 9.
• Installation result status
can be added as
component
10.
• Setup complete message
8.
7.
9.
Local Client Installation – Windows 2/2

6. In the Component Selection page, the components that should be
installed can be selected. For a list and descriptions of the Data
Protector components, see the Data Protector Installation and Licensing
Guide. Disk Agent, General Media Agent, User Interface, and
Documentation (English) are selected by default.
It is also possible to add the Installation Server as component. If added
the system will also be acting as Installation Server.
7. If Data Protector detects a Windows Firewall on your system, the
Windows Firewall configuration page is displayed. Data Protector setup
can register all necessary Data Protector executables. By default, the
selected option is Initially, enable newly registered Data Protector
binaries to open ports as needed. If you do not want to enable Data
Protector to open ports at the moment, deselect the option. For a list of
all rules see chapter Inbound rules created by Data Protector on page
47. However, note that for proper functioning of Data Protector, the
executables must be enabled.
Note that only inbound firewall rules are automatically created and you
must manually create any outbound firewall rules. For the required port
ranges, see the online help index firewall support.
8. On this screen, the component summary list is displayed. Check your
selection. Going back allows changing the list of agents that are
supposed to be installed. Clicking Install starts the installation of the
selected components. This may take several minutes.
9. After the installation has finished it shows the result.
10. Setup complete window appears.
LOCAL CLIENT INSTALLATION - UNIX

Client Installation
– the OMNISETUP.SH command can be used to install DP clients locally on

Unix and MAC OS clients locally
– SYNOPSIS
omnisetup.sh [-source directory] [-server name]
[-install component-list] [-IS] [-CM] [-autopass] [-noautopass]
• source directory: directory that holds the package
– Examples
• install the component Disk Agent (DA), Media Agent (MA), User Interface (CC), and English
Documentation (docs)
omnisetup.sh –server vmw39151.tic.dp –install DA,MA,CC,Docs
– Native OS installation tools can be used instead

• HP-UX – swinstall; Linux – rpm; Solaris – pkgadd,
• require several additional manual steps
Local Client Installation – Unix

Omnisetup.sh
If there is no Installation Server for UNIX installed within the network, or if for
some reasons the remote push installation does not work, Data Protector clients
can be installed locally with the installation DVD-ROM.
Follow the procedure below to install UNIX and Mac OS X clients locally:
1. Insert and mount the HP-UX, or Solaris and Linux installation DVD-ROM.
Note that the DVD-ROM filesystem uses the Rock Ridge extensions.
2. From the Mount_Point/LOCAL_INSTALL directory run the omnisetup.sh
command. The syntax of the command is as follows:
omnisetup.sh [-source directory] [-server name] [-
install component_list]
where:
o directory is the location where the installation DVD-ROM is mounted.
If not specified, the current directory is used.
o 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. This must be done manually, see
chapter Importing Clients on page 66.
o 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.
For further details see Installation and Licensing manual.
Notive OS installation tools

The clients on the systems HP-UX, Solaris, and Linux can be installed also using
the native tools (swinstall, pkgadd, and rmp). Please refer to the Installation and
Licensing manual for more details.
xinetd handling
The (x)inetd is a Unix daemon that listens on the network sockets to start
processes - such as omniinet, telnet, rexec, rsh, etc. - when a request for the
respective process on the associated port number comes in. The assignment of
port numbers to processes is configured in /etc/inetd.conf and /etc/services.
When the remote shell (rsh) is used for connections between clients, then the
(x)inetd is always running. If secure shell (ssh) protocol is used, then (x)inetd is not
necessarily running, but must be explicitly started by the administrator.
In earlier versions of Data Protector there was no check whether (x)inetd was
running or not. Consequently the installation process failed if it did not run. With
DP 6.2, the installation process now verifies the status of (x)inetd on the client
before it starts the remote installation:
• if the remote shell (rexec, omniinet) is used to connect to the client, then it is
implicit that the (x)inetd is running.
• if the secure shell (ssh) is used, then DP checks if (x)inetd is running.
If it is running, the remote installation continues.
• If (x)inetd is not running, then DP checks whether it is installed.
If it is not installed, then the DP installation aborts with the error message:
[Critical] <HOSTNAME> Required (x)inetd/inetd service is
not present on client system...
• If (x)inetd is installed, but not running, then for security reasons DP checks the
output of command /sbin/chkconfig to ensure that (x)inetd will not start any
other services except omniinet.
• If (x)inetd will start no other service than omniinet, then DP now starts (x)inetd
and also ensures it will be restarted on reboot in future.
Otherwise the DP installation aborts with the error message:
[Critical] <HOSTNAME> Required (x)inetd/inetd service is
not running on client system...
Port 5555 handling

On Suse Linux systems the /etc/services file per default contains an entry for
port number 5555 which is however not used. During installation, DP adds its
own entry for port 5555 to /etc/services. Thus there are now two entries for
5555 in /etc/services.
Prior to version 6.2, inetd(x) could pick the wrong 5555 port number when DP
pushed the binaries to the remote clients, which resulted in a corrupted DP
installation on the client.
In some cases the installation could not be repeated unless broken DP

components were removed manually from the client system.
DP version 6.2 uses the netstat command to ensure that the port is actually being
listened to.
• If the port is available for DP:DP proceeds with the installation
o adds the entry for Data Protector into the etc/services file (this step is
needed for other applications that may potentially use etc/services
for determining port availability)
• If the port is in use for another application:
o DP displays an appropriate error message
o discontinues installation
LOCAL CLIENT INSTALLATION - OTHERS

Client Installation
– there are OS platforms that are not supported by omnisetup, like

• Novell NetWare
− Installation is performed through a Windows system connected to the Novell network
• HP OpenVMS
− special installation via a PCSI installation file
Local Client Installation Others

Installation of the OpenVMS Client
The installation procedure of the OpenVMS client has to be performed on the
OpenVMS system. You can install the Data Protector Disk Agent, Media Agent,
and CLI Interface on systems running OpenVMS/Alpha. The product is called
Data Protector (DP), but the files and directories placed on the disk are named
OMNI*. This is historical due to the name change from Omniback to Data
Protector.
Before you install Data Protector on the OpenVMS platform, check the following:
• Make sure that TCP/IP is configured and is running.
• Set the TIMEZONE features of your system by executing
SYS$MANAGER:UTC$TIME_SETUP.COM.
• Log into the SYSTEM account of the OpenVMS system.
• Make sure that you have access to the OpenVMS client installation kit.
For additional details, see the Installation and Licensing manual.
Installing Netware Clients

The installation procedure of the Novell NetWare clients has to be performed
from a supported Windows system that is connected to the Novell network. The
Data Protector Disk Agent and the Media Agent can be installed on the systems
running Novell NetWare 6.5
There are many pre-requisites that must be satisfied before starting the
installation; see the HP Data Protector Installation and Licensing Guide for more
details and configuration steps to backup the NDS database.
The installation procedure can be performed from the Data Protector Windows
DVD. To install Data Protector to a Novell NetWare server, proceed as follows:
1. Run a command prompt on a Windows system and change the current path
to the DVD root directory, then to the NetWare sub-directory.
2. Run the installation script:
NWInstall <target server name> <NetWare version> <ALL|DA|MA>
<port_number>
Where the second parameter is the Novell NetWare target server version.
The third parameter defines which part of the Data Protector Novell Client will
be installed:
• Type ALL to install the whole Data Protector Novell NetWare client
functionality.
• Type DA to install only the Data Protector Disk Agent for Novell NetWare.
• Type MA to install only the Data Protector Media Agent for Novell
NetWare.
• The port number is optional, and will default to 5555 if not specified.
The NWInstall script will transfer the packet to the target server Novell Netware
system and perform the installation there.
MAINTENANCE
DP 6.2 Installation
and Services
Maintenance
PATCHES 1/2
Maintenance
– patches exists for existing Data Protector components (like DA, MA,
etc.), core modules and Cell Manager (also called Cell Server)
– all patches except for the Cell Server are installed
1. on the Installation Server
2. distributed to all clients via the Upgrade
functionality
– Cell Server patch

• is installed on the Cell Manager system only
– in general each patch exists for each Installation Server platform

• 4 different OS platform: Windows (DPWIN_XXXXX), HP-UX IA/PA (PHSS_XXXXX),
Solaris (DPSOL_XXXXX), Linux (DPLNX_XXXXX)
− even so the patches contains the same fixes, the numbers are different
− Windows patch contains fixes for all Windows systems
− Unix patches contains fixes for all Unix clients and MAC OS
Patches 1/2
The concept of Installation Server as explained earlier within an Data Protector cell
provides a single point where software packets can be found and redistributed to
clients within a cell.
All patches – except the Cell Server patch - need to be installed on the Installation
Server only, using the OS depending tool (swinstall on HP-UX, patchadd on Solaris,
rpm on Linux). Once all patches have been installed on the Installation Server, they
can be remotely pushed and distributed to all the DP clients via the Upgrade
functionality.
This is in general the recommended procedure; however with Add Components it is

also possible to update the software on each DP client. This method might be faster
as it only updates the existing component instead of the complete DP client
software, when performing an Upgrade Clients.
Whenever the client software is updated it is recommended to have no backup or

restore session (or any other type) running.
If the Installation Server is running together with the Cell Manager on the same
system, then it is important to know that there is a difference between
• Unix
The Cell Manager system must be upgraded like all other client systems,
once the patches were installed on the Installation System.
• Windows
When installing the patches on the Installation System they are immediately
applied to the Cell Manager. Therefore the Upgrade button is grayed out.
A Cell Server patch, that contains only fixes for the Cell Manager, has to be
installed only on the Cell Manager. Hence there is no use to install it on an Install
Server.
Note that on UNIX it is required to stop the DP services manually before the patch
installation on a CM can be started; on Windows the patch installation ensures this
automatically (services are stopped at the beginning of the patch installation and
started again at the end).
If there is no Installation Server available, the patches must be installed locally on

the systems. For the platforms that are supported for the Cell Manager (Windows,
HP-UX, Solaris, and Linux) the local installation is documented. This is not true for
local patch installation on other platforms. If this is required, please contact DP
support for some assistance.
Please note that each patch exists for each Installation Server. Where the Windows
patch includes fixes for the Windows platform, each UNIX patch (HP-UX, Solaris,
and Linux) contains fixes for all UNIX platforms, hence the content of the UNIX
patches are the same. Therefore only two Installation Servers are necessary in order
to install the patches on all Windows and UNIX clients. For example a HP-UX
Installation server can be used to patch all Unix clients and others (HP-UX, Solaris,
Linux, MAC OS, …), see Client Installation Overview on page 38.
With DP 6.2 the patches are released for four different OS platforms, as listed
within the slide above. In older versions there were 5, as for HP-UX there were two,
one for Intanium (IA) one for PA-Risc.
Example patches for DP 6.11 (different patches for HP-UX Itanium and PA-Risc):
Patch Name Description OS Date released
DPLNX_00161 Linux - Core patch intelLinux 10/17/2011
DPSOL_00455 Solaris - Core patch sparcSOL 10/17/2011
DPWIN_00521 Windows - CORE patch windows 10/17/2011
PHSS_42168 HP-UX PA-Risc - Core patch s700,s800 10/17/2011
PHSS_42169 HP-UX IA64 - Core patch s700,s800 10/17/2011
DPLNX_00167 Linux - Disk Agent patch intelLinux 10/17/2011

DPSOL_00461 Solaris - Disk Agent patch sparcSOL 10/17/2011
DPWIN_00526 Windows -Disk Agent patch windows 10/17/2011
PHSS_42492 HP-UX PA-Risc - Disk Agent s700,s800 10/17/2011
patch
PHSS_42493 HP-UX IA64 - Disk Agent s700,s800 10/17/2011
patch
DPLNX_00163 Linux - Cell Server patch intelLinux 10/17/2011

DPSOL_00457 Solaris - Cell Server patch sparcSOL 10/17/2011
DPWIN_00522 Windows - Cell Server patch windows 10/17/2011
PHSS_42287 HP-UX PA-Risc - Cell Server s700,s800 10/17/2011
patch
PHSS_42288 HP-UX IA64 - Cell Server s700,s800 10/17/2011
patch
From Data Protector 6.2 on there is only one patch for HP-UX, covering both PA-
Risc and Itanium. Hence the patches taken from the example above are called in
DP 6.2:
• HP-UX IA/PA Disk Agent
• HP-UX IA/PA Cell Server patch
• HP-UX IA/PA Core patch
PATCHES 2/2
Maintenance
– DP patches are cumulative

• latest version of patches does not require any older patches
• patch with a higher number supersedes those with a lower one
– some DP patches are dependent on each user

• most component patches have dependency on the core patch
• read always the patch description for
potential other dependencies
– installed patches are listed

within the DP GUI
go to the Clients context
right mouse click the client system and
select Properties
select Patches
Patches 2/2
Data Protector patches are always cumulative, hence the latest version supersedes
always all patches that might have been already released. Please note that some
patches are dependent on each other; please refer always the patch description.
To check which patches are installed on which system, select the appropriate client
within the Clients context and press Patches. This will pop up a window listing all
patches (see above a screenshot example).
EX- AND IMPORT OF CLIENTS

Maintenance
– a DP client can belong only to one Cell Manager

– DP clients can be exported and imported into another Cell
• export
− no software is uninstalled on the client system
− DP client is taken out of a Cell, hence the internal database (IDB) removes its references to this client
− check that all the occurrences of the client have been removed from backup specification or backup devices
• import
− DP client is taken into a Cell
– import and export concept is also available for

• pure Installation Server
(no DP client
software installed)
• MS cluster system
Ex – and import of clients

Export
Exporting a client from a Data Protector cell means removing its references from
the internal database (IDB) on the Cell Manager without uninstalling the software
from the client. This can be done using the Data Protector GUI and will be
explained in the following slide.
The export functionality is needed in the following cases:

• The client should be moved to another cell (A client can only be a member
of one cell, therefore it must be first exported before it can be imported into
the other cell).
• To remove a client from the Data Protector cell configuration which is no
longer part of the network.
• Allows to fix insufficient licenses issues. By exporting a client from a cell, the
license becomes available to some other systems.
Before a client is exported it must be ensured that

• All the occurrences of the client have been removed from backup
specifications. Otherwise, Data Protector will try to back up unknown clients
and this part of the backup specification will fail.
• The client does not have any connected and configured backup devices.
Once the system is exported, Data Protector can no longer use its backup
devices in the original cell.
Import
Some of the clients, such as Novell NetWare, HP OpenVMS, and Windows XP
Home Edition, must be imported to the cell after the installation. Importing means
manually adding a computer to a cell after the Data Protector software has been
installed. When added to a Data Protector cell, the system becomes a Data
Protector client.
Once the system is a member of the cell, information about the new client is
written to the internal database (IDB), which is located on the Cell Manager.
Installation Server & MS Cluster

The import and export concept is also available for dedicated Installation
Servers, which are systems that do not have any DP client software installed and
are only used as the software deposit for software installation. Note that in
contrast to normal clients, Installation Servers can be imported into different cells.
It is also possible to import the MS cluster environment. If the virtual cluster name
is imported, Data Protector imports all virtual cluster applications that are running
on this MS cluster.
EXPORT OF CLIENTS
Maintenance
1. • select Clients context
1.
2.
• right mouse click the
2. client
• select Delete
3.
• select No
3. 4.
4.
Export of clients
This slide describes how to export clients:
1. In the Context List, click Clients.
2. In the Scoping Pane, click Clients, right-click the client system that you
want to export, and
3. then click Delete.
4. You will be asked if you want to uninstall Data Protector software as
well. Click No. The client will be removed from the list in the Results
Area.
The export can also be performed using the CLI utility omnicc. Please check the
Command Line Interface Reference manual for a detailed description.
• select Clients context

IMPORT OF CLIENTS 1.
Maintenance • select Import Clients

1. 2.
• specify the system name

2. 3.
• select Finish
4.
3.
4.
Importing Clients
This slide describes how to import clients:
2. In the Scoping Pane, right-click Clients, and select Import Client.
3. Specify the fully qualified domain name (FQDN) of the system that
should be imported..
4. Press Finish.
The import can also be performed using the CLI utility omnicc. Please check
the Command Line Interface Reference manual for a detailed description.
ADDING COMPONENTS TO CLIENTS

Maintenance 1.
• select Clients context
2.
• select Add Component
1.
3.
• add if required additional clients
2.
4.
• select the component
5.
• select Finish
4.
3.
5.
Adding Components to clients

Adding components to existing Data Protector client(s) systems is done by the
following tasks:
2. In the Scoping Pane, click Clients, right-click the appropriate client, and
click Add Components.
3. This wizard allows you to add additional clients, on which the
components should be installed. This allows to add several components
on several client systems within one operation.
4. Select the component(s) that should be added.
5. Press Finish.
UNINSTALLATION
Maintenance
– uninstallation removes the DP software from the system

• by default it leaves the configuration data on the system
– uninstall can be started via the DP GUI or locally using the specific OS
software installation tool:
uninstallation locally via OS remotely via the

specific software DP GUI
installation tools
single component(s) √
DP clients √ √
DP Cell Manager (CM) √
and/or Installation Server (IS)
Uninstallation
Uninstalling is removing all the Data Protector software components from the
system, including all references to this system from the IDB on the Cell Manager
computer. However, by default, the Data Protector configuration data remains
on the system. If you want to remove the configuration data after uninstalling the
Data Protector software, delete the directories where Data Protector was
installed.
Before starting the uninstallation of a DP client system, the following two items
have to be checked:
• Make sure that all references to the computer are removed from the backup
specifications. Otherwise, Data Protector will try to back up unknown
systems and this part of the backup specification will fail.
• Make sure that no backup devices are connected and configured on the
system that you want to uninstall. Once the system is exported, Data
Protector can no longer use its backup devices in the original cell.
The uninstallation of a DP client system can be performed remotely using the DP

GUI or locally using the OS specific software installation tools. The uninstallation
of single component(s) or of the Cell Manager (CM)/Installation Server (IS) can
only be done using the OS specific software installation tools.
UNINSTALLATION USING DP GUI

Maintenance
1. • select Clients context
1.
2.
• right mouse click the
2. client
• select Delete
3.
• select Yes
3. 4.
4.
Uninstallation of DP clients using the DP GUI

This slide describes how to uninstall clients:
2. In the Scoping Pane, click Clients, right-click the client system on which
you want to remove the Data Protector software, and
3. then click Delete.
4. You will be asked if you want to uninstall Data Protector software as
well. Click Yes. The client will be removed from the list in the Results
Area.
Note that the Data Protector configuration data remains on the client system. If
you want to remove the configuration data, delete the directories where Data
Protector was installed.
LOCAL UNINSTALLATION
Maintenance
– works only with the OS software installation tools

• HP-UX: swremove
• Solaris : pkgrm
• Linux : rpm
• Windows: uninstall/change a program
– by default the configuration data is left on the system

• including IDB, Java GUI
Local Uninstallation
When it comes to a local uninstallation of Data Protector the OS specific software
installation tools have to be used. The slide lists an overview for all of the operating
systems that are supported by the Cell Manager (CM).
If you leave the Data Protector configuration data on the system after the
uninstallation, and you later install an earlier version of the Data Protector Cell
Manager than the uninstalled version was, note that the configuration data will be
unusable. To completely uninstall Data Protector from a system, all remaining Data
Protector directories must be removed. See the Installation and Licensing manual for
further details.
LOCAL UNINSTALLATION: WINDOWS

Maintenance 1.
• select HP Data Protector
• select Change
2.
• select Remove
2. 3.
• select option to delete configuration

1. 4. data (if needed)
• select Remove
5.
3.
4.
5.
Local Uninstallation: windows

To uninstall Data Protector locally from a Windows system the Program and
Features tool must be started:
 Control Panel
 Programs
 Uninstall a program
Note this explanation refers to Windows 2008 R2.
The following steps are required:

1. Select HP Data Protector
2. Select Change
It is also possible to select Uninstall, but that wizard does not expose the
option to permanently delete all configuration data.
3. Select Remove
With option Modify it is possible to add or remove single components
on the DP client system.
4. Select the option Permanently delete configuration data if required. By
default this option is not selected and hence the uninstallation leaves the
configuration data on the system.
5. Press Remove to start the uninstallation.
UPGRADE
Maintenance
– the installation checks whether the system already hosts a Data Protector
version and performs automatically an upgrade
– the upgrade sequence is
1. Cell Manager
2. Installation Servers
3. GUI clients
cell is useable after these four steps
4. application integration clients
5. Media Agent clients
can be done at a later time
6. Disk Agent clients
– the client can be upgraded via the Upgrade feature

• like patch installation
The Upgrade Procedure

The steps to install a fresh Data Protector version and the steps to upgrade an
existing cell are pretty similar. In both cases one inserts the Installation Media for
the new version - the product DVDs - in a drive or the electronic media in a
virtual drive (network share or whatsoever) and run the setup.exe command on
Windows or omnisetup.sh command on Unix/Linux systems. The process usually
starts with the Cell Manager.
Upgrade Cell Manager and Installation Server
In case of an upgrade, one inserts the Installation Media and runs the setup.exe
or omnisetup.sh command the same way as for a fresh installation, starting with
the existing Cell Manager.
Data Protector will detect that there is a previous version installed and will
display a message similar to:
"Setup has found Data Protector 06.10.0611 on your computer.
To upgrade it to Data Protector 06.20.0252, click Next"
Click Next, DP will report that there exists already an Internal Database and
configuration data on the system. It will ask you to either keep these items or to
create them from scratch. Of course during a normal upgrade procedure one
must select to keep the database and configuration.
The upgrade process will then proceed. If the DP setup finds an Installation
Server on the system it will upgrade it too.
Upgrade using omnisetup.sh

In case of upgrading the clients that do not reside on the Cell Manager, 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.
However, to upgrade the client components residing on the Cell Manager, run
the omnisetup.sh command with the -install component_list parameter after the
Cell Manager upgrade has been completed.
UPGRADE/MIGRATION PATHS - WINDOWS

upgrade
Upgrade/Migration Paths - Windows

This slide shows the dependencies between the current supported versions of Data
Protector on the two HW platforms, 32bit and 64-bit, and the Windows versions
supported on the DP Cell Manager.
The green arrows show the direct upgrade paths from an older Data Protector
version to a newer one.
The orange arrows (from left to right) show the various migration paths. This could
be either migration to another Windows release or a platform change, or both.
On Windows platforms, if an upgrade of both the OS and Data Protector is

planned, then first upgrade the Windows version - followed by the Data Protector
version. The reason is that DP may provide different versions of a certain binary for
different versions of Windows. The DP installation procedure picks up the
appropriate binary during installation. If you then upgrade the Windows OS
afterwards, you might end up with the wrong DP binary.
UPGRADE/MIGRATION PATHS – HP-UX

upgrade
migration
Upgrade/Migration Paths - HP-UX

The slide above shows the supported upgrade and migration paths from HP Data
Protector Cell Manager 6.0 and 6.1x to HP Data Protector Cell Manager 6.2.
Supported direct upgrade paths on
• PA-RISC platforms are from DP CM 6.0 and 6.1x to DP CM 6.2
• Itanium platforms with HP-UX 11.23 from DP 6.0 and 6.1x to DP 6.2
A platform change from PA-RISC to Itanium is possible with omnimigrate. For details
about the migration refer to the Installation and Licensing manual.
Appendix
Omnisetup.sh description
NAME
omnisetup.sh - installs or upgrades a Data Protector UNIX Cell
Manager, Installation Server, and client system locally, or Mac OS
X
client system locally
(this command is available on the Data Protector
installation DVD-ROMs
for UNIX systems)
SYNOPSIS
omnisetup.sh -version | -help
omnisetup.sh [-source directory] [-server name] [-install

Component_list] [-CM] [-IS] [-autopass]
Component_list
cc = User Interface
javagui = Java GUI Client (contains the Cell Manager

graphical
user interface and the Manager-of-Managers (MoM)
graphical user interface)
da = Disk Agent
ndmp = NDMP Media Agent
ma = General Media Agent
sap = SAP R/3 Integration
sapdb = SAP DB Integration
emc = EMC Symmetrix Agent
oracle = Oracle Integration
sybase = Sybase Integration
ssea = HP StorageWorks P9000 XP Agent
informix = Informix Integration
ov = HP Network Node Manager Integration
lotus = Lotus Integration
db2 = DB2 Integration
smisa = HP StorageWorks P6000 EVA SMI-S Agent
vls_am = VLS Automigration
vmware = VMware Integration
docs = English Documentation (Guides, Help)
jpn_ls = Japanese Documentation (Guides, Help)
fra_ls = French Documentation (Guides, Help)
chs_ls = Simplified Chinese Documentation (Guides, Help)
DESCRIPTION
The command first checks if Data Protector is already installed on
the system.
NEW INSTALLATION OR RE-INSTALLATION OF THE SAME VERSION OF DATA

PROTECTOR
If Data Protector is not installed, then the command, depending on

the selected options, installs the Cell Manager, Installation
Server, or every Data Protector software component specified with
the –install option. If none of these options are specified, the
command issues a prompt for every Data Protector software
component supported on the current system OS. Using this prompt,
software components supported on the current system OS can be
confirmed or rejected for installation, or the execution of the
command can be canceled. There is no such prompt if the -install
option is specified.
UPGRADE FROM AN EARLIER VERSION OF DATA PROTECTOR
To upgrade your cell from the earlier versions of the product to

Data Protector 6.20, proceed as follows:
+ Upgrade the Cell Manager
+ Upgrade the Installation Server
+ Upgrade the clients
To upgrade the all Data Protector components on the system, run

omnisetup.sh without options. If the Installation Server is
installed together with the Cell Manager, or if it is installed
without client components, it is upgraded automatically during the
Cell Manager upgrade.
If the Installation Server is installed with the client

components, it is removed during the Cell Manager upgrade. In this
case, a new Installation Server must be installed using the -IS
option, after the upgrade finishes.
To add a client to the Cell Manager, specify the -install option.

If the client not residing on the Cell Manager is to be upgraded,
the -install option does not need to be specified. In this case,

the setup selects the same components as were installed on the
system before the upgrade without issuing a prompt.
In all cases (new installation, re-installation or upgrade), the

following applies when using this command:
+ When using the -install option, the software components not

supported on the current system OS and mistyped software
components are skipped.
+ On the Cell Manager only, when the installation or upgrade is

started, you are prompted to install the HP AutoPass utility
(unless the -autopass option is specified - if it is, the HP
AutoPass utility is installed or upgraded without issuing a
prompt). If AutoPass is already installed on the system, it is
automatically upgraded, if the prompt is confirmed. When Data
Protector is uninstalled from the system, the HP AutoPass utility
is neither unregistered nor uninstalled. It must be uninstalled
using UNIX utilities, for example sd.
If the HP AutoPass utility is installed in a cluster environment,

it must be installed on every node in the cluster.
+ After the client (re-)installation or upgrade is finished, the

system is imported to a Data Protector cell if the -server option
was set, or if the /etc/opt/omni/client/cell_server (HP-UX,
Solaris, and Linux clients) or the
/usr/omni/config/cell/cell_server (other UNIX clients and Mac OS X
clients) file exists on the system.
+ The first time any software component is selected for

installation or reinstallation, the core component is
automatically installed (or reinstalled). Similarly, the first
time any integration software component is selected for
installation or reinstallation, the core-integ component is
automatically installed (or reinstalled).
-version
Displays the version of the omnisetup.sh command.
-help
Displays the usage synopsis for the omnisetup.sh
command.
-source directory
Sets the location of the Data Protector installation
files (DVD-ROM mountpoint). If this option is not specified, the
current directory is set as the location of Data Protector
installationfiles.
-server name
Sets the hostname of the Cell Manager of the cell to
which the installed or upgraded client is to be imported after the
installation or upgrade . If this option is not specified, andthe
/etc/opt/omni/client/cell_server (HP-UX, Solaris, and Linux
clients) or the /usr/omni/config/cell_server (other UNIX clients

and Mac OS X clients) file does not exist on the system, the
installed or upgraded client is not imported to any cell and has
to be imported manually.
-install Component_list
Sets Data Protector software components that you want to install
or upgrade on the current system. If more than one software
component is to be installed or upgraded, a listing of software
components, delimited by comma (without spaces) must be entered as
the argument. If this option is not specified (except for the case
when the client not residing on the Cell Manager needs to be
upgraded), the command issues a prompt for every Data Protector
software component supported on the current system OS; prompting
whether to install or upgrade certain Data Protector software
component or not. If the client is to be upgraded, this option
does not need to be specified. In this case, the setup selects the
same components as were installed on the system before the upgrade
without issuing a prompt.
-CM Installs/upgrades the Data Protector Cell Manager.
-IS Installs/upgrades the Data Protector Installation Server with

all remote installation packages.
Note that the Installation Server can be upgraded only after the
Cell Manager in the Data Protector cell is upgraded.
-autopass
If this option is specified, the HP AutoPass utility is
automatically installed. If AutoPass is already installed on the
system, it is automatically upgraded. This option is to be used
only on the Cell Manager.
Note that AutoPass is not available on Linux.
NOTES
This command requires that the
+ Data Protector UNIX installation DVD is mounted on the system.
+ DP_DEPOT and LOCAL_INSTALL folders are copied to the disk.
Before running the command make sure that no Data Protector

backups or restores are running on the system. The command must be
executed using the default POSIX kshor pdksh (on Linux) shell.
On MC/ServiceGuard, the HP AutoPass utility must be installed an

all nodes.
EXAMPLES
1. To upgrade a system, run:
omnisetup.sh
2. To install or re-install the General Media Agent, Disk Agent,

SMI-S Agent, and SAP R/3 Integration software components, run:
omnisetup.sh -install ma,da,smisa,sap
3. To install the Cell Manager and Installation Server together

with the HP AutoPass utility, insert and mount the UNIX
installation DVD and run the following command from the
LOCAL_INSTALL directory:
omnisetup.sh -CM -IS -autopass
SEE ALSO
ob2install(1M), omnigui(5), omniintro(9), omnimigrate.pl(1M),
omniusers(1), upgrade_cm_from_evaa(1M), winomnimigrate.pl(1M)
Installation examples
Example for a Cell Manager installation on HP-UX
# ./omnisetup.sh -source /dvdrom/DP62MR/hpux -CM
No Data Protector software detected on the target system.
Do you wish to start AutoPass installation? (Y/n)

n
Installing Data Protector A.06.20 Cell Manager...

======= 11/01/11 13:32:47 MET BEGIN swinstall SESSION
(non-interactive) (jobid=hpu077-0175)
* Session started for user "root@hpu077".

* Beginning Selection
* Target connection succeeded for "hpu077:/".
* Source connection succeeded for
"hpu077:/dvdrom/DP62MR/hpux/DP_DEPOT".
* Source: /dvdrom/DP62MR/hpux/DP_DEPOT
* Targets: hpu077:/
* Software selections:
+ B6960MA,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP
DATA-PROTECTOR.OMNI-CC,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.20,fa
DATA-PROTECTOR.OMNI-CORE,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.20,
DATA-PROTECTOR.OMNI-CS,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.20,fa
DATA-PROTECTOR.OMNI-DA,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.20,fa
DATA-PROTECTOR.OMNI-DOCS,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.20,
DATA-PROTECTOR.OMNI-JAVAGUI,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.
DATA-PROTECTOR.OMNI-MA,r=A.06.20,a=HP-UX_B.11.11_32/64,v=HP,fr=A.06.20,fa
* A "+" indicates an automatic selection due to dependency or
the automatic selection of a patch or reference bundle.
* Selection succeeded.
* Beginning Analysis and Execution

* Session selections have been saved in the file
"/.root/.sw/sessions/swinstall.last".
* "hpu077:/": There will be no attempt to mount filesystems
that appear in the filesystem table.
* The execution phase succeeded for "hpu077:/".
* Analysis and Execution succeeded.
NOTE: More information may be found in the agent logfile using the
command "swjob -a log hpu077-0175 @ hpu077:/".
======= 11/01/11 13:37:08 MET END swinstall SESSION (non-interactive)

(jobid=hpu077-0175)
Installation/Upgrade session finished.
You can see from the software selections, that the DATA-PROTECTOR.OMNI-
CS fileset is installed, which contains the Cell Manager binaries.
In addition, DA, MA, CC client components and DOCs are automatically
installed on the Cell Manager.
The omnisetup.sh command internally uses the operating system's native
installation tools. In case of HP-UX this is the swinstall command. The swinstall
command is responsible for putting the binaries, libraries and other files that are
contained in the filesets from the product media into the final installation
locations on the system:
• /opt/omni
• /var/opt/omni
• /etc/opt/omni
Example for a local client installation on HP-UX

During a local client installation, the omnisetup.sh script scans through the list of
available components which are supported on the client. For each component
that can be installed on the client, it checks whether the component name is
specified in the list following the -install parameter. The supported components
will then be installed.
If the -install parameter is not specified, and no DP component is installed yet,
then the user is prompted for each component, similar to the following:
Install (da) Disk Agent (YES, no, quit)?
Default answer is YES for da, generic ma, and cc components, and NO for any
other component – all subject to the support availability of the component on the
host.
YES Install this component
No Do not install this component
Quit quit the omnisetup.sh script
Once any one component is installed on a client, omnisetup.sh will not again
ask for each available component, but expects the –install option with the list of
component s to install.
# ./omnisetup.sh -source /dvdrom/DP62MR/hpux
Install (cc) User Interface (yes/NO/Quit)?

y
Install (da) Disk Agent (YES/no/Quit)?
y
Install (ma) Media Agent (YES/no/Quit)?
y
Install (javagui) Java User Interface (yes/NO/Quit)?
n
Install (docs) English Documentation (Guides, Help) (yes/NO/Quit)?
n
Install (jpn_ls) Japanese Documentation (Guides, Help) (yes/NO/Quit)?
n
Install (fra_ls) French Documentation (Guides, Help) (yes/NO/Quit)?
n
Install (chs_ls) Chinese Documentation (Guides, Help) (yes/NO/Quit)?
n
Install (oracle8) Oracle Integration (yes/NO/Quit)?
n
Install (sap) SAP R/3 Integration (yes/NO/Quit)?
n
Install (sapdb) SAP DB Integration (yes/NO/Quit)?
n
Install (emc) EMC Symmetrix Agent (yes/NO/Quit)?
n
Install (informix) Informix Integration (yes/NO/Quit)?
n
Install (ssea) HP StorageWorks Disk Array XP Agent (yes/NO/Quit)?
n
Install (sybase) Sybase Integration (yes/NO/Quit)?
n
Install (db2) IBM DB2 Integration (yes/NO/Quit)?
n
Install (ov) HP OpenView NNM Backup Integration (yes/NO/Quit)?
n
Install (vls_am) VLS Automigration (yes/NO/Quit)?
n
Install (smisa) HP StorageWorks EVA SMI-S Agent (yes/NO/Quit)?
n
Packets going to be (re)installed: omnicf cc da ma
Installing Core (omnicf)...

Installing User Interface (cc)...
Installing Disk Agent (da)...
Installing Media Agent (ma)...
Client was not imported into the cell.

Please perform the Import manually
Example for a Cell Manager and Installation Server installation on Linux
vmw37038:~/hr/DP62/LOCAL_INSTALL # ./omnisetup.sh -source

/root/hr/DP62/linux_x86_64/dp_depot -CM -IS
The omnisetup.sh script didn't finish last time

Cell Manager still has to be installed
Installation Server still has to be installed
The omnisetup.sh script can now continue the unfinished

installation
or it can ignore the saved state and start a new one.
If you choose to ignore, the script will erase the saved state
and will process only the command line options
Do you want to continue the unfinished installation? (Y/n)
n
Ignoring saved state...
Installing Data Protector A.06.20 Cell Manager and Installation

Server...
Installing OB2-CORE packet

Preparing...
########################################### [100%]
1:OB2-CORE
########################################### [100%]
Installing OB2-CC packet

Preparing...
########################################### [100%]
1:OB2-CC
########################################### [100%]
manpath: warning: $MANPATH set, ignoring /etc/manpath.config
Installing OB2-CS packet

Preparing...
########################################### [100%]
1:OB2-CS
########################################### [100%]
NOTE: No Data Protector A.06.20 database found.
NOTE: Data Protector A.06.20 database initialized.
DONE!
CRS started successfully.

NOTE: Checking licences.
Installing OB2-DA packet

Preparing...
########################################### [100%]
1:OB2-DA
########################################### [100%]
Installing OB2-MA packet

Preparing...
########################################### [100%]
1:OB2-MA
########################################### [100%]
Installing OB2-DOCS packet

Preparing...
########################################### [100%]
1:OB2-DOCS
########################################### [100%]
Installing OB2-JAVAGUI packet

Preparing...
########################################### [100%]
1:OB2-JAVAGUI
########################################### [100%]
Installing OB2-CORE-IS packet

Preparing...
########################################### [100%]
1:OB2-CORE-IS
########################################### [100%]
Installing OB2-CFP packet

Preparing...
########################################### [100%]
1:OB2-CFP
########################################### [100%]
Installing OB2-DAP packet

Preparing...
########################################### [100%]
1:OB2-DAP
########################################### [100%]
Installing OB2-MAP packet

Preparing...
########################################### [100%]
1:OB2-MAP
########################################### [100%]
Installing OB2-CCP packet

Preparing...
########################################### [100%]
1:OB2-CCP
########################################### [100%]
Installing OB2-INTEGP packet

Preparing...
########################################### [100%]
1:OB2-INTEGP
########################################### [100%]
Installing OB2-JPNP packet

Preparing...
########################################### [100%]
1:OB2-JPNP
########################################### [100%]
Installing OB2-FRAP packet

Preparing...
########################################### [100%]
1:OB2-FRAP
########################################### [100%]
Installing OB2-OR8P packet

Preparing...
########################################### [100%]
1:OB2-OR8P
########################################### [100%]
Installing OB2-SAPP packet

Preparing...
########################################### [100%]
1:OB2-SAPP
########################################### [100%]
Installing OB2-EMCP packet

Preparing...
########################################### [100%]
1:OB2-EMCP
########################################### [100%]
Installing OB2-INFP packet

Preparing...
########################################### [100%]
1:OB2-INFP
########################################### [100%]
Installing OB2-LOTP packet

Preparing...
########################################### [100%]
1:OB2-LOTP
########################################### [100%]
Installing OB2-NDMPP packet

Preparing...
########################################### [100%]
1:OB2-NDMPP
########################################### [100%]
Installing OB2-OVP packet

Preparing...
########################################### [100%]
1:OB2-OVP
########################################### [100%]
Installing OB2-SAPDBP packet

Preparing...
########################################### [100%]
1:OB2-SAPDBP
########################################### [100%]
Installing OB2-AUTODRP packet

Preparing...
########################################### [100%]
1:OB2-AUTODRP
########################################### [100%]
Installing OB2-SSEAP packet

Preparing...
########################################### [100%]
1:OB2-SSEAP
########################################### [100%]
Installing OB2-SYBP packet

Preparing...
########################################### [100%]
1:OB2-SYBP
########################################### [100%]
Installing OB2-DB2P packet

Preparing...
########################################### [100%]
1:OB2-DB2P
########################################### [100%]
Installing OB2-JGUIP packet

Preparing...
########################################### [100%]
1:OB2-JGUIP
########################################### [100%]
Installing OB2-DOCSP packet

Preparing...
########################################### [100%]
1:OB2-DOCSP
########################################### [100%]
Installing OB2-VMWP packet

Preparing...
########################################### [100%]
1:OB2-VMWP
########################################### [100%]
Installing OB2-VEPAP packet

Preparing...
########################################### [100%]
1:OB2-VEPAP
########################################### [100%]
Installing OB2-PEGP packet

Preparing...
########################################### [100%]
1:OB2-PEGP
########################################### [100%]
Installing OB2-SMISAP packet

Preparing...
########################################### [100%]
1:OB2-SMISAP
########################################### [100%]
Installing OB2-VLSAMP packet

Preparing...
########################################### [100%]
1:OB2-VLSAMP
########################################### [100%]
Installing OB2-CHSP packet

Preparing...
########################################### [100%]
1:OB2-CHSP
########################################### [100%]
HP Data Protector services successfully stopped.
HP Data Protector services successfully started.

2 - 1 DP - Install - L300

Uploaded by

Document Information

Original Title

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

2 - 1 DP - Install - L300

Uploaded by

Copyright:

Available Formats

HP Data Protector 6.

HP Data Protector 6.2 software

Date: December 15, 2011

Restricted Rights Legend

Logical Example path Explanation

$DP_HOME C:\Program Files\Omniback DP Home directory on all Windows

/opt/omni DP Home directory on HP-UX, Linux and

$DP_CONFIG C:\Program Files DP configuration directory on

C:\ProgramData DP configuration directory on

/etc/opt/omni/server/ DP configuration directory on HP-UX,

$DP_VAR C:\Program Files\Omniback DP Internal Database, Log and

C:\ProgramData\Omniback DP Internal Database, Log and

/var/opt/omni DP Internal Database, Log and

xinetd handling ................................................................................ 54

OVERALL INSTALLATION SEQUENCE

Check hardware and software requirements

Cell Manager Installation

Installation Server Installation

add clients / add components on existing clients

Upgrade to a new version / patch installation

Overall Installation Sequence

PLAN THE LAYOUT

Plan the layout of the cell

– which platforms will be backed up?

EXAMPLE OF A DATA PROTECTOR CELL

– Cell Manager (CM) including Installation Server (IS) on Windows

HP--UX Windows Windows HP--UX

Windows CM (IS) Windows Unix/Linux

Solaris AIX Linux Windows

Example of a heterogeneous Data Protector Cell

Hardware and Software requirements check

WINDOWS INSTALLATION REQUIREMENTS

• Windows XP Pro 32-bit

Windows Installation Requirements

UNIX INSTALLATION REQUIREMENTS

• HP-UX 11.11, 11.23, 11.31 on PA-Risc and IA

Installation Requirements – Unix

PRODUCT MEDIA / DVD CONTENTS

Product Media / DVD Contents

Electronic Delivery Program

Cell Manager (CM) and Installation Server (IS) Installation

Logon as Domain Administrator

Verify that Microsoft TCP/IP is installed and running

Verify that host name resolution is enabled (DNS)

Verify that sufficient disk space is available for IDB growth on CM

Install HP Data Protector from DVD

Install Cell Manager on Windows

INSTALLATION WIZARD ON WINDOWS

– insert product DVD

– select Install Data Protector

The Installation on Windows

The Data Protector Setup Wizard window will come up.

CM INSTALLATION ON WINDOWS 1/3

Cell Manager installation on Windows 1/3

2. Read and accept the License Agreement. Click Next.

The component selection can be changed on one of the next

CM INSTALLATION ON WINDOWS 2/3

• Lists the configuration and

Cell Manager installation on Windows 2/3

Inbound rules created during the DP Cell Manager installation:

CM INSTALLATION ON WINDOWS 3/3

Cell Manager installation on Windows 3/3

Installation Status Page