Veritas Netbackup 4.X bperror Codes
Error Number: 0
the requested operation was successfully completed
There were no problems detected with the requested operation.
None, unless this was a database backup performed through a database extension p
roduct (for example, NetBackup for Oracle or NetBackup for SQL Server). In those
instances, code 0 means the backup script that started the backup ran without e
rror. However, you must check other status as explained in the related NetBackup
manual to see if the database was successfully backed up.
Error Number: 1
the requested operation was partially successful
A problem that may require corrective action was detected during the requested o
peration.
Check the All Log Entries report and also the progress log (if there is one). So
me of the problems that can show up under status code 1 are:
* A file or directory path that is more than 1023 characters long.
For NetBackup ServerFree Agent: the maximum pathname length is 1000 character
s for frozen image backups, not 1023. When the frozen image is created, a new mo
unt point is added to the beginning of the file path. If this new mount point pl
us the original file path exceeds 1023 characters, the backup fails with status
code 1. The progress log includes the entry "ERR - Skipping long dir path."
* Could not open a file.
* On a UNIX system, NetBackup could not get the link name of a file.
* On a UNIX system, NetBackup could not process a sparse file.
* Read error encountered in a file.
* File is of an unknown type.
* On clients using Open Transaction Manager (OTM) for open file management, the
OTM cache may be full. See the recommended actions under status code 11.
* On a UNIX system, the lstat system call fails on a file that is eligible to b
e backed up. This may be a permission problem.
* On UNIX, a file could not be locked that has mandatory locking enabled.
* A vault job may terminate with status code 1 if non-fatal errors are encounte
red during one or more of the following operations:
* duplication
* suspension of unvaulted media
* expiration of disk images
* execution of vlt_ejectlist_notify script
* catalog backup
* eject and/or report
In the event of a non-fatal error, Vault will attempt to complete all the ste
ps configured in the vault profile.
Identify which of the above operations encountered an error by reviewing the
detail.log file in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Or review the vault debug log file in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Correct the problem and rerun the vault job.
Error Number: 2
none of the requested files were backed up
A backup or archive could not back up any of the files in the file list.
Verify that the files exist and you have read access to them.
* Check to see if there is a trailing space on one or more of the filenames in
the client's file list. Remove any inadvertent trailing characters (such as spac
es or tabs).
* On UNIX clients, check to see if the files or directories would be excluded b
ecause of an entry in /usr/openv/netbackup/exclude_list.
* On PC clients, check the exclude list per the instructions in the user's guid
e for the client.
* On Windows clients, verify that the account used to start the NetBackup Clien
t service has read access to the files.
If you are backing up a network drive or a UNC (universal naming convention)
path, use the Services application in the Windows Control Panel to verify that t
he NetBackup Client service does not start under the SYSTEM account. The SYSTEM
account cannot access network drives.
To back up network drives or UNC paths, change the NetBackup Client service s
tartup to log in as a user that has permission to access network drives.
Error Number: 3
valid archive image produced, but no files deleted due to non-fatal problems
The backup portion of the archive command reported problems so the files were no
t deleted.
Examine the progress log of the archive on the client to determine if you need t
o retry the archive after correcting the problem. If the problem is not serious
and the files were backed up, you can manually delete the files. To verify which
files were backed up, use the NetBackup client-user interface in restore mode a
nd browse the files in the archive. A possible cause for files not being deleted
is that you do not have the necessary permissions. NetBackup cannot delete file
s unless you are either the user that owns the files, a superuser on UNIX, or an
administrator on Windows.
Error Number: 4
archive file removal failed
The backup portion of the archive completed was successful but the delete failed
.
Verify that you have permission to delete the files and that the read-only flag
is not set for the files. On UNIX clients, verify that you have write permission
to the directories that contain the files. Since the backup was successful, you
can delete the files that were backed up (or have the system administrator dele
te the files if you do not have the necessary permissions).
Error Number: 5
the restore failed to recover the requested files
There were errors that caused the restore to fail.
Try the following.
1. Ensure that the client's server list contains entries for the master server
and for any media servers that could be used during a backup or restore.
2. Examine the progress log on the client for messages on why the restore faile
d. Also, check the All Log Entries report on the server.
3. On Windows and UNIX, check ownership and permission on directories where fil
es will be restored.
4. Correct problems that you find and retry the restore.
5. For NetBackup for EMC Fastrax: you may need to increase the CLIENT_READ_TIME
OUT and CLIENT_CONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.co
nf file. Although the optimal time-out values for your system may be different,
the following values may suffice:
CLIENT_READ_TIMEOUT = 3000
CLIENT_CONNECT_TIMEOUT = 3000
The safest approach is to increase the timeout values and rerun the restore.
Note, however, that the Fastrax system may have completed the restore successful
ly on its own, even though NetBackup experienced the timeout.
Error Number: 6
the backup failed to back up the requested files
Errors caused the user backup to fail.
Try the following.
1. Verify that you have read access to the files. Check the progress log on the
client for messages on why the backup failed. Correct problems and retry the ba
ckup.
2. On Windows clients, verify that the account used to start the NetBackup Clie
nt service has read access to the files.
3. On Macintosh clients, this code can be due to multiple backups being attempt
ed simultaneously on the same client. Some possible solutions are:
* Adjust the backup schedules.
* If the client is only in one policy, set the policy attribute, Limit jobs
per policy, to 1.
* Set the NetBackup global attribute, Maximum jobs per client, to 1 (note th
at this limits all clients in all policies).
4. For a UNIX database extension client (for example, NetBackup for Oracle), th
is can mean a problem with the script that is controlling the backup.
Check the progress report on the client for a message such as "Script exited
with status code = number" (the number will vary). The progress log also usually
names the script.
Check the script for problems. Also, check the troubleshooting logs created b
y the database extension. See the NetBackup guide that came with the database ex
tension for information on the scripts and troubleshooting logs.
Error Number: 7
the archive failed to back up the requested files
Errors caused the user archive to fail.
Verify that you have read access to the files. Check the progress log on the cli
ent for messages on why the archive failed. Correct problems and retry the archi
ve. On Windows clients, verify that the account used to start the NetBackup serv
ices has read access to the files.
Error Number: 8
unable to determine the status of rbak
On DomainOS clients, rbak is used to do restores. If rbak does not exit with a s
tatus message, NetBackup cannot determine whether the restore worked or not.
Check for a new core file to see if rbak aborted. Check the ps output to see if
rbak is hung. If so, kill it and try again. Check the progress log for any unusu
al messages from rbak.
Error Number: 9
an extension package is needed but was not installed
A NetBackup extension product is required in order to perform the requested oper
ation.
Install the required extension product.
Error Number: 10
allocation failed
Allocation of system memory failed because there is insufficient system memory a
vailable. This could be caused by the system being overloaded with too many proc
esses and not enough physical or virtual memory.
Free up memory by terminating unneeded processes that consume memory. Add more s
wap space or physical memory.
Error Number: 11
system call failed
A system call failed. This status code is used for a generic system call failure
that does not have its own status code.
Try the following.
1. Check the All Log Entries and Problems reports to determine which system cal
l failed and other information about the error.
2. For NetBackup ServerFree Agent:
* The file system specified as a frozen image source is not mounted. In this ca
se, you may see the following in the /usr/openv/netbackup/logs/bpbkar log:
17:12:51 bpbkar: FTL - frozen image processing failed, status 11
17:12:51 bpbkar: ERR - bpbkar FATAL exit status = 11: system call failed
17:12:51 bpbkar: INF - EXIT STATUS 11: system call failed
and the following in the /usr/openv/netbackup/logs/online_util log:
17:12:51 onlfi_vfms_logf: INF - cannot snap_on, err: 5
17:12:51 delete_mount_point: INF - Deleted mount point
/tmp/__jody_test:20958
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: nbu_snap, type: FIM,
function: nbu_snap_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 5; see following message:
17:12:51 onlfi_freeze: FTL - nbu_snap_freeze: Cannot turn on snapshot;
frozen image source=/opt, cache=/dev/rdsk/c1t3d1s0, snap error=5
17:12:51 onlfi_thaw: WRN - / is not frozen
Make sure that the file system specified for the frozen image source has been
mounted.
* The file system specified as the frozen image source does not correspond to t
he file system that contains the actual files (as opposed to symbolic links to t
he files). The mounted file system for the frozen image source must contain the
actual files, not symbolic links. If items in the file list, such as /oracle/dat
afile and /oracle, are actually symbolic links to /export/home/oracle, the froze
n image source must specify /export, or /export/home, not /oracle.
* vxvm is selected as the frozen image method but the frozen image source is no
t configured over a VERITAS Volume Manager VxVM volume. In this case, you may se
e the following in the /usr/openv/netbackup/logs/bpbkar log:
17:12:51 bpbkar main: FTL - frozen image processing failed, status 11
17:12:51 bpbkar Exit: ERR - bpbkar FATAL exit status = 11: system call failed
17:12:51 bpbkar Exit: INF - EXIT STATUS 11: system call failed
and something like the following in the /usr/openv/netbackup/logs/ online_uti
l log:
17:12:51 onlfi_vfms_logf: INF - vxvm_freeze: Frozen image source /cockpit1
on device /dev/dsk/c1t0d0s6 is not on a VxVM volume
17:12:51 delete_mount_point: INF - Deleted mount point
/tmp/_cockpit1_coc_group1:3518
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type: FIM, function:
vxvm_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 9; see following message:
17:12:51 onlfi_freeze: FTL - vxvm_freeze: Frozen image source /cockpit1 on
device /dev/dsk/c1t0d0s6 is not on a VxVM volume
17:12:51 onlfi_thaw: INF - fim=vxvm
17:12:51 onlfi_thaw: WRN - /cockpit1 is not frozen
Make sure that the frozen image source is configured over a VERITAS Volume Ma
nager VxVM volume.
* vxvm was selected as the frozen image method, but a VERITAS Volume Manager sn
apshot mirror of the frozen image source volume had not been created prior to ru
nning the backup, or if another backup is currently running that is using the sn
apshot mirror. In either case, you may see the following in the /usr/openv/netba
ckup/logs/online_util log:
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type: FIM, function:
vxvm_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 3; see following message:
17:12:51 onlfi_freeze: FTL - find_ready_snapshot: Cannot find available
snapshot mirror
As described under "Creating a Snapshot Mirror of the vxvm Frozen Image Sourc
e" in the NetBackup ServerFree Agent System Administrator's Guide, create a snap
shot mirror on the client before running the backup.
* vxvm was selected as the frozen image method, and a VERITAS Volume Manager sn
apshot mirror of the frozen image source volume has been created. However, two d
ifferent backup jobs (A and B) attempt to back up the same volume (for example,
vol01), but job A starts just before job B. Because there is a brief pause betwe
en finding an available snapshot mirror and actually forming the frozen image of
it, job B (running slightly behind job A) might attempt to create a frozen imag
e of the snapshot mirror just before job A (running slightly ahead) actually cre
ates the frozen image and gets the lock on it.
In this case, you may see the following in the /usr/openv/netbackup/logs/onli
ne_util log:
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: vxvm, type: FIM, function:
vxvm_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 3; see following message:
17:12:51 onlfi_freeze: FTL - vxvm_freeze: Command failed with status=11:
/usr/sbin/vxassist -g rootdg snapshot vol01 VfMSCAAu7a4Uw
/var/tmp/VfMSAAAs7a4Uw 2>/var/tmp/VfMSBAAt7a4Uw
The job that was unable to get a lock (job B in the above example) fails, and
must be run again.
* When using nbu_snap as a frozen image method, you may have stale snapshots if
status code 11 occurs with the following messages in the /usr/openv/netbackup/l
ogs/online_util log. (Stale snapshots are those that were not automatically dele
ted by nbu_snap.)
17:12:51 onlfi_freeze: FTL - VfMS error 11; see following messages:
17:12:51 onlfi_freeze: FTL - Fatal method error
17:12:51 onlfi_freeze: FTL - vfm_freeze: method: nbu_snap, type: FIM,
function: nbu_snap_freeze
17:12:51 onlfi_freeze: FTL - VfMS method error 5; see following message:
17:12:51 onlfi_freeze: FTL - nbu_snap_freeze: Cannot turn on snapshot;
frozen image source=/oracle/ufs_r, cache=/dev/rdsk/c4t1d11s4,snap error=11
a. Look for stale snapshots by running the /usr/openv/netbackup/bin/driver/s
naplist command when there are no active backups running. If the snaplist comman
d shows cache entries, there are stale snapshots. Nothing is displayed if there
are no stale snapshots.
Example snaplist output:
id ident size cached minblk err time
43 6515 8390970 0 0 0 11/16/00 13:31:36
device = /dev/rdsk/c1t6d0s0
cache = /dev/rdsk/c1t6d0s7
b. Use the snapoff command to remove the stale snapshot, as follows:
/usr/openv/netbackup/bin/driver/snapoff id
where id is the id from the snaplist output (such as 43 in the above examp
le).
* If a backup using the fsclone frozen image method failed, the NetBackup bpbka
r process should automatically remove the clone. Sometimes, however, bpbkar is u
nable to remove the clone. In this case, you may see messages such as the follow
ing in the /usr/openv/netbackup/logs/online_util log:
15:21:45.716 [4236] <4> create_mount_point: INF - Created mount point
/tmp/_vtrax_test_fastrax_dlt:4236
15:21:45.869 [4236] <2> onlfi_vfms_logf: INF - vxfs clone handle : 9600344
15:21:45.870 [4236] <2> onlfi_vfms_logf: INF - fsclone_freeze: Cannot create
checkpoint; status=17
15:21:45.872 [4236] <4> delete_mount_point: INF - Deleted mount point
/tmp/_vtrax_test_fastrax_dlt:4236
15:21:45.873 [4236] <32> onlfi_freeze: FTL - VfMS error 11; see following
messages:
15:21:45.873 [4236] <32> onlfi_freeze: FTL - Fatal method error was reported
15:21:45.873 [4236] <32> onlfi_freeze: FTL - vfm_freeze: method: fsclone,
type: FIM, function: fsclone_freeze
15:21:45.873 [4236] <32> onlfi_freeze: FTL - VfMS method error 17; see
following message:
15:21:45.874 [4236] <32> onlfi_freeze: FTL - fsclone_freeze: Cannot create
checkpoint; status=17
Remove the clone as follows.
Note: If the clone is not removed, you will not be able to use fsclone to back u
p any data in the file system where the clone is mounted.
a. List the name of the clone by entering the following VxFS command:
/usr/lib/fs/vxfs/fsckptadm list /file_system
where file_system is the name of the file system where the clone is mounte
d. Following is sample output. In this example, /vtrax_test is the file system a
nd fi_ckpt is the name of the clone.
/vtrax_test
fi_ckpt:
ctime = Mon Nov 12 10:08:13 2001
mtime = Mon Nov 12 10:08:13 2001
flags = largefiles
b. Remove the clone by entering the following:
/usr/lib/fs/vxfs/fsckptadm remove name_of_clone /file_system
c. If the clone cannot be removed, unmount the clone and retry step b.
* If a frozen image backup failed using one of the Extended Frozen Image Servic
es methods (TimeFinder, ShadowImage, BusinessCopy), there may be a VxVM clone le
ft over from a previous backup. You may see messages similar to the following in
the /usr/openv/netbackup/logs/online_util log:
19:13:07.686 [14981] <2> onlfi_vfms_logf: INF - do_cmd: Command failed with stat
us=20:
/usr/openv/netbackup/bin/bpdgclone -g wil_test -n vol01 -f /var/tmp/HDSTFCAAs7aO
qD
/var/tmp/VfMSAAAq7aOqD 2>/var/tmp/VfMSBAAr7aOqD
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- Dumping file /var/tmp/VfMSAA
Aq7aOqD (stdout):
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- End of file /var/tmp/VfMSAAA
q7aOqD
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - --- Dumping file /var/tmp/VfMSBA
Ar7aOqD (stderr):
19:13:07.687 [14981] <2> onlfi_vfms_logf: INF - clone group and volume alrea
dy exists
19:13:07.688 [14981] <2> onlfi_vfms_logf: INF - --- End of file /var/tmp/VfMSBAA
r7aOqD
NetBackup automatically creates VxVM clones for Extended Frozen Image Service
s backups of data configured over volumes. After the backup has completed, NetBa
ckup removes the VxVM clone. In this case, a system crash or reboot may have pre
vented the removal. Remove the clone as follows.
a. When no backups are running, use the following VxVM command to list any c
lones: vxdg list
The clone name will be of the form clone_disk_group_clone.
b. To remove the clone, enter the following:
/usr/openv/netbackup/bin/bpdgclone -g disk_group -n volume -c
For example:
/usr/openv/netbackup/bin/bpdgclone -g wil_test -n vol01 -c
where wil_test is the name of the disk group and volo1 is the name of the
VxVM volume.
For more information on removing a VxVM clone, refer to the NetBackup Serv
erFree Agent System Administrator's Guide. For vxdg, refer to the VERITAS Volume
Manager Administrator's Guide.
c. Before running the backup again, resynchronize the primary disk with the
secondary disk. For assistance, refer to the "Extended Frozen Image Services" ch
apter of the NetBackup ServerFree Agent System Administrator's Guide.
3. For NetBackup for EMC Fastrax:
If a backup fails with a status code 11, and the NetBackup progress log has a
message stating SYMINIT failed (see example log below), a /usr/symcli symbolic
link must be created that points to the SYMAPI libraries installed on your syste
m.
The following is an example progress log:
Backup started Thu 06 Dec 2001 03:53:52 PM CST
15:53:52 Initiating backup
15:54:01 ERR - SYMINIT failed status = -1
EXIT STATUS 11: system call failed
15:54:04 INF - Status = system call failed.
EMC releases several different versions of its SYMAPI library (libsymapi.so),
to support multi-threading, 32-bit and 64-bit machines, and so forth. The libra
ry name and install location vary, depending on your configuration.
When the SYMAPI library is being installed, the EMC package creates a link to
the correct library file name, but in some cases this link may not point to the
correct directory (/usr/symcli). This may happen if your installation has multi
ple packages, or if you install another version (such as multi-threaded, or 64-b
it symcli). Without the proper symbolic link, Fastrax backups will fail.
As a result, you may need to create a /usr/symcli symbolic link to the SYMAPI
shared libraries. For instance, NetBackup Fastrax must be able to find the foll
owing:
/usr/symcli/shlib/libsymapi.so
/usr/symcli/shlib/libsymlvm.so
The default symcli location is the following:
lrwxrwxrwx 1 root other 22 Dec 3 09:23 symcli ->
/opt/emc/SYMCLI/V4.3.2
Note that this example is for version 4.3.2.
4. A frequent cause is that the server's file system is full. For example, you
may see a message similar to the following in the Problems report or bpdbm debug
log:
06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11)
06/27/95 01:04:01 romb romb media manager terminated by parent process
06/27/95 01:05:15 romb romb backup of client romb exited with status 11
(system call failed)
On UNIX systems, run a df command on the /usr/openv/netbackup/db directory.
If the df command does not reveal the problem, check the bpdbm debug logs or
do a grep for the message
system call failed
in /usr/openv/netbackup/db/error/*
On Windows systems, verify that there is enough room in the disk partition wh
ere NetBackup is installed.
5. Verify that the system is not running out of virtual memory. If virtual memo
ry is the problem, shut down unused applications or increase the amount of virtu
al memory.
To increase virtual memory on Windows:
a. Display the Control Panel.
b. Double-click System.
c. On the Performance tab, set Virtual Memory to a higher value.
6. Check for a semaphore problem. This error can be caused by the system not ha
ving enough semaphores allocated. This is most commonly seen on Solaris 2 server
s when an RDBMS is also running.
The symptoms of the problem vary. In some cases, error messages in the NetBac
kup log indicate a backup failure due to an error in semaphore operation; anothe
r symptom is the inability of the NetBackup Device Manager service Media Manager
device daemon, ltid, to acquire a needed semaphore (this is the Media Manager D
evice Manager device daemon on UNIX).
System requirements vary; thus, no absolute recommendations can be made. One
customer running both NetBackup and ORACLE on their Solaris server made the foll
owing changes to their /etc/system file and then rebooted the system (boot -r);
the changes were found to be adequate:
set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600
Set these attributes to a value great enough to provide resources to all appl
ications on your system.
7. Check for a shared memory problem. This error can occur if the system cannot
allocate enough shared memory. This usually occurs when you use multiplexing, w
hich increases the shared memory requirements. A symptom is an entry similar to
the following in a NetBackup log (or report).
could not allocate enough shared memory
If you see this type of message, refer to the vendor documentation for your p
latform for instructions on increasing the amount of shared memory on your syste
m.
Because system requirements vary, no absolute recommendations can be made, ot
her than to use values great enough to provide resources to all applications. In
at least one instance, however, the following was found to be adequate on a Sun
platform:
set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmnu=600
set semsys:seminfo_semmns=300
After making the changes to the /etc/system file on the Sun platform and rebo
oting with boot -r, the problem was resolved. Note that in the above, shminfo_sh
mmin must be less than or equal to 100 for NetBackup processes to run.
8. Examine other debug logs or the progress log on the client.
9. If a backup on a Windows NetBackup client fails with status code 11 and the
client is using Open Transaction Manager (OTM) for open file management, it is p
ossible that the error was caused by the OTM cache file being full. If this is t
he case and bpbkar debug logs are turned on, a message similar to the following
should appear at the end of the backup:
04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005
04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled for all processes
04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!
If this error is encountered, try one of the following (the first is preferre
d):
* Set maximum OTM cache size to zero (0); at run time, OTM will determine ho
w much cache is needed and set it accordingly.
* Increase either the initial OTM cache size or the maximum OTM cache size o
n your own, depending on the requirements of your installation and your usage of
OTM.
If resizing OTM cache does not fix the problem, you may not have enough free
disk space.
Error Number: 12
file open failed
An open of a file failed.
Try the following.
* For NetBackup ServerFree Agent only:
Status code 12 may appear in the /usr/openv/netbackup/logs/bptm or bpdm log,
accompanied by the following:
tpc_read_config failed: cannot open file
/usr/openv/volmgr/database/3pc.conf
This may indicate that the policy is configured with either NetBackup Media S
erver or Third-Party Copy Device as the offhost backup method, but that the 3pc.
conf file does not exist or is in the wrong location. (When upgrading from NetBa
ckup 4.0V to 4.5, you must recreate the 3pc.conf file.) For instructions on crea
ting the 3pc.conf file, refer to the latest version of the NetBackup ServerFree
Agent System Administrator's Guide.
* Check the NetBackup Problems report. Try to determine the file and why the er
ror occurred. A possible cause is a permission problem with the file. For detail
ed troubleshooting information, create a debug log directory for the process tha
t returned this status code. Then, retry the operation, and check the resulting
debug log.
Error Number: 13
file read failed
A read of a file or socket failed. Possible causes include:
* I/O error reading from the file system.
* Read of an incomplete or corrupt file.
* Socket read failing. A socket read failure can be caused by a network problem
or a problem with the process that is writing to the socket.
* A problem specific to NetBackup ServerFree Agent (see recommended actions).
Try the following.
1. Check the NetBackup Problems report for clues on where and why the problem o
ccurred.
2. For a FlashBackup client, check the /var/adm/messages log for errors like th
e following:
Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache
/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable
This indicates that the cache partition is not large enough. If possible, inc
rease the size of the cache partition. Or, if multiple backups are using the sam
e cache, either reduce the number of concurrent backups by rescheduling some of
them or reschedule the entire backup to a time when the file system is less acti
ve.
3. For detailed troubleshooting information, create a debug log directory for t
he process that returned this status code, retry the operation, and check the re
sulting debug log.
4. For NetBackup ServerFree Agent only:
Status code 13 may appear in the /usr/openv/netbackup/logs/bpbkar log, and ca
n indicate the following:
* The files to back up reside on an IDE drive as opposed to SCSI, and the of
fhost backup method was set to either NetBackup Media Server or Third-Party Copy
Device. If you are using offhost backup, the disk containing the client files m
ust be a SCSI or Fibre Channel device.
If the disk is an IDE drive, you may see the following in the /usr/openv/
netbackup/logs/online_util log:
get_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed.
Errno = 25: Inappropriate ioctl for device
and the following may appear in the /usr/openv/netbackup/logs/bpbkar log:
bpbkar: INF - Processing /var
bpbkar: ERR - get_disk_info() failed, status 13
bpbkar: ERR - tpc_get_disk_info() failed: err 13
bpbkar: ERR - bpbkar FATAL exit status = 13: file read failed
bpbkar: INF - EXIT STATUS 13: file read failed
* The files to back up exist on a file system that is not mounted. The file sys
tem specified as the frozen image source must be mounted. If the frozen image so
urce is not mounted but the mount point is present, NetBackup may try to take a
frozen image of the directory above the directory that was specified as the froz
en image source.
Error Number: 14
file write failed
A write to a file or socket failed. Possible causes include:
* I/O error writing to the file system.
* Write to a socket failed. This can be caused by a network problem or a proble
m with the process reading from the socket.
* Writing to a full disk partition.
* The bpfsmap temporary directory (usually /tmp) became full (on Auspex FastBac
kup jobs).
Try the following.
* Check the NetBackup Problems report for clues on where and why the problem oc
curred.
* On Auspex FastBackup jobs (for NetBackup 3.0), increase the size of the /tmp
partition; there is a TMPDIR file which can be created for NetBackup 3.1.1.
* For detailed troubleshooting information, create a debug log directory for th
e process that returned this status code, retry the operation, and check the res
ulting debug log.
* Make sure that routers, bridges, and other network devices are all at "full"
duplex.
* Use a "sniffer" program to determine the number of packets being rejected and
/or re-requested.
* On Windows systems, the client bpbkar log may contain a 10054 "Connection Res
et Error"error (usually indicates a hardware error). Somewhere between the NetBa
ckup client and server, the connection was reset. When NetBackup receives this e
rror, it is unable to continue the backup. This error has been attributed to the
following:
* A hiccup in the network.
* A bad network interface card on a NetBackup client.
* A bad network interface card on the NetBackup server.
* Faulty routers.
* Other applications interfering with NetBackup connections.
* On Novell systems, status code 14 has also been attributed to network issues.
Try a "sniffer" program, as suggested above.
Error Number: 15
file close failed
A close of a file or socket failed.
Check the NetBackup Problems report for clues on where and why the problem occur
red. For detailed troubleshooting information, create a debug log directory for
the process that returned this status code, retry the operation, and check the r
esulting debug log.
Error Number: 16
unimplemented feature
The specified operation is unimplemented. This error should not occur through no
rmal use of NetBackup.
Save all error information and call customer support.
Error Number: 17
pipe open failed
Occurs in NetBackup client menu and vault areas.
None
Error Number: 18
pipe close failed
Close of a pipe failed, when one process tries to start a child process.
Check the NetBackup Problems report for clues on why the failure occurred. For d
etailed troubleshooting information, create a debug log directory for the proces
s that returned this status code, retry the operation, and check the resulting d
ebug log.
Error Number: 19
getservbyname failed
A call to getservbyname() failed. The getservbyname()function uses the name of t
he service to find a service entry in the services file (or NIS services map on
UNIX if it is configured).
Try the following.
1. Check the NetBackup Problems report for clues on why the failure occurred.
2. On a UNIX system, check that /etc/services and NIS services map (if applicab
le) have entries for the NetBackup services: bpcd, bpdbm, and bprd.
3. On a Windows system, verify that the %SystemRoot%\system32\drivers\etc\servi
ces file shows the correct entries for the NetBackup internet processes: bpcd, b
pdbm, and bprd.
Ensure that the NetBackup Client Service Port number and NetBackup Request Se
rvice Port number on the Network tab in the NetBackup Client Properties dialog m
atch the settings in the services file. To display this dialog, start the Backup
, Archive, and Restore interface and click NetBackup Client Properties on the Fi
le menu. The values on the Network tab are written to the services file when the
NetBackup Client service starts.
Also, see Verifying Host Names and Services Entries in the Troubleshooting Gu
ide.
4. Check the level of network activity. An overloaded network can cause this er
ror.
5. If the above actions do not reveal the problem, create a debug log directory
for the process that returned this status code, retry the operation, and check
the resulting debug log.
Error Number: 20
invalid command parameter
One or more command parameters were not valid. This error can occur when a maste
r and its media servers or a master server and a client have different levels of
NetBackup installed. For example, if a NetBackup master server has NetBackup 4.
5 and the media server has NetBackup 3.4. This error can also occur if the wrong
parameters are used when executing a command line.
Try the following.
1. Check the NetBackup Problems report for clues.
2. If the error occurs when executing a command on the command line, verify tha
t the parameters are valid.
3. For NetBackup ServerFree Agent:
* If the following appears in the /usr/openv/netbackup/logs/bptm log,
bptm: cannot perform Third-Party-Copy for multiplexed backups
send_brm_msg: ERROR 20
bptm: EXITING with status 20
multiplexing was enabled on a third-party copy backup. The Third-Party Cop
y Device offhost backup method is incompatible with multiplexing (the writing of
two or more concurrent backup jobs to the same storage device). You must disabl
e multiplexing for any third-party copy backups. If multiplexing is enabled, the
backup will fail.
* The media server may not have the correct 3pc.conf file entry for the clie
nt disk needed for the backup. The following appears in the /usr/openv/netbackup
/logs/bpbkar log:
14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1
EMC:SYMMETRIX:601092014000
14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive
child started, pid = 15822
14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:
15822 killed
14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1
14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain
device id string EMC:SYMMETRIX:601092014000
14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit
status = 227: no entity was found
14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no
entity was found
14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout
complete
This shows that a particular device cannot be found in the 3pc.conf file o
n the media server (14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obt
ain device id string EMC:SYMMETRIX:601092014000). The problem is one of the foll
owing:#{ ootnote }
Error Number: 21
socket open failed
A socket could not be opened.
Try the following.
1. Check the NetBackup Problems report for clues on where and why the failure o
ccurred. If you cannot determine the cause from the Problems report, create debu
g log directories for the processes that returned this status code. Then, retry
the operation and check the resulting debug logs.
2. On Sun Solaris, verify that all operating system patches are installed (see
the Operating Notes section of the NetBackup Release Notes).
3. On Windows, verify that the recommended service packs are installed.
Error Number: 22
socket close failed
A socket could not be closed.
Try the following.
1. Check the NetBackup Problems report for clues on where and why the failure o
ccurred. If you cannot determine the cause from the Problems report, create debu
g log directories for the processes that could have returned this status code. T
hen, retry the operation and check the resulting debug logs.
2. On Sun Solaris, verify that all operating system patches are installed (see
the Operating Notes section of the NetBackup Release Notes).
3. On Windows, verify that the recommended service packs are installed.
Error Number: 23
socket read failed
A read operation from a socket failed.
Try the following.
1. Check the NetBackup Problems report for clues on where and why the failure o
ccurred. If you cannot determine the cause from the Problems report, create debu
g log directories for the processes that could have returned this status code. T
hen, retry the operation and check the resulting debug logs.
2. Corrupt binaries are one possible cause for this error. For example, in one
instance, the following was seen in the bpsched debug log.
get_num_avail_drives: readline failed: socket read failed (23)
get_stunits: get_num_avail_drives failed with stat 23
Loading a fresh bptm from the install media resolved the problem.
3. On Sun Solaris, verify that all operating system patches are installed (see
the Operating Notes section of the NetBackup Release Notes).
4. On Windows, verify that the recommended service packs are installed.
5. This error may occur during a restore to a Novell client. Note the following
possible actions:
* By default, the value for Novell "Maximum Concurrent Disk Cache Writes" ma
y be too low (for example, 50); Novell recommends setting it to 100. A value of
100 increases the speed and efficiency of disk cache writes by increasing the nu
mber of write requests that can be executed at one time.
* Change to or add the following settings in the Novell sys:system\autoexec.
ncf file:
SET Maximum Packet Receive Buffers = 4000
SET Maximum Directory Cache Buffers = 4000
SET Maximum Concurrent Disk Cache Writes = 2000
SET Maximum Concurrent Directory Cache Writes = 2000
SET Maximum Physical Receive Packet Size = 1514
6. For NetBackup for EMC Fastrax: Increase the CLIENT_READ_TIMEOUT and CLIENT_C
ONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.conf file and retr
y the operation. Although the optimal time-out values for your system may be dif
ferent, the following values may suffice:
CLIENT_READ_TIMEOUT = 3000
CLIENT_CONNECT_TIMEOUT = 3000
Error Number: 24
socket write failed
A write operation to a socket failed.
Try the following.
1. Check the NetBackup Problems report for clues on where and why the failure o
ccurred. If you cannot determine the cause from the Problems report, create debu
g log directories for the processes that could have returned this status code. T
hen retry the operation and check the resulting debug logs.
2. A possible cause could be a high network load. For example, this has been se
en in conjunction with Cannot write to STDOUT when a Windows system that is moni
toring network load has detected a high load and sent an ICMP packet to other sy
stems that says the route being used by those systems was disconnected. The log
messages were similar to the following:
01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - C
annot write to STDOUT. Err no= 242: No route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.
null.com_0823125016, copy 1, fragment 1, 440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com POLICY Re
mote3SysFullW SCHED Sirius EXIT STATUS 24 (socket write failed)
3. On Sun Solaris, verify that all operating system patches are installed (see
the Operating Notes section of the NetBackup Release Notes).
4. On Windows, verify that the recommended service packs are installed.
5. This error may occur during a restore to a Novell client. Note the following
possible actions:
* By default, the value for Novell "Maximum Packet Receive Buffers" may be t
oo low (such as 100). The restore performance may be improved by changing this v
alue to 2000. To change it, issue "SET Maximum Packet Receive Buffers=" a
t the console, or enter the value in either of the following Novell files: sys:s
ystem\startup.ncf or sys:system\autoexec.ncf.
* Change to or add the following settings in the Novell sys:system\autoexec.
ncf file:
SET Maximum Packet Receive Buffers = 4000
SET Maximum Directory Cache Buffers = 4000
SET Maximum Concurrent Disk Cache Writes = 2000
SET Maximum Concurrent Directory Cache Writes = 2000
SET Maximum Physical Receive Packet Size = 1514
Error Number: 25
cannot connect on socket
A process timed out while connecting to another process for a particular operati
on. This problem can occur when a process tries to connect to the NetBackup requ
est daemon (bprd) or database manager daemon (bpdbm) and the daemon is not runni
ng. (On Windows, these daemons are the NetBackup Request Manager and NetBackup D
atabase Manager services.) It can also occur if the network or server is heavily
loaded and has slow response time, or if an evaluation license key for NetBacku
p BusinesServer or DataCenter has expired.
Try the following.
1. On a UNIX NetBackup master server, verify that the bprd and bpdbm processes
are running. If these processes are not running, start them. On aWindows master
server, verify that the NetBackup Request Manager and NetBackup Database Manager
services are running. If these services are not running, start them.
If the above processes are running, examine the All Log Entries report for th
e time of the failure to determine where the failure occurred.
* If you cannot view the report, or you get a "cannot connect on socket" err
or when trying to view it, verify again that the NetBackup Database Manager daem
on (or service) is running. Then, create a debug log directory for bpdbm, retry
the operation, and check the resulting debug log.
* If you can view the report and have not found an entry related to this pro
blem, create debug log directories for the related processes that were running w
hen the error first appeared (this process will frequently be bpbrm). Then, retr
y the operation and check the resulting debug logs.
2. Verify that the server list specifies the correct master server.
* On Windows systems, the master server is designated as CURRENT on the Serv
ers tab in the Specify NetBackup Machines dialog. To display this dialog box, st
art the Backup, Archive, and Restore interface and click Specify NetBackup Machi
nes on the Actions menu.
* On UNIX, and Macintosh systems, the master server is the first SERVER entr
y in the bp.conf file.
* On NetWare target and OS/2 clients, the master server name is the first SE
RVER entry in the bp.ini file.
* Make sure all recommended NetBackup patches have been installed. Check the
VERITAS support web site for current patch information. (Go to www.support.veri
tas.com, then select "NetBackup" followed by "files and updates".)
* If failure occurs when executing a user-directed backup from a client, mak
e sure a user-directed backup schedule exists at the master server.
* When working with NetBackup database extensions, make sure that the applic
able database product has the correct permissions allowing NetBackup to write to
the progress log on the client.
* On UNIX systems, if bpdbm is dying when the shutdown script is executed on
a media server, carefully read the K77netbackup script (in /usr/openv/netbackup
/bin/goodies) for details on how to prevent this problem.
If you change the server list on a master server, stop and restart the NetBac
kup database manager and request daemons (UNIX) or the NetBackup Database Manage
r and NetBackup Request Manager services (Windows).
3. Check the services file.
On UNIX, verify that the /etc/services file (and NIS services if NIS is used)
has entries for the NetBackup services: bpcd, bpdbm, and bprd.
On Windows, verify that the %SystemRoot%\system32\drivers\etc\services file h
as the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the NetBackup Client Service Port number and NetBackup Requ
est Service Port number on the Network tab in the NetBackup Client Properties di
alog match the settings in the services file. To display this dialog, start the
Backup, Archive, and Restore interface and click NetBackup Client Properties on
the File menu. The values on the Network tab are written to the services file wh
en the NetBackup Client service starts.
Also, see Verifying Host Names and Services Entries in the Troubleshooting Gu
ide.
4. On Sun Solaris, verify that all operating system patches are installed (see
the Operating Notes section of the NetBackup Release Notes).
5. On Windows, verify that the recommended service packs are installed.
6. When the base NetBackup BusinesServer or DataCenter license key expires, dae
mons (such as bprd and bpdbm) will terminate on the NetBackup server. If these d
aemons are not running, you are likely to encounter status code 25 errors in the
Administration GUIs. Install a valid base NetBackup license key, restart the da
emons, and restart the GUI.
Error Number: 26
client/server handshaking failed
A process on the server encountered an error when communicating with the client.
This error indicates that the client and server were able to initiate communica
tions, but encountered difficulties in completing them. This problem can occur d
uring a backup or a restore.
Determine which activity encountered the handshake failure by examining the All
Log Entries report for the appropriate time period. Determine the client and ser
ver that had the handshake failure. For detailed troubleshooting information, cr
eate a debug log directory for the process that returned this status code, retry
the operation, and check the resulting debug log.
Error Number: 27
child process killed by signal
A child of the process reporting this error was killed. This can occur because t
he backup job was terminated or the child process was terminated by another erro
r. This problem can also occur if a NetBackup process was terminated through Tas
k Manager or another utility.
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create a debug log directo
ry for the process that you suspect of returning this status code. Then, retry t
he operation and check the resulting debug log.
Error Number: 28
failed trying to fork a process
A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows
). This may be due to:
* An overloaded system
* Insufficient swap space or physical memory
* Too many processes running on the system
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create debug log directori
es for the processes that you suspect of returning this status code. Then, retry
the operation and check the resulting debug logs.
Error Number: 29
failed trying to exec a command
A command could not be executed. This can occur because the permissions of the c
ommand do not allow it to be executed, or there is lack of system resources such
as memory and swap space.
Try the following.
1. Check the NetBackup All Log Entries report for clues on where and why the fa
ilure occurred.
2. Check the permissions on the command to be executed.
3. For detailed troubleshooting information, create a debug log directory for t
he process that returned this status code, retry the operation, and check the re
sulting debug log.
Error Number: 30
could not get passwd information
Could not get the passwd entry for a user.
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create a debug log for the
process that you suspect of returning this status code. Then, retry the operati
on and check the resulting debug log.
Error Number: 31
could not set user id for process
Could not set the user ID of a process to that of the requesting user. NetBackup
executes client processes as the requesting user.
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create a debug log directo
ry for the process that you suspect of returning this status code. Then, retry t
he operation and check the resulting debug log.
Error Number: 32
could not set group id for process
Could not set the group ID of a process to the requesting user group. NetBackup
executes client processes with the group ID of the requesting user.
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create a debug log directo
ry for the process that you suspect of returning this status code. Then, retry t
he operation and check the resulting debug log.
Error Number: 33
failed while trying to send mail
An E-mail notification of backup, archive, or restore results has failed. The E-
mail could not be sent to the administrator's address as specified by the E-mail
global attribute, or in the case of a UNIX client, an E-mail address specified
with USEMAIL in the client's bp.conf file.
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create a debug log directo
ry for the process that you suspect of returning this status code. Then, retry t
he operation and check the resulting debug log.
Error Number: 34
failed waiting for child process
The bpsched process encountered a failure while waiting for a child process to c
omplete.
Check the NetBackup All Log Entries report for clues on where and why the failur
e occurred. For detailed troubleshooting information, create a debug log for the
process that you suspect of returning this status code. Then, retry the operati
on and check the resulting debug log.
Error Number: 35
cannot make required directory
Could not create a required directory. Possible causes are:
* A process does not have permission to create the directory
* The path to the directory is not valid
* An IO error occurs
* There was no space available on the device containing the directory
Try the following.
1. Check the NetBackup All Log Entries report to determine which directory coul
d not be created and why it could not be created. In particular, check for a ful
l disk partition.
2. Check the permissions on the parent directory and verify that NetBackup serv
ices are started with a "Logon as" account that has permission to create the dir
ectory.
3. For detailed troubleshooting information, create a debug log directory for t
he process that returned this status code, retry the operation, and check the re
sulting debug log.
Error Number: 36
failed trying to allocate memory
Allocation of system memory failed. This error occurs when there is insufficient
system memory available. This could be caused by the system being overloaded wi
th too many processes and there is not enough physical and virtual memory.
Free up memory by terminating unneeded processes that consume a lot of memory. A
dd more swap space or physical memory.
Error Number: 37
operation requested by an invalid server
A request was made to the NetBackup request daemon (bprd) or NetBackup database
manager daemon (bpdbm) by an invalid media server or Windows NetBackup Remote Ad
ministration Console. On Windows, these daemons are the NetBackup Request Manage
r and NetBackup Database Manager services.
Examine the NetBackup All Log Entries report for the time of this error to deter
mine which system was trying to connect to the master server. If the server is a
valid media server, verify that the storage unit for the media server is define
d. Also, verify that the server or Windows NetBackup Remote Administration Conso
le has a server list entry on the master server. If necessary, update the server
list. On a UNIX master server, add a SERVER = media_server_name to the bp.conf
file. media_server_name is the host name of the media server. On a Windows maste
r server, add the media server to the list on the Servers tab in the Master Serv
er Properties dialog (see Using the Host Properties Window in the Troubleshootin
g Guide). If a server or Windows NetBackup Remote Administration Console has mor
e than one host name (for example, if it has multiple network interfaces), verif
y that the master server has a server list entry for each of them. If you change
the server list on a UNIX master server, you must stop and then restart the Net
Backup Request daemon (bprd) and NetBackup database manager daemon (bpdbm) for t
he changes to take effect. If you change the server list on a Windows master ser
ver, stop and then restart the NetBackup Request Manager and NetBackup Database
Manager services.
Error Number: 38
could not get group information
Could not get the group entry describing a UNIX user group.
Check the NetBackup Problems report for clues on why the error occurred. For det
ailed troubleshooting information, create a debug log directory for the process
that returned this status code, retry the operation, and check the resulting deb
ug log.
Error Number: 39
client name mismatch
The name that the client used in a request to the NetBackup server did not match
the client name configured in the policy on the server.
Change either the NetBackup client name setting on the client (see the applicabl
e NetBackup users guide) or the one in the policy configuration on the server so
the two match.
Error Number: 40
network connection broken
The connection between the client and the server was broken. This status code ca
n also appear if the connection is broken between the master and media server du
ring a backup.
Try the following.
1. Try pinging the client from the server. If this is not possible, check for l
oose connections or other network problems.
2. Verify that the server list settings are correct on both the client and the
server. If the backup involves a media server, verify that these entries are cor
rect on both the master and media server. For example, if a media server does no
t have a server list entry for the master, it does not accept connections from t
he master.
* On Windows, the master server is designated on the Servers tab in the Mast
er Server Properties dialog. To display this dialog, see Using the Host Properti
es Window in the Troubleshooting Guide.
* On UNIX, and Macintosh systems, the master server is the first SERVER entr
y in the bp.conf file.
* On NetWare target and OS/2 clients the master server name is the first SER
VER entry in the bp.ini file.
If you change the server list on a UNIX master server, you must stop and then
restart the NetBackup Request daemon (bprd) and NetBackup database manager daem
on (bpdbm) for the changes to take effect. On Windows, stop and restart the NetB
ackup Request Manager and NetBackup Database Manager services.
3. Status code 40 can also be due to the operator denying a mount request.
Error Number: 41
network connection timed out
The server did not receive any information from the client for too long a period
of time.
Try the following.
1. On UNIX or Windows clients, check for the following problems with the bpbkar
client process.
* The bpbkar client process is hung on a file that has mandatory locking set
. For this case, add the following to the client's bp.conf file:
VERBOSE
and as root on the client execute:
touch /usr/openv/netbackup/bpbkar_path_tr
mkdir /usr/openv/netbackup/logs/bpbkar
Then retry the operation. The names of the files are logged in the debug l
og file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar processe
s them. The last file in the log will be the file that is causing problems.
Note: Also, use the above procedure for other, "unknown" bpbkar hangs.
If the problem is due to mandatory file locking, you can have NetBackup sk
ip the locked files by setting LOCKED_FILE_ACTION to SKIP in the /usr/openv/netb
ackup/bp.conf file on the client.
* The bpbkar client process is not hung, but due to the files and directorie
s it is scanning, it has not replied to the server within CLIENT_READ_TIMEOUT or
CLIENT_CONNECT_TIMEOUT. This has been seen to occur during backups when directo
ries have thousands of unmodified files, or during restores of sparse files that
have thousands of holes; it has also been seen when backing up file systems or
directories that reside on optical disk, which is considerably slower than magne
tic disk.
For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_
CONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.conf file. The de
fault for the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if u
nspecified.
Use your system's ps command and monitor CPU utilization to help decide which
of the above conditions exist.
When you are through investigating the problem, delete the /usr/openv/netback
up/logs/bpbkar directory, since the log files can become quite large and are not
deleted automatically. Also delete /usr/openv/netbackup/bpbkar_path_tr so you d
o not generate larger log files than needed the next time you create directory /
usr/openv/netbackup/logs/bpbkar.
2. On Windows systems, try the following:
* Disable the following file:
install_path\Veritas\NetBackup\bin\admincmd\tracker.exe
* Repair hard drive fragmentation. You could try an application called Diske
eper Lite, which is part of the Windows NT Resource Kit.
* Make sure there is enough space available in \temp.
3. If the server cannot connect to the client, create bpcd or bpbkar (UNIX and
Windows only) debug log directories on the client, retry the operation, and chec
k the resulting logs. If these logs do not provide a clue, create a bpbrm debug
log on the server, retry the operation again, and check the resulting debug log.
If the bpbrm log has entries similar to the following:
bpbrm hookup_timeout: timed out waiting during the client hookup
bpbrm Exit: client backup EXIT STATUS 41: network connection timed out
then the problem is in the routing configuration on the server.
Verify that the client IP address is correct in the name service that is bein
g used. On UNIX, if both NIS and DNS files are used, verify that they match.
Also, see Resolving Network Communication Problems in the Troubleshooting Gui
de.
4. If you are using an AIX token ring adapter and the routed daemon is running,
the timeout can occur because the token ring adapter creates dynamic routes, ca
using the routed daemon to crash.
5. For a FlashBackup client, this can happen if the file system being backed up
is very large and has a very large number of files. It can also occur if a larg
e number of concurrent data streams are active at the same time. The corrective
action is to add CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file an
d set it to increase the timeout interval.
6. Make sure all recommended NetBackup patches have been installed. Check the V
ERITAS support web site for current patch information. (Go to www.support.verita
s.com, then select "NetBackup" followed by "files and updates".)
7. Add the CLIENT_READ_TIMEOUT values to the master server, media server and cl
ient when a NetBackup database extension product is installed. The values should
all be the same for each server. The value set is dependent on the size of the
database being backed up. See the NetBackup System Administrator's Guide for mor
e information on CLIENT_READ_TIMEOUT.
8. Make sure enhanced authentication is configured correctly. See the chapter o
n enhanced authentication in the NetBackup System Administrator's Guide.
For example, the following could result in status code 41: host A is configur
ed to use enhanced authentication with host B, but host B is not configured to u
se enhanced authentication with host A. In this case, connections from host B to
host A are likely to fail with status code 41. Connections from host A to B are
likely to fail with authentication errors (status code 160).
Error Number: 42
network read failed
An attempt to read data from a socket failed.
Try the following.
1. Verify that both the client and the server are operational.
2. Perform Resolving Network Communication Problems in the Troubleshooting Guid
e.
3. Check the Problems report for clues.
Error Number: 43
unexpected message received
The client and server handshaking was not correct.
Try the following.
1. Verify that the correct version of software is running on the client and the
server.
2. Enable detailed debug logging:
* On the server, create a bpbrm debug log directory.
* On clients, create a bpcd debug log directory (created automatically on Ma
cintosh clients).
* Increase the amount of debug information included in the logs as explained
in the debug log topics in Chapter3.
3. Retry the operation and examine the logs.
Note: If you are using bpstart_notify scripts on UNIX or Windows clients, verify
that messages are not being written to stdout or stderr.
Error Number: 44
network write failed
An attempt to write data to a socket failed.
Try the following.
1. Check the Problems report for information about the error.
2. Verify that the client and servers are operational and connected to the netw
ork.
3. Create a debug log directory for the process that reported the problem and t
he operation. Examine the resulting debug log file for detailed troubleshooting
information.
4. Perform Resolving Network Communication Problems in the Troubleshooting Guid
e.
Error Number: 45
request attempted on a non reserved port
An attempt was made to access a client from a nonreserved port.
Verify that the latest software is installed on the client and server.
* On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/ver
sion file.
* On Windows NetBackup servers, check the install_path\netbackup\version.txt fi
le or the About NetBackup item on the Help menu.
* On Microsoft Windows clients, check the About NetBackup item on the Help menu
.
* On NetWare target clients, check the Version entry in the bp.ini file.
* If this is a NetBackup for NetWare client and has a version of NetBackup earl
ier than 3.0, verify that the client is in a Standard type policy.
* On Macintosh clients, check the version file in the bin folder in the NetBack
up folder in the Preferences folder.
Error Number: 46
server not allowed access
The server is trying to access a client but access is blocked. Possible causes a
re:
* The server is not listed on the client as a valid server.
* The client has been configured to require encrypted backups, but the encrypti
on attribute for the backup policy on the server has not been selected.
* The evaluation license for the NetBackup Encryption product has expired on th
e server, but the NetBackup client has been configured to require encrypted back
ups. As a result, the server attempted to make a non-encrypted backup of the cli
ent; since the client is configured to require encryption, the backup failed.
Try the following.
* If the server is a valid server but is not listed on the client, add its name
to the client's server list:
* On Windows clients, add the server on the Servers tab in the Specify NetBa
ckup Machines dialog box. To display this dialog box, start the Backup, Archive,
and Restore interface on the client and click Specify NetBackup Machines on the
Actions menu.
* On UNIX and Macintosh clients, add a SERVER entry in the bp.conf file.
* On NetWare target and OS/2 clients, add a SERVER entry in the bp.ini file.
If you continue to have problems, review Resolving Network Communication P
roblems in the Troubleshooting Guide and Verifying Host Names and Services Entri
es in the Troubleshooting Guide.
* To make non-encrypted backups of the client, set CRYPT_OPTION on the client t
o allowed or denied. For more information, refer to the NetBackup Encryption Sys
tem Administrator's Guide.
* If the NetBackup encryption evaluation license has expired on the server and
you want to continue encrypting backups of the client, you must purchase a perma
nent encryption license key and add it to the server. After you add the permanen
t encryption license key, check the attributes of the backup policy to make sure
that encryption is selected.
To check the validity of an evaluation license key, do the following:
On Windows: go to the Help menu on the NetBackup Administration window on the
NetBackup server and select License Keys. If the evaluation key is not listed i
n the NetBackup License Keys window, the key has expired. Use this window to add
the new permanent encryption key.
On UNIX: use the /usr/openv/netbackup/bin/admincmd/get_license_key command on
the server. Select option f to list the active license keys and features. If th
e evaluation key is not listed, the key has expired. Use this command to add the
new permanent encryption key.
Error Number: 47
host is unreachable
An attempt to connect to another machine failed.
Try the following.
1. Verify that the name service (or services) being used by the client is confi
gured to correctly resolve the host names of the NetBackup server.
2. Verify that the name service (or services) being used by the server is confi
gured to correctly resolve the host name of the NetBackup client.
3. Try to ping the client from the server and the server from the client.
4. If you continue to have problems, perform Resolving Network Communication Pr
oblems in the Troubleshooting Guide.
Error Number: 48
client hostname could not be found
The system function gethostbyname() failed to find the client's host name.
Try the following.
1. Verify that the client name is correct in:
* The NetBackup policy configuration on the master server.
* The General tab in the NetBackup Client Properties dialog box and the Clie
nts tab in the Specify NetBackup Machines dialog box (on Microsoft Windows and N
etWare nontarget clients). To display these dialog boxes, start the Backup, Arch
ive, and Restore interface on the client. For the General tab, click NetBackup C
lient Properties on the File menu; for Clients tab, click Specify NetBackup Mach
ines on the File menu.
* The bp.conf file on UNIX and Macintosh clients.
* The bp.ini file on OS/2 and NetWare target clients.
2. On clients and servers, verify that the name service is set up to correctly
resolve the NetBackup client names.
On UNIX clients, verify that the client's host name is in the /etc/hosts file
or the YP hosts file or NIS maps.
Error Number: 49
client did not start
The client failed to start up correctly.
Try the following.
1. Verify that software is installed on the client and it is the correct versio
n. If necessary, reinstall the client software.
2. Check for full file systems on the client.
3. Enable detailed debug logging on the client:
* Create bpcd and bpbkar (UNIX or Windows only) debug log directories.
* On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.co
nf file.
* On PC clients, increase the debug or log level as explained in the debug l
og topics in Chapter3.
4. Retry the operation and examine the resulting logs.
5. On UNIX systems, use the UNIX sum command to check for corrupt binaries.
6. On SGI IRIX 6.2/6.4 systems, clients may be missing the libdbm.so shared lib
rary. Refer to the SGI/IRIX install CD-ROM for the eoe.sw.dmi package.
Error Number: 50
client process aborted
The client backup aborted. One instance when this code appears is if a NetBackup
master or media server is shut down or rebooted when a backup or restore is in
process.
Try the following.
1. Enable detailed debug logging:
* Create a bpbkar debug log directory (UNIX or Windows only).
* Create a bpcd debug log directory (this log is created automatically on Ma
cintosh clients.)
* On UNIX clients, add the VERBOSE option to the /usr/openv/netbackup/bp.con
f file.
* On PC clients, increase the debug or log level as explained in the debug l
og topics in Chapter3.
2. Retry the operation and examine the resulting logs.
3. On UNIX clients, check for core files in the / directory.
4. On UNIX clients, check the system log (/usr/adm/messages on Solaris) for sys
tem problems.
5. This problem can sometimes be due to a corrupt binary.
On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and tar
binaries, located in /usr/openv/netbackup/bin on the client. Reinstall them if t
hey are not the same as in the client directory under /usr/openv/netbackup/clien
t on the server.
On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32
.exe executables located in the install_path\NetBackup\bin folder on the client.
Reinstall the client if these executables are not the same size as on other Win
dows clients or are not at the same release level or do not have the same NetBac
kup patches applied as other Windows clients.
Error Number: 51
timed out waiting for database information
The catalog process did not respond within five minutes.
Try the following.
1. Verify that the NetBackup Database Manager daemon (service on Windows) is ru
nning.
2. Verify that there is space in the file system that contains the NetBackup ca
talogs.
3. Create bpbrm and bpdbm debug log directories on the server and retry the ope
ration.
4. Look in the debug log files to find more information on the problem.
Error Number: 52
timed out waiting for media manager to mount volume
The requested volume was not mounted before the timeout expired. This error can
also occur if the volume happens to be a cleaning tape but was not specified as
a cleaning tape. Another possible cause: if the last available drive has a mount
request for a non-backup (such as a restore), then a backup requiring the same
drive is initiated before the mount completes. This is due to the drive not bein
g reported as busy until the mount completes.
Try the following.
1. Verify that the requested volume is available and an appropriate drive is re
ady and in the UP state.
2. If this occurs during a read operation (restore, duplicate, verify), the dri
ves could be busy. Try increasing the media mount timeout specified by the NetBa
ckup global attribute in order to allow more time for mounting and positioning t
he media.
3. Verify that the tape is not a cleaning tape that is configured as a regular
volume.
4. When the robot is controlled by an Automated Cartridge System, verify that t
he ACSLS system is up.
5. If this is an initial installation, refer to To Resolve Common Configuration
Problems in the Troubleshooting Guide.
6. On Windows, check the Event Viewer Application log for error messages that i
ndicate why the tape mount did not complete. On UNIX, check the system log.
Error Number: 53
backup restore manager failed to read the file list
The backup and restore manager (bpbrm) could not read the list of files to back
up or restore.
Verify that the server software has been installed correctly on all NetBackup se
rvers. If that is not the problem:
1. Create bpbrm and bpsched debug log directories on the server.
2. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. On a
Windows NetBackup server, set the Verbose logging level option on the Universal
Settings tab in the Master Server Properties dialog. To display this dialog, se
e Using the Host Properties Window in the Troubleshooting Guide.
3. Retry the operation and check the resulting debug logs for detailed troubles
hooting information.
Error Number: 54
timed out connecting to client
The server could not complete the connection to the client. The accept system ca
ll timed out after 60 seconds.
Try the following.
1. For a Macintosh or NetWare target client, verify that the server is not tryi
ng to connect when a backup or restore is already in progress on the client. The
se clients can handle only one NetBackup job at a time.
On a Macintosh, you can check for activity by examining the NetBackupListen f
ile in the following folder on the startup disk of the Macintosh client:
:System Folder:Preferences:NetBackup:logs:inetd:log.mmddyy
2. On a Sequent platform, verify that the system has the correct level of TCP/I
P.
3. Perform Resolving Network Communication Problems in the Troubleshooting Guid
e.
4. On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists
and that it is the correct size.
5. Check the /etc/inetd.conf file to make sure the bpcd path is correct in the
following entry:
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
6. On systems that include NetBackup master, slave, and clients (with NetBackup
database extension products installed on one or more clients), make sure the cl
ient name is in the master's /etc/hosts file.
Error Number: 55
permission denied by client during rcmd
The UNIX client does not have the server's name in its /.rhosts file.
Add the server name to the /.rhosts file on the UNIX client.
Error Number: 56
client's network is unreachable
An error was returned that the host was unreachable by the client (ENETUNREACH)
when performing a system call.
Try to ping the client from the server. Check the IP address for the client. If
you still have problems, talk to your network administrator.
Error Number: 57
client connection refused
The client refused a connection on the port number for bpcd. This can occur beca
use there is no process listening on the bpcd port or there are more connections
to the bpcd port than the network subsystem can handle with the listen() call.
Try the following.
1. For Windows NetBackup servers:
a. Make sure the NetBackup client software is installed.
b. Verify that the bpcd and bprd port numbers in the %SystemRoot%\system32\d
rivers\etc\services file on the server matches the setting on the client.
c. Verify that the NetBackup Client Service Port number and NetBackup Reques
t Service Port number on the Network tab in the NetBackup Client Properties dial
og match the bpcd and bprd settings in the services file. To display this dialog
, start the Backup, Archive, and Restore interface on the server and click NetBa
ckup Client Properties on the File menu.
The values on the Network tab are written to the services file when the Ne
tBackup Client service starts.
d. Verify that the NetBackup client service is running.
e. On Windows systems, for NetBackup 3.0 to NB3.1.1, the install_path\winnt\
system32\drivers\etc\services file may not have correct information. The followi
ng entries are correct:
bpcd 13782/tcp
bprd 13720/tcp
f. Use the following command to see if the master server returns correct inf
ormation for the client:
install_path\Veritas\NetBackup\bin\admincmd\bpclntcmd -pn
2. For UNIX servers:
a. Make sure the NetBackup client software is installed.
b. Verify that the bpcd port number on the server (either NIS services map o
r in /etc/services) matches the number in the client's services file.
3. For a Macintosh or NetWare target client, verify that the server is not tryi
ng to connect when a backup or restore is already in progress on the client. The
se clients can handle only one NetBackup job at a time.
4. Perform Resolving Network Communication Problems in the Troubleshooting Guid
e.
Error Number: 58
can't connect to client
The server was unable to connect to the client.
Perform Resolving Network Communication Problems in the Troubleshooting Guide.
Error Number: 59
access to the client was not allowed
The master or media server is trying to access the client, but the server is not
recognized by the client as a valid server.
Try the following.
1. If the server is a valid server, verify that it is in the server list on the
client. If necessary add it as follows:
* On Windows clients, add the server on the Servers tab in the Specify NetBa
ckup Machines dialog box. To display this dialog, start the Backup, Archive, and
Restore interface on the client and click Specify NetBackup Machines on the Act
ions menu.
* On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file.
* On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.
If you change the server list on a UNIX master server, you must stop and then
restart the NetBackup Request daemon (bprd) and NetBackup database manager daem
on (bpdbm) for the changes to take effect. On Windows, stop and restart the NetB
ackup Request Manager and NetBackup Database Manager services.
2. On Windows clients, enable bpinetd debug logging as follows:
a. Create a bpinetd debug log directory on the client.
b. Increase the debug or log level as explained in the debug log topics in C
hapter3.
c. Retry the backup and examine the resulting logs to determine the cause of
the failure.
3. On all but Macintosh clients, enable bpcd debug logging as follows:
a. Create a bpcd debug log directory on the client.
b. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.c
onf file.
c. On PC clients, increase the debug or log level as explained in the debug
log topics in Chapter3.
d. Retry the backup and examine the resulting logs to determine the cause of
the failure.
4. On Macintosh clients, check the inetd and bpcd debug logs. Both logs are cre
ated automatically.
* Check the inetd log to see if NetBackupListen is running.
* Check the bpbkar and tar messages in the bpcd log file.
To increase the amount of information included in the logs, set the loglev
el parameter in the mac.conf file to a higher value.
5. Check the bpcd debug log to determine the server's peername and what compari
sons are being made.
The bpcd process compares NetBackup server list entries to the peername of th
e server attempting the connection and rejects the connection if the names are d
ifferent. If necessary, change the server list entry on the client to match the
peername.
6. On Windows clients, check the following:
* Verify that NetBackup for Windows software was installed under a Windows a
dministrator account.
If NetBackup is under another type of account, reinstall it under an admin
istrator account. The installation will complete successfully under a non-admini
strator account but the NetBackup Client service is not added to Windows and the
NetBackup server cannot access the client.
* Verify that the Windows TCP/IP service specifies the domain server that re
solves names for the subnet that contains the NetBackup servers.
UNIX and Windows clients are frequently not on the same subnet and use dif
ferent domain servers. When this condition exists the NetBackup servers and Wind
ows clients may be able to ping one another, but the server is still unable to a
ccess the Windows client.
7. If the preceding steps do not resolve this problem, see Resolving Network Co
mmunication Problems in the Troubleshooting Guide.
8. If NetBackup is using multiple network interfaces with slave servers, make s
ure the interface names appear in the client's /usr/openv/netbackup/bp.conf file
.
Error Number: 60
client cannot read the mount table
The backup process on the client could not read the list of mounted file systems
.
Try the following.
1. Execute a df to see if the system can read the mount table.
2. On an SCO system, code 60 can occur because the mount-point path name exceed
s 31 characters, which is the maximum allowed on an SCO system. The bpbkar debug
log on the client will show a message similar to the following:
bpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406
To eliminate these errors for future backups, create a mount point with a sho
rter name and symbolically link the long name to the short name.
3. For detailed troubleshooting information, create a bpbkar debug log director
y, retry the operation, and examine the resulting log.
Error Number: 61
wbak was killed
The wbak process on the Apollo was killed.
Try the backup again.
Error Number: 62
wbak exited abnormally
The wbak process on the Apollo exited abnormally.
Try running wbak by hand to determine the source of the problem. Direct the outp
ut of the wbak command to /dev/null to avoid filling up your file system and use
the following parameters:
-l -nhi -pdtu -stdout -nwla and -full or -af date
Error Number: 63
process was killed by a signal
A kill signal was sent to the client process.
This is usually caused by someone intentionally terminating a backup.
Error Number: 64
timed out waiting for the client backup to start
The client did not send a ready message to the server within the allotted time.
Try the following.
1. On all but Macintosh clients, enable bpcd debug logging as follows:
a. Create a bpcd debug log directory on the client.
b. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.c
onf file.
c. On PC clients, increase the debug or log level as explained in the debug
log topics in Chapter3.
2. On Macintosh clients, check the inetd and bpcd debug logs. Both logs are cre
ated automatically.
* Check the inetd log to see if NetBackupListen is running.
* Check the bpbkar and tar messages in the bpcd log file.
To increase the logging level, set the loglevel parameter in the mac.conf
file to a higher value.
3. On a UNIX or Windows client, create the bpbkar debug log directory on the cl
ient.
4. On Windows clients, verify that the NetBackup Client service is running.
5. On a UNIX client, use the ps command to check for a client process that is u
sing too much CPU time.
6. Retry the backup and examine the debug logs for clues on the cause of the fa
ilure.
Error Number: 65
client timed out waiting for the continue message from the media manager.
The tape manager, bptm reported that the media did not load and position within
the allotted time.
Verify that the requested volume is available and the required device is in an U
P state.For detailed debug information:
1. Create a bptm debug log directory on the server.
2. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. On a
Windows NetBackup server, set the Verbose logging level option on the Universal
Settings tab in the Master Server Properties dialog (see Using the Host Propert
ies Window in the Troubleshooting Guide).
3. Retry the operation and check the bptm debug log file for information on the
drive, robot, and tape that is causing the timeout.
4. On a Windows NetBackup server (master or media), check the Event Viewer Appl
ication log for error messages that indicate why the tape mount did not complete
.
Error Number: 66
client backup failed to receive the CONTINUE BACKUP message
The client bpbkar process did not receive the message from the server that indic
ates that the server is ready to continue.
Verify that the server did not crash. If that is not the problem and you need mo
re information:
1. On UNIX and Windows clients, enable bpbkar debug logging.
a. Create a bpbkar debug log directory.
b. On a UNIX client, add the VERBOSE option to the bp.conf file. On a Window
s client, set Verbose on the TroubleShooting tab in the NetBackup Configuration
dialog box. To display this dialog box, start the Backup, Archive, and Restore i
nterface on the client and click Configure on the Actions menu.
2. On other PC clients except Macintosh, create a debug log directory for bpcd
(the bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the loggi
ng topics in Chapter3.
3. On the master server create bpsched and bpbrm debug log directories. If ther
e are media servers involved, create a bpbrm debug log directory on them.
4. Retry the operation and check the resulting debug logs.
Error Number: 67
client backup failed to read the file list
The client could not read the list of files to back up.
First, verify that the server did not crash. If that is not the problem and you
need more information:
1. Set up debug logging:
a. On the server, create a bpbrm debug log directory.
b. On UNIX and Windows clients, create a bpbkar debug log directory.
c. On other PC clients except Macintosh, create a debug log directory for bp
cd (the bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the loggi
ng topics in Chapter3.
2. Retry the operation and check the resulting debug logs.
Error Number: 68
client timed out waiting for the file list
The client did not receive the list of files to back up within the allotted time
. This list comes from the server.
First, verify that the server did not crash. If that is not the problem and you
need more information:
1. Set up debug logging:
a. On the server, create a debug log directory for bpbrm.
b. On UNIX and Windows clients, create a bpbkar debug log directory.
c. On other PC clients except Macintosh, create a debug log directory for bp
cd (the bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the loggi
ng topics in Chapter3.
2. Retry the operation and check the resulting debug logs.
Error Number: 69
invalid file list specification
The file list received from the server had invalid entries.
Try the following.
1. Check the policy file list. If wildcards are used, verify there are matching
bracket characters ([ and ]). If the file list contains UNC (Universal Naming C
onvention) names, ensure they are properly formatted.
2. For NetBackup ServerFree Agent only:
If this was an offhost backup (NetBackup Media Server or Third-Party Copy Dev
ice), code 69 may indicate that the file list contains the ALL_LOCAL_DRIVES entr
y. NetBackup does not support the ALL_LOCAL_DRIVES entry for offhost backup. Rem
ove the ALL_LOCAL_DRIVES entry from the file list.
Error Number: 70
an entry in the file list expanded to too many characters
The wildcards used in one of the file list entries caused too many files to be s
pecified.
Change the wildcards in the file list to specify fewer files.
Error Number: 71
none of the files in the file list exist
The files in the file list did not match any of the files on the client. This er
ror can occur when there is only one file in the file list and the file cannot b
e backed up due to an I/O error.
Try the following.
1. Verify that the correct file list is specified for this client.
2. On Windows clients, verify that the account used to start the NetBackup Clie
nt service has read access to the files.
If you are backing up a network drive or a UNC (universal naming convention)
path, use the Services application in the Windows Control Panel to verify that t
he NetBackup Client service does not start under the SYSTEM account. The SYSTEM
account cannot access network drives.
To back up network drives or UNC paths, change the NetBackup Client service s
tartup to log in as a user that has permission to access network drives.
3. Check the All Log Entries report for clues.
4. Set up debug logging:
* On UNIX and Windows clients, create a debug log directory for bpbkar.
* On other PC clients except Macintosh, create a debug log directory for bpc
d (the bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the loggi
ng topics in Chapter3.
5. Retry the operation and check the resulting debug logs.
6. On Novell systems, check the following:
* For the nontarget version of NetBackup for NetWare, the backup policy type
must be "NetWare", and the files list should include a forward slash (/) only.
There should be nothing else in the files list.
To check the policy type and files list, start Backup Policy Management an
d right-click the name of a policy. Click the Attributes tab to check the policy
type; click the Files tab to check the contents of the files list.
* For the target version, the backup policy type must be "Standard", and the
policy files list must be formatted as follows:
/target_name
where a forward slash precedes the variable target_name.
To check the policy type and files list, start Backup Policy Management an
d right-click the name of a policy. Click the Attributes tab to check the policy
type; click the Files tab to check the contents of the files list.
Note: For the target version, the following NetWare message may be another indic
ator of incorrect policy type (this message would appear in the Novell client's
bpcd log):
unable to connect to service, scheduled access not specified
Make sure the policy type is set to "Standard".
Error Number: 72
the client type is incorrect in the configuration database
The policy type attribute in the policy configuration indicates that the client
is one type, but the installed software is for another type.
Verify that the policy type attribute for the policy is correct. Also, for UNIX,
do not place Apollo and standard clients in the same policy.
Error Number: 73
bpstart_notify failed
The bpstart_notify script returned a nonzero exit code.
Check the bpstart_notify script on the client to see if it performs as desired.
Error Number: 74
client timed out waiting for bpstart_notify to complete
The bpstart_notify script on the client took too long.
Try to speed up the bpstart_notify script or set the BPSTART_TIMEOUT on the serv
er to a value that is larger than the default. Set BPSTART_TIMEOUT in the bp.con
f file on a UNIX NetBackup server. On a Windows NetBackup server, use Host Prope
rties to set Backup Start Notify Timeout (see Using the Host Properties Window i
n the Troubleshooting Guide).
Error Number: 75
client timed out waiting for bpend_notify to complete
The bpend_notify script on the client took too long.
Try to speed up the bpend_notify script or set BPEND_TIMEOUT on the server to a
value that is larger than the default. Set BPEND_TIMEOUT in the bp.conf file on
a UNIX NetBackup server. On a Windows NetBackup server, use Host Properties to s
et Backup End Notify Timeout.
Error Number: 76
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 77
execution of the specified system command returned a nonzero status
An immediate command returned a nonzero status.
Try the following.
1. Verify that the command is specified correctly.
2. For NetBackup ServerFree Agent only:
The policy file list may contain files that do not reside within a file syste
m that was designated as the frozen image source. For a frozen image method to b
e applied to the backup of individual files, the frozen image source must be a f
ile system (not a raw partition or Volume Manager volume) and the files in the p
olicy file list must reside within that file system.
3. Execute the command manually to see if the desired result is produced.
4. For detailed troubleshooting information, set up debug logging:
a. On UNIX and Windows clients, create a debug log directory for bpbkar.
b. On other PC clients except Macintosh, create a debug log directory for bp
cd (the bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the lo
gging topics in Chapter3.
c. Retry the operation and check the resulting debug log.
Error Number: 78
afs/dfs command failed
Indicates an AFS vos command failure.
Try the following.
1. Check the NetBackup Problems Report for additional information on why the co
mmand failed.
2. The bpbkar debug log shows the command that was executed. Create a debug log
directory for bpbkar. Retry the operation and retry the resulting debug log.
3. Try executing the vos command manually to duplicate the problem.
Error Number: 79
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 80
Media Manager device daemon (ltid) is not active
If the server is UNIX, the Media Manager device daemon, ltid, is not running. If
the server is Windows, the NetBackup Device Manager service is not running.
Try the following.
1. On Windows, use the Activity Monitor or the Services application in the Wind
ows Control Panel to see if the NetBackup Device Manager service is running. If
it is not running, start it. To enable verbose logging, place VERBOSE on a line
by itself in the install_path\Volmgr\vm.conf file before starting the service.
2. On UNIX, use vmps to see if ltid is running and if necessary start it in ver
bose mode with the following command:
/usr/openv/volmgr/bin/ltid -v
Or, add a VERBOSE entry to the Media Manager configuration file, /usr/openv/v
olmgr/vm.conf. Create the vm.conf file if necessary.
3. On UNIX, check the system logs to verify that ltid starts.
Note: ltid or the NetBackup Device Manager service is used only if devices are a
ttached to the system.
Error Number: 81
Media Manager volume daemon (vmd) is not active
The tape manager (bptm) could not communicate with the NetBackup Volume Manager
service (Windows) or the Media Manager volume daemon (UNIX). This communication
is required for most operations.
On UNIX, verify that the Media Manager device daemon (ltid) and the volume daemo
n (vmd) are running. Start them if necessary. On Windows, verify that both the N
etBackup Device Manager service and the NetBackup Volume Manager service are run
ning. Start them if necessary.
Note: ltid or the NetBackup Device Manager service is used only if devices are a
ttached to the system.
Error Number: 82
media manager killed by signal
The tape manager (bptm) or disk manager (bpdm) was terminated by another process
or a user.
This should not occur in normal operation. If you want to terminate an active ba
ckup, use the NetBackup Activity Monitor.
* When backing up a DomainOS client (for example, Apollo), this error has occur
red after the server has not received anything on the socket for at least 300 se
conds, thus causing a client read timeout and breaking the connection. The bpbka
r debug log had an entry similar to the following:
13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET
Connection reset by peer (UNIX/errno status)
Increasing the CLIENT_READ_TIMEOUT value (in this instance to 900) has resolv
ed this problem.
Error Number: 83
media open error
The tape manager (bptm) or disk manager (bpdm) could not open the device or file
that the backup or restore must use.
Try the following.
1. For additional information, check the following:
* NetBackup Problems report
* System log (UNIX)
* Event Viewer Application log (Windows)
2. Typically, this status code indicates a drive configuration problem that all
ows more than one process at a time to open the device.
On UNIX, the problem could be due to:
* Two (or more) devices were configured that are really the same physical de
vice (for different densities perhaps). Verify that none of the /dev files used
for these devices have the same major or minor numbers.
* Links exist in the file system that are allowing users access to the drive
s.
* The configuration for the drives was modified (in the administrator interf
ace or vm.conf) and the Media Manager device daemon, ltid, was not restarted. Ve
rify the configuration and start ltid.
On Windows, the problem could be that the Media Manager device configuration
was modified but the NetBackup Device Manager service was not restarted. Verify
the configuration and restart the NetBackup Device Manager service.
3. Make sure the tapes are not write protected.
4. For detailed troubleshooting information:
a. Create a debug log directory for bpdm (if the device is disk) or bptm (if
the device is tape).
b. On UNIX, restart ltid in the verbose mode by executing:
/usr/openv/volmgr/bin/ltid -v
Or, add a VERBOSE entry to the Media Manager configuration file, /usr/open
v/volmgr/vm.conf. Create the vm.conf file if necessary.
c. On Windows, enable verbose logging by adding VERBOSE on a line by itself
in the install_path\Volmgr\vm.conf file. Then, stop and restart the NetBackup De
vice Manager service.
d. Retry the operation and check the resulting debug log files.
e. On UNIX systems, look at the /usr/openv/netbackup/db/media/errors log (w
hich is also included in the /usr/openv/netbackup/bin/goodies/support script out
put) for a drive that is frequently producing errors.
Error Number: 84
media write error
The system's device driver returned an I/O error while NetBackup was writing to
removable media or a disk file.
Try the following.
1. For NetBackup ServerFree Agent only:
If the following message appears in the /usr/openv/netbackup/bptm log, and th
e values for key, asc, and ascq are all zero (0x0) as shown in this example mess
age:
tape error occurred on extended copy command, key = 0x0, asc = 0x0,
ascq = 0x0
your host-bus adapter and its driver are probably not supported by NetBackup
ServerFree Agent. The host-bus adapters and drivers supported in the release are
listed in the NetBackup Release Notes.
2. For additional information, check the following:
* NetBackup Problems report to determine the device or media that caused the
error
* System and error logs for the system (UNIX)
* Event Viewer Application and System logs (Windows)
3. If NetBackup was writing backups to a disk file, verify that the disk has en
ough space for the backup.
For a catalog backup to a disk path on a UNIX system, you may be trying to wr
ite a image greater than two gigabytes. File sizes greater than two gigabytes is
a limitation on many UNIX file systems. Tape files do not have this limit.
4. If the media is tape or optical disk, check for:
* A defective or dirty drive, in which case, clean it or have it repaired (r
efer to the tpclean command for robotic drives).
* The wrong media type. Verify that the media matches the drive type you are
using. On an optical drive, the platters may not be formatted correctly.
* Defective media. If this is the case, use the bpmedia command to set the v
olume to the FROZEN state so it is not used for future backups.
* Incorrect drive configuration. Verify the Media Manager and system configu
ration for the drive.
For example, on UNIX the drive could be configured for fixed mode when it
must be variable mode. See the Media Manager Device Configuration Guide for more
information.
This often results in the media being frozen with a message, "too many dat
a blocks written, check tape/drive block size configuration."
Error Number: 85
media read error
The system device driver returned an I/O error while NetBackup was reading from
tape, optical disk, or a disk file.
Try the following.
1. For additional information, check the following:
* NetBackup Problems report to determine the device or media that caused the
error
* System and error logs for the system (UNIX)
* Event Viewer Application and System logs (Windows)
2. Check for the following:
* A defective or dirty drive. Clean it or have it repaired (see the tpclean
command for cleaning).
* Incorrect drive configuration. Verify the Media Manager and system configu
ration for the drive.
For example, on UNIX the drive could be configured for fixed mode when it
must be variable mode. See the Media Manager Device Configuration Guide for more
information.
* Defective media. In this case, you may not be able to recover all the data
on the media. Use the bpmedia command to set the volume to the FROZEN state so
it is not used for future backups.
* The wrong media type. Verify that the media matches the drive type you are
using.
Error Number: 86
media position error
The system's device driver returned an I/O error while NetBackup was positioning
media (tape or optical disk).
Try the following.
1. For additional information, check the following:
* NetBackup Problems report to determine the device or media that caused the
error
* System and error logs for the system (UNIX)
* Event Viewer Application and System logs (Windows)
2. Check for the following:
* A defective or dirty drive. Clean it or have it repaired (see the tpclean
command for cleaning).
* Incorrect drive configuration. Verify the Media Manager and system configu
ration for the drive.
For example, on UNIX the drive could be configured for fixed mode when it
must be variable mode. See the Media Manager Device Configuration Guide for more
information.
* Defective media. In this case, some data may be lost. Use the bpmedia comm
and to set the volume to the FROZEN state so it is not used for future backups.
* The wrong media type. Verify that the media matches the drive type you are
using.
Error Number: 87
media close error
The system's device driver returned an I/O error while NetBackup was closing a t
ape or optical disk.
Try the following.
1. For additional information, check the following:
* NetBackup Problems report to determine the device or media that caused the
error
* System and error logs for the system (UNIX)
* Event Viewer Application and System logs (Windows)
2. Check for the following:
* A defective or dirty drive. Clean it or have it repaired (see the tpclean
command for cleaning).
* Defective media. In this case, some data may be lost. Use the bpmedia comm
and to set the volume to the FROZEN state so it is not used for future backups.
Error Number: 88
Auspex SP/Backup failure
NetBackup detected a problem when backing up an Auspex FastBackup client.
Check the All Log Entries report. If more details are required, create bptm and
bpbrm debug log directories on the server. Then, retry the operation and check t
he resulting log files. This error is usually due to a configuration problem.
Error Number: 89
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 90
media manager received no data for backup image
The tape manager (bptm) or disk manager (bpdm) received no data when performing
a backup, archive, or duplication. This can occur for incremental backups where
no data was backed up because no files have changed.
Try the following.
1. For additional information, check the following:
* NetBackup Problems report to determine the device or media that caused the
error
* System and error logs for the system (UNIX)
* Event Viewer Application log (Windows)
2. Verify the Media Manager and system configuration for the drive.
For example, on UNIX the drive may not be set for variable mode in a case whe
re that mode is required by NetBackup. Check the Media Manager Device Configurat
ion Guide for drive configuration information.
3. Verify that the Media Manager configuration for the backup device matches wh
at is specified for the storage unit in the NetBackup policy.
4. Verify that you are using the correct media in the drive.
5. For detailed debug information, create a bpdm or bptm debug log directory (w
hichever applies) on the server. If the client is Windows, also create a bpbkar
debug log directory on the client. Retry the operation and check the resulting d
ebug logs. Retry the operation. Check the resulting debug log file.
6. If the error was encountered by duplication or by a Vault session which is u
sing an Alternate Read Server to do duplication, verify that the Alternate Read
Server has access to the source media.
Error Number: 91
fatal NB media database error
The tape manager (bptm) received an error while reading or updating its media ca
talog.
Try the following.
1. Check the All Log Entries report for more information.
2. Check the NetBackup Media Lists report to see if the catalog is intact. If t
he catalog is not intact, consider reloading it from the latest NetBackup catalo
g backup volume.
3. Verify that the disk partition on which the catalog resides has enough space
.
4. If the above actions do not explain the problem, check the NetBackup Problem
s report.
5. For detailed troubleshooting information, create a bptm debug log directory
on the server and retry the operation. Check the resulting debug log file.
6. Contact customer support and send appropriate problem and debug log sections
.
Error Number: 92
media manager detected image that was not in tar format
When performing a restore, the tape manager (bptm) or disk manager (bpdm) could
not find a tar header at the offset it expected.
Try the following.
1. Perform a bpverify of the affected image to determine if it is written corre
ctly.
2. Check the NetBackup Problems report for additional information about the err
or.
3. Verify the Media Manager and system configuration for the drive.
For example, on some UNIX systems, for example, if you do not configure the d
rive for variable-mode block size writes, backup images written to the media pro
duce this error when an attempt is made to restore the image. For example, you s
ee the following sequence of events:
* Backup succeeds
* Verify succeeds
* Restore fails
The bptm debug log shows an error similar to
00:58:54 [2304] <16> write_data: write of 32768 bytes indicated
only 29696 bytes were written, errno = 0
In this case, configure the drive for variable-mode block sizes and suspend m
edia written on that device. See the NetBackup Device Configuration Guide.
The images written to those media may be restorable (this is platform depende
nt), but single file restores are almost guaranteed to fail. You can choose to e
xpire these media and regenerate the backups, or you can attempt to duplicate th
e images on these media to another device and then expire the original copy.
4. Error code 92 has been encountered on some relabeled and value-added 8-mm ta
pe drives where the drive's microcode incorrectly processes a "forward space rec
ord" SCSI command.
5. If the problem is not one of the above, create a debug log directory for eit
her bpdm or bptm and retry the operation. Check the resulting debug log file.
Error Number: 93
media manager found wrong tape in drive
When loading a volume for a backup or restore, the tape manager (bptm) found a v
olume loaded that did not have the expected tape header. This can indicate that
volumes in a robot are not in the slots indicated in the Media Manager volume co
nfiguration.
Try the following.
* If the volume is in a robot and the robot supports barcodes, perform a Compar
e Contents with Volume Configuration (Verify Robot Contents on UNIX). The result
ing report shows which media ID was found and validates its slot number with wha
t is in the Media Manager volume configuration. Then, either change the physical
location in the robot or change the volume configuration to show the correct sl
ot.
* If the volume was mounted on a nonrobotic drive, verify that the correct volu
me was mounted and assigned.
Error Number: 94
cannot position to correct image
When searching for a backup image to restore, the tape manager (bptm) did not fi
nd the correct backup ID at the expected position on the volume. This can indica
te a drive hardware problem.
Try the following.
1. Try the restore on another drive if possible.
2. For additional information, check the following:
* NetBackup Problems report to determine the device or volume that caused th
e error
* System and error logs for the system
* Event Viewer Application and System logs (Windows)
3. For detailed troubleshooting information, create a debug log directory for b
ptm and retry the operation. Check the resulting debug log files.
Error Number: 95
requested media id not found in NB media database and/or MM volume database
An operation was requested on a media ID for which NetBackup does not have a rec
ord. An example of this is using bpmedia to suspend or freeze a media ID that do
es not exist.
Run a NetBackup Media List report to determine the valid media IDs. Then, retry
the command with a valid media ID.
Error Number: 96
unable to allocate new media for backup, storage unit has none available
The tape manager (bptm) could not allocate a new volume for backups. This indica
tes that the storage unit has no more volumes available in the volume pool for t
his backup.
Check the NetBackup Problems report to determine the storage unit that is out of
media.
1. If the storage unit is a robot and there are empty slots, add more volumes (
remember to specify the correct volume pool).
* If there are no empty slots, move some media to nonrobotic and then add ne
w volumes.
* If you are having difficulty keeping track of your available volumes, try
the available_media script:
On UNIX, this script is in:
/usr/openv/netbackup/bin/goodies/available_media
On Windows, the script is in:
install_path\NetBackup\bin\goodies\available_media.cmd
This script lists all volumes in the Media Manager volume configuration, a
nd augments that list with information on the volumes currently assigned to NetB
ackup.
2. If the storage unit and volume pool appear to have media, verify the followi
ng:
* Volume is not FROZEN or SUSPENDED.
Check for this condition by using the NetBackup Media List report. If the
volume is frozen or suspended, use the bpmedia command to unfreeze or unsuspend
it (if that is desired).
* Volume has not expired or exceeded its maximum number of mounts.
* Volume Database Host name for the device is correct.
If you change the Volume Database Host name, stop and restart the Media Ma
nager device daemon, ltid, (if the server is UNIX) or the NetBackup Device Manag
er service (if the server is a Windows system).
* The correct host is specified for the storage unit in the NetBackup config
uration.
The host connection should be the server (master or media) that has drives
connected to it.
* The Media Manager volume configuration has media in the correct volume poo
l and unassigned or active media is available at the required retention level.
Use the NetBackup Media List report to show the retention levels, volume p
ools, and status (active and so on) for all volumes. Use the NetBackup Media Sum
mary report to check for active volumes at the correct retention levels.
3. In some configurations, the NetBackup bptm process is rejected when requesti
ng media from the vmd process (NetBackup Volume Manager service on Windows) beca
use that process cannot determine the name of the host that is making the reques
t.
This can be due to incorrect network configuration involving:
* Multiple network interfaces
* /etc/resolv.conf on those UNIX systems that use it
* Running DNS and not having reverse addressing configured
4. Create bptm and vmd debug log directories and retry the operation.
5. Examine the bptm debug log to verify that bptm is connecting to the correct
system. If an error is logged, examine the vmd log.
On UNIX, the vmd log is:
/usr/openv/volmgr/debug/daemon/log.xxxxxx
On Windows, the vmd log is:
install_path\Volmgr\debug\daemon\xxxxxx.log
6. If this is a new storage unit, and this is the first attempt to use it, stop
and restart NetBackup on the master server.
Note: The bptm debug logs (in verbose mode) usually show the NetBackup media sel
ection process.
Error Number: 97
requested media id is in use, cannot process request
An operation was requested on a media ID that is in use. An example of this is a
ttempting to suspend or freeze a volume while it is being used for a backup or r
estore.
Retry the command when the volume is not in use. Use the Device Monitor to deter
mine if the volume is in use.
Error Number: 98
error requesting media (tpreq)
The tape manager and optical manager (bptm) received an error when requesting a
media mount from the NetBackup Device Manager service on Windows or the Media Ma
nager device daemon (ltid) on UNIX.
Try the following.
* Check the NetBackup Problems report to determine the reason for the failure.
The most common cause is that the NetBackup Device Manager service on Windows or
the Media Manager device daemon (ltid) on UNIX is not running. Start it if nece
ssary.
* If duplicating backups or using Vault to duplicate backups, this error could
be an indication that the Alternate Read Server does not have access to the tape
on which the original backup resides.
Error Number: 99
NDMP backup failure
None of the paths in your NDMP policy file list was backed up successfully.
Check the NetBackup All Log Entries report for more information. A possible caus
e for this error is that none of the backup paths exist on the NDMP host.
Error Number: 100
system error occurred while processing user command
A system call failed in bparchive, bpbackup, bplist, or bprestore.
Try the following.
1. Enable debug logging for bparchive, bpbackup, bplist, or bprestore (as appro
priate) by creating debug log directories for them.
On UNIX, if a nonroot user is having problems, verify that the directory crea
ted has mode 666. Look for and correct any reported errors.
2. Retry the operation and check the resulting logs.
If the logs do not reveal the problem, use the command line version of the co
mmand and correct any problems that are reported on stderr.
Error Number: 101
failed opening mail pipe
The process that attempts to send mail could not open the pipe to the server.
Verify that mail is configured on the client. For detailed troubleshooting infor
mation, create a bpcd debug log directory and retry the operation. Check the res
ulting bpcd debug log.
Error Number: 102
failed closing mail pipe
The process that sends mail could not close the pipe to the server.
Verify that mail is configured on the client. For detailed troubleshooting infor
mation, create a bpcd debug log directory and retry the operation. Check the res
ulting bpcd debug log.
Error Number: 103
error occurred during initialization, check configuration file
None
None
Error Number: 104
invalid file pathname
None
None
Error Number: 105
file pathname exceeds the maximum length allowed
The path name built by using the current working directory exceeds the maximum p
ath length allowed by the system.
Shorten the current working directory path length.
Error Number: 106
invalid file pathname found, cannot process request
One of the file paths to be backed up or archived is not valid.
Verify that full path names are used (they start with / on UNIX), and they are l
ess than the maximum path length for the system. Also, verify that the files exi
st and the permissions allow NetBackup to access them.
Error Number: 107
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 108
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 109
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 110
Cannot find the NetBackup configuration information
On Windows, NetBackup could not read the registry entries that were created duri
ng installation. On UNIX, the /usr/openv/netbackup/bp.conf file does not exist.
On Windows, reinstall NetBackup software on the client. On UNIX, create a /usr/o
penv/netbackup/bp.conf file with at least the following lines:
SERVER = server_name
CLIENT_NAME = client_name
Error Number: 111
No entry was found in the server list
On UNIX, the SERVER = server_name line is missing in the bp.conf file. On Window
s, the server list contains no entries.
Try the following.
* On a UNIX client, add the following line to the top of the /usr/openv/netback
up/bp.conf file:
SERVER = server_name
* On a Microsoft Windows or nontarget NetWare client, add the server name on th
e Servers tab in the Specify NetBackup Machines dialog box. To display this dial
og, start the Backup, Archive, and Restore interface on the client and click Spe
cify NetBackup Machines on the Actions menu.
* On an OS/2 or NetWare target client, add the server name to the bp.ini file.
* On a Macintosh client, add the SERVER = server_name line to the bp.conf file
in the NetBackup folder in the Preferences folder.
Error Number: 112
no files specified in the file list
A restore was requested with no files in the file list.
Specify at least one file to be restored.
Error Number: 113
EC_badop
None
None
Error Number: 114
EC_error
None
None
Error Number: 115
EC_end
None
None
Error Number: 116
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 117
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 118
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 119
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 120
cannot find configuration database record for requested NB database backup
The program that backs up the NetBackup internal catalogs could not find the att
ributes that indicate which media IDs to use or paths to back up. This error sho
uld not occur under normal circumstances.
Try the following.
1. Check the NetBackup Problems report for additional information about the err
or.
2. For detailed troubleshooting information, create admin and bpdbm debug log d
irectories and retry the operation. Check the resulting debug logs.
3. Contact customer support and send appropriate problem and debug log sections
detailing the error.
Error Number: 121
no media is defined for the requested NB database backup
NetBackup attempted to back up its internal catalogs and there were no media IDs
defined in the catalog backup configuration.
Add the media IDs to the catalog backup configuration. Verify that the media IDs
are in the NetBackup volume pool.
Error Number: 122
specified device path does not exist
The NetBackup internal catalogs were backed up by using the bpbackupdb command l
ine and specifying a raw device file that does not exist.
Retry the command using a valid device file name.
Error Number: 123
specified disk path is not a directory
NetBackup attempted to back up its internal catalogs and the backup attributes w
ere set to dump to a disk. However, the disk file path already exists and is not
a directory.
Specify a different disk path for the catalog backup or delete the file that alr
eady exists.
Error Number: 124
NB database backup failed, a path was not found or is inaccessible
One or more of the paths specified in the catalog backup configuration could not
be backed up.
Try the following.
1. Check the NetBackup Problems report for additional information about the err
or. Some possible causes are:
* The path does not exist.
* On a UNIX system, there is a symbolic link in one of the paths.
2. After determining which path could not be accessed, correct the path names i
n the catalog backup configuration.
Error Number: 125
another NB database backup is already in progress
Only one NetBackup catalog backup may be active at any given time.
None.
Error Number: 126
NB database backup header is too large, too many paths specified
Too many paths were specified in the NetBackup catalog backup configuration to f
it in a fixed-size media header. This error should not occur under normal circum
stances.
Delete some of the paths from the catalog backup configuration.
Error Number: 127
specified media or path does not have a valid NB database backup header
The bprecover command was issued and the media ID specified does not have valid
catalog backup data.
Validate that the correct media ID is being used.
Error Number: 128
NB database recovery failed, a process has encountered an exceptional condition
One or more catalogs specified for recovery could not be restored. For more deta
il, refer to the error message issued just above this status code in the output
from the bprecover command.
Try the following.
1. After fixing the problem reported in the error message in the bprecover outp
ut, refer to Recovering the NetBackup Databases in the Troubleshooting Guide to
identify which NetBackup services (Windows) or daemons (UNIX) should be shut dow
n prior to attempting the NetBackup database recovery. The NetBackup services sh
ould be shut down except for the NetBackup Client Service, which must be running
for the database recovery to succeed.
2. Check the NetBackup Problems report for additional information about the err
or. Some possible causes are:
* A disk may be full.
* The NetBackup catalog tape may be corrupt.
Error Number: 129
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 130
system error occurred
An error occurred that prevents the product from operating in a consistent fashi
on. This error is usually related to a system call.
Try the following.
1. Check the NetBackup Problems report for additional information about the err
or.
2. Check the system log for reported problems.
3. For detailed troubleshooting information, create bpdbm, bpsched, bptm, and b
prd debug log directories on the master server and retry the operation. Check th
e resulting debug logs.
Error Number: 131
client is not validated to use the server
The client name, as determined from the connection to the server, did not match
any client name in the NetBackup configuration and there was no altnames configu
ration for this client on the master server. A client and server that have multi
ple network connections can encounter this problem if the name by which the clie
nt is configured is not the one by which its routing tables direct connections t
o the server.
Try the following.
1. Examine the NetBackup Problems report.
2. Create a debug log directory for bprd and retry the operation. Check the res
ulting debug log to determine the connection and client names.
Depending on the request type (restore, backup, and so on.), you may need or
want to:
* Change the client's configured name.
* Modify the routing tables on the client.
* On the master server, set up an altnames directory and file for this clien
t (see the NetBackup System Administrator's Guide for UNIX).
or
* On a UNIX master server, create a soft link in the NetBackup image catalog
.
3. Review Verifying Host Names and Services Entries in the Troubleshooting Guid
e.
Error Number: 132
user is not validated to use the server
None
None
Error Number: 133
invalid request
One of two explanations exist.
* A request was made that is unrecognized. This usually results from different
versions of NetBackup software being used together.
* If a client receives this error in response to a list or restore request, it
means that the DISALLOW_CLIENT_LIST_RESTORE or DISALLOW_CLIENT_RESTORE option ex
ists in the bp.conf file on a UNIX NetBackup server or registry on a Windows Net
Backup server. These options deny list and restore requests from all NetBackup c
lients.
Try the following.
1. If you suspect that the software versions are the problem, verify that all N
etBackup software is at the same version level.
* On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/
version file.
* On Windows NetBackup servers, check the install_path\netbackup\version.txt
file or the About NetBackup item on the Help menu.
* On Microsoft Windows clients, check the About NetBackup item on the Help m
enu.
* On NetWare target clients, check the Version entry in the bp.ini file.
If the client software is earlier than 3.0, verify that the client is in a
Standard type policy.
* On Macintosh clients, check the version file in the bin folder in the NetB
ackup folder in the Preferences folder.
2. If the server is denying list and restore requests, remove the DISALLOW_CLIE
NT_LIST_RESTORE and DISALLOW_CLIENT_RESTORE options from the bp.conf file on a U
NIX NetBackup server or registry on a Windows NetBackup server. Then, stop and r
estart the NetBackup request daemon (UNIX) or NetBackup Request Manager service
(Windows).
3. For detailed troubleshooting information, create bpdbm, bprd, and admin debu
g log directories. Then, retry the operation and check the resulting debug logs.
Error Number: 134
unable to process request because the server resources are busy
Status code 134 is an informational message indicating that all drives in the st
orage unit are currently in use. If this occurs, NetBackup automatically tries a
nother storage unit; if one is not available, NetBackup requeues the job with a
status of 134 and retries it later.
Disable automatic retry using another storage unit and create the following file
on the NetBackup media server prior to running the backups:
/usr/openv/volmgr/DISABLE_RESOURCES_BUSYIf you have already attempted the backu
p and see this error, then create the file and rerun the backups.
Error Number: 135
client is not validated to perform the requested operation
This is usually caused by a request to restore files to a client other than the
one that made the request and the request did not come from the root user (admin
istrator on Windows) on a NetBackup server.
Retry the operation as a root user (administrator on Windows) on the master serv
er. Also see status code 131.
Error Number: 136
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 137
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 138
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 139
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 140
user id was not superuser
The process was started by a user or process that did not have root privileges (
on UNIX) or administrator privileges (on Windows).
If desired, give the user or process administrator privileges (on Windows) or ro
ot privileges (on UNIX) and retry the operation.
Error Number: 141
file path specified is not absolute
The file specification must be an absolute path.
Correct the file specification and retry the command.
Error Number: 142
file does not exist
This code is reserved for future use.
None.
Error Number: 143
invalid command protocol
An ill-formed request was made to the NetBackup request daemon (UNIX) or Request
Manager service (Windows). This can be due to mismatched versions of the produc
t, corrupted network communication, or to a non-NetBackup process sending data a
cross the port for the daemon or service.
Examine the NetBackup error logs to determine the system that was the source of
the data and on that system determine the process that initiated the request. If
it was a NetBackup process, verify that the process or command is compatible wi
th the version of software on the server.
Error Number: 144
invalid command usage
This status code is due to a NetBackup process being started with improper optio
ns or an incompatibility in the product.
Either correct the command or verify that all NetBackup binaries are at the same
version level.
Error Number: 145
daemon is already running
There is another copy of the process executing.
Terminate the current copy of the process and then restart the process.
Error Number: 146
cannot get a bound socket
The daemon (service on Windows) could not bind to its socket. A system call fail
ed when the daemon (UNIX) or service (Windows) attempted to bind to its configur
ed port number. This is usually caused by another process having acquired the po
rt before the daemon or service started.
Try the following.
1. Examine the NetBackup Problems and All Log Entries reports.
2. Create bprd and bpdbm debug log directories and retry the operation. Check t
he resulting logs to see the system error message resulting from the attempt.
If another process has the port, use other system commands to determine the p
rocess. Based on this research, either change the port number in your services f
ile or map or terminate the process that has acquired the port.
On UNIX, another possible cause for this error is terminating bprd or bpdbm w
ith the kill command. If you have to stop bprd, the recommended method is to use
the Terminate Request Daemon option on the Special menu in bpadm (or the equiva
lent option in xbpadm). To stop bpdbm, use the /usr/openv/netbackup/bin/bpdbm -t
erminate command. Using the kill command to stop these processes can leave them
unable to bind to their assigned ports the next time they are started.
To identify a bprd or bpdbm problem, look for lines similar to the following
in the debug log for the respective process:
<16> getsockbound: bind() failed, Address already in use (114)
<32> listen_loop: cannot get bound socket. errno = 114
<4> terminate: termination begun...error code = 146
Similar entries can appear in the reports.
3. If the problem persists longer than ten minutes, it is possible that it will
be necessary to reboot the server.
Error Number: 147
required or specified copy was not found
The requested copy number of a backup or archive image cannot be found.
Correct the request to specify a copy number that does exist.
Error Number: 148
daemon fork failed
A NetBackup service could not create a child process due to an error received fr
om the system. This is probably an intermittent error based on the availability
of resources on the system.
Try the following.
1. Restart the service at a later time and investigate system problems that lim
it the number of processes.
2. Check the Event Viewer Application and System logs (Windows).
Error Number: 149
master server request failed
None
None
Error Number: 150
termination requested by administrator
The process is terminating (or has terminated) as a direct result of a request f
rom an authorized user or process.
None.
Error Number: 151
Backup Exec operation failed
The Global Data Manager console has reported that a Backup Exec job (backup, arc
hive, or restore) did not complete normally.
Consult the Backup Exec job history on the Backup Exec server for details.
Error Number: 152
required value not set
An incomplete request was made to the bpdbm process (NetBackup Database Manager
service on Windows). This usually occurs because different versions of software
are being used together.
Try the following.
1. Verify that all software is at the same version level.
2. For detailed troubleshooting information, create bpdbm and admin debug log d
irectories and retry the operation. Check the resulting debug logs.
Error Number: 153
server is not the master server
This status code is reserved for future use.
None.
Error Number: 154
storage unit characteristics mismatched to request
A backup was attempted and the storage unit selected for use had characteristics
that were not compatible with the backup type.
Verify that the characteristics of the storage unit involved are appropriate for
the backup attempted:
* For NetBackup ServerFree Agent only:
The policy storage unit was set to Any_available and the offhost backup metho
d was set to Third-Party Copy Device or NetBackup Media Server. Do not choose An
y_available. A particular storage unit (such as nut-4mm-robot-tl4-0) must be spe
cified when Third-Party Copy Device or NetBackup Media Server is specified as th
e offhost backup method.
* For an NDMP policy type, verify that a storage unit of type NDMP is defined a
nd the NDMP host value matches the host name of the client. For example, if the
NDMP policy specifies toaster as the client, the configuration for the storage u
nit must specify toaster as the NDMP host.
* For a policy type other than NDMP, verify that the policy specifies a Media M
anager or Disk type storage unit.
Error Number: 155
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 156
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 157
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 158
failed accessing daemon lock file
The process could not lock its lock file because an error was received from a sy
stem call. This lock file synchronizes process activities (for example, preventi
ng more than one daemon from executing at a time).
Try the following.
1. Examine the NetBackup error log to determine why the system call failed and
correct the problem. It could be a permission problem.
2. If the error log does not show the error, create a debug log directory for b
prd, bpdbm, or bpsched (depending on which process encountered the error) and re
try the operation. Examine the resulting debug log.
Error Number: 159
licensed use has been exceeded
A configuration limit has been exceeded. An example is number of drives allowed
per server.
To determine the cause, examine the NetBackup error logs for the command that wa
s being executed.
Error Number: 160
authentication failed
A problem was encountered when two systems were attempting to authenticate one a
nother.
See the NetBackup System Administrator's Guide for UNIXfor more information on t
he files and commands mentioned here.
1. Ensure that the authentication libraries exist:
Windows:
install_path\NetBackup\lib\libvopie.dll
install_path\NetBackup\lib\libnoauth.dll
UNIX (except HP-UX):
/usr/openv/lib/libvopie.so
/usr/openv/lib/libnoauth.so
UNIX (HP-UX only):
/usr/openv/lib/libvopie.sl
/usr/openv/lib/libnoauth.sl
Macintosh:
:System Folder:Extensions:libvopie.dll
:System Folder:Extensions:libnoauth.dll
2. Check the methods_allow.txt files on the systems that are having problems to
ensure that authentication is enabled. The files are in the following locations
:
Windows:
install_path\NetBackup\var\auth
UNIX:
/usr/openv/var/auth
Macintosh:
:System Folder:Preferences:NetBackup:var:auth
If one system reports authentication failed (status code 160) and the other s
ystem reports network connection timed out (status code 41), you may have enable
d authentication in the first system's methods_allow.txt file but not in the sec
ond system's methods_allow.txt file.
3. On the systems that are having the authentication problem, remove the remote
host that is not being authenticated from the methods_allow.txt file.
For example, if host A and host B are having the problem, remove host A from
the file on host B and vice versa.
Retry the operation.
* If the problem still exists, it indicates connection problems not related
to authentication.
* If connections are now successful, proceed to the next step.
4. Execute bpauthsync -vopie on the master server to resynchronize the key file
s on the systems.
On Windows:
install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers -clients
On UNIX:
/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers -clients
5. Add back the names removed in step 3 and retry the operation.
6. Create debug log directories for the processes involved in authentication be
tween NetBackup systems. These include:
* On the server, create debug log directories for bprd, bpdbm, bpcd.
* On the client, create debug log directories for bpbackup, bprestore, bpbka
r (Windows only).
Retry the operation and check the logs.
Error Number: 161
Evaluation software has expired. See www.veritas.com for ordering information.
The time allowed for the NetBackup evaluation software has ended.
Obtain a licensed copy of NetBackup.
Error Number: 162
Incorrect server platform for license
The platform identifier in the license key does not match the platform type on w
hich the key was installed.
Ensure that you are using a license key that was intended for the platform on wh
ich you are installing.
Error Number: 163
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 164
unable to mount media because it is in a DOWN drive or misplaced
A restore was attempted and the volume required for the restore was in a DOWN dr
ive in a robot. Or, the slot that should contain the volume is empty.
Try the following.
* If volume is in a DOWN drive, remove it and place it in its designated slot.
Then, retry the restore.
* If the volume is in the wrong slot, use a robot inventory option to reconcile
the contents of the robot with the Media Manager volume configuration.
Error Number: 165
NB image database contains no image fragments for requested backup id/copy numbe
r
A restore was attempted and NetBackup has no record of fragments associated with
the backup ID that has the files.
Check the NetBackup Problems report for additional information about the error.
For detailed troubleshooting information, create a debug log directory for eithe
r bpdm or bptm (whichever applies) and retry the operation. Check the resulting
debug log.
Error Number: 166
backups are not allowed to span media
An end of media (EOM) was encountered while the backup image was being written.
The backup was terminated because the NetBackup DISALLOW_BACKUPS_SPANNING_MEDIA
option was present in bp.conf on UNIX or the registry on Windows. The backup wil
l be retried automatically with a different volume if this is allowed by the bac
kup tries attribute in the NetBackup global attribute configuration.
None.
Error Number: 167
cannot find requested volume pool in Media Manager volume database
A backup to a nonrobotic drive was attempted and the tape manager (bptm) could n
ot find or add the specified volume pool.
Verify the Media Manager volume configuration. Check the NetBackup Problems repo
rt for more information about the error. For detailed troubleshooting informatio
n, create a bptm debug log directory and retry the operation. Check the resultin
g debug log.
Error Number: 168
cannot overwrite media, data on it is protected
A catalog backup was attempted to a volume that could not be overwritten because
it contains data that NetBackup, by default, does not overwrite (tar, cpio, ANS
I, and so on).
Replace the volume with a new one or set the NetBackup ALLOW_MEDIA_OVERWRITE opt
ion to the appropriate value.
Error Number: 169
media id is either expired or will exceed maximum mounts
A backup or catalog backup was attempted and the volume selected for use has rea
ched its maximum number of mounts as specified in the Media Manager volume confi
guration. For a regular backup, the volume is automatically set to the SUSPENDED
state and not used for further backups. For a NetBackup catalog backup, the ope
ration terminates abnormally.
If the volume was suspended, wait until it expires and then replace it. For NetB
ackup catalog backups, replace the media.
Error Number: 170
third-party copy backup failure
Usually indicates a problem with the 3pc.conf file or the mover.conf file. (For
detailed causes, see recommended actions.) For more information on these files,
refer to "Creating Configuration Files for Offhost Backup" in NetBackup Configur
ation chapter of the NetBackup ServerFree Agent System Administrator's Guide.
Try the following.
* If a non third-party copy device is listed in 3pc.conf file, correct or remov
e the non third-party copy device entry.
* An incorrect lun is specified in the 3pc.conf file, or the device does not ex
ist. Correct the 3pc.conf file as appropriate.
* An appropriate mover.conf file (with or without file-name extension) could no
t be found. In this case, the /usr/openv/netbackup/logs/bptm log may also show t
he following:
09:51:04 [22281] <2> setup_mover_tpc: no mover.conf.vertex_std_tpc
or mover.conf file exists, cannot perform TPC backup
09:51:04 [22281] <16> bptm: unable to find or communicate with
Third-Party-Copy mover for policy vertex_std_tpc
Make sure that an appropriate mover.conf file exists in /usr/openv/netbackup
on the media server. This file can be any of the following:
* mover.conf.policy_name file, where policy_name exactly matches the name of
the policy.
* mover.conf.storage_unit_name, where storage_unit_name exactly matches the
name of the storage unit selected in the Backup Policy Management Policy attribu
tes dialog (such as nut-4mm-robot-tl4-0).
* mover.conf file (no extention) for configurations that have only one third
-party copy device.
Note that NetBackup looks for an appropriate mover.conf file in the above ord
er.
* The SCSI pass-through path of the third-party copy device, as entered in the
mover.conf file (with or without file-name extension), does not exist. In this c
ase, the /usr/openv/netbackup/logs/bptm log may also show the following:
09:50:12 [22159] <16> setup_mover_tpc: open of passthru path
/dev/sg/cXtXlX failed, No such file or directory
09:50:12 [22159] <16> bptm: unable to find or communicate with
Third-Party-Copy mover for policy vertex_std_tpc
Correct the SCSI pass-through path of the third-party copy device that is ent
ered in the mover.conf file.
* The third-party copy device returned an error.
If you see either of the following messages in /usr/openv/netbackup/ logs/bpt
m log:
cannot process extended copy error due to truncated
sense data, may be HBA problem
disk error occurred on extended copy command, key = 0x0,
asc = 0x0, ascq = 0x0 (where key, asc and ascq are all zero)
your host-bus adapter (HBA) and its driver may need to be updated, or may not
be supported by NetBackup ServerFree Agent. The host-bus adapters and drivers s
upported in the release are listed in Chapter 2 of the NetBackup Release Notes.
* For additional troubleshooting details, refer to the Troubleshooting chapter
of the NetBackup ServerFree Agent System Administrator's Guide.
Error Number: 171
media id must be 6 or less characters
An operation, such as using bpmedia to suspend or freeze a media ID, was attempt
ed and the media ID specified was longer than six alpha-numeric characters.
Retry the command with a valid media ID.
Error Number: 172
cannot read media header, may not be NetBackup media or is corrupted
When loading a volume for a backup or restore, the tape manager (bptm), did not
find the expected tape header. This can mean that a volume in a robotic device i
s not in the slot number shown in the Media Manager volume configuration or that
a read error (I/O error) occurred.
Try the following.
1. If the volume is in a robot that supports barcodes, verify the robot content
s by using a Media Manager robot inventory option.
2. If the volume was mounted on a nonrobotic drive, verify that the correct vol
ume was mounted and assigned.
3. Check the NetBackup Problems report. If a fatal read error occurred, attempt
the operation again using another drive, if possible.
4. If your configuration has multiple servers / HBAs with access to your tape s
ervices (most likely, an SSO configuration), make sure the SCSI Reserve / Releas
e is configured correctly. For more information, refer to the NetBackup SAN Shar
ed Storage Option System Administrators Guide for UNIX and Windows.
Error Number: 173
cannot read backup header, media may be corrupted
When searching for a backup image to restore, the tape manager (bptm) could not
find the correct backup ID at the position on the media where NetBackup expected
it to be. This can indicate a drive hardware problem.
Try the following.
1. Check the NetBackup Problems report for clues as to what caused the error.
2. Try the restore on another drive if possible.
3. For detailed troubleshooting information, create a debug log directory for b
ptm and retry the operation. Check the resulting debug log.
Error Number: 174
media manager - system error occurred
An abnormal condition occurred causing a tape manager (bptm) or disk manager (bp
dm) failure. This should not occur under normal circumstances.
Note: If this occurs on a Sequent platform and you are attempting to back up mor
e than four gigabytes of data, save all your logs and call VERITAS technical sup
port. For other platforms perform the recommended actions described below.
Try the following.
1. Check the NetBackup Problems report to see if it shows the cause of the prob
lem. If you see a Problems report message similar to
"attempting to write 32767 bytes, not a multiple of 1024"
save all logs and call VERITAS customer support.
2. On UNIX, if this occurs during a restore, it may be that the tape drive is i
ncorrectly configured to write in fixed length mode when it should write in vari
able length mode.
Verify your drive's configuration, comparing it to what is recommended in the
Media Manager Device Configuration Guide (also see step 7 of this procedure).
If your configuration incorrectly specifies fixed length mode, change the con
figuration to specify variable length mode and suspend media that were written o
n that device. The images written to those media may be restorable (this is plat
form dependent), but single file restores are almost guaranteed to fail.
3. If you see the problem with only one client, verify that the client binaries
are correct, especially those for bpcd.
4. Can you read or write any other images on this media?
If so, check the following reports for clues:
* Images on Media report
* Media Contents report
5. Verify the following:
* The media by using the NetBackup image verify option.
* That you are using the correct media type for the device.
6. Check the system or console log for errors (on UNIX) or the Event Viewer App
lication log (on Windows).
7. For detailed debug information, create a debug log directory for either bptm
or bpdm (whichever applies) and retry the operation. Check the resulting debug
log.
If the bptm debug log shows an error similar to
00:58:54 [2304] <16> write_data: write of 32768 bytes
indicated only 29696 bytes were written, errno = 0
it may be that the tape drive is configured to write in fixed length mode rat
her than variable length mode, and the image being written encountered the end-o
f-media.
Take the corrective action suggested in step 2.
Error Number: 175
not all requested files were restored
When restoring files from an image, the bptm or bpdm process detected a fatal er
ror condition and terminated the restore before it completed. This should not oc
cur under normal circumstances.
Try the following.
1. Check the NetBackup Problems report and the progress log on the client for a
dditional information about the error
2. For detailed troubleshooting information, create a debug log directory for e
ither bptm or bpdm (whichever applies) and retry the operation. Check the result
ing debug log.
Error Number: 176
cannot perform specified media import operation
The tape manager (bptm) detected an error condition when attempting to import a
specific backup image. Possible reasons for this are:
* Media ID is already active in the NetBackup media catalog on this server
* Media ID is not in the Media Manager volume configuration
* Fatal tape manager (bptm) error occurred
* Total image was not obtained from Phase 1 of import
Try the following.
1. Check the NetBackup Problems report to find the exact cause of the failure.
2. Try the following:
* If the media ID is already active, duplicate all images on the original me
dia ID to another volume. Then, manually expire the original media and redo the
import.
* If the media ID is not present in the Media Manager volume configuration,
add it.
* If a fatal bptm error occurred, verify that the Media Manager volume daemo
n (vmd) is active on UNIX or the NetBackup Volume Manager service is active on W
indows.
* If the entire image is not present, perform import phase 1 on the media ID
s that have the remainder of the image.
Error Number: 177
could not deassign media due to Media Manager error
The tape manager (bptm) could not successfully deassign a media ID.
Try the following.
1. Check the NetBackup Problems report for the cause of the problem.
2. Verify that the Media Manager volume daemon (vmd) is active on UNIX or the N
etBackup Volume Manager service is active on Windows.
3. For detailed troubleshooting information, create a debug log directory for b
ptm and retry the operation. Check the resulting debug log.
Error Number: 178
media id is not in NetBackup volume pool
NetBackup attempted a backup of its catalogs and the media ID specified for the
catalog backup was not in the NetBackup volume pool. Volumes for catalog backups
must be in the NetBackup volume pool.
Check the Media Manager volume configuration to verify that the media IDs are pr
esent and in the NetBackup volume pool.
Error Number: 179
density is incorrect for the media id
An operation such as "list contents" was attempted on an invalid media ID, such
as a cleaning tape. Another possibility is that a media ID in the NetBackup cata
log backup configuration does not match the media type entered in the Media Mana
ger volume configuration.
Check the volume configuration and the NetBackup catalog backup configuration an
d correct any problems found.
Error Number: 180
tar was successful
tar returned a successful exit status.
None.
Error Number: 181
tar received an invalid argument
One of the parameters passed to tar was not valid.
On a UNIX client:
* Ensure that the tar command in /usr/openv/netbackup/bin is the one provided b
y NetBackup. If you are in doubt, reinstall it.
* Check /usr/openv/netbackup/bin/version on the client to verify that the clien
t is running the correct level software. If the software is not at the correct l
evel, update the software per the directions in the NetBackup release notes.
* On a Windows client, create a tar debug log directory, retry the operation, a
nd check the log.
* On a Macintosh client, check the version file that is in the bin folder in th
e NetBackup folder in the Preferences folder. If the software is not at the corr
ect level, install the correct software as explained in the installation guide.
Error Number: 182
tar received an invalid file name
tar cannot write to the file that is specified with the -f parameter.
Try the following.
1. Create a bpcd debug log directory on the client (on a Macintosh NetBackup cr
eates the log automatically).
2. On a Windows client, create a tar debug log directory.
3. Increase the logging level on the client:
* On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.co
nf file.
* On PC clients, increase the debug or log level as explained in the debug l
og topics in Chapter3.
4. Rerun the operation, check the resulting debug logs for the parameters passe
d to tar and call customer support.
Error Number: 183
tar received an invalid archive
The data passed to tar was corrupt.
Try the following.
* If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar
debug log directory on the client and rerun the operation.
a. Check the tar debug log file for error messages that explain the problem.
b. Reboot the client to see if this clears the problem.
c. When you are through investigating the problem, delete the /usr/openv/net
backup/logs/tar directory on the client.
* If the problem is with a Microsoft Windows, NetWare, or Macintosh client:
a. Create a bpcd debug log directory on the client (on a Macintosh NetBackup
creates the log automatically).
b. On a Windows client, create a tar debug log directory.
c. Increase the debug or log level as explained in the debug log topics in C
hapter3.
d. Rerun the operation and check the resulting debug logs.
e. Reboot the client to see if it clears the problem.
Error Number: 184
tar had an unexpected error
A system error occurred in tar.
Try the following.
* If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar
debug log directory on the client and rerun the operation.
a. Check the tar debug log file for error messages that explain the problem.
b. Reboot the client to see if this clears the problem.
c. When you are through investigating the problem, delete the /usr/openv/net
backup/logs/tar directory on the client.
* If the problem is with a Microsoft Windows, NetWare, or Macintosh client:
a. Create a bpcd debug log directory on the client (on a Macintosh NetBackup
creates the log automatically).
b. Increase the debug or log level as explained in the debug log topics in C
hapter3.
c. On a Windows client, create a tar debug log directory.
d. Retry the operation and check the resulting debug logs.
e. Reboot the client to see if it clears the problem.
Error Number: 185
tar did not find all the files to be restored
There were files in the tar file list that were not in the image.
Try the following.
* If the problem is with a UNIX client:
a. Enable bpcd debug logging by creating the /usr/openv/netbackup/logs/bpcd
directory on the client.
b. Rerun the operation, check the resulting bpcd log file for the parameters
passed to tar, and call customer support.
* If the problem is with a Microsoft Windows, NetWare, or Macintosh client:
a. Create a bpcd debug log directory on the client (on a Macintosh NetBackup
creates the log automatically).
b. Increase the debug or log level as explained in the debug log topics in C
hapter3.
c. On a Windows client, create a tar debug log directory.
d. Retry the operation.
e. Check the resulting debug logs for the parameters passed to tar and call
customer support.
Error Number: 186
tar received no data
The media manager did not send data to tar.
Try the following.
1. Retry the operation and check the progress log on the client for error messa
ges that reveal the problem.
2. Verify that the tape is available and readable.
3. Verify that the drive is in an UP state. Use the Device Monitor
4. For detailed troubleshooting information:
a. Create a bptm debug log on the server.
b. On a Windows client, create a tar debug log.
c. Retry the operation and check the resulting debug logs.
Error Number: 187
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 188
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 189
the server is not allowed to write to the client's filesystems
The client is not allowing writes from the server.
Perform the following to perform restores or install software from the server.
* On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the /usr/openv/netb
ackup/bp.conf file.
* On a Microsoft Windows or NetWare nontarget client, select Allow server-direc
ted restores on the General tab in the NetBackup Configuration dialog box. To di
splay this dialog box, start the Backup, Archive, and Restore interface on the c
lient and click Configure on the Actions menu.
* On a Macintosh client, delete DISALLOW_SERVER_FILE_WRITES from the bp.conf fi
le in the NetBackup folder in the Preferences folder.
* On a NetWare target client, set ALLOW_SERVER_WRITE to yes in the bp.ini file.
Error Number: 190
found no images or media matching the selection criteria
A verify, duplicate, or import was attempted and no images matching the search c
riteria were found in the NetBackup catalog.
Change the search criteria and retry.
Error Number: 191
no images were successfully processed
A verify, duplicate, or import was attempted and failed for all selected images.
Try the following.
* Check the NetBackup Problems report for the cause of the error. To obtain det
ailed troubleshooting information, create an admin debug log directory and retry
the operation. Check the resulting debug log.
* If the error was encountered during duplication of backups, check the duplica
tion progress log to help determine the root cause of the problem.
* If the error was encountered by a Vault job which is doing duplication, check
the duplicate.log files in your sidxxx directories to help determine the root c
ause of the problem:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Error Number: 192
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 193
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 194
the maximum number of jobs per client is set to 0
The NetBackup Maximum jobs per client global attribute is currently set to 0. Se
tting the value to 0 disables backups and archives.
To enable backups and archives, change the Maximum jobs per client value to the
desired nonzero setting. This attribute is on the Global NetBackup Attributes ta
b in the Master Server Properties dialog box. See Using the Host Properties Wind
ow in the Troubleshooting Guide.
Error Number: 195
client backup was not attempted
A backup job was in the NetBackup scheduler's worklist but was not attempted.
Try the following.
1. Retry the backup either immediately with a manual backup or allow the normal
scheduler retries.
2. For additional information, check the All Log Entries report. For detailed t
roubleshooting information, create a bpsched debug log directory on the master s
erver. After the next backup attempt, check the debug log.
Some actions to perform are:
* Verify that the vmd and ltid daemons (UNIX) or the NetBackup Volume Manage
r and NetBackup Device Manager services (Windows) are running.
* Look for a problem in an earlier backup that made the media or storage uni
t unavailable.
Error Number: 196
client backup was not attempted because backup window closed
A backup or archive operation that was queued by the backup scheduler was not at
tempted because the backup window was no longer open.
Try the following.
* If possible, change the schedule to extend the backup window for this policy
and schedule combination so it does not occur again.
* If the backup must be run, use the Manual Backup command on the Policy menu i
n the Backup Policy Management window to perform the backup. Manual backups igno
re the backup window.
Error Number: 197
the specified schedule does not exist in the specified policy
A user backup or archive request has specified the exact policy and schedule to
use when performing a backup. The policy exists but does not contain the schedul
e.
* On Microsoft Windows and NetWare nontarget clients, you can specify a policy
or schedule on the Backups tab in the NetBackup Configuration dialog box. To dis
play this dialog box, start the Backup, Archive, and Restore interface on the cl
ient and click Configure on the Actions menu.
* On UNIX and Macintosh clients, you can specify a policy or schedule by using
the bp.conf options, BPBACKUP_POLICY or BPBACKUP_SCHED.
* On NetWare target clients, you can specify a policy or schedule in the bp.ini
file.
Try the following.
1. Check the client progress log (if available) to determine the policy and sch
edule that were specified.
2. Check the configuration on the master server to determine if the schedule is
valid for the policy. If the schedule is not valid, either add the schedule to
the policy configuration or specify a valid schedule on the client.
Error Number: 198
no active policies contain schedules of the requested type for this client
A user backup or archive has been requested, and this client is not in a policy
that has a user backup or archive schedule.
Determine if the client is in any policy that has a schedule of the appropriate
type (either user backup or archive).
* If the client is in such a policy, check the general policy attributes to ver
ify that the policy is set to active.
* If the client is not in such a policy, either add a schedule of the appropria
te type to an existing policy that has this client or create a new policy that h
as this client and a schedule of the appropriate type.
Error Number: 199
operation not allowed during this time period
A user backup or archive has been requested and this client is not in a policy t
hat has a user backup or archive schedule with an open backup window. This error
implies that there is an appropriate policy and schedule combination for this c
lient.
Determine the policies to which this client belongs that also have a schedule of
the appropriate type (either user backup or archive).
* If possible, retry the operation when the backup window is open.
* If the backup window is not open during appropriate time periods, adjust a ba
ckup window for a schedule in one of the policies.
Error Number: 200
scheduler found no backups due to run
When checking the policy and schedule configuration, the NetBackup scheduler pro
cess (bpsched) did not find any clients to back up. This could be due to:
* No backup time windows are open (applies only to full and incremental schedul
es).
* Policies are set to inactive.
* The clients were recently backed up and are not due for another backup (based
on Frequency setting for the schedules).
* Policies do not have any clients.
Usually, this message can be considered informational and does not indicate a pr
oblem. However, if you suspect a problem:
1. Examine the NetBackup All Log Entries report to see if there are any message
s in addition to one indicating that the scheduler found nothing to do.
2. Examine the policy configuration for all policies or the specific policy in
question and determine if any of the reasons mentioned in the Explanation sectio
n above apply.
3. To obtain detailed troubleshooting information, create a bpsched debug log d
irectory on the master server and retry the operation. Check the resulting debug
log.
Error Number: 201
handshaking failed with server backup restore manager
A process on the master server encountered an error when communicating with the
media host (can be either the master or a media server). This error means that t
he master and media server processes were able to initiate communication, but en
countered difficulties in completing them. This problem can occur during a backu
p, restore, or media list in a single or multiple server configuration.
Try the following.
1. Determine the activity that encountered the handshake failure by examining t
he NetBackup All Log Entries report for the appropriate time period. If there ar
e media servers, determine if:
* The handshake failure was encountered between the master and a media serve
r.
or
* Only the master server was involved.
2. If necessary, create the following debug log directories for the following:
* bpcd on the NetBackup media host (can be either the master or a media serv
er).
* If the error was encountered during a backup operation, bpsched on the mas
ter server.
* If the error was encountered during a restore operation, bprd on the maste
r server.
* If the error was encountered during a media list operation, admin in the N
etBackup logs/admin directory on the master server.
3. Retry the operation and examine the resulting debug logs for information on
why the error occurred.
Error Number: 202
timed out connecting to server backup restore manager
A process on the master server timed out while trying to initiate communications
with the media host (can be either the master or a media server). This problem
can occur during a backup or restore in either a single or multiple server confi
guration.
Determine which activity encountered the connection timeout failure by examining
the All Log Entries report for the appropriate time period. If there are media
servers, determine if the timeout occurred between the master and a media server
or if only the master was involved.
1. Verify that the schedule specifies the correct storage unit.
2. Execute the ping command from one host to another by using the following com
binations:
* From the master server, ping the master and all media servers by using the
host names found in the storage unit configuration.
* From each of the media servers, ping the master server by using the host n
ame specified in the NetBackup server list. On a UNIX server, this is the first
SERVER entry in the bp.conf file. On a Windows server, the master is designated
on the Servers tab in the Master Server Properties dialog. To access this dialog
, see Using the Host Properties Window in the Troubleshooting Guide.
3. Verify that the master server can communicate with bpcd on the host that has
the storage unit.
After each backup, the scheduler checks the storage unit to see how many driv
es are available (in case the backup caused a drive to be automatically downed).
If bpsched cannot communicate with bpcd, it sets the number of available drives
in that storage unit to 0 and further backups to that storage unit fail.
The available drives remain at 0 until the scheduler is initialized again. Th
erefore, even if bpcd seems to be operating correctly now, check the bpsched and
bpcd debug logs (see below) for records of an earlier failure.
4. See Testing Media Server and Clients in the Troubleshooting Guide and Resolv
ing Network Communication Problems in the Troubleshooting Guide.
5. If necessary, create debug log directories for the following processes and r
etry the operation. Then, check the resulting debug logs on the master server:
* If the error occurred during a backup operation, check the bpsched debug l
ogs. Also, check the bpcd debug logs.
* If the error occurred during a restore operation, check the bprd debug log
s.
Error Number: 203
server backup restore manager's network is unreachable
A process on the master server could not connect to a particular host on the net
work when trying to initiate communication with the media host for a particular
operation. This problem can occur during a backup or restore in either a single
or multiple server configuration.
Determine which activity encountered the network unreachable failure by examinin
g the All Log Entries report for the appropriate time frame. If there is more th
an one NetBackup server (that is, one or more media servers) determine if the ne
twork unreachable failure was encountered between the master and a media server
or if only the master server was involved. Execute the ping command from one hos
t to another by using the following combinations:
1. From the master server, ping the master and all media servers by using the h
ost names in the storage unit configuration.
2. From each of the media servers, ping the master server host by using the hos
t name specified in the NetBackup server list. On a UNIX server, this is the fir
st SERVER entry in the bp.conf file. On a Windows server, the master is designat
ed on the Servers tab in the Master Server Properties dialog. To access this dia
log, see Using the Host Properties Window in the Troubleshooting Guide.
3. See Testing Media Server and Clients in the Troubleshooting Guide and Resolv
ing Network Communication Problems in the Troubleshooting Guide.
4. If necessary, create debug log directories for the following processes and r
etry the operation. Then, check the resulting debug logs on the master server:
* If the error occurred during a backup, check the bpsched debug logs.
* If the error occurred during a restore, check the bprd debug logs.
Error Number: 204
connection refused by server backup restore manager
The media host refused a connection on the port number for bpcd. This error can
be encountered during a backup or restore.
Execute the ping command from one host to another by using the following combina
tions:
Note: Also, see Resolving Network Communication Problems in the Troubleshooting
Guide.
1. From the master server, ping the master and all media servers by using the h
ost names in the storage unit configuration.
2. From each of the media servers, ping the master server by using the name spe
cified in the NetBackup server list. On a UNIX server, this is the first SERVER
entry in the bp.conf file. On a Windows server, the master is designated on the
Servers tab in the Master Server Properties dialog. To access this dialog, see U
sing the Host Properties Window in the Troubleshooting Guide.
3. On UNIX servers, verify that the bpcd entries in /etc/services or NIS on all
the servers are identical. Verify that the media host is listening on the corre
ct port for connections to bpcd by running one of the following commands (depend
ing on platform and operating system):
netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)
On UNIX servers, you may have to change the service number for bpcd in /etc/s
ervices and the NIS services map and send SIGHUP signals to the inetd processes
on the clients.
/bin/ps -ef | grep inetd
kill -HUP the_inetd_pid
or
/bin/ps -aux | grep inetd
kill -HUP the_inetd_pid
Note: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP to inetd
.
4. On Windows servers:
a. Verify that the bpcd entries are correct in:
%SystemRoot%\system32\drivers\etc\services
b. Verify that the NetBackup Client Service Port number and NetBackup Reques
t Service Port number on the Network tab in the NetBackup Configuration dialog m
atch the settings in the services file. To display this dialog, start the Backup
, Archive, and Restore interface and click Configure on the Actions menu.
The values on the Network tab are written to the services file when the Ne
tBackup Client service starts.
c. Stop and restart the NetBackup services.
5. See Testing Media Server and Clients in the Troubleshooting Guide and Resolv
ing Network Communication Problems in the Troubleshooting Guide.
6. If necessary, create debug log directories for the following processes and r
etry the operation. Then, check the resulting debug logs on the master server:
* If the error occurred during a backup operation, check the bpsched debug l
ogs.
* If the error occurred during a restore operation, check the bprd debug log
s.
Error Number: 205
cannot connect to server backup restore manager
A process on the master server could not connect to a process on a host on the n
etwork while trying to initiate communication with the server that has the stora
ge unit for a particular operation. This problem can occur during a backup or re
store in either a single or multiple server configuration. This can also occur w
hen the scheduler process (bpsched) is building its list of available storage un
its to use during backups.
Execute the ping command from one host to another by using the following combina
tions:
Note: Also, see Resolving Network Communication Problems in the Troubleshooting
Guide.
1. From the master server, ping the master and all media servers by using the h
ost names in the storage unit configuration.
2. From each of the media servers, ping the master server by using the name spe
cified in the NetBackup server list. On a UNIX server, this is the first SERVER
entry in the bp.conf file. On a Windows server, the master is designated on the
Servers tab in the Master Server Properties dialog. To access this dialog, see U
sing the Host Properties Window in the Troubleshooting Guide.
3. On a UNIX server, verify that the bpcd entry in /etc/services or NIS on all
the servers are identical. Verify that the media host is listening on the correc
t port for connections to bpcd by running one of the following commands (dependi
ng on platform and operating system):
netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)
4. On Windows servers:
a. Verify that the bpcd entries are correct in the services file:
%SystemRoot%\system32\drivers\etc\services
b. Verify that the NetBackup Client Service Port number and NetBackup Reques
t Service Port number on the Network tab in the NetBackup Configuration dialog m
atch the settings in the services file. To display this dialog, start the Backup
, Archive, and Restore interface and click Configure on the Actions menu.
The values on the Network tab are written to the services file when the Ne
tBackup Client service starts.
c. Stop and restart the NetBackup services.
5. See Testing Media Server and Clients in the Troubleshooting Guide and Resolv
ing Network Communication Problems in the Troubleshooting Guide.
6. Create a bpcd debug log directory on the server that has the storage unit an
d retry the operation. Then, check for additional information in the resulting d
ebug log.
Error Number: 206
access to server backup restore manager denied
The master server is trying to start a process on another server (or itself) and
the master server does not appear in the Netbackup server list on that server.
On a UNIX server, the master is the first SERVER entry in the bp.conf file. On a
Windows server, the master is designated on the Servers tab in the Master Serve
r Properties dialog. To access this dialog, see Using the Host Properties Window
in the Troubleshooting Guide.
Try the following.
1. Verify that the master server appears as a server in its own server list as
well as being listed on all media servers.
If you change the server list on a master server, stop and restart the NetBac
kup database manager and request daemons (UNIX) or the NetBackup Database Manage
r and NetBackup Request Manager services (Windows).
2. If necessary, create debug log directories for the following processes and r
etry the operation. Then, check the resulting debug logs on the master server:
* If the error occurred during a backup operation, check the bpsched debug l
ogs.
* If the error occurred during a restore operation, check the bprd debug log
s.
Error Number: 207
error obtaining date of last backup for client
An error occurred when the backup scheduler (bpsched) tried to obtain the date o
f the last backup for a particular client, policy, and schedule combination.
Try the following.
1. Verify that the NetBackup database manager (bpdbm) process (NetBackup Databa
se Manager service on Windows) is running.
2. Examine the All Log Entries report for the appropriate time frame to gather
more information about the failure.
3. For detailed troubleshooting information, create debug log directories for b
psched and bpdbm on the master server and retry the operation. Then, check the r
esulting debug logs.
Error Number: 208
failed reading user directed file list
An error occurred when the backup scheduler (bpsched) attempted to read the list
of files requested for a user backup or archive. This error indicates either a
client-server communication problem, or a system problem on the master server wh
ere the NetBackup scheduler process (bpsched) is running.
For detailed troubleshooting information, create debug log directories for bpsch
ed and bprd on the master server and retry the operation. Then, check the result
ing debug logs.
Error Number: 209
error creating or getting message queue
An error occurred when the backup scheduler (bpsched) attempted to create an int
ernal message queue construct for interprocess communication. This error indicat
es a problem on the master server and is most likely due to a lack of system res
ources for System V interprocess communication.
Create a bpsched debug log directory on the master server and retry the operatio
n. Then, determine the type of system failure by examining the error message in
the bpsched debug log. On UNIX servers, also gather the output of the ipcs -a co
mmand to see what system resources are currently in use.
Error Number: 210
error receiving information on message queue
An error occurred when one of the backup scheduler (bpsched) processes attempted
to receive a message from another bpsched process on an internal message queue
construct. This error indicates a problem on the master server and is likely due
to problems with or a lack of system resources for System V interprocess commun
ication.
Create a bpsched debug log directory on the master server and retry the operatio
n. Then, determine the type of system failure by examining the error message in
the bpsched debug log on the master server. On UNIX servers, also gather the out
put of the ipcs -a command to see what system resources are currently in use.
Error Number: 211
scheduler child killed by signal
A backup scheduler (bpsched) child process, which interacts with the backup rest
ore manager (bpbrm) on the media host, was terminated. This can occur because of
system administrator action.
Create a debug log directory for bpsched on the master server and retry the oper
ation. Then, to determine the cause of the child termination, examine the messag
es in the bpsched debug log.
Error Number: 212
error sending information on message queue
The backup scheduler (bpsched) encountered an error when attempting to attach to
an already existing internal message queue construct for interprocess communica
tion. This error indicates a problem on the master server and is likely due to a
lack of system resources for System V interprocess communication.
Create a bpsched debug log directory on the master server and retry the operatio
n. Then, determine the type of system failure by examining the error message in
the bpsched debug log. On a UNIX server, also, gather the output of the ipcs -a
command to see what system resources are currently in use.
Error Number: 213
no storage units available for use
The NetBackup scheduler process (bpsched) did not find any of its storage units
available for use. Either all storage units are unavailable or all storage units
are configured for On demand only and the policy and schedule does not require
a specific storage unit.
Try the following.
1. Examine the Backup Status and All Log Entries report for the appropriate tim
e period to determine the policy or schedule that received the error.
2. Verify that the storage unit's drives are not down or waiting for media from
a previous operation that did not complete.
3. Verify that all the storage units do not have their Maximum concurrent jobs
attribute set to 0 (for disk storage units) and Maximum concurrent drives used f
or backup attribute set to 0 (for Media Manager storage units).
4. Verify that the robot number and host name in the storage unit configuration
matches the Media Manager device configuration.
5. Determine if all storage units are set to On demand only for a policy and sc
hedule combination that does not require a specific storage unit. If this is the
case, either specify a storage unit for the policy and schedule combination or
turn off On demand only for a storage unit.
6. If the storage unit is on a UNIX NetBackup media server, it could indicate a
problem with bpcd. Check /etc/inetd.conf on the media server to verify that the
bpcd entry is ok.
If the storage unit is on a Windows NetBackup media server, verify that the N
etBackup Client service has been started on the Windows NetBackup media server.
7. For detailed troubleshooting information, create a bpsched debug log directo
ry on the master server and retry the operation. Then, check the resulting debug
log.
Error Number: 214
regular bpsched is already running
The NetBackup scheduler (bpsched) performs periodic checking of the policy and s
chedule configuration to determine if there are new backups due. Error 214 indic
ates that when a new instance of NetBackup starts, it finds that a scheduler pro
cess is already checking the policy and schedule configuration.
Usually, no action is required for this condition. However, NEVER kill bpsched b
efore doing some checking. For example, bpsched could be calling bpdbm (NetBacku
p Database Manager service on Windows) to clean up and compress the catalogs.
* To determine what the running bpsched is currently doing, examine the bpsched
debug log on the master server. If necessary, enable bpsched debug logging by c
reating a bpsched debug log directory on the master server and retrying the oper
ation.
* To check for backups do the following:
On a UNIX master server:
1. Check for active or queued backups by using the job monitor.
2. Check for active bp processes with bpps. This reveals if there are bpbrm or
bptm processes running and a backup is active.
3. If there is no reason for bpsched to be running, then use kill -HUP to termi
nate it.
Error Number: 215
failed reading global config database information
During the periodic checking of the NetBackup configuration, the NetBackup sched
uler process (bpsched) was unable to read the global configuration parameters.
Try the following.
1. On a UNIX master server, verify that the NetBackup database manager (bpdbm)
process is running. On a Windows master server, verify that the NetBackup Databa
se Manager service is running.
2. Attempt to view the global configuration settings by using the NetBackup adm
inistration interface.
3. For detailed troubleshooting information, create debug log directories for b
psched and bpdbm on the master server and retry the operation. Then, check the r
esulting debug logs.
Error Number: 216
failed reading retention database information
During its periodic checking of the NetBackup configuration, the NetBackup sched
uler process (bpsched) could not read the list of retention levels and values.
Try the following.
1. On a UNIX master server, verify that the NetBackup database manager (bpdbm)
process is running. On a Windows master server, verify that the NetBackup Databa
se Manager service is running.
2. For detailed troubleshooting information, create debug log directories for b
psched and bpdbm on the master server and retry the operation. Then, check the r
esulting debug logs.
Error Number: 217
failed reading storage unit database information
During its periodic checking of the NetBackup configuration, the NetBackup sched
uler process (bpsched) could not read the storage unit configuration.
Try the following.
1. On a UNIX server, verify that the NetBackup database manager (bpdbm) process
is running. On a Windows server, verify that the NetBackup Database Manager ser
vice is running.
2. Attempt to view the storage unit configuration by using the NetBackup admini
stration interface.
3. For detailed troubleshooting information, create debug logs for bpsched and
bpdbm on the master server and retry the operation. Then, check the resulting de
bug logs.
Ensure that the correct master server is being specified for the connection.
Error Number: 218
failed reading policy database information
During the periodic checking of the NetBackup configuration, the NetBackup sched
uler process (bpsched) could not read the policy (backup policy) configuration.
Try the following.
1. On a UNIX server, verify that the NetBackup Database Manager (bpdbm) process
is running. On a Windows server, verify that the NetBackup Database Manager ser
vice is running.
2. Attempt to view the policy configuration by using the NetBackup administrati
on interface.
3. For detailed troubleshooting information, create debug log directories for b
psched and bpdbm on the master server and retry the operation. Then, check the r
esulting debug logs.
Ensure that the correct master server is being specified for the connection.
Error Number: 219
the required storage unit is unavailable
The policy or schedule for the backup requires a specific storage unit, which is
currently unavailable. This error also occurs for other attempts to use the sto
rage unit within the current backup session.
Look in the Job Details window for the failed job.
1. Verify that the schedule specifies the correct storage unit and the storage
unit exists.
2. Verify that the Media Manager device daemon (ltid) is running (if the server
is UNIX) or the NetBackup Device Manager service is running (if the server is a
Windows system). Use bpps on UNIX and the Activity Monitor on Windows.
3. Verify that the Maximum concurrent jobs attribute is not set to 0 (for a dis
k storage unit) and the Maximum concurrent drives attribute is not set to 0 (for
a Media Manager storage unit).
4. If the storage unit is a tape or optical disk, verify that at least one of t
he drives is in the UP state. Use the Device Monitor.
5. Verify that the robot number and host in the storage unit configuration matc
hes what is specified in the Media Manager device configuration.
6. Verify that the master server can communicate with the bpcd process on the s
erver that has the storage unit.
a. Verify that bpcd is listening on the port for connections.
On a UNIX server, executing
netstat -a | grep bpcd
should return something similar to the following:
*.bpcd *.* 0 0 0 0 LISTEN
Do this on the server where the storage unit is connected.
On a Windows NetBackup server, executing
netstat -a
prints out several lines of output. If bpcd is listening, one of those lin
es is similar to the following:
TCP myhost:bpcd 0.0.0.0:0 LISTENING
Do this on the server where the storage unit is connected.
b. If bpcd seems to be operating correctly, create bpsched and bpcd debug lo
g directories and retry the operation. Check the resulting debug logs for record
s of an earlier failure.
After each backup, the scheduler checks the storage unit to see how many d
rives are available (in case the backup caused a drive to be automatically downe
d). If bpsched cannot communicate with bpcd, it sets the number of available dri
ves in that storage unit to 0 and further backups to that storage unit during th
is backup session will fail.
The number of available drives remains at 0 until the scheduler is initial
ized again.
c. If the cause of the problem is not obvious, perform some of the steps in
Resolving Network Communication Problems in the Troubleshooting Guide.
Error Number: 220
database system error
The bpdbm process (NetBackup Database Manager service on Windows) could not crea
te a directory path for its configuration catalogs due to the failure of a syste
m call. This is usually due to a permission problem or an "out of space" conditi
on.
Create a debug log directory for bpdbm and retry the operation. Check the result
ing debug log for information.
Error Number: 221
continue
This status code is used in coordinating communication between various NetBackup
processes and normally does not occur. If the logs show that it is associated w
ith a subsequent error, it usually indicates a communication problem. In this ca
se, concentrate your troubleshooting efforts on the subsequent error.
Determine the cause of the status code that follows this one.
Error Number: 222
done
This status code is used in coordinating communication between various NetBackup
processes and is normally not seen. If the error logs show that it is associate
d with a subsequent error, it usually indicates a communication problem. In this
case, concentrate your troubleshooting efforts on the subsequent error.
Determine the cause of the status code that follows this one.
Error Number: 223
an invalid entry was encountered
A request to the bpdbm process (NetBackup Database Manager service on Windows) h
ad invalid or conflicting information. This is usually a result of using softwar
e from different versions together, but can also be caused by incorrect paramete
rs on a command.
Verify that all NetBackup software is at the same version level and the command
parameters are specified correctly. If neither of these is the problem, obtain d
etailed troubleshooting information by creating a bpdbm debug log directory and
retrying the operation. Check the resulting debug log.
Error Number: 224
there was a conflicting specification
A request to the bpdbm process (NetBackup Database Manager service on Windows) h
ad conflicting information. This is usually a result of using software from diff
erent version levels together.
Verify that all NetBackup software is at the same version level. If that is not
the problem, obtain detailed troubleshooting information by creating bpdbm and a
dmin debug log directories and retrying the operation. Check the resulting debug
logs.
Error Number: 225
text exceeded allowed length
A request containing text that exceeds a buffer size was made to the bpdbm proce
ss (NetBackup Database Manager service on Windows). This is usually a result of
using software from different version levels together.
Verify that all NetBackup software is at the same version level. If that is not
the problem, create debug log directories for bpdbm and admin. Then, retry the o
peration and examine the resulting debug logs.
Error Number: 226
the entity already exists
The configuration already has an entity with the same name or definition. For ex
ample, you see this status if you try to add a new policy when an existing polic
y has the same name or definition (attributes, clients, and so on).
Correct your request and re-execute the command.
Error Number: 227
no entity was found
The item requested was not in the catalog. For example, the entity could be a fi
le or policy information.
Try the following.
1. A common cause for this problem is a query that has no matching images. Spec
ify different parameters or options for the operation and try it again.
2. For NetBackup ServerFree Agent only:
* Check the /usr/openv/netbackup/logs/online_util log on the client for the
following messages:
onlfi_get_fsmap_info: FTL - /usr/openv/netbackup/fi.conf open
failed. Errno = 2: No such file or directory
onlfi_process_fs_list_fs_entry: FTL - No frozen image mapping
information for /vol1
This indicates that the frozen image configuration file was not found. The
frozen image configuration file is created with the Frozen Image Client Configu
ration dialog as described in the "NetBackup Configuration" chapter of the NetBa
ckup ServerFree Agent System Administrator's Guide.
* Check the /usr/openv/netbackup/logs/online_util log for the following mess
age:
onlfi_process_fs_list_fs_entry: FTL - No frozen image
mapping information for /vol1
If you find this message but no "fi.conf open failed" message, the fi.conf
.master server file was created, but the frozen image source has not been specif
ied in the file. To specify a frozen image source, see the instructions in the "
NetBackup Configuration" chapter of the NetBackup ServerFree Agent System Admini
strator's Guide.
Error Number: 228
unable to process request
An inconsistency exists in the catalog or a request was made that would be impro
per to satisfy.
Try the following.
1. If this involves a media server, verify that its server list specifies the c
orrect master server. On a UNIX server, the master server is the first SERVER en
try in the bp.conf file. On a Windows server, the master is designated on the Se
rvers tab in the Master Server Properties dialog. To access this dialog, see Usi
ng the Host Properties Window in the Troubleshooting Guide.
2. For detailed troubleshooting information, create a bpdbm debug log directory
and retry the operation. Then, check the resulting debug log.
Error Number: 229
events out of sequence - image inconsistency
A request was made which, if satisfied, would cause the image catalog to become
inconsistent.
Obtain detailed troubleshooting information by creating a debug log directory fo
r bpdbm. Then, retry the operation, save the resulting debug log, and call custo
mer support.
Error Number: 230
the specified policy does not exist in the configuration database
The specified policy name does not exist.
Correct your parameters or options and retry the operation.
Error Number: 231
schedule windows overlap
The start and duration times specified for one day of the schedule overlap with
another day of the schedule.
Correct the schedule to eliminate the overlapping backup windows.
Error Number: 232
a protocol error has occurred
This is an intermediate status code that usually precedes another status code. I
t indicates that either the bpdbm process (NetBackup Database Manager service on
Windows) or the process communicating with it has received unexpected informati
on.
Create a debug log directory for bpdbm. Then, retry the operation, save the debu
g log, and call customer support.
Error Number: 233
premature eof encountered
This is an intermediate status code that usually precedes another status code an
d is associated with a problem in network communication.
During a restore, this means that tar (on the client) received a stream of data
that was not what it expected. If this is a new configuration, verify that the t
ape drive is configured for variable mode (see the Media Manager Device Configur
ation Guide). If the communication failure is not due to an interrupt on a clien
t system, save all error information and call customer support.
Error Number: 234
communication interrupted
This is an intermediate status code that usually precedes another status code an
d is associated with a problem in network communication. A process, either serve
r or client, received an interrupt signal.
Save all error information and call customer support.
Error Number: 235
inadequate buffer space
This code usually indicates a mismatch between server and client software versio
ns.
Try the following.
1. Verify that all NetBackup software is at the same version level. Update earl
ier versions of NetBackup software.
* On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/
version file.
* On Windows NetBackup servers, check the install_path\NetBackup\version.txt
file or the About NetBackup item on the Help menu.
* On Microsoft Windows clients, check the About NetBackup item on the Help m
enu.
* On NetWare target clients, check the Version entry in the bp.ini file.
If the client software is earlier than 3.0, verify that the client is in a
Standard type policy.
* On Macintosh clients, check the version file in the bin folder in the NetB
ackup folder in the Preferences folder.
2. If the problem persists, save all error information and call customer suppor
t.
Error Number: 236
the specified client does not exist in an active policy within the configuration
database
A client name was not specified or the specified client does not exist.
Activate the required policy, correct the client name, or add the client to a po
licy that meets your needs. After making the correction, retry the operation.
Error Number: 237
the specified schedule does not exist in an active policy in the configuration d
atabase
The specified schedule does not exist in the NetBackup configuration.
Activate the required policy, correct the schedule name, or create a schedule in
a policy that meets your needs. After making the correction, retry the operatio
n.
Error Number: 238
the database contains conflicting or erroneous entries
The catalog has an inconsistent or corrupted entry.
Obtain detailed troubleshooting information for bpdbm (NetBackup Database Manage
r service on Windows) by creating a debug log directory for it. Then, retry the
operation, save resulting debug log, and call customer support.
Error Number: 239
the specified client does not exist in the specified policy
The specified client is not a member of the specified policy.
Correct the client name specification, specify a different policy, or add the re
quired client name to the policy. After making the correction, retry the operati
on.
Error Number: 240
no schedules of the correct type exist in this policy
The appropriate schedule was not found in the specified policy. For example, a u
ser backup specified a policy name but no user backup schedule exists in that po
licy.
Specify a different policy or create a schedule of the needed type in the policy
. After making the correction, retry the operation.
Error Number: 241
the specified schedule is the wrong type for this request
The schedule that was specified for an immediate manual backup is not for a full
nor an incremental backup. It must be one of these.
Specify only full or incremental schedules for manual backups. If one does not e
xist in the policy, create one.
Error Number: 242
operation would cause an illegal duplication
Processing the request would cause a duplicate catalog entry. This is usually du
e to a mistake in specifying media IDs for NetBackup catalog backups.
Check the error reports to determine the specific duplication that would occur.
Correct the settings for the operation and retry it.
Error Number: 243
the client is not in the configuration
The specified client name was not in the catalog.
Either correct the client name or add the client to the desired policy.
Error Number: 244
main bpsched is already running
A bpsched process tried to become the main backup scheduler but another process
is currently in this mode.
None.
Error Number: 245
the specified policy is not of the correct client type
A user backup specified a policy that is not the type required for the client.
Retry the operation by specifying a policy that is the correct type for the clie
nt. If such a policy does not exist, create one.
Error Number: 246
no active policies in the configuration database are of the correct client type
A user backup request was not satisfied because no active policies were the type
required for the client.
Create or activate an appropriate policy so the user backup request can be satis
fied.
Error Number: 247
the specified policy is not active
Backups for the specified policy are disabled because the policy is inactive.
Activate the policy and retry the operation.
Error Number: 248
there are no active policies in the configuration database
No active policy was found that would satisfy the request.
Activate the appropriate policy and retry the operation.
Error Number: 249
the file list is incomplete
The server timed out while waiting for the client to finish sending the file lis
t, or a sequencing problem occurred.
Obtain additional information by first creating debug logs and then attempting t
o recreate the error. The debug logs to create are as follows:
* On the server, bptm, bpbrm, and bpdbm.
* On UNIX and Windows clients, bpbkar.
* On other clients, bpcd.
Note: To increase the amount of information included in the logs, see Debug Logs
on PC Clients in the Troubleshooting Guide.
Error Number: 250
the image was not created with TIR information
This is an internal error and should not be seen by customers.
Obtain detailed troubleshooting information by creating debug logs for bptm and
bpdbm on the server. Then, retry the operation and check the resulting debug log
s.
Error Number: 251
the TIR information is zero length
For a true-image backup, the client sent no file information to the master serve
r. NetBackup discovered this condition when it attempted to write the TIR inform
ation to media.
Try the following.
1. Check the file list for the policy and the exclude and include lists on the
client to verify that the client has files that are eligible for backup. For exa
mple, this status code can appear if the exclude list on the client excludes all
files.
2. To obtain detailed troubleshooting information, create debug logs for bptm a
nd bpdbm on the server. Then, retry the operation and check the resulting debug
logs.
Error Number: 252
the error status has been written to stderr
If a Vault job fails with a status code greater than 255, it exits with status 2
52; the actual Vault status code is written to stderr. This is because status co
des greater than 255 are not supported by all operating systems. The Vault job t
hen reports the actual status code found in stderr (for example, 256) as the job
completion status, as seen in the Activity Monitor.
For more information on a Vault status code, refer to the NetBackup Troubleshoot
ing Guide or to the Activity Monitor's troubleshooter.
Error Number: 253
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 254
server name not found in the bp.conf file
This error should not occur through normal use of NetBackup.
Save all error information and call customer support.
Error Number: 255
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 256
logic error encountered
An internal vault error occurred.
Contact customer support and send appropriate logs.
Error Number: 257
cannot create log file
When a vault session is started, vltrun needs to create log files in the followi
ng directories:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name
Windows: install_path\Netbackup\vault\sessions\vault_name
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path \NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Ensure that the following directory exists, is writable by root, and that the
disk is not full:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name
Windows: install_path\NetBackup\vault\sessions\vault_name
Error Number: 258
a child process failed for an unknown reason
A child process of the vault job died with an invalid exit status.
Contact customer support and send appropriate logs.
Error Number: 259
vault configuration file not found
This error should not occur.
Contact customer support and send appropriate logs.
Error Number: 260
vault internal error 260
This error code should not occur.
Contact customer support and send appropriate logs.
Error Number: 261
vault internal error 261
This error code should not occur.
Contact customer support and send appropriate logs.
Error Number: 262
vault internal error 262
This error code should not occur.
Contact customer support and send appropriate logs.
Error Number: 263
session id assignment failed
The unique identifier to be assigned to the vault session is bad.
Verify that the session id stored in the session.last file is valid.
UNIX:
/usr/openv/netbackup/vault/sessions/vault_name/session.last
Windows: install_path\Netbackup\vault\sessions\vault_name\session.last
Make sure that the file system is not full and that no one has inadvertently
edited the session.last file. You can correct the problem by storing in the sess
ion.last file the highest session id that has been assigned to a session for thi
s vault. If the problem persists, contact customer support and send the appropri
ate logs.
Error Number: 264
Error: Can't find Troubleshooting Guide, or status code not available.
Error Number: 265
session id file is empty or corrupt
The session id stored in the following file is bad.
UNIX:
/usr/openv/netbackup/vault/sessions/vault_name/session.last
Windows: install_path\NetBackup\vault\sessions\vault_name\session.last
Ensure that the session id stored in the session.last file is not corrupt. Make
sure that the file system is not full and that no one has inadvertently edited t
he file. You can correct the problem by storing in the session.last file the hig
hest session id that has been assigned to a session for this vault. If the probl
em persists, contact customer support and send the appropriate logs.
Error Number: 266
cannot find robot, vault, or profile in the vault configuration
The profile name or triplet robot_name/vault_name/profile_name specified on the
vault command (vltrun, vlteject, vltoffsitemedia), or by means of vltopmenu, was
not found in the vault configuration.
Please rerun the command with the correct profile_name or triplet robot_name/vau
lt_name/profile_name.
Error Number: 267
cannot find the local host name
A vault job obtains the local host name via an OS call. This error occurs when t
he vault job is unable to get the local host name.
Issue a hostname command at the OS command prompt. See the hostname (or gethostb
yname) man page for an explanation of the conditions that would cause it to fail
. Refer to the OS System Administrator Guide for more information
Error Number: 268
the vault session directory is either missing or inaccessible
This error occurs when a vault job cannot access the following:
UNIX: /usr/openv/netbackup/vault/sessions
Windows: install_path\NetBackup\vault\sessions
This directory is created when vault is installed.
Make sure you are running on the master server where vault is installed and conf
igured. Also ensure that no one has accidently removed the sessions directory or
changed permission on the directory path so it is inaccessible to the vault job
.
Error Number: 269
no vault session id was found
This error is encountered when vltopmenu cannot find a sidxxx session id directo
ry for the specified profile. It means that either no vault jobs were run for th
is profile or that the corresponding sidxxx session id directory (or directories
) were removed from the following directory:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name
Windows: install_path\NetBackup\vault\sessions\vault_name
You can either specify a different profile for which vault jobs have been run or
exit vltopmenu, run a vault job for the specific profile and rerun vltopmenu an
d select the profile.
Error Number: 270
unable to obtain process id, getpid failed
This error occurs when a vault process is unable to obtain its process id by mea
ns of the getpid() OS system call.
Look at the system log for any unusual system problems. Wait for a while and try
running the process again when system resources have been freed up.
Error Number: 271
the initialization of the vault configuration file failed
This error occurs when configuration initialization code fails.
Ensure that the following is accessible:
UNIX: /usr/openv/netbackup/lib/libxerces-c1_4nmt.so
Windows: install_path\NetBackup\lib\libxerces-c1_4nmt.so
Error Number: 272
execution of a vault notify script failed
This error occurs when the vault process is unable to execute a vault notify scr
ipt due to permissions problems or coding problems in the script or if an error
is returned by the script.
Ensure that the notify script is executable and runs without errors. You must de
bug the script by running it manually to eliminate coding errors.
Error Number: 273
invalid jobID
This error should not occur.
Contact customer support and send appropriate logs.
Error Number: 274
no profile was specified
This error should not occur.
Contact customer support and send the appropriate logs.
Error Number: 275
a session is already running for this vault
This error occurs when you start a session for a vault and another session is al
ready running for this vault. Only one session is allowed for a vault at any giv
en time.
Start the vault session after the previous session has completed.
Error Number: 276
invalid sessionID
This error should not occur.
Contact customer support and send the appropriate logs.
Error Number: 277
unable to print reports
This error should not occur.
Contact customer support and send the appropriate logs.
Error Number: 278
unimplemented error code
This error should not occur.
Contact customer support and send the appropriate logs.
Error Number: 279
unimplemented error code
This error should not occur.
Contact customer support and send the appropriate logs.
Error Number: 280
unimplemented error code
This error should not occur.
Contact customer support and send the appropriate logs.
Error Number: 281
vltcore error
An internal vault error occurred.
Contact customer support and send the appropriate logs.
Error Number: 282
vltcore system error
An internal system exception was encountered by the vault job.
Contact customer support and send appropriate logs.
Error Number: 283
vltcore unhandled error
The vault job encountered a system exception.
Contact customer support and send appropriate logs.
Error Number: 284
error caused by invalid data in vault configuration file
This error is returned by a vault job or a command when it cannot interpret the
information extracted from the vault configuration file. For example, if the vau
lt configuration file is corrupt or refers to non-existent or misconfigured obje
cts.
Ensure that your vault configuration is correct (that it refers to functional ro
bots, media servers, volume pools, and so forth). Also ensure that the vault pro
file is defined in the configuration and has not been accidently removed after t
he vault job was started. This can happen when more than one vault interface is
changing the configuration at the same time. Examine the vault logs for detailed
information about configuration problems. To correct the problem, you may need
to restore the following file from a backup copy:
UNIX: /usr/openv/netbackup/db/vault/vault.xml
Windows: install_path\NetBackup\db\vault\vault.xml
Error Number: 285
unable to locate vault directory
This error is returned by a vault job or command when it cannot locate the follo
wing directory:
UNIX: /usr/openv/netbackup/vault
Windows: install_path\NetBackup\vault
The vault directory is created when the vault package is installed on the master
server. Ensure that the vault job or command is started as root on the master s
erver and that the vault directory has not been inadvertently removed or made in
accessible to root user.
Error Number: 286
vault internal error
This error should never occur.
Contact customer support and send the appropriate logs.
Error Number: 287
failed attempting to copy (consolidated) report file
This error occurs when a vault job is unable to copy the consolidated reports to
the destination directory specified in the vault profile.
Ensure that the destination directory specified in the profile exists and is wri
table by root. Also the vault job or command must be started with root privilege
s. Correct the path and/or permissions of the destination directory and rerun th
e vault job or command.
Error Number: 288
attempt to open a log file failed
This error occurs when a vault job cannot create the detail.log file or summary.
log file in the following directory:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\Netbackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id.)
Ensure that the above directory exists and has not been inadvertently removed af
ter the vault job was started. Ensure that this directory is writable by root an
d that the disk is not full. Rerun the vault job after correcting the problem.
Error Number: 289
an error occurred when calling vltcore
The error can occur during a normal vault job or when vlteject is executed for a
specific session or when vltopmenu is used to generate individual reports, if a
ny of the following conditions exists:
* vltcore binary is removed
* vltopmenu binary is not executable
* the disk (on which NetBackup is installed) is full
* the following directory is removed or made inaccessible to root (where xxx is
the session id):
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\netbackup\vault\sessions\vault_name\sidxxx
To identify which of the above conditions led to the failure, review the vault d
ebug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log file in each of the sidxxx directories that had pr
oblems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
Correct the problem and rerun the vault job. If the problem persists, please
contact customer support and send the appropriate logs.
Error Number: 290
one or more errors detected during eject processing
This error occurs when more than one error is encountered during an eject proced
ure via vltopmenu. Any "eject" errors in the range 291 to 300 could have occurre
d in any of the sessions being ejected.
For detailed information, review the vault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
The media that was not ejected may need to be ejected manually by means of vl
teject or vltopmenu, after the problem has been identified and corrected.
This error often indicates that the media were left in the offsite vault volu
me group but still physically reside in the robot or in the robotic MAP. To solv
e this problem, do one of the following:
* Manually remove any media that are in the offsite vault volume group but are
still in the robotic library.
* Inventory the robotic library. This puts any media that were in the offsite v
ault volume group back into the robotic volume group. Then, rerun the vault sess
ions that failed.
Error Number: 291
number of media has exceeded capacity of MAP; must perform manual eject using vl
topmenu or vlteject
This error occurs when a vault job is run for a profile that has selected automa
tic eject mode and the number of media to be ejected exceeds the capacity of the
MAP.
Use vltopmenu to manually eject the media for the selected profile and session i
d. The vltopmenu option will let you eject the selected media, a MAP-full (or le
ss) at a time.
Error Number: 292
eject process failed to start
This error occurs when the eject processing cannot be started by the vault job o
r vlteject command or via vltopmenu.
For detailed information about the problem, review the vault debug log in the fo
llowing directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Use the robtest utility to ensure that you can communicate with the vault rob
otic library. Once the problem is resolved, rerun the vault session, vlteject co
mmand, or vltopmenu command.
Error Number: 293
eject process has been aborted
This error occurs when the eject processing has been aborted. This error could b
e encountered during a vault job or when using vlteject or the vltopmenu eject c
ommand.This error can occur because of one of the following conditions:
* Could not open a pipe to vmchange -verify_eject call.
* Unexpected output from vmchange -verify_eject call.
* There are no MAP elements to eject media into.
* The robotic library had problems putting media into the MAP.
* The user hit Return in interactive mode without first removing the media from
the MAP. In this case, the media that were in the MAP will be put back into the
ir original slots in the robotic library.
For detailed information about why the process was aborted, review the vault deb
ug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
This error often indicates that the media were left in the offsite vault volu
me group but still physically reside in the robot or in the robotic MAP. To solv
e this problem, do one of the following:
* Manually remove any media that are in the offsite vault volume group but are
still in the robotic library.
* Inventory the robotic library. This puts any media that were in the offsite v
ault volume group back into the robotic volume group. Then, rerun the vault sess
ions that failed.
Error Number: 294
Database backup failed
The catalog backup step failed during a vault job.
For detailed information about why the process failed, review the vault debug lo
g in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s, to find the actual problem that caused the catalog backup (bpbackupdb) to fai
l:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Correct the problem and rerun the vault job.
Error Number: 295
eject process could not obtain information about the robot
This error occurs when the eject process cannot collect information about the ro
botic library and its associated MAPs and volumes.
For detailed information about why the process failed, review the vault debug lo
g in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Correct the error and rerun the vault session, vlteject command, or vltopmenu
eject command.
Error Number: 296
process called but nothing to do
This error occurs under the following conditions:
* The vlteject command is executed to eject and/or report for a specific sessio
n id and the session id does not exist, or the vault name is bad or the session
has no media to eject and reports to be generated.
* When vltopmenu or vlteject runs ejects or reports, it finds no sessions with
media to eject or reports to run. For a given session id, the reports will be ge
nerated only once. Subsequently the reports can be rerun for the individual sess
ion id but will not appear in a consolidated operation.
If this error was obtained via vlteject, rerun vlteject with the correct vault n
ame and session id. If vltopmenu is being used, ensure that the selected vault h
as sessions with media pending ejects or outstanding reports that need to be gen
erated
Error Number: 297
all volumes are not available to eject
This error occurs when an attempt is made to eject a non-existent or bad media i
d during the eject phase of a vault session, vlteject command, or vltopmenu comm
and.Possible reasons for this occurring are:
* The bad media id was added by means of the vlt_ejectlist_notify script.
* The bad media id is already in the MAP or not in the robotic library.
* The bad media id is in a robotic drive.
* The bad media id is in transit in the robotic library.
Remove or correct the bad media id from the vlt_ejectlist_notify script and reru
n the vault session. If the bad media id is in the MAP or a drive or in transit,
something is misconfigured.
Error Number: 298
the library is not ready to eject volumes
This error occurs if the robotic library is not in a state to support ejecting m
edia.Possible reasons for this include:
* The library is currently ejecting media
* The library is pending ejecting media
* The library is currently injecting media
* The library is pending injecting media
Wait until the robotic library can support the eject action and rerun the vault
session, vlteject command, or vltopmenu command.
Error Number: 299
there is no available MAP for ejecting
The robotic library you are vaulting from does not have a MAP available for use
and so media cannot be ejected.
Wait until the robotic library's MAP is available for use and rerun the vault se
ssion, vlteject command, or vltopmenu command.
Error Number: 300
vmchange eject verify not responding
During the eject process, the vmchange command is called with a "-verify_eject"
call until all of the volumes for the request are in the MAP. This command call
failed or did not return the proper information to the vault eject process.
For detailed information about why the process failed, review the vault debug lo
g in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
This error often indicates that the media were left in the offsite vault volu
me group but still physically reside in the robot or in the robotic MAP. To solv
e this problem, do one of the following:
* Manually remove any media that are in the offsite vault volume group but are
still in the robot.
* Inventory the robot. This puts any media that were in the offsite vault volum
e group back into the robotic volume group. Then, rerun the vault sessions that
failed.
Error Number: 301
vmchange api_eject command failed
During the eject process, the vmchange command is called with an "-api_eject" ca
ll to begin the process of ejecting media. This command call failed.
For detailed information about why the process failed, review the vault debug lo
g in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Once the problem is resolved, rerun the vault session, vlteject command, or v
ltopmenu command.
Error Number: 302
error encountered attempting backup of catalog (Two Phase BU)
This error occurs when the NetBackup command used for stage one of the two-stage
catalog backup fails.
For the actual error that caused the failure, review the vault debug log in the
following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Review the detail.log in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
In addition, review the admin debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/admin
Windows: install_path\NetBackup\logs\admin
Correct the error and rerun the vault session.
Error Number: 303
error encountered executing Media Manager command
This error occurs when a Media Manager command fails during a vault job.
For the actual error that caused the Media Manager command to fail, review the v
ault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Try running the Media Manager command (with the same arguments as in the log
file) to see the actual error. Ensure that the Media Manager daemons are running
. Also ensure that the robot is functional and you can communicate with it (for
example, inventory the robot via the GUI).
Error Number: 304
specified profile not found
This error occurs when the profile name specified on the vault command is not de
fined in the vault configuration.
Please rerun the vault command with a profile name that is defined in the vault
configuration.
Error Number: 305
duplicate profile specified, use full robot/vault/profile
This error occurs when duplicate profile names have been defined in two or more
vault configurations and only the profile name is specified on the vault command
.
You must rerun the vault command with the triplet robot_name/vault_name/profile_
name. The triplet will uniquely identify the profile in your vault configuration
.
Error Number: 306
errors encountered, partial success
This error occurs when a vault job is partially successful, in other words, when
not all images have been successfully duplicated and/or the catalog backup fail
ed.
For more information, review the vault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
A common cause of failure is the lack of resources, such as no more media ava
ilable in the specified pools for duplication and catalog backup. Correct the pr
oblem and rerun the vault job. Note that the NetBackup scheduler will retry a va
ult job that has terminated with this error.
Error Number: 307
eject process has already been run for the requested vault session
This error occurs when vlteject is run to eject media for a session id for which
media has already been ejected.
Rerun vlteject for another session id for which media has not been ejected.
Error Number: 308
no images duplicated
This error occurs when vault failed to duplicate any images.
For more information, review the vault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problem
s:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Look for the log entry that gives the total number of images processed. A com
mon cause of failure is a lack of resources, such as no more media available in
the specified pools for duplication. Correct the problem and rerun the vault job
. Note that the NetBackup scheduler will retry a vault job that has terminated w
ith this error. Review the admin debug log for bpduplicate entries and the bptm
debug log.
Error Number: 309
report requested without eject being run
This error occurs when a report is run that requires media to have been ejected
first.
Perform one of these actions:
* Rerun vlteject or vltopmenu to eject the media for the session before generat
ing the reports.
* Reconfigure the profile to allow the eject step to be performed when the next
vault session for this profile runs.
* Disable the report generation in the profile for reports that require media t
o be ejected.
Error Number: 310
invalid configuration for duplication to disk
This error occurs when an invalid disk storage unit is configured in the vault p
rofile used to duplicate images to disk, or when the profile is configured to cr
eate more than one copy and one of the copies is targeted for a disk storage uni
t. The latter configuration will be prevented by the vault interface and should
not occur unless the vault configuration file has been manually altered.
Ensure that a valid disk storage unit is configured in the profile by means of t
he duplication tab. Also ensure that the vault configuration file has not been m
anually altered.