Veritas NetBackup

From The System Administrator Zone

Configuration Options

How do BAR CODE RULES work?

From the Veritas-bu e-mail list:

You can use media ID generation rules on your vm.conf file as follows:

The media ID generation rule has the following syntax:
The robot_number is the robot number, barcode_length is the number of characters in the media's barcode format,

  • c1 is the first character of the Media ID
  • c2 is the second character of the Media ID
  • c3 is the third character of the Media ID
  • c4 is the fourth character of the Media ID
  • c5 is the fifth character of the Media ID
  • c6 is the sixth character of the Media ID

  • c1-c6 can specify a character from the media barcode or specify a fixed character by prefixing the character with a "#".

MEDIA_ID_BARCODE_CHARS 0 8 #N:1:3:4:5:6 generates media IDs for robot 0 using the character N and the 1st, 3rd, 4th-6th characters of the 8 character barcode, and for the barcode, 123456L1 generates media ID N13456.
MEDIA_ID_BARCODE_CHARS 0 8 1:2:3:4:5:6 generates media IDs for robot 0 using the 1st-6th characters of the 8 character barcode, and for the barcode 006498L2 generates media ID 006498.

Exclude and Include Lists

The exclude and include lists go on the client system and refer to all automatic policies, full and incremental, that backup that particular client. Exclude and include lists do not apply to user backups and archives.

If you want to exclude them from only a certain policy or schedule the, the list file name would be in the form of:


Syntax Rules

The following syntax rules apply to exclude lists:

  • Blank lines or lines beginning with a pound sign (#) are ignored.
  • Only one pattern per line is allowed.
  • The following special or wildcard characters are recognized: [ ] ? * { }
  • A single back-slash acts as an escape character only when it precedes a special or wild card character


  • End a file path with / to exclude only directories with that path name (/tmp/example/dir/). If the pattern does not end in / (/tmp/example/dir), NetBackup excludes both files and directories with that path name.
  • To exclude all files with a given name, regardless of their directory path, just enter the name without a preceding slash. For example: "example" rather than "/example" This is equivalent to prefixing the file pattern with all of /, /*/, /*/*/, /*/*/*/ and so on.
  • Do not use patterns with links in the names. For example, assume /home is a link to /usr/home and /home/doc is in the exclude list. The file is still backed up in this case because the actual directory path, /usr/home/doc, does not match the exclude list entry, /home/doc.

Here is an example *exclude_list*

# this is a comment line


Include lists can only include files and directories that are listed in the exclude lists so that they are not excluded.

Where is the Veritas-bu e-mail list?

See: Veritas-bu

Also: NetBackup FAQ

In the problem reports: WRN - could not reset access time of /etc/mnttab

When NetBackup sends a file to the media server, it stores the access time before opening the file, to reset if after the transfer is finished.

This message means another application has accessed the file while it was sent by the client - this is informational only.

netbackup "global database host not responding"

Running jnbSA, I received the "global database host not responding", followed by the name of the wrong host. To check the global database host setting, use;
/opt/openv/volmgr/bin/vmglob -get_gdbhost

To set it to the correct value, use;
/opt/openv/volmgr/bin/vmglob -set_gdbhost [desired-hostname]

What is the difference between jnbSA and jbpSA?

jnbSA is used to start the netbackup administrator's interface on the server.
jbpSA is used to start the netbackup client-user interface on the client.

Installing a client when the automatic tool fails

The the client installation script is not clearly documented and will only work from the GUI if you allow rsh connections.

Say, for example, you want to install a RedHat client using the 2.6 kernal. This can be done with ssh this way;

/usr/openv/netbackup/client/Linux/RedHat2.6/install_client ssh CLIENTHOSTNAME

However, given that consistency is the sign of an idle mind, for a Solaris or SuSE client you need a different route.

/usr/openv/netbackup/client/Solaris/Solaris10/ssh_to_client CLIENTHOSTNAME

/usr/openv/netbackup/client/Linux-IA64/SuSE2.6/ssh_to_client CLIENTHOSTNAME

If you don't have things setup for automatic SSH connectivity, you will have to enter the root password of the remote system at least three or four times.

NB-Java.tar.Z is missing

On Solaris systems, you may run into the error:

/usr/openv/NB-Java.tar.Z: No such file or directory

You will need to copy this file from the installation CDs.

Configuring the Linux xinetd services


# default: on
service bpcd
        flags           = REUSE
        socket_type     = stream
        wait            = no
        user            = root
        server          = /opt/openv/netbackup/bin/bpcd
        log_on_failure  += USERID
        disable         = no


# default: on
service vopied
        flags           = REUSE
        socket_type     = stream
        wait            = no
        user            = root
        server          = /opt/openv/bin/vopied
        log_on_failure  += USERID
        disable         = no


# default: on
service bpjava-msvc
        flags           = REUSE
        socket_type     = stream
        wait            = no
        user            = root
        server          = /opt/openv/netbackup/bin/bpjava-msvc
        server_args     = -transient
        log_on_failure  += USERID
        disable         = no

Netbackup Information Links

Backup Central Netbackup FAQ
TekTips Netbackup FAQ
Veritas NetBackup (tm) 5.0 Manuals
Veritas NetBackup (tm) 5.1 Manuals
Veritas NetBackup (tm) 6.0 Manuals
Veritas NetBackup (tm) 6.5 Manuals

Veritas NetBackup TechNotes

Top Ten Recommended Veritas NetBackup TechNotes
NetBackup 6.0 jobs are failing with Status 800 (resource request failed)

Adding a Red Hat x64 Client

Some Veritas binaries depend upon 32-bit operating system libraries instead of 64-bit libraries.

The 32-bit version of the required dependencies listed in the error(s) (GLIBCXX_3.4, ACL_1.0) must be installed prior to Veritas product installation.

Missing Libaries


The 32-bit version of the required libraries are available from the RHEL 4 distribution CDs, or via the Red Hat Network Update functionality that is built into the Operating System.

Client / Server Authorization

If you get the error:

status 59: access to the client was not allowed

Unix Clients

Edit /usr/openv/netbackup/bp.conf file and ensure that there is a “SERVER=” line for any Master and Media Servers that connect to the client.

NetWare and OS/2 Clients

Add a SERVER entry in the Sys\openv\netback\bp.ini file as needed.

Windows Clients

  1. Open the Backup, Archive, and Restore interface.
  2. Select File > “Specify NetBackup Machines and Policy Type”.
  3. Select the “Servers” tab.
  4. Verify that the Master/Media Server(s) are added to this server list, and that the Master Server is set as “current”.
  5. Click OK after adding any needed servers and exit Backup, Archive and Restore.

Tape Tricks

Most commands are hiding in the /usr/openv/netbackup/bin/admincmd directory.

Expire a Previously Used Tape

Prompt for a reply before expiring the media

bpexpdate <media id> 0 d -ev

Force the media to expire, without prompting for a confirmation

bpexpdate <media id> 0 d -force -ev 

Unfreeze a Tape

bpmedia -unfreeze -ev <media id>

ltid can not be started while resources are assigned to the host.

If you get the proceeding error message;

  • nbrbutil -dump* output shows media server resources still allocated for the media server.

The fix is to reset the media server.

  • nbrbutil -resetMediaServer <media server>*

Windows Notes

Starting / Stopping Netbackup on a Windows server

  • C:\Program Files\VERITAS\NetBackup\bin\bpup.exe
  • C:\Program Files\VERITAS\NetBackup\bin\bpdown.exe

See Also