Veritas-bu

[Veritas-bu] Q re NBU write errors and restarts

2002-10-28 15:26:32
Subject: [Veritas-bu] Q re NBU write errors and restarts
From: Jeffrey_Dykzeul AT raytheon DOT com (Jeffrey Dykzeul)
Date: Mon, 28 Oct 2002 12:26:32 -0800
NBU 3.2 running on Solaris 2.5.1


We experienced some tape drive write errors (exit code 84) during backups
over the weekend. I have some questions about how NBU handled this.

If I use the job monitor GUI to look at the full report for a backup job
which finishes normally, the last two lines in the status pane are

      dd/mm/yy hh:mm:ss - end writing; write time: hhh:mm:ss
      (0) the requested operation was successfully completed

In the full report for each of the jobs that experienced write errors, the
last two lines are

      10/26/02 12:32:41 - end writing; write time: 004:27:46
      (196) client backup was not attempted because backup window closed

The "end writing" message suggests to me that the backup data had completed
its writing to tape, even though there is no "successfully completed"
message. Would it be incorrect to interpret it that way?  There are no
references to write errors in this pane, but if I look in the "all log
entries" report for this time period, there are write errors starting at
12:32:45, immediately after the "end writing" timestamp, one for each of
the backup jobs which were running at that time. Immediately after the
write error messages in the "all log entries" report, there are messages
indicating that client backups were not attempted because the backup window
had closed. Again, there is one such message for each of the backup jobs
which had been running. It looks like NBU tried to restart each job,
perhaps in response to the write errors.

 Is it normal behavior for jobs to restart after failures such as write
errors? Is this configurable somewhere?


Jeff Dykzeul
Raytheon



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