Mehdi

If I've followed your posts correctly, you are trying to run a 5.3
library manager and a 6.2 library client, and now you've added lan-free
into the mix.

The "not supported" status for the down-level library manager is not
there because things in general are likely to break it is because the
developers have too many combinations to test to make sure it all works
correctly in every respect.

Given that you have gone ahead with the down-level library manager,
then you may see these sorts of corner cases cropping up, and if you do
you are on your own.

The restrictions are there for a reason and it is wise to stick to
them.  I think you need to move the library management function to 6.2
as soon as you can.

Regards

Steve.

Steven Harris
TSM Admin
Canberra, Australia.



On Tue, 3 May 2011 15:32:35 +0100, Steven Langdale
<steven.langdale AT GMAIL DOT COM> wrote:

OK, so the storage agent gets a drive and doesn't appear to release
it when
completed?
TBH - I've only ever had reservation conflicts on windows clients.
You are
100% sure the paths are correct i.e. drive serial numbers match up on
client
and in the path defs for it?

On 3 May 2011 14:38, Mehdi Salehi <ezzobad AT gmail DOT com> wrote:

I have setup LAN-free backup, but sometimes the storage agent causes
reservation conflict. The only way to remove this conflict is the
following
command on storage agent:
# chdev  -l rmt0 -a reserve_type=persistent
and then
# chdev  -l rmt0 -a reserve_type=reserve_6

Here a library manger controls who should use the tape. I do not
understand
why this happens.

Thank you,
Mehdi