Netbackup Important Error Codes

These are the error codes seen in the Netbackup and also these can be seen using
command bperror -S -r and in Netbackup troubleshooting guide.
Status Code 0
====================
the requested operation was successfully completed
No problems were detected with the requested operation.
Status Code
====================
the requested operation was partially successful
! problem was detected that may require correcti"e action during the requested
operation.
Status Code #
====================
none of the requested files were backed up
! backup or archi"e did not back up any of the files in the file list.This status code
applies primarily to automatic backups using $otus Notes or S%$ database agents& when
all of the backups related to the 'ob ha"e failed. (t should not occur for standard file
system backups.)pen a Net*ackup support case +recommended in Symantec document
#,-.0/.pdf0 if you encounter this error for the following1 a 2N(3 or 4indows file
system backup& or for database agents other than S%$ Ser"er or $otus Notes.
Status Code /
====================
"alid archi"e image produced& but no files deleted due to non-fatal problems
The backup portion of the archi"e command reported problems so the files were not
deleted.
Status Code 5
====================
archi"e file remo"al failed
The backup portion of the archi"e completed was successful but the delete failed.
Status Code 6
====================
the restore failed to reco"er the requested files
7rrors caused the restore to fail.
Status Code -
====================
the backup failed to back up the requested files
7rrors caused the user backup to fail.
Status Code ,
====================
the archi"e failed to back up the requested files
7rrors caused the user archi"e to fail.
Status Code 8
====================
unable to determine the status of rbak
)n 9omain)S clients& rbak is used to do restores. (f rbak does not e:it with a status
message& Net*ackup cannot determine whether the restore worked or not.
Status Code .
====================
an e:tension package is needed& but was not installed
! Net*ackup e:tension product is required to perform the requested operation.
Status Code 0
====================
allocation failed
The system memory allocation fails because of insufficient system memory a"ailable. !
possible cause is that the system is o"erloaded with too many processes and not enough
physical or "irtual memory.
Status Code
====================
system call failed
! system call has failed. This status code is used for a generic system call failure that
does not ha"e its own status code.
Status Code #
====================
file open failed
!n open of a file failed.
Status Code /
====================
file read failed
! read of a file or socket failed. ;ossible causes include1
< !n (=) error occurred during a read from the file system.
< >ead of an incomplete file or a corrupt file.
< Socket read failure. ! network problem or a problem with the process that writes to
the socket can cause socket read failure.
< ! problem specific to Net*ackup Snapshot Client +see recommended actions0.
Status Code 5
====================
file write failed
! write to a file or socket failed. ;ossible causes include1
< !n (=) error occurred during a write to the file system.
< 4rite to a socket failed. Cause of this failure1 a network problem or a problem with
the process that reads from the socket.
< 4riting to a full disk partition.
Status Code 6
====================
file close failed
! close of a file or socket failed.
Status Code -
====================
unimplemented feature
The specified operation is not implemented. This error should not occur through normal
use of Net*ackup.
Status Code ,
====================
pipe open failed
)ccurs in Net*ackup client menu and ?ault areas.
Status Code 8
====================
pipe close failed
! pipe close failed when one process tries to start a child process.
Status Code .
====================
getser"byname failed
! call to getser"byname+0 failed. The getser"byname+0function uses the name of the
ser"ice to find a ser"ice entry in the ser"ices file. +)r N(S ser"ices map on 2N(3 if it is
configured.0
Status Code #0
====================
in"alid command parameter
)ne or more command parameters were not "alid. This error can occur when
incompatible le"els of Net*ackup are installed on a master and its media ser"er+s0 or
client+s0. @or e:ample& a Net*ackup master ser"er has Net*ackup -.6 and the media
ser"er or the client has Net*ackup 5.6. This error can also occur if the wrong
parameters are used when you run a command line.
Status Code #
====================
socket open failed
! socket was not opened.
Status Code ##
====================
socket close failed
! socket was not closed.
Status Code #/
====================
socket read failed
! read operation from a socket failed.
Status Code #5
====================
socket write failed
! write operation to a socket failed.
Status Code #6
====================
cannot connect on socket
! process that timed out while connecting to another process for a particular operation.
This problem can occur in the following situation1 when a process tries to connect to the
Net*ackup request daemon +bprd0 or database manager daemon +bpdbm0 and the
daemon is not running. +)n 4indows& these daemons are the Net*ackup >equest
Aanager and Net*ackup 9atabase Aanager ser"ices.0 (t can also occur in the following
situations1 the network or ser"er is hea"ily loaded and has slow response time or an
e"aluation license key for Net*ackup e:pired. Bowe"er& the most common cause of this
error is a host name resolution problem. )ther possible causes of this error1
< nb'm is unable to connect to bpcd on the media ser"er
< nbpem is unable to connect to nbpro:y
< bptm on the media ser"er is unable to connect to nb'm on the master ser"er.These
errors are caused either by network connecti"ity issues or if a required process such as
pb:Ce:change is not running.
Status Code #-
====================
client=ser"er handshaking failed
! process on the ser"er encountered an error when it communicated with the client.
This error indicates that the client and ser"er were able to initiate communications& but
encountered difficulties and the communications did not complete. This problem can
occur during a backup or a restore.
Status Code #,
====================
child process killed by signal
! child of the process that reported this error was terminated. This error may occur if
the backup 'ob was terminated or another error terminated the child process. This
problem may also occur if a Net*ackup process was terminated through Task Aanager
or another utility.
Status Code #8
====================
failed trying to fork a process
! fork of a child process failed +on 2N(30 or a Create;rocess failed +on 4indows0.
This failure may be due to the following1
< !n o"erloaded system
< (nsufficient swap space or physical memory
< Too many processes are running on the system
Status Code #.
====================
failed trying to e:ec a command
! command was not run. This error can occur because the permissions of the command
do not allow it to be run. )r it occurs due to a lack of system resources such as memory
and swap space.
Status Code /0
====================
could not get passwd information
Could not get the passwd entry for a user.
Status Code /
====================
could not set user id for process
Could not set the user (9 of a process to the user (9 of the requesting user. Net*ackup
runs client processes as the requesting user.
Status Code /#
====================
could not set group id for process
Could not set the group (9 of a process to the requesting user group. Net*ackup runs
client processes with the group (9 of the requesting user.
Status Code //
====================
failed while trying to send mail
!n email notification about backup& archi"e& or restore results has failed. The email was
not sent to the administratorDs address as specified by the email global attribute. 4ith a
2N(3 client& the email was not sent to an email address specified with 2S7A!($ in the
clientDs bp.conf file.
Status Code /5
====================
failed waiting for child process
! Net*ackup process encountered a failure while waiting for a child process to
complete.
Status Code /6
====================
cannot make required directory
Could not create a required directory. ;ossible causes are1
< ! process does not ha"e permission to create the directory
< The path to the directory is not "alid
< !n () error occurs
< No space is a"ailable on the de"ice that contains the directory
Status Code /-
====================
failed trying to allocate memory
!llocation of system memory failed. This error occurs when an insufficient system
memory is a"ailable. This cause of this error may be that the system is o"erloaded with
too many processes and it does not enough physical and "irtual memory.
Status Code /,
====================
operation requested by an in"alid ser"er
!n in"alid media ser"er or 4indows Net*ackup >emote !dministration Console made
a request to the Net*ackup request daemon +bprd0 or Net*ackup database manager
daemon +bpdbm0. )n 4indows& these daemons are the Net*ackup >equest Aanager
and Net*ackup 9atabase Aanager ser"ices.
Status Code /8
====================
could not get group information
Could not get the group entry that describes a 2N(3 user group.
Status Code /.
====================
client name mismatch
The client used a name in a request to the Net*ackup ser"er that did not match the
configured name in the policy on the ser"er.
Status Code 50
====================
network connection broken
The connection between the client and the ser"er was broken. This status code can also
appear if the connection is broken between the master and the media ser"er during a
backup.
Status Code 5
====================
network connection timed out
The ser"er did not recei"e any information from the client for too long a period of time.
Status Code 5#
====================
network read failed
!n attempt to read data from a socket failed.
Status Code 5/
====================
une:pected message recei"ed
The client and the ser"er handshake was not correct.
Status Code 55
====================
network write failed
!n attempt to write data to a socket failed.
Status Code 56
====================
request attempted on a non reser"ed port
!n attempt was made to access a client from a non-reser"ed port.
Status Code 5-
====================
ser"er not allowed access
The ser"er tries to access a client& but access is blocked. ;ossible causes are as follows1
< The ser"er is not listed on the client as a "alid ser"er.
< The client was configured to require encrypted backups& but the encryption attribute
for the backup policy on the ser"er was not selected.
< The e"aluation license for the Net*ackup 7ncryption product has e:pired on the
ser"er& but the Net*ackup client was configured to require encrypted backups. !s a
result& the ser"er attempts to make a non-encrypted backup of the client. Since the client
is configured to require encryption& the backup failed.
Status Code 5,
====================
host is unreachable
!n attempt to connect to another machine failed.
Status Code 58
====================
client hostname could not be found
The system function gethostbyname+0 failed to find the clientDs host name.
Status Code 5.
====================
client did not start
The client failed to start up correctly.
Status Code 60
====================
client process aborted
The client backup terminated abnormally. @or e:ample& this error occurs if a Net*ackup
master or media ser"er is shut down or rebooted when a backup or restore is in progress.
Status Code 6
====================
timed out waiting for database information
The catalog process did not respond within fi"e minutes.
Status Code 6#
====================
timed out waiting for media manager to mount "olume
The requested "olume was not mounted before the timeout e:pired. This error can also
occur if the "olume is a cleaning tape but was not specified as a cleaning tape. !nother
possible cause1 the last a"ailable dri"e has a mount request for a non-backup +such as a
restore0. Then a backup that requires the same dri"e is initiated before the mount
completes. This error is due to the dri"e not being reported as busy until the mount
completes.
Status Code 6/
====================
backup restore manager failed to read the file list
The backup and restore manager +bpbrm0 did not read the list of files to back up or
restore.
Status Code 65
====================
timed out connecting to client
The ser"er did not complete the connection to the client. The accept system or winsock
call timed out after -0 seconds.
Status Code 66
====================
permission denied by client during rcmd
The 2N(3 client does not ha"e the ser"erDs name in its =.rhosts file.
Status Code 6-
====================
clientDs network is unreachable
!n error reported that the client could not reach the host +4S!7N7T2N>7!CB on
4indows or 7N7T2N>7!CB on 2N(30 when the client performed a system call.
Status Code 6,
====================
client connection refused
The client refused a connection on the port number for bpcd. This error can occur
because of the following1
< No process listening acti"ity occurs on the bpcd port
< The number of connections to the bpcd port is more than the network subsystem can
handle with the listen+0 call
Status Code 68
====================
canDt connect to client
The ser"er was unable to connect to the client.
Status Code 6.
====================
access to the client was not allowed
The master or the media ser"er tries to access the client& but the client does not
recogniEe the ser"er as a "alid ser"er.
Status Code -0
====================
client cannot read the mount table
The backup process on the client did not read the list of mounted file systems.
Status Code -
====================
Status code not a"ailable.
Status Code -#
====================
Status code not a"ailable.
Status Code -/
====================
process was killed by a signal
! kill signal was sent to the client process.
Status Code -5
====================
timed out waiting for the client backup to start
The client did not send a ready message to the ser"er within the allotted time.
Status Code -6
====================
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.
Status Code --
====================
client backup failed to recei"e the C)NT(N27 *!CF2; message
The client bpbkar process did not recei"e the message from the ser"er that indicates that
the ser"er is ready to continue.
Status Code -,
====================
client backup failed to read the file list
The client did not read the list of files to back up.
Status Code -8
====================
client timed out waiting for the file list
The client did not recei"e the list of files to back up within the allotted time. This list
comes from the ser"er.
Status Code -.
====================
in"alid filelist specification
The file list from the ser"er had in"alid entries.
Status Code ,0
====================
an entry in the filelist e:panded to too many characters
The wildcards& which were used in one of the file list entries& specified too many files.
Status Code ,
====================
none of the files in the file list e:ist
The files in the file list did not match any of the files on the client. This error can occur
with only one file in the file list and the file cannot be backed up due to an (=) error.
Status Code ,#
====================
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.
Status Code ,/
====================
bpstartCnotify failed
The bpstartCnotify script returned a nonEero e:it code.
Status Code ,5
====================
client timed out waiting for bpstartCnotify to complete
The bpstartCnotify script on the client takes too long.
Status Code ,6
====================
client timed out waiting for bpendCnotify to complete
The bpendCnotify script on the client takes too long.
Status Code ,-
====================
client timed out reading file
! fifo was specified in the file list and no data was produced on the fifo within the
allotted time.
Status Code ,,
====================
e:ecution of the specified system command returned a nonEero status
!n immediate command returned a nonEero status.
Status Code ,8
====================
afs=dfs command failed
(ndicates an !@S "os command failure.
Status Code ,.
====================
unsupported image format for the requested database query
;ossible causes are that the images to be synthesiEed were generated as follows1 using
an !SC(( catalog& for a pre-6.0 client& on a pre-6.0 master ser"er. )r one or more of the
images to be synthesiEed was encrypted. These images cannot be synthesiEed.
Status Code 80
====================
Aedia Aanager de"ice daemon +ltid0 is not acti"e
(f the ser"er is 2N(3& the Net*ackup de"ice manager daemon& ltid& is not running. (f
the ser"er is 4indows& the Net*ackup 9e"ice Aanager ser"ice is not running.
Status Code 8
====================
Aedia Aanager "olume daemon +"md0 is not acti"e
The tape manager +bptm0 did not communicate with the Net*ackup ?olume Aanager
+"md0. This communication is required for most operations.
Status Code 8#
====================
media manager killed by signal
!nother process or a user terminated the tape manager +bptm0 or disk manager +bpdm0.
Status Code 8/
====================
media open error
The tape manager +bptm0 or disk manager +bpdm0 did not open the de"ice or file that
the backup or restore must use.
Status Code 85
====================
media write error
The systemDs de"ice dri"er returned an (=) error while Net*ackup wrote to remo"able
media or a disk file.
Status Code 86
====================
media read error
The system de"ice dri"er returned an (=) error while Net*ackup reads from tape&
optical disk& or a disk file.
Status Code 8-
====================
media position error
The systemDs de"ice dri"er returned an (=) error while Net*ackup was positioning
media +tape or optical disk0.
Status Code 8,
====================
media close error
The systemDs de"ice dri"er returned an (=) error while Net*ackup closed a tape or
optical disk.
Status Code 88
====================
Status code not a"ailable.
Status Code 8.
====================
problems encountered during setup of shared memory
The Net*ackup processes use shared memory for some operations. This status is
returned when an error is encountered in the initialiEation of the shared memory by the
operating systemDs !;(s.
Status Code .0
====================
media manager recei"ed no data for backup image
The tape manager +bptm0 or disk manager +bpdm0 recei"ed no data when it performed a
backup& archi"e& or duplication. This error can occur for incremental backups where no
data was backed up because no files ha"e changed.
Status Code .
====================
fatal N* media database error
The tape manager +bptm0 recei"ed an error while it read or updated its media catalog.
Status Code .#
====================
media manager detected image that was not in tar format
4hen you performed a restore& the tape manager +bptm0 or disk manager +bpdm0 did
not find a tar header at the offset it e:pected.
Status Code ./
====================
media manager found wrong tape in dri"e
4hen you load a "olume for a backup or restore& the tape manager +bptm0 found a
"olume that loaded without the e:pected tape header. This error may mean that "olumes
in a robot are not in the slots that are indicated in the Aedia and 9e"ice Aanagement
"olume configuration.
Status Code .5
====================
cannot position to correct image
The tape manager +bptm0 searched for a backup image to restore but did not find the
correct backup (9 at the e:pected position on the "olume. This error can indicate a dri"e
hardware problem.
Status Code .6
====================
media id is not assigned to this host in the 7AA database
!n operation was requested on a media (9 for which Net*ackup does not ha"e a record
assigned to the requesting ser"er. !n e:ample of this is using bpmedia to suspend or
freeEe a media (9 that does not e:ist or is not assigned to the requesting ser"er.
Status Code .-
====================
unable to allocate new media for backup& storage unit has none a"ailable
The tape manager +bptm0 did not allocate a new "olume for backups. This error
indicates that the storage unit has no more "olumes a"ailable in the "olume pool for this
backup. Note that Net*ackup does not change storage units during the backup.
Status Code .,
====================
requested media id is in use& cannot process request
!n operation was requested on a media (9 that is in use. !n e:ample of this operation is
the attempt to suspend or freeEe a "olume while it is in use for a backup or restore.
Status Code .8
====================
error requesting media +tpreq0
The tape manager and optical manager +bptm0 recei"ed an error when they requested a
media mount from the following1 the Net*ackup 9e"ice Aanager ser"ice +on
4indows0 or the Aedia Aanager de"ice daemon +ltid0 +on 2N(30.
Status Code ..
====================
N9A; backup failure
The paths in your N9A; policy file list did not back up successfully.
Status Code 00
====================
system error occurred while processing user command
! system call failure in bparchi"e& bpbackup& bplist& or bprestore.
Status Code 0
====================
failed opening mail pipe
The process that attempts to send mail did not open the pipe to the ser"er.
Status Code 0#
====================
failed closing mail pipe
The process that sends mail could not close the pipe to the ser"er.
Status Code 0/
====================
error occurred during initialiEation& check configuration file
None
Status Code 05
====================
in"alid file pathname
None
Status Code 06
====================
file pathname e:ceeds the ma:imum length allowed
The path name +built by using the current working directory0 e:ceeds the ma:imum
path length that the system allows.
Status Code 0-
====================
in"alid file pathname found& cannot process request
)ne of the file paths to be backed up or archi"ed is not "alid.
Status Code 0,
====================
Status code not a"ailable.
Status Code 08
====================
Status code not a"ailable.
Status Code 0.
====================
in"alid date specified
This error can occur when you run a command on the command line that contains a date
option. The format of a date option can "ary depending on the locale of the master
ser"er.
Status Code 0
====================
Cannot find the Net*ackup configuration information
)n 4indows& Net*ackup did not read the registry entries that were created during
installation. )n 2N(3& the =usr=open"=netbackup=bp.conf file does not e:ist.
Status Code
====================
No entry was found in the ser"er list
)n 2N(3& the S7>?7> = ser"erCname line is omitted from the bp.conf file. )n
4indows& the ser"er list contains no entries.
Status Code #
====================
no files specified in the file list
! restore was requested with no files in the file list.
Status Code /
====================
Status code not a"ailable.
Status Code 5
====================
unimplemented error code
This error should not occur. (f nb'm recei"ed a negati"e error number& status 5 is
issued.
Status Code 6
====================
Status code not a"ailable.
Status Code -
====================
?:SS authentication failed
)n either end of a socket connection& the parties did not mutually authenticate each
other.
Status Code ,
====================
?:SS access denied
The user identity that was used to attempt an operation does not ha"e the permissions
that are needed to perform the action.
Status Code 8
====================
?:SS authoriEation failed
Net*ackup was unable to complete the authoriEation check against the !uthoriEation
ser"ice.
Status Code .
====================
Status code not a"ailable.
Status Code #0
====================
cannot find configuration database record for requested N* database backup
The program that backs up the Net*ackup internal catalogs did not find the attributes
that indicate which media (9s to use or paths to back up. This error should not occur
under normal circumstances.
Status Code #
====================
no media is defined for the requested N* database backup
4hen Net*ackup attempted to back up its internal catalogs& no media (9s were defined
in the catalog backup configuration.
Status Code ##
====================
specified de"ice path does not e:ist
The Net*ackup internal catalogs were backed up in the following manner1 by using the
bpbackupdb command line and by specifying a de"ice path +on 4indows0 or a raw
de"ice file +on 2N(30 that does not e:ist.
Status Code #/
====================
specified disk path is not a directory
4hen Net*ackup attempted to back up its internal catalogs& the backup attributes were
set to dump to a disk. Bowe"er& the disk file path already e:ists and is not a directory.
Status Code #5
====================
N* database backup failed& a path was not found or is inaccessible
)ne or more of the specified paths in the catalog backup configuration were not backed
up.
Status Code #6
====================
a Net*ackup catalog backup is in progress
)nly one Net*ackup catalog backup can be acti"e at any gi"en time. Certain operations
are not allowed during an online catalog backup. +These include catalog archi"ing&
catalog compression& and e:piration of the last copy of an image.0
Status Code #-
====================
N* database backup header is too large& too many paths specified
Too many paths were specified in the Net*ackup catalog backup configuration to fit in
a fi:ed-siEe media header. This error should not occur under normal circumstances.
Status Code #,
====================
specified media or path does not contain a "alid N* database backup header
The bpreco"er command was issued and the media (9 specified does not ha"e "alid
catalog backup data.
Status Code #8
====================
N* database reco"ery failed& a process has encountered an e:ceptional condition
(n the catalogs that were specified for reco"ery& one or more cannot be restored. @or
more detail& refer to the error message that precedes this status code in the output from
the bpreco"er command.
Status Code #.
====================
9isk storage unit is full
!s Net*ackup writes to the file system for the disk storage unit& runs out of space. 2ntil
more file system space is a"ailable& images of similar siEe or larger may fail with this
error when written to this disk storage unit.(n a scheduled backup 'ob that writes to a
storage unit group +which contains this disk storage unit0& the following occurs1 the
Net*ackup scheduler requests the storage unit with the greatest a"ailable capacity when
the 'ob is retried.@or the retry& when the scheduler requests the storage unit with the
greatest a"ailable capacity& note the following1
< ! tape storage unit in the storage unit group has preference o"er any disk storage units
since tape storage units usually ha"e more capacity.
< (f the storage unit with the most unused capacity is busy& Net*ackup skips it.
Net*ackup then selects an a"ailable storage unit with the ne:t largest& unused capacity.
< (f the storage unit with the greatest unused capacity is the one that lacked capacity
when the 'ob first failed& the scheduler tries it again. That storage unit may ha"e more
unused capacity now than it did when the 'ob failed.
Status Code /0
====================
system error occurred
!n error occurred that pre"ents the product from operating in a consistent fashion. This
error is usually related to a system call.
Status Code /
====================
client is not "alidated to use the ser"er
The client name& as determined from the connection to the ser"er& did not match any
client name in the Net*ackup configuration. No altnames configuration for this client
e:ists on the master ser"er. ! client and ser"er with multiple network connections can
encounter this problem in the following situation1 the name by which the client is
configured is not the one by which its routing tables direct connections to the ser"er.
Status Code /#
====================
user is not "alidated to use the ser"er from this client
None
Status Code //
====================
in"alid request
)ne of two e:planations e:ist.
< ! request was made that is not recogniEed. This usually results from different "ersions
of Net*ackup software being used together.
< (f a client recei"es this error in response to a list or restore request& then the
9(S!$$)4CC$(7NTC$(STC>7ST)>7 or 9(S!$$)4CC$(7NTC>7ST)>7. option
e:ists in the bp.conf file on the following1 a 2N(3 Net*ackup ser"er or in the registry
on a 4indows Net*ackup ser"er. These options deny list and restore requests from all
Net*ackup clients.
Status Code /5
====================
unable to process request because the ser"er resources are busy
Status code /5 is an informational message that indicates that all dri"es in the storage
unit are currently in use. (f all dri"es are in use& Net*ackup automatically tries another
storage unit. (f one is not a"ailable& Net*ackup re-queues the 'ob with a status of /5
and retries it later.
Status Code /6
====================
client is not "alidated to perform the requested operation
!n alternate client restore was attempted that did not come from the root user +on
2N(30 or the administrator +on 4indows0.
Status Code /-
====================
tir info was pruned from the image file
The T(> information was pruned from one or more of the component +differential or
cumulati"e0 backup images being synthesiEed. This situation arises when the following
occurs1
< The most recent backup image for the client is a synthetic full or cumulati"e backup
< The T(> information from one or more of the component images before the synthetic
full +or cumulati"e0 backup is prunedThe T(> information is automatically restored to
the image catalog if you do the following1 e:pire the synthetic backup +full or
cumulati"e0 image and try to rerun the synthetic backup 'ob for the client. Bowe"er& the
synthetic backup 'ob fails with this error if the T(> restore fails due to bad& missing& or
"aulted media or a bad dri"e.
Status Code /,
====================
Status code not a"ailable.
Status Code /8
====================
Status code not a"ailable.
Status Code /.
====================
Status code not a"ailable.
Status Code 50
====================
user id was not superuser
! user or process that did not ha"e root pri"ileges +on 2N(30 or administrator
pri"ileges +on 4indows0 started the process.
Status Code 5
====================
file path specified is not absolute
The file specification must be an absolute path.
Status Code 5#
====================
file does not e:ist
To back up a ?:@S file system with Snapshot Client& the ?:@S file system on the client
must be patched with correct& dynamically linked libraries. (f the correct ?:@S libraries
are not installed& the backup fails with status 5#.
< @or most snapshot backups& the following message appears in the
=usr=open"=netbackup=logs=bpfis log on the client1
0.1/-158.#.. G6#,H I/#J fsCde"CrtCcheck1 @T$ - snapshot method1 nbuCsnap abort -
required ?:@S dynamic linked libraries for Net*ackup are not installed. ;lease "isit the
?eritas support web site& and refer to Technote number #-###6 for further information.
< @or the backups that run from a @lash*ackup policy& the following appears in the
=usr=open"=netbackup=logs=bpbkar log on the client1
010.16-.6-- G5-H I/#J bpfsmap1 @T$ - bpfsmap1 @lash*ackup abort - required
?:@S dynamic linked libraries for Net*ackup are not installed. ;lease "isit the ?eritas
support web site& and refer to Technote number #-###6 for further information.
010.16-.6, G5-H I-J bpbkar 7:it1 7>> - bpbkar @!T!$ e:it status = 5#1 file
does not e:ist
010.16-.6,/ G5-H I5J bpbkar 7:it1 (N@ - 73(T ST!T2S 5#1 file does not e:ist
Status Code 5/
====================
in"alid command protocol
! poorly formed request was made to the Net*ackup request daemon +2N(30 or to the
>equest Aanager ser"ice +4indows0. This error can be due to the following1
mismatched "ersions of the product& corrupted network communication& or to a non-
Net*ackup process sending data across the port for the daemon or ser"ice.
Status Code 55
====================
in"alid command usage
This status code is due to a Net*ackup process being started with improper options or
an incompatibility in the product.
Status Code 56
====================
daemon is already running
!nother copy of the process is running.
Status Code 5-
====================
cannot get a bound socket
The ser"ice or daemon did not bind to its socket. ! system call fails when the daemon
+2N(30 or ser"ice +4indows0 attempts to bind to its configured port number. This error
is usually caused when another process acquired the port before the daemon or ser"ice
started.
Status Code 5,
====================
required or specified copy was not found
The requested copy number of a backup or an archi"e image cannot be found.
Status Code 58
====================
daemon fork failed
! Net*ackup ser"ice did not create a child process due to an error that was recei"ed
from the system. This error is probably an intermittent error that is based on the
a"ailability of resources on the system.
Status Code 5.
====================
master ser"er request failed
None
Status Code 60
====================
termination requested by administrator
The process terminates +or has terminated0 as a direct result of a request from an
authoriEed user or process.
Status Code 6
====================
*ackup 7:ec operation failed
The Klobal 9ata Aanager console reported that a *ackup 7:ec 'ob +backup& archi"e& or
restore0 did not complete normally.
Status Code 6#
====================
required "alue not set
!n incomplete request was made to the bpdbm process +on 2N(30& or the Net*ackup
9atabase Aanager ser"ice +on 4indows0. This error usually occurs because different
"ersions of software are used together.
Status Code 6/
====================
ser"er is not the master ser"er
This status code is reser"ed for future use.
Status Code 65
====================
storage unit characteristics mismatched to request
! backup was attempted and the storage unit selected for use had the characteristics that
were not compatible with the backup type.
Status Code 66
====================
disk is full
The write to the catalog file failed because the disk that contains the catalog database is
full.
Status Code 6-
====================
snapshot error encountered
This status code indicates a snapshot-backup related error regarding 4indows )pen @ile
*ackup or Snapshot Client.
Status Code 6,
====================
suspend requested by administrator
Status code 6, is an informational message& which indicates that the administrator
suspended the 'ob from the !cti"ity Aonitor. The 'ob is in the suspended state in the
!cti"ity Aonitor. (t can be resumed from the last checkpoint by the administrator.
Status Code 68
====================
failed accessing daemon lock file
The process cannot lock its lock file because an error was recei"ed from a system call.
This lock file synchroniEes process acti"ities +for e:ample& it pre"ents more than one
daemon from running at a time0.
Status Code 6.
====================
licensed use has been e:ceeded
! configuration limit was e:ceeded. @or e:ample& a 'ob fails with this error code if a
policy is set up that specifies the following1
< ! storage unit that is on a S!N media ser"er
< ! client that is not the S!N media ser"er itselfS!N media ser"ers can only back up
themsel"es.This status code is used when the creation of a storage unit on a S!N media
ser"er fails because L)n demand onlyL is not selected. L)n demand onlyL is required for
storage units on a S!N media ser"er.
Status Code -0
====================
authentication failed
Net*ackup encounters a problem when two systems attempt to authenticate one another.
Status Code -
====================
7"aluation software has e:pired. See www."eritas.com for ordering information
The time that was allowed for the Net*ackup e"aluation software ended.
Status Code -#
====================
incorrect ser"er platform for license
The platform identifier in the license key does not match the platform type on which the
key was installed.
Status Code -/
====================
media block siEe changed prior resume
Status code -/ is an informational message. (t indicates that the media block siEe was
changed before a backup 'ob from the last checkpoint resumed. Since the media block
siEe must be consistent& the 'ob was restarted from the beginning.
Status Code -5
====================
unable to mount media because it is in a 9)4N& or otherwise not a"ailable
! restore was attempted and the "olume required for the restore was in a 9)4N dri"e
in a robot. )r& the slot is empty that should contain the "olume.
Status Code -6
====================
N* image database contains no image fragments for requested backup id=copy number
! restore was attempted and Net*ackup has no record of the fragments that are
associated with the backup (9 that has the files.
Status Code --
====================
backups are not allowed to span media
!n end of media +7)A0 was encountered while the backup image was written. The
backup was terminated because the Net*ackup
9(S!$$)4C*!CF2;SCS;!NN(NKCA79(! option was present in bp.conf +on
2N(30 or in the registry +on 4indows0. The backup is retried automatically with a
different "olume if the backup tries attribute allows it in the Net*ackup global attribute
configuration.
Status Code -,
====================
cannot find requested "olume pool in 7AA database
! backup to a nonrobotic dri"e was attempted and the tape manager +bptm0 cannot find
or add the specified "olume pool.
Status Code -8
====================
cannot o"erwrite media& data on it is protected
! catalog backup was attempted to a "olume that cannot be o"erwritten because it
contains data that by default Net*ackup does not o"erwrite. +This data includes items
such as tar& cpio& and !NS(.0
Status Code -.
====================
media id is either e:pired or will e:ceed ma:imum mounts
! backup or a catalog backup was attempted and the "olume selected for use has
reached its ma:imum number of mounts. The ma:imum number is specified in the
Aedia and 9e"ice Aanagement "olume configuration. @or a regular backup& the
"olume is automatically set to the S2S;7N979 state and not used for further backups.
@or a Net*ackup catalog backup& the operation terminates abnormally.
Status Code ,0
====================
third party copy backup failure
2sually indicates a problem with the /pc. file or the mo"er.conf file. +@or detailed
causes& see recommended actions.0 @or more information on these files& refer to the
Net*ackup Snapshot Client Configuration online document. @or help accessing this
document& see LSnapshot Client !ssistanceL in the Net*ackup Snapshot Client
!dministratorDs Kuide.
Status Code ,
====================
media id must be - or less characters
operation& such as using bpmedia to suspend or freeEe a media (9& was attempted and
the media (9 specified was longer than si: alpha-numeric characters
Status Code ,#
====================
cannot read media header& may not be Net*ackup media or is corrupted
4hen you loaded a "olume for a backup or restore& the tape manager +bptm0& did not
find the e:pected tape header. This error can mean that a robotic de"ice "olume is not in
the slot number that is in the Aedia and 9e"ice Aanagement "olume configuration. (t
also can mean that a read error +(=) error0 occurred.
Status Code ,/
====================
cannot read backup header& media may be corrupted
4hen the tape manager +bptm0 searches for a backup image to restore& the following
occurs1 it cannot find the correct backup (9 at the position on the media where
Net*ackup e:pected it. This status code can indicate a dri"e hardware problem.
Status Code ,5
====================
media manager - system error occurred
!n abnormal condition caused a tape manager +bptm0 or disk manager +bpdm0 failure.
Status Code ,6
====================
not all requested files were restored
4hen the bptm or the bpdm process restores files from an image& it detected a fatal
error condition and terminated the restore before it completed. 2nder normal
circumstances& this error should not occur.
Status Code ,-
====================
cannot perform specified media import operation
The tape manager +bptm0 detected an error condition when it attempted to import a
specific backup image. ;ossible reasons for this error are as follows1
< Aedia (9 is already acti"e in the Net*ackup media catalog on this ser"er
< Aedia (9 is not in the "olume configuration
< @atal tape manager +bptm0 error occurred
< Total image was not obtained from ;hase of import
Status Code ,,
====================
could not deassign media due to Aedia Aanager error
The tape manager +bptm0 cannot successfully unassign a media (9.
Status Code ,8
====================
media id is not in Net*ackup "olume pool
Net*ackup attempted a backup of its catalogs and the media (9 that was specified for
the catalog backup was not in the Net*ackup "olume pool. ?olumes for catalog backups
must be in the Net*ackup "olume pool.
Status Code ,.
====================
density is incorrect for the media id
!n operation such as Llist contentsL was attempted on an in"alid media (9& such as a
cleaning tape. !nother possibility1 a media (9 in the Net*ackup catalog backup
configuration does not match the media type that was entered in the "olume
configuration.
Status Code 80
====================
tar was successful
tar returned a successful e:it status.
Status Code 8
====================
tar recei"ed an in"alid argument
)ne of the parameters that was passed to tar was not "alid.
Status Code 8#
====================
tar recei"ed an in"alid file name
tar cannot write to the file that is specified with the -f parameter.
Status Code 8/
====================
tar recei"ed an in"alid archi"e
The data that was passed to tar was corrupt.
Status Code 85
====================
tar had an une:pected error
! system error that occurred in tar.
Status Code 86
====================
tar did not find all the files to be restored
The tar file list contained files that were not in the image.
Status Code 8-
====================
tar recei"ed no data
Net*ackup did not send data to tar.
Status Code 8,
====================
Status code not a"ailable.
Status Code 88
====================
Status code not a"ailable.
Status Code 8.
====================
the ser"er is not allowed to write to the clientDs filesystems
The client does not allow writes from the ser"er.
Status Code .0
====================
found no images or media matching the selection criteria
! "erify& duplicate& or import was attempted and no images that matched the search
criteria were found in the Net*ackup catalog.
Status Code .
====================
no images were successfully processed
! "erify& duplicate& or import was attempted and failed for all selected images.
Status Code .#
====================
?:SS authentication is required but not a"ailable
)n one side of a Net*ackup network connection& the system requires ?:SS
authentication. )n the other side of the connection& the other system is not configured to
use ?:SS. ?:SS authentication is used with the Net*ackup !ccess Control feature
+N*!C0. The connection was terminated because ?:SS authentication cannot be
completed.
Status Code ./
====================
?:SS authentication is requested but not allowed
)n one side of a Net*ackup network connection& the system requires ?:SS
authentication. The system on the other side of the connection is not configured to use
?:SS. ?:SS authentication is used with the Net*ackup !ccess Control feature
+N*!C0. The connection has been terminated because ?:SS authentication cannot be
completed.
Status Code .5
====================
the ma:imum number of 'obs per client is set to 0
The Net*ackup Aa:imum 'obs per client global attribute is currently set to 0. Setting
the "alue to 0 disables backups and archi"es.
Status Code .6
====================
client backup was not attempted
! backup 'ob was in the Net*ackup schedulerDs worklist but was not attempted.
Status Code .-
====================
client backup was not attempted because backup window closed
! backup or an archi"e operation that the backup scheduler queued was not attempted
because the backup window was no longer open.
Status Code .,
====================
the specified schedule does not e:ist in the specified policy
! user backup or archi"e request specified the e:act policy and schedule to use when a
backup is performed. The policy e:ists but does not contain the schedule.
< )n Aicrosoft 4indows and Net4are nontarget clients& you can specify a policy or
schedule on the *ackups tab in the Net*ackup Client ;roperties dialog bo:. To display
this dialog bo:& start the *ackup& !rchi"e& and >estore interface on the client and select
Net*ackup Client ;roperties on the @ile menu.
< )n 2N(3 and Aacintosh clients& you can specify a policy or schedule by using the
bp.conf options& *;*!CF2;C;)$(CM or *;*!CF2;CSCB79.
< )n Net4are target clients& you can specify a policy or schedule in the bp.ini file.
Status Code .8
====================
no acti"e policies contain schedules of the requested type for this client
! user backup or archi"e was requested& and this client is not in a policy that has a user
backup or archi"e schedule.
Status Code ..
====================
operation not allowed during this time period
! user backup or archi"e was requested and this client is not in a policy that has the
following1 a user backup or archi"e schedule with an open backup window. This error
implies that an appropriate policy and schedule combination e:ists for this client.
Status Code #00
====================
scheduler found no backups due to run
4hen the Net*ackup scheduler process +nbpem0 checked the policy and the schedule
configuration& it did not find any clients to back up. This error may be due to the
following1
< No backup time windows are open +applies only to full and to incremental schedules0.
< ;olicies are set to inacti"e.
< The clients were recently backed up and are not due for another backup +based on
@requency setting for the schedules0.
< ;olicies do not ha"e any clients.
Status Code #0
====================
handshaking failed with ser"er backup restore manager
! process on the master ser"er encountered an error when it communicated with the
media host +can be either the master or a media ser"er0. This error means that the master
and the media ser"er processes were able to initiate communication& but were not able
to complete them. This problem can occur during a backup& restore& or media list in a
single or a multiple ser"er configuration.
Status Code #0#
====================
timed out connecting to ser"er backup restore manager
! master ser"er process that tried to initiate communications with the media host timed
out +can be either the master or a media ser"er0. This problem can occur during a
backup or restore in either a single or a multiple ser"er configuration.
Status Code #0/
====================
ser"er backup restore managerDs network is unreachable
! process on the master ser"er cannot connect to a particular host on the network when
it tries to initiate communication with the media host. This problem can occur during a
backup or restore in either a single or a multiple ser"er configuration.
Status Code #05
====================
connection refused by ser"er 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.
Status Code #06
====================
cannot connect to ser"er backup restore manager
! process on the master ser"er cannot connect to a process on a host on the network.
This error occurs when the process tries to initiate communication with the ser"er that
has the storage unit. This problem can occur during a backup or restore in either a single
or a multiple ser"er configuration.
Status Code #0-
====================
access to ser"er backup restore manager denied
The master ser"er tries to start a process on another ser"er +or itself0 but does not appear
in the Net*ackup ser"er list on that ser"er. )n a 2N(3 ser"er& the master is the first
S7>?7> entry in the bp.conf file. )n a 4indows ser"er& the master is designated on the
Ser"ers tab in the Aaster Ser"er ;roperties dialog bo:.To access this dialog bo:& see
L2sing the Bost ;roperties windowL in the Troubleshooting Kuide.
Status Code #0,
====================
error obtaining date of last backup for client
4hen nbpem tries to obtain the date of the last backup for a particular client& policy& and
schedule combination& an error occurs.
Status Code #08
====================
Status code not a"ailable.
Status Code #0.
====================
error creating or getting message queue
4hen a Net*ackup process attempts to create an internal message queue construct for
inter-process communication& an error occurs. This error indicates a problem on the
master ser"er. )n 2N(3 systems& this error may be due to a lack of system resources for
System ? inter-process communication.
Status Code #0
====================
error recei"ing information on message queue
4hen a Net*ackup process attempts to recei"e a message from a Net*ackup daemon
using bprd on an internal message queue construct& an error occurs. This error indicates
a problem on the master ser"er. )n 2N(3 systems& this error may be due to a lack of
system resources for System ? inter-process communication.
Status Code #
====================
Status code not a"ailable.
Status Code ##
====================
error sending information on message queue
4hen a Net*ackup process attempts to attach to an already e:isting internal message
queue construct for inter-process communication& an error occurs. This error indicates a
problem on the master ser"er. )n 2N(3 systems& this error may be due to a lack of
system resources for System ? inter-process communication.
Status Code #/
====================
no storage units a"ailable for use
The Net*ackup resource broker +nbrb0 did not find any storage units a"ailable for use.
7ither all storage units are una"ailable or all storage units are configured for )n demand
only. (n addition& the policy and schedule does not require a specific storage unit.
Status Code #5
====================
Status code not a"ailable.
Status Code #6
====================
failed reading global config database information
9uring the periodic checking of the Net*ackup configuration& nbpro:y was unable to
read the global configuration parameters.
Status Code #-
====================
failed reading retention database information
9uring its periodic checking of the Net*ackup configuration& nbpem did not read the
list of retention le"els and "alues.
Status Code #,
====================
failed reading storage unit database information
9uring its periodic checking of the Net*ackup configuration& nbpem did not read the
storage unit configuration.
Status Code #8
====================
failed reading policy database information
9uring the periodic checking of the Net*ackup configuration& nbpem did not read the
backup policy configuration.
Status Code #.
====================
the required storage unit is una"ailable
The policy or schedule for the backup requires a specific storage unit& which is currently
una"ailable. This error also occurs for other attempts to use the storage unit within the
current backup session.
Status Code ##0
====================
database system error
The bpdbm process +2N(30& or the Net*ackup 9atabase Aanager ser"ice +4indows0
did not create a directory path for its configuration catalogs. This error is due to a
system call failure& which is usually due to a permission problem or an Lout of spaceL
condition.
Status Code ##
====================
continue
This status code is used to coordinate communication between "arious Net*ackup
processes and normally does not occur. (f the logs show that it is associated with a
subsequent error& it usually indicates a communication problem. (n this case&
concentrate your troubleshooting efforts on the subsequent error.
Status Code ###
====================
done
This status code is used to coordinate communication between "arious Net*ackup
processes and is normally not seen. (f the error logs show that it is associated with a
subsequent error& it usually indicates a communication problem. (n this case&
concentrate your troubleshooting efforts on the subsequent error.
Status Code ##/
====================
an in"alid entry was encountered
! request to the bpdbm process +on 2N(30 or the Net*ackup 9atabase Aanager ser"ice
+on 4indows0 had in"alid information or some information that conflicted. This error is
usually a result of the use of software from different "ersions. !nother cause can be
incorrect parameters on a command.
Status Code ##5
====================
there was a conflicting specification
! request to the bpdbm process +on 2N(30 or the Net*ackup 9atabase Aanager ser"ice
+on 4indows0 had some information that conflicted. This error is usually a result of the
use of software from different "ersion le"els together.
Status Code ##6
====================
te:t e:ceeded allowed length
Te:t in a request e:ceeds a buffer siEe. The request was made to the bpdbm process +on
2N(30 or the Net*ackup 9atabase Aanager ser"ice +on 4indows0. This error is usually
a result of the use of software from different "ersion le"els.
Status Code ##-
====================
the entity already e:ists
The configuration already has an entity with the same name or definition. @or e:ample1
this status appears if you add a new policy when an e:isting policy has the same name
or definition such as attributes or clients.
Status Code ##,
====================
no entity was found
The item requested was not in the catalog. @or e:ample& the entity can be a file or it can
be policy information.
Status Code ##8
====================
unable to process request
!n inconsistency e:ists in the catalog or a request was made that would be improper to
satisfy.
Status Code ##.
====================
e"ents out of sequence - image inconsistency
! request was made that would cause the image catalog to become inconsistent if
satisfied
Status Code #/0
====================
the specified policy does not e:ist in the configuration database
The specified policy name does not e:ist.
Status Code #/
====================
schedule windows o"erlap
The specified start and the duration times for one day of the schedule o"erlap with
another day of the schedule.
Status Code #/#
====================
a protocol error has occurred
This error is an intermediate status code that usually precedes another status code. (t
indicates the following1 either the bpdbm process +on 2N(30 or the Net*ackup
9atabase Aanager ser"ice +on 4indows0 or the process that communicates with it has
recei"ed une:pected information.
Status Code #//
====================
premature eof encountered
This status code is an intermediate one that usually precedes another status code and is
associated with a problem in network communication.
Status Code #/5
====================
communication interrupted
This status code is an intermediate one that usually precedes another status code and is
associated with a problem in network communication. 7ither a ser"er or a client process
recei"ed an interrupt signal.
Status Code #/6
====================
inadequate buffer space
This code usually indicates a mismatch between ser"er and client software "ersions.
Status Code #/-
====================
the specified client does not e:ist in an acti"e policy within the configuration database
! client name was not specified or the specified client does not e:ist.
Status Code #/,
====================
the specified schedule does not e:ist in an acti"e policy in the configuration database
The specified schedule does not e:ist in the Net*ackup configuration.
Status Code #/8
====================
the database contains conflicting or erroneous entries
The catalog has an inconsistent or a corrupted entry.
Status Code #/.
====================
the specified client does not e:ist in the specified policy
The specified client is not a member of the specified policy.
Status Code #50
====================
no schedules of the correct type e:ist in this policy
The appropriate schedule was not found in the specified policy. @or e:ample& a user
backup specified a policy name but no user backup schedule e:ists in that policy.
Status Code #5
====================
the specified schedule is the wrong type for this request
The specified schedule for an immediate manual backup is not for a full nor an
incremental backup. (t must be one of these.
Status Code #5#
====================
operation would cause an illegal duplication
(f the request is processed& it causes a duplicate catalog entry. This error is usually due
to a mistake in the specification of media (9s for Net*ackup catalog backups.
Status Code #5/
====================
the client is not in the configuration
The specified client name was not in the catalog.
Status Code #55
====================
Status code not a"ailable.
Status Code #56
====================
the specified policy is not of the correct client type
! user backup specified a policy that is not the type that is required for the client.
Status Code #5-
====================
no acti"e policies in the configuration database are of the correct client type
! user backup request was not satisfied because no acti"e policies were the type that
were required for the client.
Status Code #5,
====================
the specified policy is not acti"e
*ackups for the specified policy are disabled because the policy is inacti"e.
Status Code #58
====================
there are no acti"e policies in the configuration database
No acti"e policy was found that would satisfy the request.
Status Code #5.
====================
the file list is incomplete
4hile the ser"er waited for the client to finish sending the file list& it timed out or a
sequencing problem occurred.
Status Code #60
====================
the image was not created with T(> information
This error is internal and should not appear to customers.
Status Code #6
====================
the tir information is Eero length
@or a true-image backup& the client sent no file information to the master ser"er.
Net*ackup disco"ered this condition when it attempted to write the T(> information to
media.
Status Code #6#
====================
!n e:tended error status has been encountered& check detailed status
(f a process was unable to report the e:tended error status as the final 'ob status& the 'ob
e:its with status #6#. +The e:tended error status has a number greater than #66.0
Status Code #6/
====================
the catalog image .f file has been archi"ed
The catalog image .f file was archi"ed.
Status Code #65
====================
ser"er name not found in the Net*ackup configuration
This error should not occur through normal use of Net*ackup.
Status Code #66
====================
Status code not a"ailable.
Status Code #6-
====================
logic error encountered
!n internal ?ault error occurred.
Status Code #6,
====================
failed to get 'ob data
This error can indicate either of the following1
< ?ault failed to get 'ob data because of a broken connection with the 'ob manager
+nb'm0.
< ?ault recei"ed empty 'ob data. This error occurs if a user-specified 'ob (9 on the
"ltrun -haltdups command is out of range +not among the 'ob (9s created by 'ob
manager0.
Status Code #68
====================
?ault duplication was aborted by administrator request
The administrator initiated an abort request on the acti"e "ault duplication 'ob.
Status Code #6.
====================
"ault configuration file not found
This error should not occur.
Status Code #-0
====================
failed to send signal
"ltrun failed to send a signal to the ?ault duplication 'ob.
Status Code #-
====================
"ault internal error #-
This error code should not occur.
Status Code #-#
====================
"ault internal error #-#
This error code should not occur.
Status Code #-/
====================
session id assignment failed
The unique identifier to be assigned to the ?ault session is corrupt.
Status Code #-5
====================
Status code not a"ailable.
Status Code #-6
====================
session id file is empty or corrupt
The session (9 that is stored in the following file is corrupt.
2N(31 =usr=open"=netbackup="ault=sessions="aultCname=session.last
4indows1 installCpathNNet*ackupN"aultNsessionsN"aultCnameNsession.last
Status Code #--
====================
cannot find robot& "ault& or profile in the "ault configuration
Net*ackup cannot find the specified profile name or triplet
robotCname="aultCname=profileCname on the ?ault command +"ltrun& "lte'ect&
"ltoffsitemedia0 or in "ltopmenu in the ?ault configuration.
Status Code #-,
====================
cannot find the local host name
! ?ault 'ob obtains the local host name through an )S call. This error occurs when the
?ault 'ob is unable to get the local host name.
Status Code #-8
====================
the "ault session directory is either missing or inaccessible
This error occurs when a ?ault 'ob cannot access the following1
2N(31 =usr=open"=netbackup="ault=sessions
4indows1 installCpathNNet*ackupN"aultNsessions
This directory is created when ?ault is installed.
Status Code #-.
====================
no "ault session id was found
This error is encountered when "ltopmenu cannot find a sid::: session id directory for
the specified profile. 7ither no ?ault 'obs were run for this profile or the corresponding
sid::: session id directory +or directories0 were remo"ed from the following directory1
2N(31 =usr=open"=netbackup="ault=sessions="aultCname
4indows1 installCpathNNet*ackupN"aultNsessionsN"aultCname
Status Code #,0
====================
unable to obtain process id& getpid failed
This error occurs when a ?ault process is unable to obtain its process (9 by means of
the getpid+0 )S system call.
Status Code #,
====================
"ault 3A$ "ersion mismatch
The ?ault upgrade process failed.
Status Code #,#
====================
e:ecution of a "ault notify script failed
This error occurs when the ?ault process is unable to run a ?ault notify script due to
permissions problems or coding problems in the script. (t also occurs if the script returns
an error.
Status Code #,/
====================
in"alid 'ob id
This error can occur in either of the following situations1
< The specified 'ob is not an acti"e ?ault 'ob
< The specified acti"e ?ault 'ob is not at the duplication step
Status Code #,5
====================
no profile was specified
This error should not occur.
Status Code #,6
====================
a session is already running for this "ault
This error occurs when you start a session for a "ault and another session is already
running for this "ault. )nly one session is allowed for a "ault at any gi"en time.
Status Code #,-
====================
in"alid session id
This error should not occur.
Status Code #,,
====================
unable to print reports
This error should not occur.
Status Code #,8
====================
unable to collect pre e'ect information from the !;(
This error occurs when robotic information cannot be retrie"ed before e'ection.
Status Code #,.
====================
e'ect process is complete
This error occurs when the e'ect process is completed successfully.
Status Code #80
====================
there are no "olumes to e'ect
This error occurs when media to be e'ected are not in the library.
Status Code #8
====================
"ault core error
!n internal ?ault error occurred.
Status Code #8#
====================
cannot connect to nb"ault ser"er
The "ault 'ob cannot connect to the Net*ackup ?ault Aanager ser"ice +nb"ault on
2N(3& nb"ault.e:e on 4indows0. ;ossible causes are1
< The Symantec ;ri"ate *ranch 7:change ser"ice +?>TSpb:0 or Net*ackup >equest
Aanager +bprd0 is down.
< The Net*ackup ?ault Aanager ser"ice is down& possibly because of the following1 the
?ault is not licensed& the "ault.:ml configuration file is corrupt& or the "ault.:ml
configuration file upgrade failed during an upgrade installation.
Status Code #8/
====================
error+s0 occurred during "ault report generation
?ault encountered errors during the report generation phase.
Status Code #85
====================
error+s0 occurred during "ault report distribution
?ault encountered errors during the report distribution phase. ;otential reasons include
the following1
< >eports were not emailed +possibly because of malformed email addresses in the
"ault.:ml file0.
< )n 4indows& the third party mail client +such as blat0 is not configured properly.
< The reports destination directory is not
sent or it does not ha"e appropriate permissions.
< The printer is not set up correctly or the printer command in "ault.:ml is incorrect.
Status Code #86
====================
unable to locate "ault directory
! ?ault 'ob or a command for a missing or a corrupt directory of the session in question
returns this error.
Status Code #8-
====================
"ault internal error
This error should ne"er occur.
Status Code #8,
====================
"ault e'ect failed
This error occurs when ?ault fails to e'ect any of the media that was identified for e'ect
during a ?ault Session. ;otential reasons1 Aedia and 9e"ice Aanagement ser"ices are
down& the robot is down& or no empty slots are a"ailable in the media access port
+A!;0.
Status Code #88
====================
"ault e'ect partially succeeded
This error occurs when not all of the media that was identified for e'ect during a ?ault
session can be e'ected. ;otential reasons include the following1
< Some of the media is in use by Net*ackup
< Some of the media are in a dri"e
< Not enough empty slots are a"ailable in the media access port +A!;0
Status Code #8.
====================
cannot consolidate reports of sessions from container and slot-based "aults
This error occurs when you consolidate reports and at least one session uses slots and
another uses containers.
Status Code #.0
====================
one or more errors detected during e'ect processing
This error occurs when more than one error is encountered during an e'ect procedure by
"ltopmenu. !ny Le'ectL errors that range from #. to /00 may ha"e occurred in any of
the sessions being e'ected.
Status Code #.
====================
number of media has e:ceeded capacity of A!;O must perform manual e'ect using
"ltopmenu or "lte'ect
This error occurs in the following situation1 a ?ault 'ob is run for a profile that selected
automatic e'ect mode and the number of media to be e'ected e:ceeds the A!; capacity.
Status Code #.#
====================
e'ect process failed to start
This error occurs when the following cannot start the e'ect process1 the ?ault 'ob& the
"lte'ect command& or the use of the "ltopmenu.
Status Code #./
====================
e'ect process has been aborted
This error occurs when the e'ect process is canceled. This error can be encountered
during a ?ault 'ob or with the "lte'ect or the "ltopmenu e'ect command.This error can
occur because of one of the following conditions1
< Could not open a pipe to "mchange -"erifyCe'ect call.
< 2ne:pected output from "mchange -"erifyCe'ect call.
< No A!; elements e:ist to e'ect media into.
< The robotic library had problems putting media into the A!;.
< The user pressed >eturn in interacti"e mode and did not first remo"e the media from
the A!;. (n this case& the media that were in the A!; are put back into their original
slots in the robotic library.
Status Code #.5
====================
"ault catalog backup failed
9uring a ?ault 'ob& the catalog backup step failed.
Status Code #.6
====================
e'ect process could not obtain information about the robot
This error occurs when the e'ect process cannot collect information about the robotic
library and its associated A!;s and "olumes.
Status Code #.-
====================
process called but nothing to do
This error occurs in the following situations1
< "lte'ect is called with -e'ect but the system has no tapes to e'ect
< "lte'ect is called with -e'ect and the e'ect is already done
< "lte'ect is called with -report and the reports are already done
< "lte'ect is called with -e'ect and -report& and both the e'ect and the reports are done
Status Code #.,
====================
all "olumes are not a"ailable to e'ect
This error occurs when an attempt is made to e'ect a non-e:istent or bad media (9
during the e'ect phase of the following1 a ?ault session& a "lte'ect command& or a
"ltopmenu command.;ossible reasons for this error are as follows1
< The bad media (9 was added by means of the "ltCe'ectlistCnotify script.
< The bad media (9 is already in the A!; or not in the robotic library.
< The bad media (9 is in a robotic dri"e.
< The bad media (9 is in transit in the robotic library.
Status Code #.8
====================
the library is not ready to e'ect "olumes
This error occurs if the robotic library is not in a state to support e'ecting media.
;ossible reasons for this error include the following1
< Currently& the library e'ects media
< The library waits to e'ect media
< Currently& the library in'ects media
< The library waits to in'ect media
Status Code #..
====================
there is no a"ailable A!; for e'ecting
The robotic library you "ault from does not ha"e a A!; a"ailable for use and so media
cannot be e'ected.
Status Code /00
====================
"mchange e'ect "erify not responding
9uring the e'ect process& the "mchange command is called with a L-"erifyCe'ectL call
until all of the "olumes for the request are in the A!;. This command call failed. )r it
did not return the proper information to the ?ault e'ect process.
Status Code /0
====================
"mchange apiCe'ect command failed
9uring the e'ect process& the "mchange command is called with an L-apiCe'ectL call to
begin the process to e'ect media. This command call failed.
Status Code /0#
====================
error encountered attempting backup of catalog +multiple tape catalog backup0
This error occurs when the Net*ackup command that was used for stage one of the two-
stage catalog backup fails.
Status Code /0/
====================
error encountered e:ecuting Aedia Aanager command
This error occurs when a Aedia and 9e"ice Aanagement command fails during a ?ault
'ob.
Status Code /05
====================
specified profile not found
This error occurs when the profile name that is specified on the ?ault command is not
defined in the ?ault configuration.
Status Code /06
====================
multiple profiles e:ist
This error may occur when duplicate profile names are defined in multiple ?ault
configurations and only the profile name is specified on the ?ault command.
Status Code /0-
====================
"ault duplication partially succeeded
This error occurs when all selected images are not duplicated successfully.
Status Code /0,
====================
e'ect process has already been run for the requested ?ault session
This error occurs when "lte'ect is run to e'ect media for a session (9 for which media
has already been e'ected.
Status Code /08
====================
no images duplicated
This error occurs when ?ault failed to duplicate any images.
Status Code /0.
====================
report requested without e'ect being run
This error occurs when a report is run that requires media to ha"e been e'ected first.
Status Code /0
====================
2pdating of Aedia Aanager database failed
This error occurs when ?ault physically e'ects tapes but fails to update the 7AA
database to reflect the e'ect operation. ! typical reason for this failure is that 7AA
detected a mismatch between the media type and its "olume group.
Status Code /
====================
(ron Aountain >eport is already created for this session
This error occurs when an (ron Aountain report has already been generated for the
session.
Status Code /#
====================
in"alid container database entry
Net*ackup ?ault has found an in"alid entry while reading the container database. 7ach
container entry in the container database must follow the e:pected format. The
container database e:ists in file cntr9*& which is located at
=netbackup="ault=sessions=cntr9*.
Status Code //
====================
container does not e:ist in container database
The specified container does not ha"e an entry in the container database. The container
database e:ists in file cntr9*& which is located at =netbackup="ault=sessions=cntr9*.
Status Code /5
====================
container database truncate operation failed
!n error occurs while truncating the container database. This error may occur during the
modification or deletion of an entry from the container database. The container database
e:ists in file cntr9*& which is located at =netbackup="ault=sessions=cntr9*.
Status Code /6
====================
failed appending to container database
This error can occur while appending a container record to the container database. This
error may occur with the addition& modification& or deletion of an entry from the
container database. The container database e:ists in file cntr9*& which is located at
=netbackup="ault=sessions=cntr9*.
Status Code /-
====================
containerCid is not unique in container database
Net*ackup ?ault has found a pre"iously-e:isting entry for this container (9 in the
container database while adding it to the container database. 7ach container record in
the container database must ha"e a unique container (9. Note that the container
database e:ists in file cntr9*& which is located at =netbackup="ault=sessions=cntr9*.
Status Code /,
====================
container database close operation failed
This error occurs while closing the container database. This error may occur during the
reading& addition& modification& or deletion of an entry from the container database.
Note that the container database e:ists in file cntr9*& which is located at
=netbackup="ault=sessions=cntr9*.
Status Code /8
====================
container database lock operation failed
This error occurs while locking the container database. This error may occur during the
addition& modification& or deletion of an entry from the container database. Note that the
container database e:ists in file cntr9*& which is located at
=netbackup="ault=sessions=cntr9*.
Status Code /.
====================
container database open operation failed
This error occurs while opening the container database. This error may occur during the
reading& addition& modification& or deletion of an entry from the container database.
Note that the container database e:ists in file cntr9*& which is located at
=netbackup="ault=sessions=cntr9*.
Status Code /#0
====================
the specified container is not empty
This error occurs if you try to delete a container from the container database& but the
container still holds media. Mou can only delete empty containers.
Status Code /#
====================
container cannot hold any media from the specified robot
This error occurs while trying to place media from an une:pected 7AA database host
into a container. !ll the media that are placed in a container should belong to the same
7AA database host. @or e:ample& you ha"e media from a robot that belongs to one
7AA database host. Then you try to put this media into a container that already holds
media from the robots that belong to a different 7AA database host.
Status Code /##
====================
cannot find "ault in "ault configuration file
Net*ackup ?ault cannot find an entry for the specified ?ault name into the ?ault
configuration file. Note that the ?ault configuration file is located at
=netbackup=db="ault="ault.:ml.
Status Code /#/
====================
cannot find robot in "ault configuration file
Net*ackup ?ault cannot find an entry for the specified robot number in the ?ault
configuration file. Note that the ?ault configuration file is located at
=netbackup=db="ault="ault.:ml.
Status Code /#5
====================
in"alid data found in retention map file for duplication
This error occurs when the retention mapping file +either generic or for a specific "ault0
contains in"alid data. (f the file contains too much or too little data or the user defines
in"alid retention le"els in the file& this error occurs.The retention mapping file is used as
follows1 in a ?ault session when a ?ault profile duplication is configured with the 2se
mappings retention le"el configured for one of the copies for duplication. The product
installs a mapping file template named retentionCmappings in =netbackup=db="ault.To
specify a mappings file for any single "ault& copy the retentionCmappings template to
another file and append the name of the "ault. @or e:ample&
netbackup=db="ault=retentionCmappings.?
Status Code /#6
====================
unable to find policy=schedule for image using retention mapping
This error occurs with duplication of the backup policy or the schedule of an image by
?ault. The 2se mappings option on the 9uplication tab of the ;rofile dialog bo: is
selected& but the policy or the schedule no longer e:ists.
Status Code /#-
====================
specified file contains no "alid entry
The specified file contains no "alid entries for media (9s or the alphanumeric
equi"alent of bar codes. !s per the e:pected format& each line should contain only one
string that represents either a media (9 or the bar code numeric equi"alent.
Status Code /#,
====================
no media e'ected for the specified "ault session
This error occurs while mo"ing media e'ected by the specified ?ault session to a
container. 7ither the specified ?ault session has not e'ected any media& or you specified
an incorrect ?ault name or session (9.
Status Code /#8
====================
in"alid container id
This error occurs while adding a container record to the container database. The
container (9 is found in"alid. Note that the container database e:ists in file cntr9*&
which is located at =netbackup="ault=sessions=cntr9*.
Status Code /#.
====================
in"alid recall status
This error occurs while adding a container record to the container database. The
container recall status is found in"alid. Note that the container database e:ists in file
cntr9*& which is located at =netbackup="ault=sessions=cntr9*.
Status Code //0
====================
in"alid database host
This error occurs while adding a container record to the container database. The 7AA
database host name is found in"alid. Note that the container database e:ists in file
cntr9*& which is located at =netbackup="ault=sessions=cntr9*.
Status Code //
====================
in"alid container description
This error occurs while adding a container record to the container database. The
container description is found in"alid. Note that the container database e:ists in file
cntr9*& which is located at =netbackup="ault=sessions=cntr9*.
Status Code //#
====================
error getting information from 7AA database
This error can occur while the backup process communicates with the 7AA database to
retrie"e some information.
Status Code ///
====================
error getting information from media manager command line
This error occurs when ?ault cannot retrie"e robot information such as map
information& "olume information& library status& and so on. (t is an internal error.
Status Code //5
====================
unable to recei"e response from robotO robot not ready
This error occurs when a problem e:ists with the robot.
Status Code //6
====================
failure occurred while suspending media for e'ect
This error occurs when ?ault cannot suspend the media. (t is an internal error.
Status Code //-
====================
failure occurred while updating session information
?ault cannot update the session files. (t is an internal error.
Status Code //,
====================
failure occurred while updating the e'ect.mstr file
?ault cannot update the e'ect list file. (t is an internal error.
Status Code //8
====================
"ault e'ect timed out
This error occurs when a problem e:ists with the robot.
Status Code //.
====================
"ault configuration file format error
The ?ault configuration file is malformed. 2nless the file has been manually modified&
this is an internal error. Note that the ?ault configuration file is located at
installCpath=netbackup=db="ault="ault.:ml.
Status Code /50
====================
"ault configuration tag not found
!n optional attribute may be missing in the ?ault configuration file. This internal error
generally does not cause problems in ?aultDs functioning. Note that the ?ault
configuration file is located at installCpath=netbackup=db="ault="ault.:ml.
Status Code /5
====================
"ault configuration serialiEation failed
?ault failed to write out the ?ault configuration file. (t is an internal error. Note that the
?ault configuration file is located at installCpath=netbackup=db="ault="ault.:ml.
Status Code /5#
====================
cannot modify - stale "iew
This error can occur if an administration interface +Net*ackup !dministration Console
or ?ault !dministration menu user interface0 tries to modify the following1
< ! robot or "ault or profile in between the read
< )perations of the same robot or "ault
< ;rofile by another instance of an administration interface
Status Code /5/
====================
robot already e:ists
This error can occur during addition of a robot while a robot with the same name
already e:ists.
Status Code /55
====================
"ault already e:ists
This error can occur during addition of a "ault if a "ault with the same name already
e:ists in the same robot.
Status Code /56
====================
profile already e:ists
This error can occur during addition of a profile if a profile with the same name already
e:ists within the same "ault.
Status Code /5-
====================
duplicate A!;
! duplicate A!; was added in the ?ault configuration file. (t is an internal error.
Status Code /5,
====================
"ault configuration cache not initialiEed
This error should ne"er occur.
Status Code /58
====================
specified report does not e:ist
!n in"alid ?ault report was requested for generation. (t is an internal error.
Status Code /5.
====================
incorrect catalog backup policy
This error can occur when a ?ault session tries to run a catalog backup. The specified
policy for the catalog backup in the ?ault profile is either blank or is not of type N*2-
Catalog.
Status Code /60
====================
incorrect "ault catalog backup schedule
This error can occur when a ?ault session tries to run a catalog backup. The specified
?ault catalog backup schedule for catalog backup in the ?ault profile is either blank or
is not of type ?ault Catalog *ackup.
Status Code /6
====================
all configured "ault steps failed
This error occurs when multiple ?ault steps are configured for a session and all of them
fail.