875-1940-10 Veritas NetBackUp PDF
875-1940-10 Veritas NetBackUp PDF
875-1940-10 Veritas NetBackUp PDF
4
Installation Guide
UNIX
June 2000
100-001549
Disclaimer
The information contained in this publication is subject to change without notice. VERITAS Software Corporation
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. VERITAS Software Corporation shall not be liable for errors
contained herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this manual.
Copyright
Copyright 2000 VERITAS Software Corporation. All rights reserved. VERITAS is a registered trademark of
VERITAS Software Corporation. The VERITAS logo, VERITAS NetBackup, and VERITAS NetBackup
BusinesServer are trademarks of VERITAS Software Corporation. All other trademarks or registered trademarks
are the property of their respective owners.
Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright
1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.
Printed in the USA, June 2000.
VERITAS Software Corporation.
1600 Plymouth St.
Mountain View, CA 94043
Phone 650.335.8000
Fax 650.335.8050
http://www.veritas.com
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Type Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Notes and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Key Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Command Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Chapter 1. Installation and Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Installing NetBackup DataCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
What Does the Script Do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
What Should I Do Before I Start the Script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
How to Install NetBackup DataCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Modify Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configure Storage Devices for the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configure NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Install the NetBackup Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Windows 95/98/2000/NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
NetWare Target and Nontarget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
OS/2 Warp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Install Alternative Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
iii
iv
Preface
The purpose of this guide is to help NetBackup system administrators install
NetBackup DataCenter. The NetBackup system administrator is responsible for
maintaining backups and disaster recovery plans using NetBackup.
This guide assumes:
Your SCSI devices are properly attached and configured for the operating system.
Caution If a device is not properly configured for the operating system, backups made to
that device may be difficult to restore.
Organization
Conventions
The following explains typographical and other conventions used in this guide.
Conventions
Type Style
Table 1. Typographic Conventions
Typeface
Usage
Fixed width
Italics
Book titles, new terms, or used for emphasis. For example: Do not ignore cautions.
Placeholder text or variables. For example: Replace filename with the name of your
file.
Graphical user interface (GUI) objects, such as fields, menu choices, etc.
For example: Enter your password in the Password field.
Key Combinations
Some keyboard command sequences use two or more keys at the same time. For example,
you may have to hold down the Ctrl key before you press another key. When this type of
command is referenced, the keys are connected by plus signs. For example:
Press Ctrl+t
Command Usage
The following conventions are frequently used in the synopsis of command usage.
brackets [ ]
The enclosed command line component is optional.
Vertical bar or pipe (|)
Separates optional arguments from which the user can choose. For example, when a
command has the following format:
vi
Getting Help
command arg1|arg2
Getting Help
For updated information about this product, including system requirements, supported
platforms, supported peripherals, and a list of current patches available from Technical
Support, visit our web site:
http://www.veritas.com/
For product assistance, contact VERITAS Customer Support.
US and Canadian Customers: 1-800-342-0652
International Customers: +1 (650) 335-8555
VERITAS Customer Support can also be reached through electronic mail at:
[email protected]
Preface
vii
Getting Help
viii
Configure NetBackup
Adds entries to the /etc/services file for NetBackup and Media Manager services
(for example, robotic daemons). The /etc/services file contains UNIX system
information. The script shows the default port numbers and asks if you want to
change them.
Checks to see if your server is running Network Information System (NIS). NIS is the
UNIX directory service utility. If it is running, you are instructed to add entries to
your NIS services map.
For some peripherals and platforms, kernel reconfiguration is required. See the
NetBackup DataCenter Media Manager System Administrators Guide - UNIX for details.
Adequate disk space to install the software (see the NetBackup Release Notes for
binary sizes).
All NetBackup servers must recognize and be recognized by their client systems. In
some environments, this means that each must be defined in the others /etc/hosts
file. Other environments may use the Network Information Service (NIS) or Domain
Name Service (DNS).
Identify the devices you plan to use in your NetBackup configuration. Ensure that
these devices appear on the list of DataCenter supported devices (included in the
Release Notes).
If you are not adding any NetBackup media servers, ignore all references to them.
On the NetBackup server, the install location contains the software and the
NetBackup catalog and can become quite large.
For the Solaris NetBackup installation, the default location is /opt/openv with a
link to /usr/openv.
For the all other UNIX NetBackup installations, the default location is
/usr/openv.
Because the product uses file locking, VERITAS recommends that you not install
NetBackup in an NFS mounted directory. File locking in NFS mounted file systems
can be unreliable.
For Hewlett Packard servers, install NetBackup on a file system that supports long file
names. Also, install HP-UX 10.x compatibility links.
Where cd_rom_directory is the path to the directory where you can access the
CD-ROM. On some platforms, it may be necessary to mount the directory.
6. Execute the install script:
./install
When the menu appears, choose option 1 (NetBackup). This installs both Media
Manager and NetBackup software on the server.
7. Follow the prompts in the installation scripts.
Note The correct NetBackup client software is automatically installed on the master
server. Do not install additional client software on any media servers.
Note The installation script offers you the option to load onto the server the UNIX client
software for each of the UNIX client types supported by NetBackup. Later you can
push this client software from the server to your UNIX clients.
Be certain to load onto the server the software for all the UNIX client types you
intend to back up. Otherwise, you will not be able to add these UNIX client types to
the NetBackup class configuration.
8. Remove Java files used by platforms for which you have no clients, as follows:
On HP700, HP800, and Solaris servers, NetBackup installation creates some large files
in the /usr/openv/java directory, including:
Solaris_JRE_117B.tar.Z
Solaris_X86_JRE_117B.tar.Z
hp1020_jre116.tar.Z
hp110_jre116.tar.Z
These files are needed for installs on the following NetBackup clients and are used by
the NetBackup Java interface applications on those platforms:
NetBackups Java client GUI runs on the following platforms:
Delete any of the tar files used by platforms for which you have no clients:
Platform/OS
Tar file
SPARC: Solaris
Solaris_JRE_117B.tar.Z
Solaris_X86_JRE_117B.tar.Z
HP-UX 10.20
hp1020_jre116.tar.z
HP-UX 11.0
hp110_jre116.tar.z
Modify Scripts
You may want to create or modify system startup scripts so they start the Media Manager
and NetBackup daemons when the system boots and terminate them at system shutdown.
Always start the Media Manager daemons before the NetBackup daemons.
In your initialization scripts for media servers, start and stop only ltid. Do not start and
stop bprd from media-server initialization scripts.
All server platforms have various scripts in the following directory:
/usr/openv/netbackup/bin/goodies
For DEC Alpha, Solaris 2.x, SGI, NCR, Pyramid and Sequent, the goodies directory
contains the S77netbackup and K77netbackup scripts. S77netbackup starts the
NetBackup and Media Manager daemons and K77netbackup stops the NetBackup
and Media Manager daemons.
For all except DEC Alpha, place these scripts in the servers /etc/rc2.d
(startup) and /etc/rc0.d (shutdown) directories.
For DEC Alpha, place them in the /sbin/rc3.d (startup) and /sbin/rc0.d
(shutdown) directories.
For HP 10.x and HP 11.0, the goodies directory contains the S777netbackup and
K77netbackup scripts. S777netbackup starts the NetBackup and Media
Manager daemons and K77netbackup stops the NetBackup and Media Manager
daemons. Place these scripts in the servers /etc/rc2.d (startup) and /etc/rc0.d
(shutdown) directories.
For Auspex servers, the /etc/rc.local file can be changed by adding lines similar
to those in the example below. In the test environment, these lines were placed after
the test for /etc/exports and before the test for /tftpboot.
if [ -f /usr/openv/volmgr/bin/ltid ]; then
/usr/openv/volmgr/bin/ltid
sleep 2
echo Media Manager daemons have been started. > /dev/console
else
echo Media Manager daemons have not started. > /dev/console
fi
if [ -f /usr/openv/netbackup/bin/initbprd ]; then
/usr/openv/netbackup/bin/initbprd
sleep 2
echo NetBackup request daemon started. > /dev/console
else
echo NetBackup request daemon not started. > /dev/console
fi
For IBM servers, the goodies directory contains the rc.veritas.aix script.
This script starts the Media Manager and NetBackup daemons. Place this script into
the server's /etc directory and call it during the level 2 boot process. Edit the server's
/etc/inittab file and add this line:
veritas:2:wait:/etc/rc.veritas.aix
Call this script after most of the other level 2 inittab entries like rctcpip and
diagd.
Configure NetBackup
After the server software has been installed and storage devices have been configured,
perform the following steps. Refer to the NetBackup DataCenter System Administrators
Guide - UNIX for more information.
1. Configure NetBackup on Each Server
2. Configure Volumes
3. Configure the Catalog Backup
4. Create a Backup Policy
Macintosh
For Macintosh installation instructions, refer to the NetBackup Installation Guide - PC
Clients.
OS/2 Warp
1. Copy PC_Clnt\OS2\nbuos2.exe to a temporary directory on the OS/2 Warp
computer.
2. Execute nbuos2.exe from the temporary directory to extract the installation files.
3. Execute install.exe from the temporary directory to install NetBackup for OS/2.
10
UNIX
To use a UNIX client, the software for that type of UNIX computer must first be loaded
onto your UNIX server. If you did not chose to do this during the installation of your
UNIX server, do so now by following the instructions provided in Add a UNIX Client
Type After Initial Server Installation on page 16.
UNIX clients can be installed in two different ways: either locally at the client computer, or
remotely, from your UNIX NetBackup server.
Locally: You must install the client software locally if remote installation is not
possible. Remote installation is not possible if your NetBackup server is an NT/2000
computer or if there is a firewall that prevents remote installation.
Remotely: You can push the client software from your UNIX NetBackup server to
your UNIX client computers.
On all UNIX clients: the xbp interface. For instructions on the use of xbp, see the
NetBackup Users Guide - UNIX.
11
Where cd_rom_directory is the path to the directory where you can access the
CD-ROM. On some platforms, it may be necessary to mount the directory.
3. Start the install program.
./install
12
13
5. In the Dont install on these clients box, select the clients you want to install and click
the right arrows.
The clients are moved to the Install these clients box.
6. Click the Install Client Software button to start the installation.
Client software installation can take a minute or more per client. NetBackup writes
messages in the Progress box as the installation proceeds. If the installation fails on a
client, NetBackup notifies you but keeps the client in the class. You cannot stop the
installation once it has started.
During installation, NetBackup does the following:
14
Adds the required entries to the clients /etc/services and inetd.conf files.
The only way to install client software to a different location on the client is to create
the directory where you want the software to reside and then create
/usr/openv/netbackup as a link to that directory prior to installing software.
7. When the install is complete, click Close.
Installing NetBackup Software on Secure UNIX Clients
As defined here, a secure UNIX client is one that does not have an entry for the NetBackup
server in its /.rhosts file.
Note Add the secure clients to a backup policy (class), if this has not already been done.
1. Move software from the server to temporary space in the /tmp directory on the client
by executing the install_client_files script from the NetBackup server. To
execute this script, you must have a login ID and password that you can use to access
the clients through ftp.
To move software to only one client at a time, execute:
/usr/openv/netbackup/bin/install_client_files ftp client user
ALL specifies that you want to install all clients which are configured in any
backup policy (class) on the server.
The install_client_files script prompts you for a password for each client if
you do not have a .netrc file set up.
2. After the install_client_files script is done, the root user on each of the clients
must execute the client_config script to complete the installation:
sh /tmp/bp/bin/client_config
The client_config script installs the binaries and updates the /etc/services
and inetd.conf files on the client.
15
Where cd_rom_directory is the path to the directory where you can access the
CD-ROM. On some platforms, it may be necessary to mount the directory.
3. Use the install program to load the client software onto the NetBackup server.
./install
16
UNIX
Windows NT/2000
Windows 98 or Windows
95
17
4. On the NetBackup - Install screen, click the Install option beneath NetBackup Server.
5. Enter the NetBackup base product license key.
For more information on administering NetBackup licenses see the NetBackup
DataCenter System Administrators Guide - UNIX.
6. Click Administration Client.
7. Follow the prompts to complete the installation.
Note On the NetBackup System Names screen, the name of the Administration Client
should be in the first entry field. You must enter the name of the remote NetBackup
DataCenter computer in the Master Server field.
When the software is installed, a set of NetBackup documents are also installed in the
following directory:
install_path\Help
By default, install_path is C:\Program Files\VERITAS.
By default, the Administration Client interface will automatically begin as soon as
you click Finish in the installation program. (If you did not choose that default, go to
the Windows Start menu on the Administration Client computer and select Programs,
VERITAS NetBackup, NetBackup Administration.)
18
2. On the NetBackup - Install screen, click on the Install option beneath NetBackup - Java
Display Console for MS. A welcome dialog box appears.
3. Click Next and follow the prompts to complete the installation.
4. When the software is installed, see the following document for information on using
the display console (this document is installed with the software):
install_path\Java\Readme.txt
Where, by default, install_path is C:\Program Files\VERITAS.
19
20
Requirements
Caution Back up your NetBackup databases before upgrading NetBackup software on
the master server.
As a general rule, ensure that the NetBackup release level on each server is at least
equal to that on the clients. Older versions of server software can encounter problems
with newer clients. Upgrade all servers first so they are at the same level.
You can upgrade to 3.4 only if you currently have NetBackup 3.1.1, 3.2, or 3.3 software
installed.
21
If you have 3.2 or 3.3 clients that are unsupported at 3.4 and encounter problems with
using the new features of 3.4, move those clients to a separate class.
2. On Solaris and HP, stop all instances of the NetBackup Java interface applications.
You can find the process IDs for the NetBackup Java applications by piping the output
of ps into grep.
On Solaris, for example:
If you are upgrading from NetBackup 3.2 or later:
ps -ef | grep jre | grep openv
If you are upgrading from NetBackup 3.1.1, you must first terminate all instances of
web browsers that initiated the NetBackup Java client application:
ps -ef | grep "java jbpMServer" | grep openv
When asked:
Are you doing this pkgrm as a step in an upgrade process?
Answer y.
22
Procedure
As the root user, install the NetBackup server software first on the master server and then
on all remote media servers. The steps for each server are as follows:
1. Check the license keys included with this order to make sure that you have license
keys for all the NetBackup servers, clients, options, and agents that you have ordered.
When installing a NetBackup server, master or media, you must enter a NetBackup
base product license key. On the master server, you must also enter license keys for
any additional NetBackup software product options or agents used on the server or
its clients. For more information on administering NetBackup licenses see the
NetBackup Datacenter System Administrators Guide - UNIX.
2. Log in as the root user on the server.
3. Insert the CD-ROM in the drive.
4. Change your working directory to the CD-ROM directory:
cd cd_rom_directory
Where cd_rom_directory is the path to the directory where you can access the
CD-ROM. On some platforms, it may be necessary to mount the directory.
5. Execute the install script:
./install
6. When the menu appears, choose option 1 (NetBackup). This installs both Media
Manager and NetBackup software on the server.
Option 2 (NetBackup Client Software) is for local installation on UNIX clients (see
Install Client Software Locally on page 11) or for reinstalling client software without
disturbing the NetBackup and Media Manager installation.
7. Follow the prompts in the installation script.
If this is a remote media server, install only the Media Manager and the server
software for NetBackup. The correct NetBackup client software is automatically
installed. Do not install the other client software on a remote media server.
23
Note: On Solaris, if you have done the pkgrm, you will not be prompted to
update your NetBackup clients. Refer to step 8 for information on upgrading
clients after the installation.
Note If your server is not HP or Solaris, you must install client software locally to install
NetBackup Java on HP and Solaris NetBackup clients. NetBackup Java is only
installed and distributed to HP and Solaris NetBackup clients from an HP or Solaris
NetBackup master server.
If you have more than 30 clients to upgrade:
When asked:
Do you want to update the NetBackup software on the clients?
(y/n) [y]
Answer y.
The script proceeds as follows:
Starting update_clients script.
There are N clients to upgrade.
Do you want the bp.conf file on the clients updated to list this
server as the master server? (y/n) [y]
Answer n.
You will need to upgrade clients later with install_client_files
or update_clients -ClientList filename.
The complete list of UNIX clients can be found in
/tmp/NB_CLIENT_LIST.04-29-1533.13195.
You can delete clients and change OS levels. The format of each entry in the file is:
hardware_type os_level client_name
Where hardware_type os_level and client_name are as defined for the clients in
the NetBackup class configuration.
24
For more than 30 clients, you can divide the list into multiple files and execute
update_clients for each file.
You can also upgrade only one client by creating an entry for just that client in the
-ClientList file.
8. If you did not update the NetBackup client software on all currently configured UNIX
client systems when running the installation script, do so now by performing the
following steps as root user on the NetBackup master server.
a. Check whether bprd is running by executing:
/usr/openv/netbackup/bin/bpps
b. If only one bprd shows up in the bpps output, there are no active backups or
restores. You can terminate the bprd daemon by executing:
/usr/openv/netbackup/bin/admincmd/bprdreq -terminate
c. Update UNIX client software by executing the update_clients script with one
of the following commands:
If you are using a -ClientList file (as explained in step 7) execute the following
(all on one line):
/usr/openv/netbackup/bin/update_clients -ClientList file_name
9. After all servers and clients have been updated, start NetBackup and Media Manager
daemons as the root user on the master server by entering the commands:
/usr/openv/volmgr/bin/ltid
/usr/openv/netbackup/bin/initbprd
At this point, UNIX server and UNIX client updates are complete.
25
26
backup_notify
backup_exit_notify
bpps
dbbackup_notify
diskfull_notify
initbpdbm
initbprd
restore_notify
session_notify
session_start_notify
userreq_notify
For example, an upgrade from NetBackup 3.2 to 3.4 would result in changing:
/usr/openv/netbackup/bin/goodies
to
/usr/openv/netbackup/bin/goodies.3.2GA
and changing
/usr/openv/netbackup/bin/initbprd
to
/usr/openv/netbackup/bin/initbprd.3.2GA
3. If you are updating from 3.2 and are going to use the Motif interfaces (xbpadm,
xvmadm and so on), update the 3.2 resource files for these interfaces so they all use
XNB.
To make it easier to configure all of the Motif interfaces to look the same, these
interfaces now use a common resource file named XNB.
Your X interface program searches for the XNB resource file by going through the
paths listed in the XFILESEARCHPATH in your environment. This varies from
operating system to operating system. Often resource files are kept in
/usr/lib/X11/app_defaults. For Solaris CDE environments, the directory
/usr/dt/app_defaults is usually used.
In NetBackup 3.0, the Motif interfaces used the following resource files:
XNB
XBpmon
XBpadm
XVmadm
27
If you changed any of these files to control the look of the NetBackup 3.2 Motif
interfaces, perform the following procedure.
a. Apply those changes to the XNB resource file (located in
/usr/openv/netbackup/bin or /usr/openv/volmgr/bin).
b. Copy XNB into your X resource directory (listed in XFILESEARCHPATH).
c. Remove the old XBpmon, XBpadm, and XVmadm files from
/usr/openv/netbackup/bin, /usr/openv/volmgr/bin, and from your X
resource directory.
4. If this is a master server upgrade installation and the site had previously allowed
nonroot users to administer NetBackup, the default permissions and group on the
newly installed files allow only a root user to perform NetBackup administration.
Refer to Chapter 2 in the NetBackup System Administrators Guide - UNIX to determine
how to restore nonroot administrator capability.
5. If you are going to use the NetBackup Java interfaces, see the NetBackup Release Notes
for configuration information. The online help provides operating instructions.
Note On HP700, HP800, and Solaris servers, NetBackup installation creates some large
files in the /usr/openv/java directory, including: Solaris_JRE_117B.tar.Z,
Solaris_X86_JRE_117B.tar.Z, hp1020_jre116.tar.Z, and
hp110_jre116.tar.Z. These files are needed for installs on Solaris 2.6, 7, 8,
Solaris x86 2.6/7/8, HP 10.20, and HP 11.0 NetBackup clients and used by the
NetBackup Java graphical-user-interface applications on those platforms. Delete
these tar files if you do not have NetBackup clients with these hardware and
operating system combinations.
28
Run the kill command as follows. The process ID is the first number displayed in the
output from the ps comamnd.
kill -1 process ID
The ps command options may vary from one client platform to another.
29
11. Execute the following command to remove the NetBackup-Java application state data
for the root account:
/bin/rm -rf /.nbjava
12. Inform NetBackup-Java users that they can remove their $HOME/.nbjava directory.
The $HOME/.nbjava directory contains application state information (for example,
table column order and size) that is saved when the user exits NetBackup-Java
applications. The uninstall process removes this directory for the root user only.
/usr/openv
-rf *
/
-f /usr/openv
Caution The rm -f /usr/openv command will also de-install your VERITAS Storage
Migrator product and any NetBackup Add-on products installed on this
machine.
30
Additional Files
AIX
/etc/rc.veritas.aix
Alpha
/sbin/rc3.d/S77netbackup
/sbin/rc0.d/K77netbackup
HP
Other servers
/etc/rc2.d/S77netbackup
/etc/rc0.d/K77netbackup
File
NetBackup Entry
AIX
/etc/inittab
/etc/rc.veritas.aix
Auspex
/etc/rc.local
/usr/openv/netbackup/bin/initbprd
/usr/openv/volmgr/bin/ltid
NCR
/etc/inet/inetd.local /usr/openv/netbackup/bin/bpcd
/usr/openv/netbackup/bin/vopied
/usr/openv/netbackup/bin/bpjava-msvc
b. Run the kill command as follows. The process ID is the first number displayed in
the output from the previous comamnd.
kill -1 process ID
The ps command options may vary from one client platform to another.
Chapter 3, Uninstall NetBackup DataCenter and Clients
31
10. Execute the following command to remove the NetBackup-Java application state data
for the root account:
/bin/rm -rf /.nbjava
11. Inform NetBackup-Java users that they can remove their $HOME/.nbjava directory.
The $HOME/.nbjava directory contains application state information (for example,
table column order and size) that is saved when the user exits NetBackup-Java
applications. The uninstall process removes this directory for the root user only.
Macintosh
Novell NetWare
OS/2
/usr/openv
-rf *
/
-f /usr/openv
4. Remove the NetBackup entries in the /etc/inetd.conf file. For NCR this file is
called inetd.local.
5. Execute the following two shell commands to cause inetd to read the updated
inetd.conf (or inetd.local) file.
a. Enter the following.
For most UNIX clients:
ps -ea | grep inetd
b. Run the kill command as follows. The process ID is the first number displayed in
the output from the ps comamnd.
kill -1 process ID
The ps command options may vary from one client platform to another.
6. For Solaris and HP NetBackup clients running NetBackup-Java graphical interfaces,
remove the NetBackup-Java state data by executing the following:
/bin/rm -rf /.nbjava
33
34
Related Documents
This appendix lists and describes the technical manuals that pertain to NetBackup.
The CD-ROM for each NetBackup product has a copy of the related manuals in Adobe
Portable Document Format (PDF). The PDF files are either in the root directory or the
Docs directory on the CD-ROM.
To view the PDF copies of the manuals, you need an Adobe Acrobat reader, which you
can download from the Adobe website at www.adobe.com. VERITAS assumes no
responsibility for the correct installation or use of the reader.
Release Notes
NetBackup Release Notes
Provides important information about NetBackup software, such as the platforms and
operating systems that are supported and operating notes that may not be in the
manuals or the online help.
35
Installation Guides
Installation Guides
36
37
You may also need the following resources from Microsoft Corporation:
Microsoft Exchange Server whitepapers and FAQs (go to
http://www.microsoft.com/exchange and search for "Disaster Recovery")
Microsoft Exchange Administrators Guide
Microsoft Exchange Concepts and Planning Guide
Microsoft TechNet
Microsoft BackOffice Resource Kit
http://www.msexchange.org
38
For this product, you may also need the following manuals from Oracle Corporation:
Oracle7 Enterprise Backup Utility Installation and Configuration Guide
Oracle7 Enterprise Backup Utility Administrators Guide
Oracle7 Server Administrators Guide
Oracle8 Server Backup and Recovery Guide
Oracle8 Server Administrators Guide
NetBackup for Oracle - Advanced BLI Agent for Backups without RMAN System
Administrators Guide
Explains how to verify NetBackup for Oracle Advanced BLI Agent for Backups
Without RMAN.
For this product, you may also need the following manuals from Oracle Corporation:
Oracle Enterprise Manager Administrators Guide
Oracle8 Server Backup and Recovery Guide
For this product, you may also need the following manuals from VERITAS Software:
Database Edition for Oracle Administrators Guide
Storage Edition for Oracle Administrators Guide
NetBackup for Oracle - Advanced BLI Extension System Administrators Guide
39
Users Guides
Users Guides
40
Troubleshooting Guides
41
Troubleshooting Guides
42
Index
Macintosh client 10
NetBackup options 19
NetWare nontarget client 10
OS/2 Warp client 10
server
notes 3
procedure 4
requirements 2
script 2
UNIX client 16
locally from CD-ROM 11, 16
secure 15
trusting 13
UNIX clients on server 4
Windows client 9
Interface
setup, Java 6
A
Add a UNIX Client 16
Administration Client
adding to the server list of remote server
17
installing 17
starting 18
AutoRunI.exe 17
B
bp.conf file 2
C
CDE (Common Desktop Environment)
set up for NetBackup-Java 6
Client
adding after initial install 16
client_config script 15
Clients
installation (see Installation)
uninstalling 32
Configuration
of devices for the operating system 8
J
Java interface, setup 6
M
Macintosh client
installation 10
Mwm*keyboardFocusPolicy X resource 6
D
Devices
configuration for the operating system 8
Domain Name Service (DNS) 3
N
NetBackup
installation 2
options installation 19
NetWare Directory Services (NDS) files 9
NetWare nontarget client
installation 10
Network Information Service (NIS) 3
NFS mounted directory 3
F
file locking 3
firewall 11
H
hosts file 3
I
inetd.conf file 2
install_client_files script 15
Installation
Administration Client 17
O
OS/2 Warp client
installation 10
43
U
rc2.d directory 2
Remote administration 17
requirements for installation 2
Rockridge format for CR-ROM 4, 11
Uninstalling
NetBackup clients 32
NetBackup server 29
UNIX client
local installation 11, 16
UNIX clients 4
S
Scripts
client_config 15
install_client_files 15
server installation 2
Server
installation 2
services file 2
44
W
Window Manager, Java, setup 6
Windows client
installation 9
X
xbp 11