Pages From DP 9 Installation 2017 03
Pages From DP 9 Installation 2017 03
Pages From DP 9 Installation 2017 03
If you selected more than one client and you want to install different components on each client,
click Specify components for each client individually and then click Next. Select the
components for each client independently.
Click Finish to start the installation.
Note: Windows XP Home Edition and HP OpenVMS clients can be installed locally. Remote
installation is not supported.
Prerequisites
l For system requirements, disk space requirements, supported platforms, processors, and Data
Protector components, see the HPE Data Protector Product Announcements, Software Notes, and
References.
Note: You can also use the following procedure to upgrade the UNIX clients locally. The script will
detect a previous installation and will prompt you to perform the upgrade.
Installation Procedure
To install UNIX and Mac OS X clients locally
1. Insert and mount the UNIX installation DVD-ROM or ISO image (for HP-UX or Linux).
Note that the DVD-ROM filesystem uses the Rock Ridge extensions.
2. From the MountPoint/LOCAL_INSTALL directory execute the omnisetup.sh command.
The syntax of the command is as follows:
omnisetup.sh [-source directory] [-server name] [-install component_list]
where:
l directory is the location where the installation DVD-ROM or ISO image is mounted. If not
specified, the current directory is used.
l name is a full hostname of the Cell Manager of the cell to which you want to import the client. If
not specified, the client will not be automatically imported to the cell.
Note: In case of upgrading the client that resides on the Cell Manager or Installation
Server, you do not need to specify -install component_list. In this case, the setup will
select the same components that were installed on the system before the upgrade without
issuing a prompt.
Note: In case of upgrading the client, the setup will select the same components that were
installed on the system before the upgrade started, without issuing a prompt.
The list of the components is presented in the table below. The exact list of the components is
subject to the availability on the particular system. For the description of the components, see
"Data Protector components" on page 58.
cc User Interface
da Disk Agent
Example
The example below shows how you can install the Disk Agent, General Media Agent, User
Interface, and Informix Integration components on a client that will be automatically
imported to the cell with the Cell Managercomputer.company.com:
./omnisetup.sh -server computer.company.com -installda,ma,cc,informix
3. Setup informs you if the installation was completed and if the client was imported to the Data
Protector cell.
The CORE component is installed the first time any software component is selected for installation.
The CORE-INTEG component is installed the first time any integration software component is
selected for installation or reinstallation.
Note: The Linux depot does not support local installation. You must copy the HP-UX depot, even
on Linux systems.
For example, if you copy installation packages to /var/dp80, the directories must be a subdirectory of
/var/dp62:
# pwd
/var/dp80
# ls
DP_DEPOT
LOCAL_INSTALL
After you have copied this to the hard disk, change to the LOCAL_INSTALL directory and execute the
following command:
omnisetup.sh [-server name] [-install component_list]
For example:
./omnisetup.sh -install da
Note, that if you copied the DP_DEPOT directory to a different directory (for example due to disk space
constraints), the -source option is also required.
Next steps
If you did not specify the name of the Cell Manager during the installation, the client will not be imported
to the cell. In this case, you should import it using the Data Protector graphical user interface. For the
procedure, see "Importing clients to a cell " on page 187. For information on additional configuration
tasks, see the HPE Data Protector Help.
Note: You need special licenses that depend on the number of drives and slots used in the
StorageTek library. For more information, see "Data Protector Licensing" on page 306.