No, I used that as an example because that's how I found it.

The way to get around it is to run the report a day later.  If it's crucial
to have the report ASAP then you could run one report to give the data you
need at that moment and then another report to update that data later.

Example time
Window: 00:00 01/01/2004 -> 23:59 01/01/2004  
 => Run report at 08:00 01/02/2004 (next day) this will miss any backups
running during 01/01/2004 through 8am (a 12 hour backups starting at 11pm
for instance)
 => Run report at 08:00 01/03/2004 (two days after).  This should get all
the images but comes a bit late - I'd use this to update the report from the
2nd.

So, each day you'd run two reports.  One for the previous day (with possible
exclusions) and then an updated report for two days prior.

- Cuyler


-----Original Message-----
From: Jason Helfman [mailto:jason.helfman AT ticketmaster DOT com] 
Sent: March 16, 2004 5:27 PM
To: Dingwell, Cuyler
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] bpimagelist command help, discrepency?


Do you think using the "-hoursago 24" flag would make any difference in 
this case?

Dingwell, Cuyler wrote:
> Good day,
> 
>   I noticed this as well when creating reports to count the amount of 
> data backed up.  Netbackup records the start of the back as the image 
> file create time however it doesn't show up until after the backup is 
> finished.  This causes a backup that run while the report is running 
> to not show up.
> 
> For instance, if I run a report for all the images in the past 24 
> hours at 8am on day1 and a backup that day runs from 6am to 10am that 
> day then on the report will not show that backup (since the image 
> isn't in the database until 10am).  When I run the report the next day 
> at 8am the backup from day1 doesn't show up since the image is from 
> 6am (26 hours ago).
> 
> Hope this helps - it was a headache for me.
> 
> - Cuyler
> 
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Jason 
> Helfman
> Sent: March 16, 2004 4:08 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] bpimagelist command help, discrepency?
> 
> 
> Hello,
> 
> This is the first time I am writing to the list. I am utterly confused
> why some images are getting picked up by this script I wrote, and some 
> simply are not. This is a script that basically dumps the output of the 
> previous day to a dump file and then inserts it into our own historical 
> database. I am running into issues with the right information being 
> outputted, though.
> 
> #!/bin/bash
> MYDATE=`/usr/local/bin/date --date '1 day ago' +%m/%d/%y` 
> MYDATE1=`/usr/local/bin/date --date '1 day ago' +%m%d%Y` 
> /opt/openv/netbackup/bin/admincmd/bpimagelist -A -d $MYDATE 00:00:01 
> -e $MYDATE 23:59:59 > /path/imglist-$MYDATE1.dmp
> 
> When echoing the actual command that is run, I get the following 
> output: /opt/openv/netbackup/bin/admincmd/bpimagelist -A -d 03/15/04 
> 00:00:01 -e 03/15/04 23:59:59 > /path/imglist-03152004.dmp
> 
> This is run from cron nightly at 12:05 am:
> 5 0 * * * /img_rpt.sh > /dev/null 2>&1
> 
> The problem is that if jobs are running over midnight, for some reason
> the jobs aren't being picked up in the dump that I am running.
> 
> Here is an output from the imagedb on Veritas:
> [root@lax1bkm1 bin]# bpimagelist -d 02/01/04 -st FULL -policy ads_backup
-U
> Backed Up         Expires       Files       KB  C  Sched Type   Policy
> ----------------  ---------- -------- --------  -  ------------
------------
> 03/11/2004 21:03  04/11/2004   533432 193913000  N  Full Backup
ads_backup
> 03/04/2004 21:00  04/04/2004   535866 152247698  N  Full Backup
ads_backup
> 02/26/2004 07:00  03/28/2004   532958 113190277  N  Full Backup
ads_backup
> 02/19/2004 07:06  03/21/2004   532160 72436731  N  Full Backup  ads_backup
> 
> Here is our db that inserts based off of the data dump that is 
> performed
> nightly on the script I am trying to figure out:
> 
> ./nb.pl |grep ads_backup |grep Full
> ads ads_backup 2004-02-12 07:06:11 05:14:44 155394658 Full ads 
> ads_backup 2004-02-19 07:06:17 03:02:58 72436731 Full ads ads_backup 
> 2004-02-26 07:00:34 04:05:45 113190277 Full
> 
> As you can see, any Full backup in the month of March doesn't show up,
> however it is in the database of Veritas. The diffs have no issues in 
> getting into the our database.
> 
> I am wondering how the dump script I am running is any different then
> what I would run on the commmandline? I can run the command on 
> commandline or just execute the script and I get the expected results 
> that we should be getting, but when running it from cron at that time, 
> seems to be giving us different results. But what I don't get is, that 
> even if we don't get the image entry for today, it should be picked up 
> by the next days dump.
> 
> I see the -hoursago option is available in bpimagelist. I am going to
> try this tonight, but I don't see how it would be any different.
> 
> The Full for this schedule runs from 21:00:00 to 05:00:00, and the 
> Diffs
> run on the other days.
> 
> I would appreciate any insight into this.
> 
> Thanks,
> Jason Helfman
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
Jason G Helfman, Ticketmaster
8800 W. Sunset Blvd.
West Hollywood, CA 90069
213/739-5174 Direct
310/345-1554 Cell
310/360-3300 Main
jason.helfman AT ticketmaster DOT com
GnuPG Fingerprint: A349 3CAA 5085 DC6E C485  7356 13C3 5772 F865 C926