Richard,

Does the test cell's tape drive have the same device name
as your production cell's tape drive?  That's the only gotcha
I can think of.


------------------------------------------------------------------------
Bill Pitre      Battelle PNNL, Box 999  M/S K1-87, Richland WA 99352
[EMAIL PROTECTED]        Phone: 509-375-2091       FAX: 509-375-6631
------------------------------------------------------------------------
      "We all need to be salvaged every once in a while."
                   -Troy Thompson (Battelle PNL)


On Fri, 19 Jul 1996 10:19:24 -0400  Richard J Bouchard wrote:
--------
> 
>     Hi
> 
>   I have a question about a Exabyte-10e tape stacker unit
> 
>  I have one installed in a cell on a machine that is running
>  AFS3.3B with AFS3.4 Beta running the Buserver, and BUTC and BACKUP
>  commands.  I have an automated environment which uses these stacker
>  for AFS backup (This was setup between TRANSARC and Peter Chan).
>   I have built a test cell, to which I FTP'd all the binary, configuration
>  and AFS libraries from the existing working cell.  When I try to run
>  backup in this environment I receive the errors
>      Can't open tape
>           butm: can't open tape: Device not ready
>  but the dump continues and seems to work fine.  I have upgraded the
>  buserver, BUTC and BACKUP on the test cell to AFS 3.4  5  and I still
>  receive the same error.  The stacker has the exact same settings as on 
> the
>  production cell.  The production box is a 7011-250 and the test cell is
>  a 7009-C10.  Can anyone give me some ideas on what I've not set-up 
>  correctly that would get these errors??  One other thing I seem to notice
>  is that if you run it interactively I don't get the error but if I run 
> it 
>  in the background I do. I had turned on tracing in the program and the 
>  error is coming out from the butc executable.
> 
>    Any help is greatly appreciated
> 
>     Rick Bouchard
>   IBM AIX support
>   1-802-769-4204
> 
> --
> Richard J Bouchard
> e-mail: [EMAIL PROTECTED]
> 
> 

--------

Reply via email to