NDMP over FC in the mix could cause some reservation headaches.  We have
our netapp's set to persistent, but AIX set to the default (reserve_6)
and all is well.


Regards,
Shawn
________________________________________________
Shawn Drew




Internet
rrhodes AT FIRSTENERGYCORP DOT COM

Sent by: ADSM-L AT VM.MARIST DOT EDU
05/04/2011 01:57 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] tape reservation types in AIX






We had a big problem with reservations that turned out to be caused by
using different versions of Atape across our tsm servers and storage
agents.  As we were working with IBM, we would point out that there was
different versions of Atape across our systems.  They told us there was no
problem with having different versions of Atape  across our systems (all
AIX).  But, the solution that  finally worked was to get all systems to
the same (latest/greatest) Atape.

Rick




From:   Steven Langdale <steven.langdale AT GMAIL DOT COM>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   05/03/2011 10:34 AM
Subject:        Re: tape reservation types in AIX
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



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
>




-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.