Installing the Linux Client System
The Linux client systems can be installed locally by using the
distribution media, or remotely using the Installation Server for UNIX.
See http://www.openview.com/products/omniback/specifications/ for
details about supported Linux platform versions.
NOTE OmniBack II uses the default port number 5555. Therefore, this
particular port number should not be used by another program. This is
possible on some versions of Linux (such as 6.4). If the port number 5555
is already in use, you should make it available for OmniBack II or you
can change this value to an unused port number. See Appendix B ,
“Changing the Default Port Number,” on page B-11.
Local Installation If you do not have an Installation Server for UNIX installed in your
environment, you have to perform local installation from the distribution
media, that is the OmniBack II CD-ROM for UNIX. See “Local Client
Installation on the non-HP-UX Platforms” on page 87 for instructions.
Remote
Installation
At this point you should have Installation Server for UNIX already
installed on your system. See “Installing the OmniBack II Cell Manager
(CM) and Installation Servers (IS)” on page 16.
You remotely install a Linux client system by distributing the OmniBack
II components from the Installation Server for UNIX to the Linux
system, using the OmniBack II graphical user interface. For the
step-by-step procedure for distributing the software, refer to
“Distributing the OmniBack II Software to Clients” on page 34. Before
that, note which components you select when distributing the OmniBack
II software to the Linux system:
Disk Agent Select the Disk Agent component to be able to back up filesystem data
with OmniBack II.
User Interface Select the User Interface component if you want to have access to the
OmniBack II command-line interface on the client system.
Media Agent The Media Agent component is needed only if the client system has a
backup device connected.
For information on other OmniBack II components, refer to “OmniBack
II Components” on page 38.
As soon as the client components have been installed, the target system
automatically becomes a member of the OmniBack II cell.
Troubleshooting If you run into problems with remote installation on a Linux client
system, ensure that root account has rights to access the system either
by using exec or shell services. To achieve this, do the following:
1. Edit the /etc/xinetd.conf. Find the definitions for exec and shell
services and add the following line to the definition of these two
services:
server_args = -h
For example:
service shell
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/in.rshd
server_args = -L -h
}
service exec
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/in.rexecd
server_args = -h
}
NOTE Some Linux distributions have these services configured in separate files
in /etc/xinetd.d directory. In this case locate the appropriate file
(/etc/xinetd.d/rexec and /etc/xinetd.d/rsh) and modify it as
described above.
2. Kill inetd process with the HUP signal:
kill -HUP $(ps ax|grep inet|grep -v grep|cut -c1-7)
3. Create a ~root/.rhosts file with the entry:
root
That will allow administration access from the Installation Server.
After you have installed OmniBack II, you can remove the entry from
~root/.rhosts file, -h flag from the /etc/inet.conf (/etc/inetd.conf for
RedHat 6.1) file and repeat the kill command from the step 2.
For more information, see rexecd(8), rexec(3), rshd(8), rsh(1) or pam(8)
manpages. If this fails, refer to “Local Client Installation on the
non-HP-UX Platforms” on page 87 for instructions.
What’s Next? Once the installation procedure has been completed and the backup
devices have been properly connected to the Linux client system, refer to
the HP OpenView OmniBack II Administrator’s Guide for information
about configuring backup devices and media pools or other configuration
tasks.
Share with your friends: |