ADSM-L

Re: Win32 baclient dies when backing up system object !?

2003-09-09 12:01:31
Subject: Re: Win32 baclient dies when backing up system object !?
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 9 Sep 2003 12:00:36 -0400
We have exactly the same problem.

Started happening when we started rolling out SP3.

An SP3 machine will back up OK for a while, then inexplicably refused to
back up the system files component of system objects.

Upgraded to 5.1.6.2, that fixes the problem for us.


-----Original Message-----
From: Kjetil Furnes [mailto:kjetil.furnes AT WIDECOMPUTING DOT COM]
Sent: Tuesday, September 09, 2003 11:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Win32 baclient dies when backing up system object !?


Hi !

I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing a manual backup, I find out that it is the system files that
cause the application to die.
(It doesn't hang, it just terminates and disappears !)

When running as a Scheduler service, this causes the Scheduler service
to stop,
giving the backup a failed status. (I don't know if it actually backs up
ordinary files first, but it discards them due to the failure)
The server reports the following:

09.09.2003 06:00:00   ANR2580E Schedule DAILY_DAP in domain PIPELINE_DAP
for
                                 node OSLDAP01 failed.


09.09.2003 05:59:55   ANR0480W Session 11689 for node OSLDAP01 (WinNT)

                                 terminated - connection with client
severed.


I've tried to reinstall the clients, also to different versions with the
same result.
Currently I have this problem on baclient versions 5.1.0.1 and 4.2.1.20.
(Have also tried various other versions)
My server is a version 4.1.3.0 (WinNT)

The weird thing, is that this problem seems to appear "overnight" for no
specific reason !?
(Same configuration as last 18 months without problems)

The scheduler logfile looks just fine (no errors)
The baclient error log states that the backup of local drives is
finished.
(usually with one or two errors due to a file being in use -> the object
is in use by another process, which is no big deal)


Anyone seen this before ?
Tips ? Workarounds ?


Kjetil Furnes
System Administrator
Wide Computing AS