Re: Failure of Archive Events with 4.11.16 client on NT

Methinks it's not a universal bug... we've got plenty of 3.1 & 3.7 clients
that get marked "failed" when archive can't access a file.  Sounds like they
regressed the event process somewhere in 4.1(?), or am I mistaken?

Don France

Technical Architect - Unix Engineering/P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph:   (408) 257-3037

 -----Original Message-----
From:   Rushforth, Tim [mailto:TRushfor AT CITY.WINNIPEG.MB DOT CA]
Sent:   Thursday, November 30, 2000 8:16 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Failure of Archive Events with 4.11.16 client on NT

I opened a problem regarding this with IBM.  They have confirmed that this
is a bug in the 3.7 and 4.1 client.  This will be fixed in the 4.12 client.
So with 4.12, processing will be as Andy described below.

Tim Rushforth
City of Winnipeg
trushfor AT city.winnipeg.mb DOT ca

>  -----Original Message-----
> From:         Rushforth, Tim
> Sent: Monday, November 20, 2000 11:35 AM
> To:   ADSM-L@VM. MARIST. EDU (E-mail)
> Subject:      Failure of Archive Events with 4.11.16 client on NT
>
> Andy Raibeck wrote in March 1999:
> "In the case of a SELECTIVE backup or an ARCHIVE, if one or more files can
> not be backed up (or archived) then the event will be failed. The
> rationale for this is that if you ask to selectively back up or archive
> one or more files, the assumption is that you want each and every one of
> those files to be processed. If even one file fails, then the event will
> have a status of failed. So the basic difference is that with incremental
> we expect that one or more files might not be able to be processed, so we
> do not flag such a case as failed. In other cases, like SELECTIVE or
> ARCHIVE, we expect that each file specified *must* be processed
> successfully, or else we flag the operation as failed."
>
> Has this changed?  Under 3.1.06 client on NT, an archive would show as
> failed if a file was in use.  With the 4.11.16 client, archive does not
> show as failed when files are in use or when archiving drives that do not
> exist.
>
> Thanks,
> Tim Rushforth
> trushfor AT city.winnipeg.mb DOT ca
>