I disagree with you on this one, in prior versions TSm was reporting a
success even if it failed on backup of thousands of files.
I'd much rather see it as a failure if one file fails backup




"Stumpf, Joachim" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 10/18/2001
02:08:59 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:

Subject:  Fw: FW: v4.2.1 TSM Clients


I think it's true!

I tested the new client on a W2k machine and I got the same RC you
described
below.
If one file fails (e.g. it's in use by another proccess), the schedule
returns with a result code of 4.

I hope Tivoli works on a fix for that.
We have some automatically checking for result code <> 0 (if there was
a problem while backing up; and I think "file in use..." isn't a big
problem)

regards,
Joachim Stumpf
Datev eG

"Subash, Chandra" <[EMAIL PROTECTED]> (Donnerstag, 18. Oktober
2001, 06:41:31, MEST):

> i HAVE GOT THIS EMAIL FROM ONE OF MY FRIENDS. GUYS WHAT DO YOU THINK IS
IT
> TRUE ?
>
> Hi Guys
>
> According to Tivoli Support they have made an alteration to way client
> v4.2.1 reports Result code 4 to the server. Earlier version clients would
> allow for a certain number of files to fail during the backup and still
> report to the server that the Schedule was successful. However version
4.2.1
> has been altered so that a result code of failed will be reported to the
> server even if 1 file fails during a backup.
> ntcmachine had been failing on some WINNT system files which I have added
> exceptions for under direction of Tivoli support and now backups of this
> machine seem to be successful.
> Bob from Tivoli suggested that if we are worried about seeing failed
result
> codes on the daily report that there may be a way to generate a report
> listing statistics of how many files or how much data had been backed up
> from each machine to provide a more accurate picture as to whether the
> backups were successful.
>

--


(See attached file: Unbekannt.txt)

Unbekannt.txt

Reply via email to