Diana,
Have you tried backing this node up under a different node name as a test??
I had a problem similar to this on a client. All bacukps were running fine,
then one day, strange messages in activity log. We could get a backup to
finish under a different node name. All that we could surmise was some type
of bad or invalid entry in the TSM DB for that node name.
Regards,
Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP
-----Original Message-----
From: Diana Noble [mailto:djk AT umich DOT edu]
Sent: Tuesday, September 10, 2002 8:50 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANR0444W Protocol Error - Type GroupHandler
Andy -
Thanks for all the good information. I have opened a pmr with support on
this.
I'm not seeing any other errors in the activity log around this time. The
dsmsched.log on the client reports an unknown system error. This error is
only occurring on one system, that previous to a week ago backed up
fine. The error occurs every time the machine is backed up, either through
a scheduled backup or a backup started through the gui. There were some
server changes made about a month ago, but none recently. I have not done
a trace yet, but will do so when I can work out a time with the owner of
the client machine. I will keep you posted as to what I find out.
Thanks a bunch,
Diana
At 01:39 PM 9/5/02 -0600, Andrew Raibeck wrote:
>I forgot to address your question about "GroupHandler".
>
>GroupHandler is a TSM verb (an element of the "language" that TSM
>components use to communicate with each other) used to relate a number of
>different objects so that they are handled as a single logical group on
>the server.
>
>A protocol error occurs when there is a violation of the well-defined
>sequence in which verbs are exchanged between TSM components. An analogy
>would be a situation where you pass a friend in the hall, and you say "Hi,
>how are you doing?" Normally you would expect your friend to respond with
>something like, "I'm doing great! How about yourself?". But instead, if
>your friend responds with something like, "The sky is blue", you'll be
>left scratching your head; because while the response was a valid
>sentence, it didn't make sense within the context of your greeting, i.e.
>it was a "protocol violation". In the case of TSM, the client apparently
>sent a GroupHandler verb to the server when the server was not expecting
>it.
>
> >From the Admin CLI, run the command
>
> HELP 0444
>
>to find out more about the ANR0444W message.
>
>If you want to know more about the GroupHandler verb, you can check the
>TSM API manual and start looking at the dsmGroupHandler() function. Also
>check out "File Grouping" in the index. But in this case, knowing what
>GroupHandler is all about won't help you resolve this problem, but it will
>help the IBM/TSM support and development folks figure out what is going
>on.
>
>Regards,
>
>Andy
>
>Andy Raibeck
>IBM Software Group
>Tivoli Storage Manager Client Development
>Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
>Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
>
>The only dumb question is the one that goes unasked.
>The command line is your friend.
>"Good enough" is the enemy of excellence.
>----- Forwarded by Andrew Raibeck/Tucson/IBM on 09/05/2002 12:20 -----
>
>
>Andrew Raibeck
>09/05/2002 08:14
>
>
> To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> cc:
> From: Andrew Raibeck/Tucson/IBM@IBMUS
> Subject: Re: ANR0444W Protocol Error - Type GroupHandler
>
>
>
>
>
>
>Diana,
>
>Off-hand, I do not know what this problem is.
>
>Are there any other messages in the activity log that could signal a
>problem around the time this problem occurs?
>
>Is there anything in the dsmerror.log file that coincides with the time
>this problem occurs?
>
>What else is in the dsmsched.log file around the time the problem occurs?
>If you are running with the QUIET option, comment it out, then retry the
>backup and see what other detailed messages you get.
>
>What is the history of this problem in your shop? Does it occur on just
>one machine, some machines, or all machines? On the machines where the
>problem occurs, does it occur every time, intermittently, or just once? On
>the machines where the problem occurs, did the backups ever run without
>trouble? If so, then what (if anything) changed in your environment that
>might coincide with when the trouble started to occur?
>
>I would also recommend gathering the following documentation and
>contacting IBM support:
>
>1) A client SERVICE trace that shows the problem. Add the following to
>your client options file (dsm.opt):
>
> TRACEMAX 20
> TRACEFILE C:\TRACE.TXT
> TRACEFLAGS SERVICE
>
>If the problem happens within a few minutes after the the backup starts,
>you can eliminate the TRACEMAX line. Also, from your original description,
>it sounds like the backup stops altogether when the error occurs. If this
>is not the case, and the backup keeps going, then eliminate the TRACEMAX
>line.
>
>Also, if you have QUIET in your client options file, remove it. If you
>have a client options set with the QUIET option in it, remove that, too
>(at least temporarily) so that you can see detailed output from the
>console and/or dsmsched.log.
>
>If you can quickly reproduce the problem by running "dsmc incremental",
>then try it that way. Otherwise stop and restart the scheduler, so you'll
>get the trace the next time the backup runs.
>
>2) dsm.opt
>
>3) dsmsched.log
>
>4) dsmerror.log
>
>5) TSM server activity log from one hour before the error occurs to one
>hour after the error occurs.
>
>6) Client options set information (output from QUERY CLOPTSET) if your
>node has a client options set associated with it.
>
>That should be good for starters.
>
>Feel free to keep me posted on your progress.
>
>Regards,
>
>Andy
>
>Andy Raibeck
>IBM Software Group
>Tivoli Storage Manager Client Development
>Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
>Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
>
>The only dumb question is the one that goes unasked.
>The command line is your friend.
>"Good enough" is the enemy of excellence.
>
>
>
>
>Diana Noble <djk AT UMICH DOT EDU>
>Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>09/04/2002 07:01
>Please respond to "ADSM: Dist Stor Manager"
>
>
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: ANR0444W Protocol Error - Type GroupHandler
>
>
>
>Hi Everyone -
>
>We have a Windows 2000 Active Directory client running TSM 5.1 which has
>started receiving the following message in the activity log:
>
>ANR0444W Protocol error on session 11716 for node DCITCS (WinNT) -
>out-of-sequence verb (type GroupHandler) received.
>ANR0484W Session 11716 for node DCITCS (WinNT) terminated - protocol
>violation detected.
>
>The client scheduler log specifies an unknown system error. I haven't
>been
>able to find anything on "type GroupHandler". The server is TSM 4.2.2.5
>running on AIX 4.3.3. We receive this error on both scheduled backups and
>selective incremental backups. Does anyone have any information on what
>may be causing this or what "type GroupHandler" means?
>
>Thank you,
>
>Diana Noble
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.
|
