hi isabel,
this was fixed with client version 4.2.1.20,
------ snip ---- out of readme from version 4.2.1.20
IC31844 - Skipped files causes scheduled backups to be reported as failIC31844
- Skipped files causes scheduled backups to be reported as failed. *
* *
* Prior to 4.2.1.0, if a scheduled backup had files that were *
* skipped but otherwise ran successfully, the scheduled event *
* would still be reported as successful. This was the correct *
* behavior. With 4.2.1.0, that same scheduled event with skipped *
* files is reported as failed with a return code of 4. The fix in *
* this patch reinstates the correct behavior, which is to report *
* scheduled backups that ran successfully, except for skipped *
* files, as successful.
------- snap -------
Mit freundlichen Grüßen / Best Regards
Mit freundlichen Grüßen / Best Regards
Uwe Schreiber
Isabel.Gerhardt AT FERNUNI-HAGEN DOT DE
Sent by: ADSM-L AT VM.MARIST DOT EDU
26.04.2002 09:46
Please respond to ADSM-L
To: ADSM-L AT VM.MARIST DOT EDU
Subject: ANR2579E (return code 4)
Hi Listmembers,
some of our nodes suddenly fail their daily backup with a returncode 4.
They receive some file-errors, but sometimes it's returncode 0 and
sometimes it's returncode 4. I can't see the difference... In the
eventlog they show failed.
Please help!
Greetings,
Isabel Gerhardt
04/19/02 20:08:24 ANE4007E (Session: 7970, Node: <NODE1>) Error
processing '\\orga-archiv\c$\pagefile.sys':
access to the
object is denied
04/19/02 20:08:39 ANE4987E (Session: 7970, Node: <NODE1>) Error
processing '\\orga-archiv\c$\MSSQL7\Data
\master.mdf':
the object is in use by another process
.......... (many ANE4987E) ........
.......... (Status Summary with successful and failed objects) ........
04/19/02 20:08:56 ANR2579E Schedule <SCHED> in domain <DOMAIN> for
node
<NODE1> failed (return code 4).
Server:
TSM 4.1.5.0
AIX 4.3
Client:
PLATFORM_NAME: WinNT
CLIENT_VERSION: 4
CLIENT_RELEASE: 2
CLIENT_LEVEL: 1
CLIENT_SUBLEVEL: 0
CLIENT_OS_LEVEL: 4.00
|