Veritas Netbackup 5.0: Installation Guide
Veritas Netbackup 5.0: Installation Guide
Veritas Netbackup 5.0: Installation Guide
Installation Guide
for Windows
N102378
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 © 1999-2003 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS
SOFTWARE, the VERITAS logo, VERITAS NetBackup, and all other VERITAS product names and
slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA
and/or other countries. VERITAS and the VERITAS logo Reg. U.S. Pat. and Tm. Off. Other product
names and/or slogans mentioned herein may be trademarks or registered trademarks of their
respective companies.
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.
VERITAS Software Corporation
350 Ellis Street
Mountain View, CA 94043
USA
Phone 650–527–8000
Fax 650–527–2901
www.veritas.com
Third-Party Copyrights
ACE 5.2A: ACE(TM) is copyrighted by Douglas C.Schmidt and his research group at Washington University and University of California, Irvine,
Copyright (c) 1993-2002, all rights reserved.
IBM XML for C++ (XML4C) 3.5.1: Copyright (c) 1999,2000,2001 Compaq Computer Corporation; Copyright (c) 1999,2000,2001 Hewlett-Packard
Company; Copyright (c) 1999,2000,2001 IBM Corporation; Copyright (c) 1999,2000,2001 Hummingbird Communications Ltd.; Copyright (c)
1999,2000,2001 Silicon Graphics, Inc.; Copyright (c) 1999,2000,2001 Sun Microsystems, Inc.; Copyright (c) 1999,2000,2001 The Open Group; All
rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission
notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting
documentation.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
JacORB 1.4.1: The licensed software is covered by the GNU Library General Public License, Version 2, June 1991.
Open SSL 0.9.6: This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)
TAO (ACE ORB) 1.2a: TAO(TM) is copyrighted by Douglas C. Schmidt and his research group at Washington University and University of
California, Irvine, Copyright (c) 1993-2002, all rights reserved.
NetBackup Release 5.0 Revision History
The following table summarizes the revisions made to this document for NetBackup
release 5.0.
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
What is in this Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Related Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Additional NetBackup Server and Client Installation Terms . . . . . . . . . . . . . . . . . .xii
Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
v
Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Contents vii
Silent Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
NetBackup Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Uninstalling NetBackup Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Installing UNIX NetBackup Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Install Client Software Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Install Client Software Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Adding a UNIX Client Type After Initial Server Installation . . . . . . . . . . . . . . 99
Uninstalling UNIX NetBackup Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Installing Mac OS X 10.2.x Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Caution If a device is not properly configured for the operating system, backups made to
that device may lead to backup failure and/or data loss.
ix
Getting Help
Getting Help
Use the VERITAS Technical support web set to get help for if you have questions.
2. Click the Phone Support icon. A page that contains VERITAS support numbers from
around the world appears.
2. Click the E-mail Support icon. A brief electronic form will appear and prompt you to:
◆ Select a language of your preference
◆ Select a product and a platform
◆ Associate your message to an existing technical support case
◆ Provide additional contact and product information, and your message
Related Resources
Glossary
If you encounter unfamiliar terminology, consult the NetBackup online glossary. The
glossary contains terms and definitions for NetBackup and all additional NetBackup
options and agents.
The NetBackup online glossary is included in the NetBackup help file.
1. In the NetBackup Administration Console (or from the Backup, Archive, and Restore
client interface), click Help > Help Topics.
3. Double-click Glossary.
Preface xi
Accessibility Features
Active node
The designated node in a clustered environment where NetBackup is installed and from
which NetBackup can push to other nodes in the cluster. In addition, the NetBackup
services are running on an active node.
Inactive node
An inactive node in a clustered environment has NetBackup installed, however
NetBackup and the NetBackup services are not running.
Migrating
Migrating, commonly referred to as failover, occurs when a node becomes unavailable,
and the cluster resources are migrated to an available node.
Nodes
In a server cluster, two or more servers (called nodes) are linked in a network, and run
cluster software that allows each node access to the shared SCSI bus to which any number
of disks can connect.
Virtual IP address
This is the IP address of the cluster. The address that the virtual server name should
resolve to.
Accessibility Features
NetBackup contains features that make the user interface easier to use by people who are
visually impaired and by people who have limited dexterity. Accessibility features
include:
◆ Support for assistive technologies such as screen readers and voice input (Windows
servers only)
◆ Support for keyboard (mouseless) navigation using accelerator keys and mnemonic
keys
For more information, see the NetBackup System Administrator’s Guide, Volume I.
Conventions
The following section explains typographical and other conventions used in this guide.
Product-Specific Conventions
The following term is used in NetBackup documentation to increase readability while
maintaining technical accuracy.
◆ Microsoft Windows, Windows
Generic terms used to describe a specific product or operating system developed by
Microsoft, Inc. Some examples are, Windows 2000, Windows Server 2003, Windows
servers, Windows clients, Windows platforms, or Windows GUI. For more
information on the Windows operating systems that NetBackup supports, refer to the
VERITAS NetBackup Release Notes for UNIX and Windows or go to the VERITAS support
web site at http://www.support.veritas.com.
Note When a specific Windows product is identified in the documentation, only that
particular product is valid in that instance.
Typographical Conventions
Here are the typographical conventions used throughout the manuals:
Conventions
Convention Description
GUI Font Used to depict graphical user interface (GUI) objects, such as fields, list
boxes, menu commands, and so on. For example: Enter your password in
the Password field.
Italics Used for placeholder text, book titles, new terms, or emphasis. Replace
placeholder text with your specific text. For example: Replace filename
with the name of your file. Do not use file names that contain spaces.
This font is also used to highlight NetBackup server-specific or operating
system-specific differences. For example: This step is only applicable for
NetBackup Enterprise Server.
Preface xiii
Conventions
Conventions (continued)
Convention Description
Code Used to show what commands you need to type, to identify path names
where files are located, and to distinguish system or application text that
is displayed to you or that is part of a code example.
Key+Key Used to show that you must hold down the first key while pressing the
second key. For example: Ctrl+S means hold down the Ctrl key while
you press S.
You should use the appropriate conventions for your platform. For example, when
specifying a path, use backslashes on Microsoft Windows and slashes on UNIX.
Significant differences between the platforms are noted in the text.
Tips, notes, and cautions are used to emphasize information. The following samples
describe when each is used.
Note Used for important information that you should know, but that shouldn’t cause any
damage to your data or your system if you choose to ignore it.
Caution Used for information that will prevent a problem. Ignore a caution at your own
risk.
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:
command arg1|arg2
In this example, the user can use either the arg1 or arg2 variable.
❖ Select Start > Programs > VERITAS NetBackup > NetBackup Administration
Console.
The corresponding actions could be described in more steps as follows:
4. Move your cursor to the right. First highlight and then click NetBackup
Administration Console.
Preface xv
Conventions
1
How does NetBackup work?
Master Server
The master server is the computer where NetBackup server software is installed. There can
be only one Master Server per backup domain. The NetBackup master server is
responsible for the following functions:
◆ Contains the backup configurations and policies
◆ Runs the Scheduler that initiates the automated backups
◆ Maintains databases/catalogs that track the location and contents of all backups
Media Servers
A Media Server, in a NetBackup Enterprise Server configuration, can be a standalone
server that receives requests for backup and restore operations from the Master Server. (A
master server can also be configured as a media server.) There can be multiple Media
Servers in a backup domain. In a NetBackup Server configuration the media server is the
same machine as the master server.
Media Servers can:
◆ Communicate with the Media Manager (on the same system) to select media for
backup and restore operations. Refer to “Media Manager” on page 7 for more
information.
◆ Communicate with NetBackup Clients during a backup or restore operation
◆ Monitor the status of storage devices
NetBackup Clients
NetBackup Clients are the remote computers that have NetBackup client software installed.
A NetBackup Enterprise Server configuration can virtually have an unlimited number of
clients for each backup domain. With the proper conditions set, a client can direct a user
request to the Master Server to perform a backup or restore operation.
Clients can perform the following functions:
◆ Validate connection requests from the NetBackup server
◆ Support compression of the backup stream
◆ Support include and exclude lists
In general, NetBackup clients can have any combination of the following operating
systems:
◆ AIX
◆ HP-UX Tru64/Alpha
◆ HP-UX 9000
◆ Linux
◆ Macintosh
◆ Novell
◆ Solaris
◆ Windows NT/2000/XP (32 and 64 bit)/2003 (32 and 64 bit)
For a complete list of supported clients and corresponding version numbers, refer the
NetBackup Release Notes.
Storage Unit
A storage unit is a term that describes a storage device where NetBackup stores files and
data. A storage unit can be a location on a disk, a set of drives in a robot, or one or more
single tape drives of the same type that connect to the same host.
In the screen below, selecting Storage Units in the tree displays the individual units in the
Details pane.
Storage units simplify administration because once they are defined, NetBackup points to
a storage unit rather than to individual devices. For example, if a storage unit contains
two drives and one is busy, NetBackup can use the other drive without administrator
intervention.
Media
Media can be physical magnetic tapes, magnetic disks (also called removable media), or
optical disks. Media is where data is stored. Non-removable media commonly referred to
as hard disk share is usually a directory on a hard disk.
Media Manager
Media Manager, which is part of NetBackup, manages the robots, tape drives, and
removable media. Media Manager primarily uses four tools:
◆ The Device Configuration Wizard, which guides you through device configuration in
a step-by-step manner.
◆ The Volume Configuration Wizard, which guides you through volume configuration
in a step-by-step manner.
◆ The Media and Device Management graphical interface, which allows you to
reconfigure storage devices and volumes separately.
◆ The Device Monitor graphical interface, which displays any pending requests for
volumes and allows you to control and manage devices.
Graphical Interfaces
The NetBackup Administration Console that is installed on a server is used for
configuring, scheduling, monitoring, and managing NetBackup. The NetBackup user
interface (referred to as Backup, Archive, and Restore) that is installed on a client can be
used for starting backups, managing archives, and initiating restores for that particular
computer. The following figures are examples of both of these interfaces.
NetBackup Wizards
NetBackup provides the following wizards to assist you with installation and
configuration. Once you have completed your initial setup with the Getting Started
wizard, the individual configuration wizards allow you to reconfigure devices, volumes,
catalog backups, and backup policies separately as needed.
Wizards Description
Configure Volumes Helps you define volumes for robots and standalone drives.
Configure Catalog Backup Helps you configure how and when the NetBackup catalog is
backed up.
Create a Backup Policy Helps you configure regular backups for a client or a set of
clients.
Import Images Assists you in stepping through the import image process.
Configure a Shared Drive Helps you configure a new shared drive or reconfigure an
existing shared drive.
2. NetBackup Installations
3. Upgrading NetBackup
11
Configuring Storage Devices for Windows
The remainder of this chapter discusses the necessary steps to install NetBackup. For
specific installation procedures about a particular add-on product, refer to the
product-specific information associated with that product.
Caution An improperly configured device may lead to loss of data during a restore.
5. Select the Product Version, Platform, and Language from the appropriate drop-down
menus.
7. Click Device and Library Compatibility Information - All Versions and Platforms.
8. A new web page appears, and enables you to select the product level that you want to
reference. Select an appropriate product level.
9. From this page you can choose to view device support information by individual
vendor, or all support drives, libraries, or robot types.
Note When installing NetBackup for the first time, VERITAS recommends that you install
the latest device drivers for your storage device immediately after you install the
NetBackup software and before you configure the product.
If you are upgrading NetBackup, you can install the latest device drivers before you
upgrade NetBackup.
The VERITAS Tape Device Driver Install wizard (located on the NetBackup CD)
steps you through the process of installing the latest device drivers. The steps below
describe how to initiate this wizard.
If you do not have a CD-ROM, you can download the NetBackup Tape Device
Driver Install software from the VERITAS support web site:
http://www.support.veritas.com
3. In the VERITAS Browser, click the Additional Product Installations > NetBackup
Tape Device Driver link. The NetBackup Tape Installer wizard appears.
4. Follow the prompts throughout the wizard to install the latest device drivers for your
storage device.
Note As VERITAS supports more devices, you can download the latest external device
mapping files on the Updates and Patches web page on the VERITAS support web
site: http://www.support.veritas.com.
NetBackup Installations
This section prepares you for the installation of your NetBackup product by providing
system requirements, license key information, and step-by-step instructions on:
◆ NetBackup Server Installation Requirements
◆ Installing NetBackup Server Software
◆ Customizing a NetBackup Installation
◆ Remotely Installing NetBackup
◆ Installing NetBackup in a Clustered Environment
◆ Installing NetBackup Silently
By definition, your NetBackup server is also a NetBackup client. When you installed the
NetBackup server software, both the NetBackup server and NetBackup client software
were installed on the server.
For more information on installing NetBackup client software, refer to “Installing
NetBackup Client Software” on page 83.
Caution Before installing your NetBackup product, make sure you have the most
current operating system patches and updates applied to your system. If you
are not certain of your OS level, contact your OS vendor and request the latest
patches and upgrades.
Note It is important that you ensure all NetBackup servers have a release level installed
that is at least equal to the version level installed on the clients. (Older versions of
server software can encounter problems with newer clients.)
◆ All clustered nodes must be running the same operating system, service pack level,
and version of NetBackup. Mixing server versions is not supported in a clustered
environment.
1. Master servers
4. NetBackup clients
◆ On Windows systems with AutoPlay enabled for CD-ROM drives, the VERITAS
NetBackup installation browser starts automatically.
◆ On Windows systems that have AutoPlay disabled, run Launch.exe in the
top-level directory on the CD.
5. Click Install Server Software. A welcome window appears informing you that the
NetBackup setup wizard is about to install the software on your system.
6. Click Next.
7. To proceed with the installation, you must check the I accept the terms of the license
agreement option, then click Next.
8. Select Install to this computer only and click Next to perform a local installation.
9. Enter the base product license key that you received when you purchased your
product. The license key determines which installations are available to install. For
example, the NetBackup Media Server option is only available with NetBackup
Enterprise Server.
Note Installing the NetBackup Remote Administration Console does not require a license
key.
11. Click Next. The Setup Type wizard appears. You can elect to perform a typical or a
custom installation. Refer to “Customizing a NetBackup Installation” to see the
differences in the installation processes.
Note NetBackup Enterprise only: If installing a media server, the NetBackup System Names
window will have an additional line with the local media server filled in. You must
enter the name of the master to which the media server is configured.
13. Enter the server names and click Next. The NetBackup Global Device Database Host
window appears.
Note To make changes to the installation settings, click Back until you reach the page you
want to change, or click Cancel and exit the wizard.
15. Click Install. The installation process begins. This process could take several minutes.
Note After the installation completes, a NetBackup installation log file is generated and
placed in your default TEMP directory. The following procedures explain how to
verify the location of your TEMP environment variable.
▼ To locate the NetBackup installation log file for Windows 2000, XP, and 2003
systems
a. Select Start > Programs > Accessories > Command Prompt. A Command Prompt
window appears.
Note Make sure you can view all hidden files and folders. To set this option, select Tools
> Folder Options.... in the Control Panel window; click the View tab; select the
Show hidden files and folders option; and click OK.
b. Enter echo %TEMP% and press the Return key on your keyboard. The location of
your TEMP directory will display.
a. Select Start > Settings > Control Panel. The Control Panel window appears.
Note Make sure you can view all hidden files and folders. To set this option, select View
> Folder Options... in the Control Panel window; click the View tab; select the
Show All Files option; and click OK.
c. Click the Environment tab. The Environment Variables, including the TEMP
variable, appear along with the corresponding paths for each variable.
16. Prior to clicking Finish, the NetBackup installation prompts you to enter additional
license keys or complete the installation and continue the setup process by
configuring your NetBackup product. By default the Launch NetBackup
Administration Console now check box is selected.
b. To complete the installation and configure your product, click Finish. For more
information on how to configure your product, see “Configuring NetBackup
Server Software” on page 77.
c. To complete the installation and wait to configure your product at another time,
clear the Launch NetBackup Administration Console now option, then click
Finish.
Note VERITAS recommends that you continue with the product setup and configuration
by clicking the Getting Started link in the details pane of the NetBackup
Administration Console and continuing through this wizard until you have
completed the production configuration.
2. Install the VERITAS Security Services (VxSS) components on your system so that you
are then able to use Access Control.
NetBackup Access Control can be turned on and run at any time after you have
installed or upgraded to NetBackup 5.0. After you have installed or upgraded to
NetBackup 5.0, you can run NetBackup Access Control by configuring VxSS and
making some NetBackup Access Control-related bp.conf entries. For more
information about this, refer to VERITAS Security Services™ Version 4.0 Administrators
Guide for Windows and UNIX and the NetBackup System Administrator’s Guide,
Volume II.
The VxSS components reside on a clearly marked CD-ROM in your NetBackup
Product package. The following table contains the VxSS components that you must
install as they apply to each NetBackup system, and after you have successfully
installed NetBackup.
3. After you have finished installing NetBackup and the VxSS components applicable to
the type of NetBackup system you are installing to, you will be ready to configure the
access control features. For detailed information on how to configure Access Control,
refer to the NetBackup System Administrator’s Guide, Vol II.
Note By default, the NetBackup Debugger Symbols features are marked not available on
initial installation.
From this window you can choose which product feature, and in some cases
subfeatures, to install. To mark a feature as unavailable do the following:
a. Select the icon next to the feature that you want to change. A pop-up window
appears.
b. Click This feature will not be available. A red “X” appears in the icon signifying
the feature will not be installed.
c. Click Change to select a new location to install NetBackup. The Change Current
Destination Folder window appears. This window enables you to browse to a
new location and designate a new folder where NetBackup will be installed.
2. Click Next.
From NetBackup Services window you:
◆ Enter a Username, Password, and Domain or check the Use the built-in system
account check box.
◆ Choose a startup type to use for the NetBackup services
◆ Elect to start the services after install by checking the Start NetBackup Server
Services After Install check box.
5. Enter the name of the current server and then enter the names of the other systems
that are allowed to access this server. From the dialog, you can list each server on a
separate line or in a comma-delimited list.
6. Click Next. The NetBackup Global Device Database Host window appears.
7. Enter the Global Device Database Host Name and click Next. The Ready to Install
the Program window appears.
Note If you want to make changes to the installation settings, click Back until you reach
the page you want to change, or click Cancel and exit the wizard.
9. At the end of the installation, the Completing the NetBackup wizard window appears
and enables you to add additional NetBackup license keys.
In addition, if you elected to start the NetBackup services during the install process,
then the Launch NetBackup Administration now check box will be checked.
Note Review the installation requirements for NetBackup on page 14 before starting this
procedure.
Follow these instructions to install the NetBackup software on selected Windows NT,
Windows 2000, Windows XP, or Windows 2003 servers on your network (one of these
systems can be your local system). You may stop the installation process at any time by
clicking Cancel.
Note It is recommended that you perform all remote installations before you upgrade the
system you are performing the remote installs from. If you upgrade your current
system to the latest version and then attempt to perform a remote install, the
upgrade procedure will not prompt you with the correct screens to begin a remote
installation.
1. Log on as Administrator on the server where you will be installing NetBackup from.
◆ Browse the CD
◆ The NetBackup link selected (by default) and these available options:
◆ Begin NetBackup Installation
◆ View available documentation
◆ Link to VERITAS Technical Support
◆ Link to VERITAS e-Learning
6. To proceed with the installation, you must check the I accept the terms of the license
agreement option, then click Next.
7. Select the Select from available computers on the network option and click Next to
install NetBackup to remote systems.
8. Enter the base product license key that you received when you purchased your
product. During this installation process, the following occurs to ensure you have
proper credentials to perform remote installations:
◆ If you are installing for the first time on the host system, you will need to enter a
valid license key.
◆ When performing an upgrade a new license key is not required. Your current
license key will be used.
◆ After you select a remote system to install to:
◆ A check determines if you have proper administration credentials on that
system. If you do not have the proper credentials the system is not added to
the list.
◆ If you do have the proper credentials, a second check determines if a license
key is needed. If a license is needed and one was not entered, the system
cannot be added to the list. You must enter a valid license key to install to that
remote system.
◆ If you enter an invalid license key, the NetBackup License Key and Server Type
screen will remain visible until a valid key is entered.
The license key that you enter will determine which of the three installations are
available for you to install. For example, a NetBackup Enterprise Server key will
enable all installation choices as shown in the following diagram. Entering a
NetBackup Server key means the NetBackup Media Server installation choice is not
available.
Note Installing NetBackup Remote Administration Console does not require a license
key.
10. From the Setup Type window, you can elect to perform a typical or a custom
installation. Refer to “Customizing a NetBackup Installation” to see the differences in
the installation processes.
11. Select Typical and click Next. The NetBackup System Names window appears.
From this window you can enter the names of the systems that will have access to this
current system. During a remote upgrade the following applies.
◆ You cannot change the installation location on a remote install. NetBackup will
use the existing location of the previous install. In addition, you cannot change
the installation location on an upgrade or a new installation when using the
system default settings.
◆ The master server name will not change even if you are pushing an upgrade to
servers with other masters.
◆ NetBackup Enterprise only: If installing a media server, the NetBackup System
Names window will have an additional line with the local media server filled in.
You must enter a master server name for the NetBackup Administration Console
and the Remote Administration Console that this media server is configured to.
12. Enter additional server names and click Next. You can cut, copy, or delete a server
from the list by selecting a server and using the right mouse button functionality.
Note All destination servers systems share the same server list.
13. From the NetBackup Global Device Database Host window, choose a device database
setting and click Next. This window enables you to choose which device database
settings you want to install on the destination servers that do not have NetBackup
installed. Servers that already have NetBackup installed will retain their current
Global Device Database Host setting.
Note The NetBackup Global Device Database Host window only appears for master and
media server installations.
14. In the Install NetBackup to remote systems screen, select the servers from the list of
Available Systems and add them to the Destination Systems list. You are choosing the
systems that you want to remotely install NetBackup on. Each time you choose a
system, NetBackup performs the following system and license checks:
◆ Verifies the system for a server install that matches the type that you selected. If
the system does not have NetBackup installed, it is considered verified. If the
system already has NetBackup installed, the installation type on that system is
compared to the installation type that you are requesting. If you are requesting an
invalid combination (for example, trying to install a Remote Administration
Console on a system that already contains master server software) you will be
notified of this and the selection of that system is disallowed. In addition, if the
remote system is at a platform level of Windows ME or less, or a 64-bit Windows
system, the install is disallowed.
◆ Verifies that you have proper administration credentials on the remote system
that you chose. If you do not have administration credentials, the Enter Network
Password window appears and prompts you to enter the administrator’s user
name and password. Click OK, and continue selecting destination systems.
Note This process repeats for each server that you select. In addition, you can elect to
remember the user name and password and only be prompted when the user name
or password is not valid on a particular system.
15. Click Next when you have finished selecting remote systems.
Note You may need to reboot the remote systems after the installation is complete.
A summary screen appears that shows you the progress of the installation and each of
the systems. You can right-click on a system listed in the screen to see a status of the
install, for example, it can see if an install failed on a particular system. You would
then be able to obtain more information about the failure by viewing the remote
install log. The remote install log is named nbpinst.log and is located in the
Windows installation directory.
17. Click Finish. The remote install is complete and NetBackup is now running on your
remote system.
Note The NetBackup server setup program cannot clean up an aborted install. Therefore,
if you stop Setup while it is copying files to a client, the files that have been
successfully installed are not uninstalled.
2. After you take the cluster offline bring the shared disk back online (for MSCS clusters)
or freeze the active node (VCS clusters). You are now ready to begin the installation
process. Perform the procedure, “Installing NetBackup in a Clustered Environment”.
1. Log on as Administrator on the active node. The active node is the node that owns the
disk that will be used as the NetBackup shared disk.
6. To proceed with the installation, you must check the I accept the terms of the license
agreement option, then click Next.
7. This step applies only to MSCS clusters. Select Perform a clustered install of
NetBackup, then click Next.
Note The installation process references the registry settings of your system to determine
if your system is configured for a Windows MSCS clustered environment. If your
system is configured for a MSCS clustered environment, the Perform a clustered
install of NetBackup option will be available for selection.
8. Enter the base product license key that you received when you purchased your
product. During this installation process, the following occurs to ensure you have
proper credentials to perform remote installations:
◆ When you select a clustered system to install on:
11. In the Cluster Settings window, enter the appropriate data in each of the fields. These
fields are listed below along with a brief description of each field.
◆ NetBackup Cluster Group Name - A name used to identify a NetBackup service
group or resource group. A resource group is comprised of resources that are
related and interdependent to each other.
◆ Virtual Host Name - The name of the cluster as known by the NetBackup
environment. This is the name that the clients will have in their server list. It is
also the name that the server uses when communicating to the client nodes.
◆ Virtual IP Address - This is the IP address of the cluster. The address that the
virtual server name should resolve to.
◆ Subnet Mask - A mask used to identify a subnetwork so that IP addresses can be
shared on a local area network. This number correlates directly to the virtual IP
address of the cluster.
◆ Path to Shared Data - This path indicates a directory on one of the shared disks in
the cluster where NetBackup will store its configuration.
◆ Public Network - When installing NetBackup on a clustered system, you chose
one of the public networks assigned to the node of the cluster.
Note You must not select the private network assigned to this cluster.
13. Enter additional server names and click Next. You can cut, copy, or delete a server
from the list by selecting a server and using the right mouse button functionality. All
of the nodes of the cluster should be added to the Additional Servers list in this
window.
Note All of the nodes identified in the cluster will receive the same server list.
14. Enter the name of the NetBackup Global Device Database Host and click Next. The
Global Device Database Host serves as the repository for global device configuration
information (refer to the NetBackup Media Manager System Administrator’s Guide for
Windows).
By default, the Global Device Database host is the virtual cluster name. Under most
circumstances, this can be left as the default. However, you may need to enter a
different host name in the following situations:
◆ If the system shares drives with the Shared Storage Option (SSO), all NetBackup
servers must use the same host for storing device information.
◆ If the system has multiple master servers, enter the name of the server that will
store the global device configuration information. Conflicting host information
may result in an error.
15. In the Install NetBackup to Clustered Nodes screen, select the cluster nodes from the
Available Systems list and add them to the Destination Systems list. Make sure you
select your local machine when you are selecting systems to install.
Each time you choose a different node in the cluster group to install, NetBackup
performs the following system and license checks:
◆ Verifies the system for a server install matches the type that you selected. The
installation type on that system is compared to the installation type that you are
requesting. If you are requesting an invalid combination, you will be notified of
this and the selection of that system is disallowed.
◆ Verifies that you have proper administration credentials on the node that you
chose. If you do not have administration credentials, the Enter Network Password
window appears and prompts you to enter the administrator’s user name and
password. Click OK, and continue selecting destination systems.
Note This process repeats for each node that you select. In addition, you can elect to
remember the user name and password and only be prompted when the user
name or password is not valid on a particular system.
The following is a list of facts associated with the push-install process in a clustered
environment:
◆ There is no limit to the number of nodes that you can install NetBackup on. The
only limit to the number of nodes in a cluster is that set by the clustering service
and not NetBackup.
◆ NetBackup add-on products such as Global Data Manager (GDM) and
NetBackup Archive and Restore (NBAR) cannot push their installs. These add-on
products must be installed on each individual node in the cluster group. For
instructions on how to install these products, refer to NetBackup documentation
for each product.
◆ Only the license key that was entered at the beginning of this procedure is pushed
to the other nodes in this cluster. If the license key includes add-on products such
as GDM and NBAR, and the nodes you are pushing NetBackup to already have
GDM and NBAR installed, then this key will enable you to use these products.
16. Click Next when you have finished selecting cluster nodes. The installation process
begins pushing the install to all of the selected nodes. The following NetBackup
Installation window appears, providing a status of which nodes are being installed as
well as a completion status.
17. On the Ready to Install the Program screen, click Install. The cluster install pushes
NetBackup to all selected nodes.
Note You may need to reboot each of the cluster nodes after the installation is complete.
Note For MSCS clusters: Under normal circumstances, cluster configuration is one of the
final steps in installing NetBackup in a cluster. If this step is not done or does not
complete successfully, you can use the bpclusterutil command from the active
node to perform this step. The bpclusterconfig -c command runs the cluster
configuration step performed by installation. Using the -a option with the
appropriate option name configures the NetBackup option in a cluster. This
command can be run multiple times. See the NetBackup High Availability System
Administrator's Guide for more information
A summary screen appears that shows you the progress of the installation and each of
the systems. You can right-click on a system listed in the screen to see a status of the
install, for example, it can show if an install failed on a particular system. You would
then be able to obtain more information about the failure by viewing the remote
install log. The remote install log is named nbpinst.log and is located in the
Windows installation directory.
18. Click Next. A screen appears that enables you to do two things before completing the
install:
a. You can select a check box to display the NetBackup Administration Console.
b. You can select a button to enter more license keys on the system you are currently
installing on.
Note If you enter a license key at this time, the key will not be pushed to the other
nodes in the cluster group. You must go to each node in the group and add the
key or keys that you want to add.
1. During a cluster installation you can open the Cluster Administrator interface to see
your current structure.
2. In the previous procedure a new cluster named NetBackup Master Server Group was
created. In the following figure you can see Disk Y in the left pane and no other cluster
group NetBackup Master Server Group exists.
3. After you have completed the installation and configuration process, the Cluster
Administrator’s interface updates with the new cluster group in the left pane.
Note The files contained on the CD-ROM are read-only. Change the permissions for these
files on the hard drive to allow the update.
3. In that temporary directory, modify the appropriate script. (The following list shows
the available items and the corresponding commands.)
◆ To install a master server, edit: silentmaster.cmd
◆ To install a media server, edit: silentmedia.cmd
◆ To install a NetBackup Remote Administration Console, edit:
silentadmin.cmd
4. If only one master server will be accessing the machine, remove the following line
from the script:
SET ADDITIONALSERVERS=media1,media2,media3
6. Check the log file (NetBackup Install.log in the default TEMP directory) to
verify that the install was successful.
Note After the installation completes, a NetBackup installation log file is generated. You
can find this log file at the default temp directory. To determine where your TEMP
directory is located, refer to “To locate the NetBackup installation log file for
Windows 2000, XP, and 2003 systems” on page 22 or “To locate the NetBackup
installation log file for Windows NT systems” on page 23.
Note If this installation is an upgrade, you must reboot the computer for the changes to
take effect.
Caution Before you upgrade the NetBackup software on the master server:
– Back up your NetBackup catalogs.
– Verify that the catalog backup was successful.
49
Upgrading to NetBackup 5.0
Upgrading to this version of NetBackup is as easy as following the normal installation
process. In fact, that is exactly what you do. The installation process will detect an earlier
version of NetBackup, if one exists, and determine if it is possible to upgrade to this
version from the one detected. Read through the notes and requirements that follow
before you begin upgrading your version of NetBackup.
The following sections describe how to upgrade to this version of NetBackup. Also
included in this section is a procedure on how to perform upgrades in a clustered
environment.
Note VERITAS does not support an upgrade directly from NetBackup 3.4 and 3.4.1 to
NetBackup 5.0. If you currently have one of these versions of NetBackup
installed, you must upgrade to NetBackup 4.5GA, 4.5 FPx, or 4.5 MPx first and
then upgrade to this version of NetBackup.
a. Master server
d. NetBackup clients
Note When you upgrade from a NetBackup server evaluation license key to a permanent
NetBackup Enterprise Server-based product license key on Windows, restart the
NetBackup services. Restarting the services ensures that the proper licensing
information is displayed after selecting Help > About NetBackup Administration
Console.
Note If you make and save any license key updates (including adding and deleting
license keys), you must restart the NetBackup Administration Console.
5. The system may require a reboot to complete the upgrade. When prompted to reboot,
click OK.
Note The NetBackup server setup program cannot clean up an aborted install. Therefore,
if you stop Setup while it is copying files to a client, the files that have been
successfully installed are not uninstalled.
2. After you take the cluster offline (for MSCS clusters) or freeze the active node (VCS
clusters), you are ready to begin the upgrade process. Perform the procedure,
“Upgrading NetBackup in a Clustered Environment”.
◆ Upgrading NetBackup in a VCS cluster installs each node as non-clustered. When
the installation is complete, run the VCS configuration wizard for NetBackup.
6. To proceed with the installation, you must check the I accept the terms of the license
agreement option, then click Next.
7. This step applies only to MSCS clusters. Select Perform a clustered install of
NetBackup, then click Next.
Note The installation process references the registry settings of your system to determine
if your system is configured for a Windows MSCS clustered environment. If your
system is configured for a MSCS clustered environment, the Perform a clustered
install of NetBackup option will be available for selection.
8. Enter the base product license key that you received when you purchased your
product. During this installation process, the following occurs to ensure you have
proper credentials to perform remote installations:
◆ When performing an upgrade a new license key is not required. Your current
license key will be used.
◆ When you select a clustered system to install on:
◆ A check determines if you have proper administration credentials on all node
in the cluster. If you do not have the proper credentials the system is not
added to the list.
◆ If you do have the proper credentials, a second check determines if a license
key is needed. If a license is needed and one was not entered, the system
cannot be added to the list. You must enter a valid license key to install to that
node.
◆ If you enter an invalid license key, the NetBackup License Key and Server Type
screen will remain visible until a valid key is entered.
The license key that you enter will determine which of the installation options are
available for you to install.
11. In the Cluster Settings window, enter the appropriate data in each of the fields. These
fields are listed below along with a brief description of each field.
Note During an upgrade, these parameters must match the existing parameters to
successfully complete the upgrade.
Note You must not select the private network assigned to this cluster.
Note The cluster configuration settings that you enter in the Cluster Settings dialog
must be identical to the settings on the existing NetBackup configuration for the
cluster group.
Note All of the nodes identified in the cluster will receive the same server list.
14. In the Install NetBackup to Clustered Nodes screen, select the cluster nodes from the
Available Systems list and add them to the Destination Systems list. Make sure you
select your local machine when you are selecting systems to install.
Each time you choose a different node in the cluster group to install, NetBackup
performs the following system and license checks:
◆ Verifies the system for a server install matches the type that you selected. The
installation type on that system is compared to the installation type that you are
requesting. If you are requesting an invalid combination, you will be notified of
this and the selection of that system is disallowed.
◆ Verifies that you have proper administration credentials on the node that you
chose. If you do not have administration credentials, the Enter Network Password
window appears and prompts you to enter the administrator’s user name and
password. Click OK, and continue selecting destination systems.
Note This process repeats for each node that you select. In addition, you can elect to
remember the user name and password and only be prompted when the user
name or password is not valid on a particular system.
15. Click Next when you have finished selecting cluster nodes. The installation process
begins pushing the install to all of the selected nodes. The following NetBackup
Installation window appears and provides a status of which node is being installed
along with the completion status. You can right-click on a system listed in the screen
to see a status of the install, for example, it can show if an install failed on a particular
system. You would then be able to obtain more information about the failure by
viewing the remote install log. The remote install log is named nbpinst.log and is
located in the Windows installation directory.
Note Reboot any of the inactive cluster nodes that the summary screen displayed as a
required reboot. After you have rebooted all inactive nodes that required rebooting,
proceed to reboot the active node (the node where you ran the install) if the
summary screen says it requires a reboot. It is imperative that you reboot the
inactive nodes before you reboot the active node.
Note For MSCS clusters: Under normal circumstances, cluster configuration is one of the
final steps in installing NetBackup in a cluster. If this step is not done or does not
complete successfully, you can use the bpclusterutil command from the active
node to perform this step. The bpclusterconfig -c command runs the cluster
configuration step performed by installation. Using the -a option with the
17. Click Next. A screen appears that enables you to do two things before completing the
install:
a. You can select a check box to display the NetBackup Administration Console.
b. You can select a button to enter more license keys on the system you are currently
installing on.
Note If you enter a license key at this time, the key will not be pushed to the other
nodes in the cluster group. You must go to each node in the group and add the
key or keys that you want to add.
1. During a cluster installation you can open the Cluster Administrator interface to see
your current structure.
2. After you have completed the installation and configuration process, the Cluster
Administrator’s interface updates the cluster group in the left pane.
The subsections in this chapter provide the installation procedures for each
system/interface combination shown in the table.
Note The Windows NetBackup servers that support the NetBackup Remote
Administration Console are Windows NT, Windows 2000, Windows XP, and
Windows 2003. For information about the supported platforms for the
NetBackup 5.0 release, refer to the Supported Platforms and Peripherals chapter in
NetBackup Release Notes for UNIX and Windows.
63
Although the NetBackup Remote Administration Console cannot be used as a master or
media server, in order for it to remotely administer a NetBackup server, it must be added
to the server list on that server in the same way that other NetBackup servers are added to
the server list to give them access to that server.
The NetBackup manuals and on-line help do not, in most cases, specifically refer to the
NetBackup Remote Administration Console since, for all practical purposes, using the
NetBackup Server for Windows interfaces on the NetBackup Remote Administration
Console is identical to using them locally on the server that is being administered. Of
course, the master server or device host shown in the interface will be the server name
that is being administered instead of the local server name.
4. Click OK.
5. Click Next.
6. Click I Accept.
7. Click Next.
9. Click Next.
When the software is installed, a set of NetBackup documents are also installed in the
following directory:
install_path\Help
The variable, install_path, is a default location that is typically defined by your
system. For some systems this path is, C:\Program Files\VERITAS.
By default, the NetBackup Remote Administration Console 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 NetBackup Remote Administration
Console computer and select Start > Programs > VERITAS NetBackup > NetBackup
Administration Console.)
▼ The following steps will add the NetBackup Remote Administration Console host to
the server list of the remote Enterprise server.
Note On a UNIX system, there are two procedures that you can use to add the host to the
server list; you can use the NetBackup-Java Administration Console (if your system
is NetBackup-Java Console compatible) or you can edit the bp.conf file. Step 1
describes this process using the NetBackup-Java Administration Console and Step 2
describes how to edit the bp.conf file.
1. Use the NetBackup-Java Administration Console to specify and add the remote UNIX
Enterprise server to the server list. (If you perform this step you can proceed to
step 3.)
b. Right-click on the name of the host server in the Master Servers window in the
right pane.
d. In the Master Server Properties window, select the Servers icon from the tree in
the left window pane.
g. Click OK. The name of the host appears in the Additional Servers list.
h. Click OK.
2. Edit the bp.conf file to add the remote UNIX Enterprise server to the server list.
3. If you have an existing NetBackup Remote Administration Console installed and you
want to add a remote master server, perform the following steps.
Note If this is a clean installation, you can add the masters that you want to administer as
additional servers during the install.
b. In the left pane of the NetBackup Remote Administration Console, select Host
Properties > Master Server. The host server appears in the main window.
c. Right-click on the name of the host server in Master Server window on the right
pane.
f. In the Global Operations box, in the field labeled Add to all lists, type the name
of the host that is to run the NetBackup Remote Administration Console. Then
click the “+” button. (The name of the host appears in the Additional Servers list.)
g. Click OK.
Note You can install the NetBackup-Java Windows Display Console from the NetBackup
CD.
Requirements
For the computer on which you want to run the NetBackup-Java Windows Display
Console, VERITAS recommends 512 MB of physical memory.
1. On the system where you are performing the install, insert the CD that contains the
NetBackup server software.
◆ On Windows systems with AutoPlay enabled for CD-ROM drives, the NetBackup
install program starts automatically.
◆ On Windows systems that have AutoPlay disabled, run Launch.exe in the
top-level directory on the CD.
2. On the NetBackup Install browser, click the Install Java Windows Display Console
link.
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.
Note It is always good practice to backup your NetBackup catalogs before uninstalling.
1. Select Start > Settings >Control Panel. The Control Panel window appears.
2. From the Control Panel window, double click the Add/Remove Programs icon. The
Add/Remove Programs window appears.
4. Click Remove.
69
Uninstalling NetBackup Server Software
▼ To uninstall NetBackup server software and save catalog data for Windows 2000
(and greater) users
Note For Windows 2000 (and greater) users, clicking Remove during a product uninstall,
by default, removes all NetBackup configuration and catalog information. The
following procedure explains the necessary steps to retain this information for
future reinstalls.
1. Select Start > Settings >Control Panel. The Control Panel window appears.
2. From the Control Panel window, double click Add/Remove Programs. The
Add/Remove Programs window appears.
4. Click Change. This action enables you to modify, repair, or remove NetBackup.
6. Clear the Remove all NetBackup Configuration, Catalog, and Log files check box
to disable this function. (This check box contains a check mark by default.)
7. Click Remove.
Note Files are generated in the \NetBackup directory only by the single sign-on
operation of the NetBackup Administration Console on the host upon which
the console is run. NetBackup Administration Console cleans these files when
an exit function is performed. (It is common to have no temporary files in this
directory.) If a system crash were to occur, these files may be left behind. With
the console shutdown, you can delete these files safely with no data loss.
NetBackup also creates cached certificates for client and server NetBackup
applications. These files reside within the \NetBackup directory. These files will
typically have a name that is consistent with a DNS entry for a network interface that
is readable by a human, for example, machine.company.com.
Example directory entries for Windows;
<user_dir>\Local Settings\Applications Data\VERITAS\
NetBackup\machine.company.com
user_dir>\Local Settings\Applications Data\VERITAS\
NetBackup\dhcp
These files are created with the command bpnbat -LoginMachine. If considering a
reinstallation of NetBackup at a later date on the machine in question, you should
preserver the certificates in the \NetBackup directory or be prepared to provide the
machine identity password as originally set on the Root+AB broker. As an alternative,
one may reset the password on the Root+AB broker at reinstall time. For more
information on Root+AB brokers please see the VERITAS Security Subsystem
Administrators Guide.
1. When reinstalling a NetBackup product, you should have your license key(s)
available throughout the installation process.
Caution You must reinstall this product in the exact location as the previous installation
to ensure that your saved configuration, catalog, and log files will function
properly with the new product.
5. Click the appropriate installation link (client or server) that you want to start. The
NetBackup Setup wizard begins.
7. Check the I accept the terms of the license agreement option, then click Next.
8. Select where you want to install NetBackup (locally, or to another computer) and click
Next. The NetBackup License Key and Server Type window appears.
9. Enter the base product license key that you received when you purchased your
product. The license key determines which installations are available for you to
install.
Note Installing the NetBackup Remote Administration Console does not require a license
key.
11. Click Next. The Setup Type window appears. You can elect to perform a typical or a
custom installation. Refer to “Customizing a NetBackup Installation” to see the
differences in the installation processes.
12. Select Typical and then click Next. The NetBackup System Names window appears.
13. In the NetBackup System Names window, enter the names of other systems that are
allowed access to this server.
14. Enter the server names and click Next. The NetBackup Global Device Database Host
window appears.
Note If you want to make changes to the installation settings, click Back until you reach
the page where you can make the change, or click Cancel and exit the wizard.
16. Click Install. The installation process begins. This process could take several minutes.
Note After the installation completes, a NetBackup installation log file is generated and
placed in your default TEMP directory. The following procedures explain how to
verify the location of your TEMP environment variable.
▼ To locate the NetBackup Installation log file for Windows 2000 systems
a. Select Start > Programs > Accessories > Command Prompt. A command prompt
window appears.
b. Enter echo %TEMP% and press the Return key on your keyboard. The location of
your TEMP directory will display.
a. Select Start > Settings > Control Panel. The Control Panel window appears.
Note Make sure you can view all hidden files and folders. To set this option, select Tools
> Folder Options... in the Control Panel window. Then click the View tab; set the
Show hidden files and folders option, and click OK.
c. Click the Environment tab. The Environment Variables including the TEMP
variable appears along with the corresponding paths for each variable.
Note If you elected to not have the console start after the installation by default, you
can open the console by selecting, Start Programs > VERITAS NetBackup >
NetBackup Administration Console.
◆ If you are configuring NetBackup for the first time, we recommend that you click
on the Getting Started icon and using this set of wizards to guide you through
the process.
◆ If you have already configured NetBackup and you want to change a particular
area, you can click on the any of the remaining options.
◆ Configuring Master and Media Servers
This bulleted item applies only to NetBackup Enterprise Server.
The process of configuring a master or media server is very similar, and the versatility
of NetBackup enables you to install either server first. However, VERITAS
recommends that you install and configure the master server before you install and
77
configure a media server. You can then configure the media server information (such
as storage devices and volumes) on the master to ensure the master server will
properly administer the media server. The following list offers some tips when
configuring a media server.
◆ The NetBackup Administration Console appears after you install the media
server. The name of the master server will appear as the Host server name in the
left window pane of the NetBackup Administration Console if the master server
was installed before the media server.
◆ The name of the media server will appear as the Host server name in the left
window pane of the NetBackup Administration Console if any of the following
conditions exist:
◆ The master server has not been installed.
◆ The media server does not have permissions set on the master server.
◆ A network problem exists blocking the media server from communicating
with the master server.
Caution If any of these situations exist, you will still be presented with the opportunity
to run three of the configuration wizards (Storage Device, Volumes, and
Configure a Shared Drive). Do not run these wizards. If you run these wizards,
the information that you enter will not be recognized by the master server.
VERITAS recommends that you correct the problem (such as installing the
master server, correcting the permission settings, or solving the network
problem) and run the configuration wizards from the master server.
Configuring NetBackup
To begin configuring your product, click on the Getting Started icon in the main window
of the NetBackup Administration Console. The Getting Started - Welcome to NetBackup
window appears. This will lead you through a series of wizards designed to make it easy
for you to configure the following:
◆ Configure Storage Devices for NetBackup
◆ Configure Volumes
◆ Configure the Catalog Backup
◆ Create a Backup Policy
The following subsections contain helpful tips as you step through the wizard. For
detailed information about the NetBackup Administration Console, or a particular part of
a wizard, refer to the NetBackup System Administrator’s Guide for Windows.
c. Verify all installation procedures specified by the device and operating system
vendor have been performed successfully.
Note The VERITAS Tape Device Driver Install wizard (preloaded on your CD-ROM) will
step you through the process of installing the latest device drivers. If you do not
have a CD-ROM, you can download the NetBackup Tape Installer software from
the VERITAS support web site.
Configuring Volumes
This procedure enables you to initiate an inventory process of each configured robot.
NetBackup automatically updates the volume database if it finds new robotic media
during the inventory. In addition, you can define new volumes for use in standalone
drives. For more detailed information about volumes or configuring volumes for
standalone drives, refer the to Media Manager System Administrator’s Guide.
◆ Select a robot to inventory or the drive type that you want to configure.
◆ If you specify a standalone media, you will determine the number of volumes for
your device, and complete this process.
◆ If you specify multiple drive types the following is true:
◆ A robot is considered to have more than one type of drive if the media written in
any one drive cannot be read or written in any other drive.
◆ If the robot has more than one type of drive, then the wizard cannot inventory the
robot.
◆ After the inventory process of your device completes, the software prompts you to
identify which slots within your device contain cleaning media.
If you have just upgraded NetBackup and have pre-existing bar-code rules, then the
bar-code reader will automatically detect slots designated for cleaning media.
Otherwise, if you do not designate a cleaning slot(s), then NetBackup will consider all
media (including cleaning media) as typical media and try to overwrite it.
◆ This wizard does not enable you to configure cleaning tapes for standalone drives.
Caution Make sure there are no invalid paths in the list of catalog files to be backed up,
especially after moving catalog files, deleting old paths, or adding new paths to
the catalog backup configuration as explained in this chapter. If NetBackup
cannot find or follow a path, the entire catalog backup fails. If you have
installed NetBackup in a MSCS or VCS 1.2.1 for NT cluster environment, verify
that the NetBackup Catalog Backup entries are correct. See the NetBackup
System Administrator’s Guide for Windows, Volume I for more information.
◆ The Alternating Destinations window enables you to specify a second location for
backing up the Catalog.
1. Click the Start an immediate backup of NetBackup server to verify the installation
check box.
2. Click Next. The Getting Started - Setup is Complete window appears. You have
completed a basic installation and configuration of NetBackup.
3. After you click Finish, NetBackup will begin the backup process according to your
installation configuration.
In addition, the help is auto-started and the Activity Monitor in the NetBackup
Administration Console updates and monitors the status of this backup. You can view
this status by selecting the Activity Monitor in the NetBackup Administration
Console.
You can then click the right mouse on the picture of the server in the Topology
window pane and select Job Details. The Job Details window appears and provides a
status of the current job.
83
Installing NetBackup on Microsoft Windows Clients
Installation Overview
The NetBackup client setup program for Microsoft Windows allows you to select
appropriate setup and installation options from a series of windows. Once the options
have been selected, the NetBackup client setup program displays a window that enables
you to verify your selections before continuing with the actual install.
While the installation is in progress, a dialog window provides details of the installation
and setup progress. When complete, a final window indicates the results of the
installation.
Note You cannot install NetBackup client software on PCs that currently have NetBackup
server software installed. In these cases, you must first uninstall the NetBackup
server software.
◆ Local installations - the setup program installs the client software only on the PC
where the installation is started.
◆ Remote installations - the setup program scans your network for available clients
where you can install the client software. The source PC (or primary node) must have
Windows NT, Windows 2000, Windows XP, or Windows 2003 server installed. In
addition, a remote installation requires system administrator privileges and is only
available for Windows NT, Windows 2000, 32-bit Windows XP, and32-bit Windows
2003 machines.
Note You cannot remote install from a UNIX system to Windows NT, Windows 2000,
Windows XP, or Windows 2003 machines.
Local and remote installations can be either new or upgrade installations, depending on
whether there is any existing NetBackup client software installed on the client PCs.
Silent Installations
A silent installation is one where the installation process does not require interactive
input. It does, however, require input in the form of editing the silentclient.cmd file
before execution.
New Installations
NetBackup setup enables you to specify one set of configuration options to be used for all
new installations. These options include:
For typical and custom installations:
◆ Specifying master and media server names
For custom installations only:
◆ Specifying an installation directory (local install only)
◆ Entering bpcd and bprd port numbers
◆ Starting the NetBackup Client Service automatically or manually
◆ Starting the NetBackup Client Service on the client after installation is complete
◆ Starting the NetBackup Client Job Tracker automatically
◆ Installing VSP
◆ Installing debug symbols
◆ Installing the NetBackup documentation
System Requirements
This section describes the hardware and software that is required for successful
installation of NetBackup software.
◆ The person performing the remote installation must have administrator privileges on
all of the client PCs.
NetBackup Server
◆ This version of the NetBackup server software or later must be installed.
6. When prompted to choose where you want to install the NetBackup client software,
select Install to this computer only.
8. Click Next.
10. Click Install to initiate the installation and Finish when the install is complete.
Note You may need to reboot your PC for the changes to take effect.
4. When prompted to select where you want to install the NetBackup client software,
choose Select from available computers on the network.
Note If you choose Select from available computers on the network, the client will not
be installed on the local machine unless it is added to the list of systems to which
you are going to install.
6. Click Next.
8. Click Install to initiate the installation and Finish when the install is complete.
Note Clicking the Cancel button anytime after you have clicked the Install button and
started the remote install process will not cancel the install on the remote system
that is in progress at the time Cancel is clicked. The installation will continue until it
is finished. Any remote installs that remain will not be performed, and any remote
installs that were successful to that point will continue to be successful.
Note You may need to reboot your PC or the remote systems for the changes to take
effect.
A silent installation is one where the installation process does not require interactive
input. It does, however, require input in the form of editing the silentclient.cmd file
before execution.
Follow these instructions to perform a silent installation of the NetBackup client software
on selected Windows clients on your network (one of these clients can be your local PC).
Note Do not run instmsiw.exe on Windows 2000, Windows XP, or Windows 2003
Server systems.
3. Copy the contents of the PC_Clnt\ directory to a temp folder on your hard drive
(for example, C:\temp).
4. The files contained on the CD-ROM are read-only. Change the permissions for these
files on the hard drive to allow the update.
5. In the temporary directory, use a text editor to edit the silentclient.cmd file so
the script will install the client software as you wish.
Note Be sure to update the client, master server, and additional servers to the minimum
required version level of NetBackup.
7. Check the NetBackup Install.log log file to verify that the install was
successful. The following procedures will help you locate the proper log file.
▼ Locating the NetBackup Installation log file for Windows 2000 and newer systems
a. Select Start > Programs > Accessories > Command Prompt. A Command Prompt
window appears.
b. Enter echo %TEMP% and press the Return key on your keyboard. The location of
your TEMP directory will display.
a. Select Start > Settings > Control Panel. The Control Panel window appears.
Note Make sure you can view all hidden files and folders. To set this option, select Tools
> Folder Options... in the Control Panel window. Then click the View tab; set the
Show hidden files and folders option, and click the OK button.
c. Click the Environment tab. The Environment Variables including the TEMP variable
will appear along with the corresponding paths for each variable.
Note You may need to reboot the PCs for the changes to take effect.
1. Open the Windows Control Panel (select Start, Settings, and then Control Panel).
Note If you are running NetBackup on a Windows NT, Windows 2000, Windows 2003
Server computer, or if there is a firewall that prevents remote installation, you
cannot push an install to a UNIX client. You must install UNIX clients locally.
The Macintosh OS X10.2.x clients are UNIX-based clients and as such, you should
follow the UNIX client installation procedures that follow.
◆ Locally: you must install the client software locally if remote installation is not
possible. Remote installation is not possible if your NetBackup server is a
Windows NT, Windows 2000, or Windows 2003 computer or if there is a firewall
that prevents remote installation.
To install NetBackup locally on IBM zSeries Linux clients, you must transfer the
contents of the NetBackup CD-ROM image to a location that is readable by the
virtual Linux environment. This can be done by using FTP or NFS mounting
commands.
◆ Remotely: you can “push” the client software from your UNIX NetBackup server
to your UNIX client computers. This is the preferred method of installing. To push
a UNIX client, the software for that type of UNIX computer must first be loaded
onto your UNIX server. If you did not choose to do this during the installation of
your UNIX server, do so now by following the instructions provided in “Adding a
UNIX Client Type After Initial Server Installation” in the NetBackup Installation
Guide for UNIX. Clients such as NetBackup to the IBM zSeries Linux, may not
have a locally mounted CD-ROM device, making it impossible to perform a
standard local install. To install NetBackup to clients with no local CD-ROM
drive, you must push the NetBackup installation from a UNIX master server. For
instructions on how to install NetBackup on a secure client, refer to “Installing
NetBackup Software on Secure UNIX Clients” on page 98. For instructions on
how to install NetBackup on an unsecure client, refer to “Installing NetBackup
Software on Trusting UNIX Clients” on page 95.
To initiate a backup or a restore from a UNIX client computer, the following graphical
interfaces are available:
◆ Clients that are compatible with NetBackup-Java will use the NetBackup-Java
interface (jbpSA). Refer to the NetBackup Release Notes for a list of NetBackup-Java
capable hosts.
◆ Clients that are not compatible with NetBackup-Java will use the xbp interface
(except the Macintosh OS X 10.2.x). Refer to the NetBackup Release Notes for UNIX
and Windows for a list of clients with xbp installed. In addition, for instructions on
how to use the xbp interface, see the NetBackup System Administrator’s Guide,
Volume I.
Note For this release, the IBM zSeries Linux clients (Linux SuSe and Linux RedHat) do
not support the NetBackup-Java Administration Console or the xbp interface.
Note Macintosh OS X 10.2.x and FreeBSD are available through the bp interface or from a
Solaris, HP-UX, AIX, Tru64, or Linux NetBackup client console using the jbpSA
command.
1. Insert the NetBackup CD-ROM into the drive on the client computer.
b. Macintosh OS X 10.2.x systems only: you can access the CD-ROM from:
◆ /volumes/<cd name>
Note The binaries provided for the client OS levels represent the OS levels on which the
binaries were compiled. Often the binaries will function perfectly on newer versions
of the operating system. For example, Solaris 7 binaries also are used on the
The install script attempts to load the appropriate binaries for your system. If the
script does not recognize the local OS, it will present choices to the user.
Note In a clustered environment, the capability to push client software is only available
from the active node.
A trusting UNIX client is one that has an entry for the server in its /.rhosts file. The
/.rhosts entries enable software installation, but are not necessary for correct operation
of NetBackup software.
Note Add the trusting clients to a backup policy, if this has not already been done.
Note For Macintosh OS X 10.2.x users: By default, Macintosh OS X 10.2.x does not enable
the remote shell daemon (rshd). You must enable this daemon to perform the
following procedure successfully. You can enable rshd by removing the
commenting in the “shell” line in the /etc/inetd.conf file and sending an HUP
signal to the inetd process.
3. Click the Policies icon in the left window pane. The All Policies window pane
populates with a list of available policies.
6. In the Don’t install these clients window, select the clients you want to install and
click the Add >> button.
The clients are moved to the Install these clients window.
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/ as
a link to that directory prior to installing software.
Note Add the secure clients to a backup policy, if this has not already been done.
Note For Macintosh OS X 10.2.x users: By default, Macintosh OS X 10.2.x does not enable
the FTP daemon (ftpd). You must enable this daemon to perform the following
procedure successfully. You can enable ftpd by checking Allow FTP access in the
sharing pane of the System Preferences application.
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
To move software to all clients at once, execute:
/usr/openv/netbackup/bin/install_client_files ftp ALL user
Where the options are defined as follows:
◆ client is the hostname of the client.
◆ user is the login id required by ftp on the client.
◆ ALL specifies that you want to install all clients which are configured in any
backup policy 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.
Note In a clustered environment, the capability to push client software is only available
from the active node.
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 or xinetd.d directory as appropriate.
Note In a clustered environment, the following steps should be performed on the active
node.
3. Use the install program to load the client software onto the NetBackup server.
./install
5. Follow the prompts, selecting the additional client platforms that you want.
Note The binaries provided for the client OS levels represent the OS levels on which the
binaries were compiled. Often the binaries will function perfectly on newer versions
of the operating system. For example, Solaris 7 binaries also are used on the
Solaris 8 level of the operating system.
Note If your master server is NetBackup-Java capable and the client being added is
NetBackup-Java capable, then you will receive a message during this process
informing you to run option 3, to install the NetBackup client Java software.
8. You must now install the NetBackup client software on these additional client
computers, as described earlier in this chapter. Refer to “Install Client Software
Remotely” on page 95).
Caution The rm -f /usr/openv command will also uninstall any add-on products
installed on this machine.
Note For Macintosh OS X 10.2.x systems, the NetBackup installer updates the
/services directory of the Netinfo database with these entries. To uninstall
NetBackup and its services from one of these clients, you must use the NetManager
utility to remove bpcd, bpjava-msvc, bprd, vnetd, and vopied from the
/services directory in the Netinfo database.
5. Execute the following two shell commands to cause inetd to read the updated
inetd.conf (or inetd.local) file.
b. Run the kill command as follows. The process ID is the first number displayed
in the output from the ps command.
kill -1 process_ID
The ps command options may vary from one client platform to another.
Note There should be no space between the slash “/” and the period “.” of
“/.nbjava”. Adding a space between these characters removes all of your files
starting from the root level.
7. Inform users of this machine that they can remove their $HOME/.nbjava and
portions of $HOME/.java directories.
The $HOME/.nbjava and $HOME/.java directories contain application state
information (for example, table column order and size) that is saved when the user
exits NetBackup-Java applications.
The common subdirectory in $HOME/.java/.userPrefs/vrts can be removed.
105
Entering License Keys
Agent license key will turn on the NetBackup 5.0 Oracle Agent in a NetBackup 5.0
Enterprise Server environment. And a NetBackup 4.5 BusinesServer Oracle agent will
turn on the NetBackup 5.0 Oracle agent in the NetBackup Server environment.
What does the license key look like? What information does it contain?
The key is a multi-digit alphanumeric string (for example:,
8EPP-ABCD-9XYZ-XYZ9-8881-VCF4-OIUF-AJDC). It contains information on whether
the key is for NetBackup Server or NetBackup Enterprise Server, whether it is for a server,
client, agent, or option (and which one), whether it is a permanent or evaluation key, and
information about how and where the key was generated.
Note You will still need a unique key for each type of NetBackup component purchased -
NetBackup server, Lotus Notes agent, NDMP option, UNIX client, and so forth.
Note VERITAS Technical Support will not issue permanent keys. This can only be done
through VERITAS Order Management. However, Technical Support is prepared to
provide temporary one-month keys to you to keep you up and running while any
issue regarding permanent license keys is resolved.
Release Notes
◆ VERITAS NetBackup Release Notes for UNIX and Windows
NetBackup_Release_Notes.pdf
Provides important information about NetBackup on UNIX- and Windows-based
servers, such as the platforms and operating systems that are supported and
operating notes that may not be in the NetBackup manuals or the online help.
Installation Guides
◆ VERITAS NetBackup Installation Guide for Windows
NetBackup_Install_Win.pdf
Explains how to install NetBackup software on Windows-based platforms.
◆ VERITAS Security Services Installation Guide
VxSS_InstallGuide.pdf on the VERITAS Security Services CD-ROM.
Explains install and configure the VERITAS Security Services.
111
System Administrator’s Guides - Basic Product
NetBackup_AdminGuide_LotusNotes_Win.pdf
Explains how to install, configure, and use NetBackup for Lotus Notes to back up and
restore Lotus Notes databases and transaction logs on a Windows client.
◆ VERITAS NetBackup for Microsoft Exchange Server System Administrator’s Guide
NetBackup_AdminGuide_MSExchg_Win.pdf
Explains how to configure and use NetBackup for Microsoft Exchange Server to
perform online backups and restores of Microsoft Exchange Server.
◆ VERITAS NetBackup for Microsoft SQL Server System Administrator’s Guide for Windows
NetBackup_AdminGuide_MSSQL_Win.pdf
Explains how to install, configure, and use NetBackup for Microsoft SQL Server to
back up and restore Microsoft SQL Server databases and transaction logs.
◆ VERITAS NetBackup for NDMP System Administrator’s Guide
NetBackup_AdminGuide_NDMP.pdf
Explains how to install, configure, and use NetBackup for NDMP to control backups
on an NDMP host.
◆ VERITAS NetBackup for Oracle System Administrator’s Guide for Windows
NetBackup_AdminGuide_Oracle_Win.pdf
Explains how to install, configure, and use NetBackup for Microsoft Oracle to back up
and restore Oracle databases that are on a Windows NetBackup Client.
◆ VERITAS NetBackup for SAP System Administrator’s Guide for Windows
NetBackup_AdminGuide_SAP_Win.pdf
Explains how to install, configure, and use NetBackup for SAP on Windows-based
servers.
◆ VERITAS NetBackup for SYBASE System Administrator’s Guide on Windows
NetBackup_AdminGuide_Sybase_Win.pdf
Explains how to install, configure, and use NetBackup for SYBASE to back up and
restore Sybase databases that are on a Windows NetBackup client.
◆ VERITAS NetBackup Global Data Manager System Administrator’s Guide for UNIX and
Windows
NetBackup_AdminGuide_GDM.pdf
Explains how to install, configure, and use Global Data Manager (GDM) for
NetBackup on UNIX and Windows-based operating systems.
◆ VERITAS NetBackup Vault System Administrator's Guide for UNIX and Windows
NetBackup_AdminGuide_Vault.pdf
Describes how to configure and use logical vaults and profiles to duplicate backups,
perform catalog backups, eject media, and generate reports.
◆ VERITAS NetBackup Advanced Reporter System Administrator's Guide for UNIX and
Windows
NetBackup_AdminGuide_AdvancedReporter.pdf
Explains how to install, configure, and use NetBackup Advanced Reporter to monitor
and report on Netbackup activities.
User’s Guides
◆ VERITAS NetBackup User’s Guide for Windows
NetBackup_UserGuide_Windows.pdf
Explains how to use NetBackup on a Microsoft Windows clients to perform backups,
archives, and restores. This guide also contains some configuration instructions for
the NetBackup Backup, Archive, and Restore software.
◆ VERITAS NetBackup Vault Operator's Guide for UNIX and Windows
NetBackup_OperGuide_Vault.pdf
Describes procedures for sending tapes offsite, receiving tapes on site, and running
reports on offsite media and vault jobs.
◆ VERITAS NetBackup Administrator's Guide for Novell NetWare Client
NetBackup_AdminGuide_NetWare_Client.pdf
Explains how to install and use the NetBackup’s NetWare Client software. With the
NetWare Client, full and incremental backups can be scheduled to occur
automatically and unattended under the control of the NetBackup master server. The
NetWare Client also provides two methods for performing user-directed backups and
restores: Target, which uses a character-based, menu-driven interface running on the
NetWare server, and NonTarget, which uses the NetBackup for NetWare NonTarget
Browser that is installed and run from a Windows computer.
Troubleshooting Guide
◆ VERITAS NetBackup Troubleshooting Guide for UNIX and Windows
NetBackup_Troubleshoot_Guide.pdf
NetBackup Commands
◆ VERITAS NetBackup Commands for Windows
NetBackup_Commands_Win.pdf
Describes NetBackup and Media Managercommands and processes that can be run
from a Windows command prompt.
117
locally 94 N
install_client_files script 98 NetBackup
Installation architecture 2
silent install custom installation 16
media server software 47 Device Database Host 21, 40, 74
server software 46 installation 13
installation installing 16
NetBackup Remote Administration peripherals 15
Console 64 port numbers 16
servers silent installation 46
procedure 16 upgrade 50
upgrade 50 NetBackup Access Control 23
UNIX clients 94 NetBackup Administration Console 8, 77
locally from CD-ROM 99 NetBackup client service 86
secure 98 NetBackup client software
trusting 96 add a UNIX client type 99
installation log file install locally 94
Windows 2000 systems 22, 75, 91 install on secure UNIX clients 98
Windows NT systems 23, 75, 91 NetBackup clients 5
installing NetBackup Java Windows Display Console
client software install requirements 68
Windows 87, 88, 90 installation 68
overview NetBackup license keys 105
Macintosh OS X and OS server 103 NetBackup Remote Administration
Windows 84 Console 16, 21, 31, 73
remotely installing 63, 67
Windows 29, 35, 52, 85, 86, 88 NetBackup software 14
requirements custom installation 25
Windows 86 installation 17
installing alternative administration installation requirements 14
interfaces 63 NetBackup upgrade installation 49
installing NetBackup 1 notes 50
Internet Explorer 15, 86 requirements 50
NetBackup wizards 10
L
NetBackup, functions 1
license key 17
Novell 5
license keys 20, 30, 37, 54, 73, 106
NTFS partition 15
license keys, administering 51
Linux 5 O
on-line documentation 15
M
OTM
Macintosh 5
Windows 84
Master server 3
media 7 P
Media and Device Management 8 ping command 15
media manager 7 policy 1
Media server 4, 21, 32, 39, 56, 73 private network 39
Microsoft Windows ix, 83 public network 39
Index 119