[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

701.0. "I/O error and scheduled backup" by EVTAI1::POUSSARD () Thu May 22 1997 04:23

	Hi,


	I would know the behavior of NetWorker ( alias NSR ), when there is
an I/O error on the tape. I know that it declares the tape full, but doesn't 
seem to continue scheduled backups.


	I think this subject was already developped but I don't find really a 
clear explanation through the notes.



	My customer had an I/O error on a tape, during a scheduled backup, and 
all sessions were blocked on both TZ877. We could think that NSR tags the tape
full and asks for another tape in the pool, allowing scheduled backup to
continue, but it seems not to be the case.

	Is it a normal behavior from NSR ?????


	My other question is:


	How can I configure the notification ressource, to trigger something
in case of an I/O error ??

	I mean, in the NSR ressource:

		- what do I put in the notification field ?
		- in the event field ?
		- in the Priority field ?

	Is there some examples or experiences about that ??



		Thanks 



				Gilles. 
T.RTitleUserPersonal
Name
DateLines
701.1DECWET::RWALKERRoger Walker - Media ChangersThu May 22 1997 09:0221
	For us to help we would need to know a lot more about why
	the backups did not continue.  Some changes have been made
	in this area to prevent the software from retrying all night
	and generating thousands of mail messages.

	What versions of NetWorker and O/S are in use?

	What state is the system in when it stops? 

	Are there any more tapes in the loader labeled and ready
	to use?

	Is the tape drive listed as "disabled"?

	Normally NetWorker will try to continue with another tape
	but this is not a common occurance and you may have found
	a combination of events that needs our attention.

	The "Critical" level of waiting for a backup tape should
	provide a good event to watch for this and other problems
	that would pervent the backups from finishing.
701.2montlake.zso.dec.com::lenoxthis note posted from NetNotesThu May 22 1997 09:155
The last time I had an error when writing to a tape, 
which was last week, it took about an hour for NetWorker
and the tape drive to get to the point where it switched to
using a new tape.
701.3EVTAI1::POUSSARDFri May 23 1997 07:273
    	I just discovered that it' is an AIX Networker server