Conference decwet::networker

484.0. "pool algorithm to choose a label" by EVTAI1::POUSSARD () Thu Mar 13 1997 07:39

	Hi,


	I remember this question was already answered but I didn't success 
to find where, so I ask him again.

	A customer runs NetWorker 3.2A on Digital UNIX 3.2C


	He configured a pool attached to a specific label template.

	Let's assume, this label is from toto.001 --> toto.999

	Let's assume toto.002, toto.003, toto.004 are labelled, in the 
jukebox , and appendable.

	One day ( Monday ), a savegroup begins and NSR suggest mounting 
toto.002,then saves correctly on toto.002.

	On Tuesday, he asks again for toto.002 and save runs succesfully 
and the tape isn't still full.

	On Wednesday, instead of asking toto.002, which is not still full, 
he asks for toto.003, and save successfully on toto.003.

	On Thirday, he asks again for toto.002 , write on toto.002 until it 
is full and after ask for toto.003



	My question is:



	- why NSR doesn't finish to fulfill toto.002 before asking for a new 
tape ?? Is it possible, or can a special process like inventoring modify the 
order NSR asks for tapes in a pool, asking to write toto.003 instead of 
finish writing on toto.002 ??

	- What is the algorithm , a pool uses to choose a tape ??


	Thanks for your answer


			Gilles.

	The tape selection order is unpredictable in NetWorker version
	3.2.  This has been changed in NetWorker version 4.2 and above
	to give preference to the oldest (by date of labeling) tape that
	qualifies.

    	Thanks for your reply