Which log has information of drive being downed

[Junaid_Mohammad]

Can you tell me which log will have information when a tape drive is down'ed. I thought it was bptm or db/error/daily.log log.

I have written a script to send a email out each morning to tell us the status of the drives (using the vmoprcmd command), but I want to improve the script, so it will notify us when the drive goes down. Any ideas??

Thanks

Junaid

[zippy]

Junaid,

You can run this script or turn the logs on.
######## cut here ###############
#!/bin/sh
#created by jim dunn
# Aug 6 2000
#Used to force a Downed drive backup or
#used to check for down tape drives
#uncomment what you need today
##############################
set -vx
alias openfile=exec
alias closefile=exec
DRVL=/tmp/TD

if /usr/openv/volmgr/bin/tpconfig -d | grep DOWN
then
/usr/bin/touch /tmp/TD
#echo "!! MASTER_HOST_NAME has a downed tapedrive !! `date`" | mail tapedrive
fi
/usr/openv/volmgr/bin/vmoprcmd | grep DOWN-TLD | awk '{print $1}'> /tmp/TD
openfile 5<$DRVL
while read -u5 -r DRIVELIST
do
#/usr/openv/volmgr/bin/vmoprcmd -up $DRIVELIST
done
closefile 5<&-
####### cut here ###################

/usr/openv/netbackup/logs

The README file states....................

* $Id: README.debug,v 1.6.4.1 2004/03/15 15:42:46 $
***************************************************************************
* $VRTScprght: Copyright 1993 - 2004 VERITAS Software Corporation, All Rights Reserved $ *
***************************************************************************

This directory (/usr/openv/netbackup/logs) contains the user_ops
sub-directory and, optionally, sub-directories where detailed debug logs
will be created.

The directory /usr/openv/logs contains the sub-directories where the
detailed debug logs for the vnetd and vopied daemons will be created.
You will need to create the /usr/openv/logs directory if it does not
exist and you want debug logs for vnetd or vopied.

The user_ops sub-directory is created during the install of NetBackup on
all servers and clients. It is used by the NetBackup - Java GUI applications
for placement of job and progress log files generated by the end-user client
application (jbp) and temporary files generated while using these
applications. This directory must exist for successful operation of any
of these GUI applications and must have public read, write and execute
permissions. One sub-directory in logs/user_ops will exist for every user
that is using these GUI applications. The pruning of files in this
sub-directory is done per the semantics of the KEEP_LOGS_DAYS
bp.conf option - default is 3 days.

All other sub-directories in /usr/openv/netbackup/logs are optional and
should only be created if unexplained problems are occurring with the
NetBackup product and more information is required to isolate the problem.

Miscellaneous notes about these optional NetBackup logs contained in this
directory:
-each NetBackup process has its own debug log directory
-one debug log file is created per process per day. The file names
created are of the form:
log. (e.g., log.110891)
-debug logging is only in affect for a process if that process's
debug log directory is defined.
-The log files in these directories are automatically deleted by
the NetBackup request daemon, bprd. The administrative parameter
"keep logs x days" determines how long the log files exist.
-volume of debug logging can be increased by enabling "verbose"
mode by defining the string "VERBOSE" in the /usr/openv/netbackup/bp.conf
file.
WARNING: Some of these logs can potentially grow very large, and should
only be enabled if unexplained problems exist.

The following directories can be individually created on the server, to cause
the corresponding NetBackup server process to log information:

/usr/openv/netbackup/logs/admin
/usr/openv/netbackup/logs/bpbrm
/usr/openv/netbackup/logs/bpbrmds
/usr/openv/netbackup/logs/bpcd
/usr/openv/netbackup/logs/bpcoord
/usr/openv/netbackup/logs/bpdbm
/usr/openv/netbackup/logs/bpdm
/usr/openv/netbackup/logs/bpjava-msvc
/usr/openv/netbackup/logs/bpjava-susvc
/usr/openv/netbackup/logs/bpjobd
/usr/openv/netbackup/logs/bprd
/usr/openv/netbackup/logs/bpsched
/usr/openv/netbackup/logs/bpsynth
/usr/openv/netbackup/logs/bptm
/usr/openv/netbackup/logs/symlogs
/usr/openv/logs/vnetd
/usr/openv/logs/vopied

