cancel
Showing results for 
Search instead for 
Did you mean: 

Cool link for news one netbackup

Omar_Villa
Level 6
Employee
I think this can go to anyone favorites:
 
 
 
Enjoy.
5 REPLIES 5

Stumpr2
Level 6
too slow...
 
I prefer to use commandline
 
#  bperror -r -statuscode 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 Advanced Client (see recommended actions).
Try the following:
1.  Check the NetBackup Problems report for clues on where and why the problem occurred.
2.  For a FlashBackup client, check the /var/adm/messages log for errors like the 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, increase the size of the cache partition. Or, if multiple backups are using the same 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 active.
3.  For detailed troubleshooting information, create a debug log directory for the process that returned this status code, retry the operation, and check the resulting debug log.
4.  For NetBackup Advanced Client only:
   Status code 13 may appear in the /usr/openv/netbackup/logs/bpbkar log, and can indicate the following:
   *  The files to back up reside on an IDE drive as opposed to SCSI, and the offhost 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 must 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 system specified as the snapshot source must be mounted. If the snapshot source is not mounted but the mount point is present, NetBackup may try to take a snapshot of the directory above the directory that was specified as the snapshot source.

Nathan_Kippen
Level 6
Certified
or even shorter ..
 
bperror -r -S #
 
 

J_H_Is_gone
Level 6
Well I like it because it links to the troubleshooting database for hints.

Stumpr2
Level 6
I go directly to the search engine several times in a day and I have it as a link on my IE
 
 

Roobix_Cube
Level 5
Interesting link, but I find a well crafted Google search gets me what I'm after....