Networker

Re: [Networker] What are the barcode requirements for Networker

2012-11-05 13:38:43
Subject: Re: [Networker] What are the barcode requirements for Networker
From: Yaron Zabary <yaron AT ARISTO.TAU.AC DOT IL>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 5 Nov 2012 20:27:47 +0200
This is the what I see here as well. I have four unlabelled tapes in my library for a few months now that Networker hasn't touched while merrily labels recycled tapes. AMM is on.

On 11/04/2012 03:19 PM, Dag Nygren wrote:
On Friday 02 November 2012 15:25:11 Tony Albers wrote:
Dag, can you point me to that documentation?

I'm seeing a different behaviour, so I'd like to check to make sure.


Hi again,

sorry for the late answer. Have been a bit busy.

The "documentation" I was talking about is the in the class material of the
offcial training for Networker I am teaching. The slide has been there for some 
years and
it might well reflect old behaviour...
Would be nice to get it confirmed/revised by someone from engineering.
It needs to be fixed in case it is wrong!

Best
Dag

On 10/31/2012 07:59 PM, Dag Nygren wrote:
On Wednesday 31 October 2012 15:26:21 Tony Albers wrote:

Is the behaviour on a VTL really different than in a normal jukebox on this 
one, Tony?
Cannot find anything in my docus on that and normally Networker always
prefers recyclable tapes to unlabeled ones.


No, it's exactly the same, NW always uses an unlabeled tape before
recycling a tape. That's just NW's way of trying to preserve data you
might want to use even though you've let it expire.

Nope, he is not.
An unlabeled tape is the last one in the flowchart. And only iff "auto media 
management" is enabled.

The selection steps for a backup are:

1. Appendable mounted tape in required Pool
2. Appendable unmounted tape in required Pool
3. Recyclable tape in required Pool
4. Recyclable tape in other Pool (with suitable "Recycle to" and "Recycle from" 
settings)
5. Unlabeled tape if "Auto media management" is turned on

Haven't tested all of those, but this is what the documentation says.

And the point 5 is definitely last.
Just thought that it for some reason might behave differently on VTL as the 
"Virtual" also triggers
other different behaviour.

Best
Dag



--

-- Yaron.