Veritas-bu

[Veritas-bu] OTM Enabled Backups Failing with 0

2001-07-12 10:36:32
Subject: [Veritas-bu] OTM Enabled Backups Failing with 0
From: RobertThelen AT FirstUSA DOT com (Thelen, Robert (FUSA))
Date: Thu, 12 Jul 2001 10:36:32 -0400
I have some more answers to questions that have been asked so far.

After some investigation, we have discovered at least 5 Windows NT servers
that are doing very similar things (not backing up all drives) and about 20
Windows 2000 servers that are missing System_State "drives" on the backups.

Penelope -
We created a test class that used /C/ nad /D/ instead of ALL_LOCAL_DRIVES
and the backup worked perfectly fine.

Ken -
The data does physically exist on this server.  It is not a CIFS share or
virtual filesystem.

Rob / Veritas -
We do not have CA Unicenter installed.  However, we do have Tiviloi
Framework installed, if this matters.

Rob Thelen
Storage Management
First USA 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

<Prev in Thread] Current Thread [Next in Thread>