This exactly what happened before I switched on persistent binding, and
also have each storage node "see" only the drive it's supposed to write
to. Then things went well.
 
Also wouldn't the rewind happen much faster when backing up to disk?
Then while one node is writing to a tape another, also writing to the
same tape, sends a bus reset. The first node is not aware of this reset
and then just carries on writing.
 
Am I correct in understanding it this way?

>>> howard.martin AT EDS DOT COM 2006/11/02 05:55 PM >>>
On Wed, 1 Nov 2006 15:57:14 +0200, Dag Nygren <dag AT NEWTECH DOT FI> wrote:

>>> I believe that drives with a tape mounted but not being written to
when
>a
>>> bus reset occurs will show an error with scanner along the lines
of
>>> expected file number X got file number X+N.
>
>And here the reset will have no effect other than perhaps generating
an 
error
>message about an unexpected filenumber in the log. The data will still
be
>intact.
>
>The dangers of top-posting....
>
>Best
>Dag
>
But the reset will rewind the tape and networker will not know it, I 
thought that although it might check the media label it still assumes
it 
was where it last wrote to the tape and would therefore overwrite the 
previous backups. This is the behaviour I believe I have seen with 
networker 6.1.4.

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER















Medihelp is an Authorised Financial Services Provider
---------------------------------------------------------------------------
NOTICE: Please note that this eMail, and the contents thereof,
is subject to the standard Medihelp eMail disclaimer which may be found at:
http://www.medihelp.co.za/disclaimer.htm
<<<< GWAVASIG >>>>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER