WOW!  That's as bad as things get!  Have you looked at the index files 
generated by some of the OTM-based backups?  (I mean manually looking at 
them on the command line with vi or some such utility.)  Look at 
/usr/openv/netbackup/db/images/client.

At 12:37 PM 7/10/2001 -0400, Thelen, Robert (FUSA) wrote:
>We are have recently encountered an issue that appears to involve OTM on
>Windows NT and Windows 2000 servers.  For months we have been running
>backups on roughly 135 NT and 2000 servers and most of them have reported a
>backup status of 0.  We were recently asked by a user to restore some lost
>data.  When going into xbp and later bp to select the missing files, we
>noticed that all that was backed up on the D drive was the identifier /D/
>(Unix Master).  Under the identified /C/, we were able to find all of the C
>drive files, but nothing on the D drive was backed up.
>
>The backup successfully completed, though!  Veritas has been looking into
>this issue for us (Case 150-081-114), but they have been unable to find
>anything as of yet.
>
>I disabled OTM and ran an incremental last night and the backup completed
>successfully.  I was expecting to find that all of the files on the D drive
>were backed up - the files were never backed up, so an incremental would
>pick them up.  Instead, the files that were backed up were the files that
>changed since the last backup.   It is as if NBU really thought that the
>files were backed up.

---
W. Curtis Preston
Principal Consultant for Storage Designs, your storage experts
Webmaster: http://www.backupcentral.com Phone: 760 710 7017