There is a debug file you can use.
– Use at own risk – will eat up disk space -
(example for unix)
In /usr/openv/netbackup/db/images/<servername>
Touch debug_file_history
Then after
the job runs go into
/usr/openv/netbackup/db/images/<servername>/<##########>
(something like 1281000000)
In here
you will find a file for each job that ran after the file was touched.
AIX_233_1281423259_FULL_debug_dump.f
(in this case the policy is AIX_233 and it was a full backup.)
This file
will list all the files backed up.
I have used
this to test some of the issues that support has posted, like weather it does
or does not back up some type of file, pr to see if my exclude/include list
works as expected.
When done –
remove the touch file you created and it won’t make the list any more.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
Sent: Monday, August 16, 2010 4:23 PM
To: Nate Sanders
Cc: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] watching a running job
On Mon, Aug 16, 2010 at 4:17 PM, Nate Sanders <sandersn AT dmotorworks DOT com> wrote:
Is it possible to watch a running job and find out what
files it is
backing up? I'm under suspicion that some of our policies are not
adhering to ALL_LOCAL_DRIVES or exclude files. I just found a job that's
running 5+ hours and in the status window shows me a Warning about a NFS
path. Those shouldn't be backed up by ALL_LOCAL_DRIVES, right?
There's an option in the policy as to whether or not to follow NFS
mounts. Do a quick check on the policy:
[root@osiris ~]# bppllist 00TEMPLATE-UNIX -U | grep NFS
Follow NFS Mounts: no
If you've got a previous run, have a look at the STREAMS file (in
/usr/openv/netbackup/db/images/<client>/STREAMS* and you can quickly tell
what mount points have been backed up. Of course, you can do a bplist
too.
.../Ed
