I'll do my best to answer the few questions that have been asked so far.

Evan -
My exclude lists are empty.

Penelope -
I am currently using ALL_LOCAL_DRIVES.  I need to to break this server out
into it's own class and then I will try the backups again using C: and D:.

Curtis -
I looked through several index files and all I see is the identifier for /D/
with nothing under it.  Here is an example of the end of the file:

11479 1799 25 50 2192241 1 0 0 -1 /C/WINNT/Web/zdnet_wl.gif 33216 root root
1683 938195242 933009168 933009168
11480 272 3 47 2192249 1 0 0 -1 /D/ 16832 root root 0 989114117 989114117
989114117
<EOF>

Brian -
The NT system that I am looking at does not have drive compression turned
on.  As a rule, none of the servers in the organization should have drive
compression turned on.


Thank you all for your input.  Hopefully, we will get some answers.

RobertThelen AT FirstUSA DOT com
Storage Management
FirstUSA Bank

-----Original Message-----
From: Thelen, Robert (FUSA) [mailto:RobertThelen AT firstusa DOT com]
Sent: Tuesday, July 10, 2001 11:38 AM
To: 'Veritas-bu (E-mail)'
Subject: [Veritas-bu] OTM Enabled Backups Failing with 0


Greetings all.

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.

Has anyone else seen this problem before?

RobertThelen AT FirstUSA DOT com
Storage Management
FirstUSA Bank

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu