Backup is working fine, but to further avoid any errors I want to identify
the reason for the same.

We are working on TSM version 5.1.0.

Regards
Akash Jain



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard Sims
Sent: Monday, 16 May 2005 5:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Core Dump while taking backup

On May 16, 2005, at 3:31 AM, Akash Jain wrote:

> Hi experts,
>
>
> After checking the logs it has been observed that dsm generated an
> core dump
> on one of the backup node.
>
> What could be the possible reasons for the same?
>
> Any suggestions or ideas are welcome?
> ...
> SIGNAL NUMBER
>            6
> ...


When posting, include your TSM level so that we can provide
reasonable advice.

I'm not aware of a Signal 6 (user abort) occurring beyond the TSM 4.1
level.
It might be a response to encountering a truncated control file (client
options file) or an artificial virtual memory exhaustion condition.
Look to the client dsmerror.log for possible error indications. The
server
Activity Log might happen to have some info.

The usual problem analysis approach, of course, asks if the backup
has been
going well over time until now, and then would seek environmental
changes
which caused the aberrant behavior. Did a client option or Include/
Exclude
change? You may be able to boost your maintenance level within whatever
version/release you are running, but ascertaining cause will help avoid
potential recurrence.

    Richard Sims