If you are on TSM 3.7/4.1 and have migrated from ADSM 3.1, please make sure
that the mount point limit for the node is > 0 if you are directing data to
tape (check your copygroups). In upgrading the data base, the default mount
limit for existing nodes is zero, for newly-defined nodes it is two. You
can change the limit using upd node * maxnummp=2 or whatever number of
drives you'd like the client to use.
Joerg Pohlmann
Richard Sims <[EMAIL PROTECTED]> on 2000-10-11 10:46:23 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: ANS1312E Server media mount not possible
>10/11/00 12:50:04 ANR0406I Session 7978 started for node RSCWS (AIX) =
> (Tcp/Ip 129.10.199.10(40421)).
>10/11/00 12:50:09 ANR0406I Session 7979 started for node RSCWS (AIX) =
> (Tcp/Ip 129.10.199.10(40423)).
>10/11/00 12:50:10 ANR0403I Session 7979 ended for node RSCWS (AIX).
>10/11/00 12:50:11 ANR0480W Session 7978 for node RSCWS (AIX) terminated
=
> - connection with client severed.
>
>
>>> [EMAIL PROTECTED] 10/11/00 11:33AM >>>
>>ANS1312E Server media mount not possible
Larry - That's very interesting...no indication of even trying to mount a
volume. Apparently, the server immediately knew that it could not
satisfy the request: there was no timeout as indicated in the ANS1312E
message description, and MOUNTWait could not be the issue since its unit of
measurement is minutes, and the rejection here was in seconds.
You didn't say, but I'll assume that you are set up to back up directly
to tape. I'll also assume the common collocation choice of "by node". In
that case the server would want to append the new data to the end of the
tape that it was last filling for that node. Perhaps that volume is in a
peculiar state - not bad enough to cause the server to go use a new scratch
or, if no scratches left, the end of any other tape. See if you can
determine
what that tape was, from the prior successful backup for that node
reflected
in the Activity Log or queries, and then do a Query Volume F=D to see what
it's state is; and also check that it is still in the library.
If you are backing up to an intermediate disk storage pool, check its
status and capacity.
Beyond that, see if there is any dsmerror log with further indications.
Richard Sims, BU