In order for non-root administrators to be able to write to the log files,
the "admin" directory should be created with access modes of 777.

The following directories can be individually created on the client, to cause
the corresponding NetBackup client process to log information:

/usr/openv/netbackup/logs/bp
/usr/openv/netbackup/logs/bparchive
/usr/openv/netbackup/logs/bpbackup
/usr/openv/netbackup/logs/bpbkar
/usr/openv/netbackup/logs/bpcd
/usr/openv/netbackup/logs/bpdbsbora
/usr/openv/netbackup/logs/bpfilter
/usr/openv/netbackup/logs/bpjava-msvc
/usr/openv/netbackup/logs/bpjava-usvc
/usr/openv/netbackup/logs/bpkeyutil
/usr/openv/netbackup/logs/bplist
/usr/openv/netbackup/logs/bpnbat
/usr/openv/netbackup/logs/bporaexp
/usr/openv/netbackup/logs/bporaexp64
/usr/openv/netbackup/logs/bporaimp
/usr/openv/netbackup/logs/bporaimp64
/usr/openv/netbackup/logs/bprestore
/usr/openv/netbackup/logs/bphdb
/usr/openv/netbackup/logs/dbclient
/usr/openv/netbackup/logs/symlogs
/usr/openv/netbackup/logs/tar
/usr/openv/logs/vnetd

In order for users on the client to be able to write to the log files, the
directories should be created with access modes of 777.

Here are descriptions of NetBackup processes:

bprd
-request daemon
-can be terminated and initiated from the admin interfaces
-responds to client and administrative requests
-restores
-backups
-archives
-"list files backed-up or archived"
-manual/immediate backups
-reread configuration database
bpsched
-backup scheduler
-started by bprd on user directed backups and archives
-started by bprd on immediate/manual backups
-started by bprd every "Wakeup Interval" for regularly
scheduled incremental and full backups
-uses information from the policy & storage unit databases to
determine what clients to start, when to start them, and
what storage unit to write backups/archives to
bpdm
-disk manager
-used on storage units of type Disk
-started by bpbrm on backups and restores
-during backups and restores, one of these is started (on the
server with the storage unit) for each client backup or restore
bptm
-removable media (tape) manager
-used on storage units of type Logical Tape
-started by bpbrm on backups and restores
-during backups and restores, one of these is started (on the
server with the storage unit) for each client backup or restore
-also responsible for managing the media database
-used to display info in the Media Reports screen when you
select Media List
bpbrm
-backup/restore manager
-started by bpsched on backups/archives
-started by bprd on restores
-during backups and restores, one of these is started (on the
server with the storage unit) for each client backup or restore
-responsible for managing both the client and the media manager
processes. uses error status from both to determine ultimate
status of backup or restore.
bpbrmds
-backup/restore manager for Disk Staging duplications
-started by bpsched when handling a Disk Staging schedule
-responsible for starting, and managing, a bpduplicate process.
bpdbm
-database manager
-manages policy, config/behavior, storage unit, and error DB's
bpjobd
-job manager
-manages backup and restore jobs for the activitiy monitor GUIs
bpsynth
-NetBackup synthetic backup manager
-started by bpsched on synthetic backups
-runs on master server and manages the creation of a
synthetic image.
bpcoord
-NetBackup synthetic backup read coordinator
-started by bpsynth for synthetic backups
-runs on master server and coordinates reading required
blocks from existing images.
bpcd
-"client daemon"
-used on clients (and remote servers) to initiate other product
programs, without requiring /.rhosts entries for the server
on each client
-started by the inetd(1M) process
bpjava-msvc
-NetBackup-Java application server authentication service program
-started by inetd during startup of the NetBackup-Java GUI applications
-authenticates the user that started the NetBackup-Java GUI application
bpjava-susvc
-NetBackup-Java application server user service program on NetBackup
servers
-started by bpjava-msvc upon successful login via the NetBackup-Java
GUI applications login dialog window
-services all requests from the NetBackup-Java GUI applications
for administration and end-user operations on the host on which the
NetBackup-Java application server is running
-additional bpjava-susvc processes get started to respond to requests
from the NetBackup-Java GUI applications
bpjava-usvc
-NetBackup-Java application server user service program on NetBackup
clients
-started by bpjava-msvc upon successful login via the NetBackup-Java
GUI applications login dialog window
-services all requests from the NetBackup-Java GUI applications
for administration and end-user operations on the host on which the
NetBackup-Java application server is running
-additional bpjava-usvc processes get started to respond to requests
from the NetBackup-Java GUI applications
bpdbjobs
-command-line activity monitor for backup and restore jobs
bparchive
-command-line program on clients to initiate archives
-communicates with bprd on server
bpbackup
-command-line program on clients to initiate backups
-communicates with bprd on server
bpbkar
-program used on standard clients to generate backup images
-not used directly by client users
bplist
-command-line program on clients to initiate file lists
-communicates with bprd on server
bprestore
-command-line program on clients to initiate restores
-communicates with bprd on server
bpnbat
-command-line program to manage NetBackup Access Control
authentication
bphdb
-program used to start obackup to do Oracle database backups
dbclient
-log for the DB Extension clients
tar
-program used on standard clients to restore backup images
wbak
-program used on Apollo clients to generate backup images
rbak
-program used on Apollo clients to restore backup images
bp
-menu user interface for backups, archives, and restores
xbp
-X/Motif user interface for backups, archives, and restores
bpadm
-menu user interface for administrative tasks
bpdbsbora
-command-line program used to initiate template based
user-directed backup and recovery
-enables generation of a shell script from a template
bporaexp
-command-line program on clients to export Oracle
data in XML format
-communicates with bprd on server
bporaexp64
-64-bit command-line program on clients to export Oracle
data in XML format
-communicates with bprd on server
bporaimp
-command-line program on clients to import Oracle
data in XML format
-communicates with bprd on server
bporaimp64
-64-bit command-line program on clients to import Oracle
data in XML format
-communicates with bprd on server
bpfilter
-client program used to filter backup images between the media
server and bpbkar or tar on the client
bpkeyutil
-command-line program to manage Encryption key files
vnetd
-VERITAS Network Daemon
-Used to create "firewall friendly" socket connections
-started by the inetd(1M) process
vopied
-VERITAS OPIE authentication Daemon
-Used by servers to authenticate non-root users via
VOPIE authentication
-started by the inetd(1M) process

