ADSM-L

Re: Failed archive schedule

2003-11-03 09:39:04
Subject: Re: Failed archive schedule
From: "Tomáš Hrouda Ing." <throuda AT HTD DOT CZ>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 3 Nov 2003 15:41:19 +0100
Hi Richard,

thanks for your reply, but I meen this is not point of problem. Mentioned
server is fileserver and one of users has removed ALL permisions from his
files at this fileserver (including system account, which is running TSM
Scheduler), so his files cannot be backed up. He know about it and
understand it, that's OK, but now point of problem is how to exclude these
files (exactly directories) from archives. As far as I know, exclude.dir
acts only for backups and when I put exclude.archive option for files, TSM
will try to archive directories though. Am I true?

Tom

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Richard Sims
> Sent: Monday, November 03, 2003 1:47 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> 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>