I guess that the reason here is that your phusycall device that does the backups is not avaiable - backup-hcart2. Was this already working and stopped. is backup-hcart2 a robot? if so restart the library of the robot (by browser). Also check if you are choosing the correct backup device. Going to the policy and choosing "any avaiable" is one good option. Also restarting bprd (resource deamon) deamon and putting verbose=5 on the deamon is a good option (verbose will give you detailed logs.
keep me posted.
Main Topics
Browse All Topics





by: rbarnhardtPosted on 2009-01-08 at 08:02:09ID: 23326303
You could try to reinstall the remote agent if these errors occure on a single client, which looks like that is the case.
nffile.
s (Windows). the client. Reinstall them if they are not the same as in the client directory under /usr/openv/netbackup/clien ton the server. Run the NetBackup Configuration Validation Utility (NCVU) for the associated NetBackup clients. Note the client software checks in section folder on the client. Reinstall the client if these files are as follows:
One of your status codes is 50. Below is a series of things to try to troubleshoot this problem:
1 Enable detailed debug logging:
Create a bpbkar debug log directory (UNIX or Windows only).
On UNIX: enable debug logging to the system logs by including the verbose option (-v) on the
command that you use to start a daemon. This command can be:
The ltidcommand that started the device management processes. If the -v option is included
on the ltid command, all daemons that were started as a result also have the -v option in
effect.
A command to start a specific daemon (for example, acsd -v).
Create a bpcddebug log directory (this log is created automatically on Macintosh clients.)
On UNIX clients, add the VERBOSEoption to the /usr/openv/netbackup/bp.co
On PC clients, increase the debug or log level as explained in the debug log topics in Chapter 3.
2 Retry the operation and examine the resulting logs.
3 This error may occur if nbjm terminated while a backup job was running. Examine the unified logging files on the NetBackup server for nbjm (117) for more detail on the error. All unified logging is written to /usr/openv/logs(UNIX) or install_path\NetBackup\log
4 On UNIX clients, check for core files in the / directory.
5 On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems.
6 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, which are located in /usr/openv/netbackup/binon
two.On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32.exe files, which are located in the install_path\NetBackup\bin
Not the same size as on other Windows clients
Not at the same release level
Do not have the same NetBackup patches as other Windows clients