JD

[Ankur_Kumar]

Hi Junaiid,
The bptm log should represent the data on the drive status. Do have the verbosity set to 5 for the detail output.


Chiao Come va
Ankur Kumar

[AKopel]

And if you are using windows. it's very similar:
I prefer the -l switch as it gives you the names of the drives to parse out
tpconfig -l | qgrep drive (qgrep is included in the W2K3 Resource Kit)

[zippy]

Ankur,

Lets try to make him think a bit...



JD

[Junaid_Mohammad]

Verbose for bptm is set to 5, i am finding that i am only getting the following output, when a tape drive is downed by NBU. - These are NDMP drives, so that could be the reason. We don't really get than many DOWN drives on are sso drives.

cat log.061206 | grep -i DOWN

11:37:26.306 <8> write_backup: media id 601337 is unavailable (in a DOWN drive, misplaced, or not available for another reason), attempting retry with a different media id
11:37:32.571 <2> set_job_details: LOG 1150108652 8 bptm 23600 media id 601095 is unavailable (in a DOWN drive, misplaced, or not available for another reason), attempting retry with a different media id

[Nathan_Kippen]

I probably don't know what I'm talking about but have you checked the device paths?


ioscan -nfC tape

I guess I ran into this problem the other day.. think its only good for fibre though.


What was happening to me is the drive would take a tape and then netbackup would report the tape couldn't be found and down the drive... the problem was that the write path to the device was missing.

nk

[Junaid_Mohammad]

I have used the /var/adm/messages log to grep the following syntax

"is being DOWNED"

[Stumpr2]

I edited my netbackup startfile by changing ltid to start in verbose mode by adding a -v

$LTID -v

[zippy]

Jun

yes this is the Servers log messages, use the netbackup logs.

JD