Ysbrand:

We use a 3rd party product ITO to monitor system events such as a full file 
system.

As far as the daemons go, you can schedule jobs to perform bpps -a and grep for 
processes.

We also schedule a backup to a disk storage unit on the master (just backs up a 
small file) that runs every 10 minutes through cron. We monitor this job (what 
we call a "schedule_check") via another script. If it doesn't complete every 
1/2 hour or so, alerts get sent that the job has not run and something may be 
hung.

Charlie Somogyi
BMS
Princeton, NJ





Message: 1
Date: 13 Jun 2001 19:01:56 MET DST
From: ysbrand bergman <ysbrand AT usa DOT net>
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Netbackup prventive maintanance, anyone??

Hi,

Just wondering, is anybody doing some preventive maintenance, or let say,
preventive monitoring of their Netbackup environment? If so, what are you
doing.

Explanation,
We all are checking if our backups jobs have been running on a regular basis,
but I see this as a kind of after the fact thing. What I'm really looking for
is how can I make sure that everything is in shape to run  my backups
properly.

Things I've been thinking about are:
- Are my daemons running on all servers
- Can I contact my clients over the network
- Netbackup catalog checks
- Filespace monitoring for the filesystem that Netbackup is using for
catalogues etc.

Any ideas?

Ysbrand