4 Operator

 • 

14.4K Posts

September 21st, 2007 06:00

NW is not scanner aware - meaning that while you run scanner to BW that looks like idle device. Could be that idle device timeout simply kicks out tape because of that. As for nsrck -L7 I'm not sure as I have never tested, but I would expect NW to be aware of that operation.

2 Intern

 • 

2K Posts

September 21st, 2007 10:00

I thought so but since save set recovery was ON I could not experiment with it. I wonder we need to readjust this everytime we need to run scanner.

For nsrck, I mentioned the wrong information earlier. When I run nsrck, it says NSR server busy, will retry in 30 seconds and keeps retrying for few minutes till you hit Ctrl+C to abort.

Any ideas.

4 Operator

 • 

14.4K Posts

September 22nd, 2007 07:00

busy mean that at least one resource required for operation to proceed is "busy" with something else. As for scanner, put drive to RO mode (across all shared instances) and load tape outside NW knowledge (eg. by using sjimm).

2 Intern

 • 

2K Posts

September 27th, 2007 06:00

Increasing device idle timeout has worked.

5 Posts

September 3rd, 2015 08:00

1--  SSH into Netowkrer Server

2-- nsradmin -c "type:NSR jukebox"

3-- Tab over to Options

4-- Tab over to Hidden and press Enter ---To show all hidden attributes

5-- Press Esc

6-- Tab to Edit   

7-- Arrow down to idle device timeout

8-- Press i -- to enter insert mode

9-- Change value to 0 --This will disable timeout

10- Press Esc and Enter to save

No Events found!

Top