ADSM-L

Re: Failed archive schedule

2003-11-03 08:35:37
Subject: Re: Failed archive schedule
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 3 Nov 2003 06:35:12 -0700
I also have to wonder which version of the client the originator of this
thread is running. Version 4.2.1.0 had a bug in it, APAR IC31844, where
skipped files would cause the event to be reported as "Failed".

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.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/03/2003 05:46
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Failed archive schedule


>Question1: what does it mean return code RC=4 in failed client archive
>schedule?

Your first point of reference should be the Backup-Archive Clients manual,
which fully explains this.  RC=4 simply means that some file could not be
processed, as you cited...

>There are some folders with access restrictions for TSM (for all users
>including system account with the exception of owner) and there are many
>errors at files inside these folders in activity.log - example:
>
>02-11-2003 01:13:54      ANE4007E (Session: 397, Node: NT1)  Error
>processing
>                          '\\nt1\e$\Uzivatelske
>oblasti\SPS\Home\SCL\B\d\wichtig\P-
>                          odpora HMG.doc': access to the object is denied
>
>No other erors weren't founded at all. Is it possible that these errors
>causes general schedule error RC=4?
>
>I have exclude.dir for these folders (for backup), but not
exclude.archive.

By all means, exclude things you know should not or cannot be treated by
TSM -
providing that you don't want them handled by TSM at all.  If the owner of
the
files is operating under the same options file, then they will be subject
to the
same rules, so consider that in formulating your options environment.

  Richard Sims, BU

<Prev in Thread] Current Thread [Next in Thread>