ADSM-L

Re: [ADSM-L] SV: Scheduled Exc backup failing on -1073741819

2009-07-14 10:25:56
Subject: Re: [ADSM-L] SV: Scheduled Exc backup failing on -1073741819
From: Matthew Large <mlargedellteam AT GOOGLEMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 14 Jul 2009 15:24:38 +0100
Hi Christian,

The schedule is a defined command
"C:\Program Files\Tivoli\TSM\TDPExchange\tdpexcc.exe BACKUP * INCREMENTAL"
The same schedule works on 6 other Exchange server just fine.

Cheers,
Matthew
On Tue, Jul 14, 2009 at 3:09 PM, Christian Svensson <
Christian.Svensson AT cristie DOT se> wrote:

> When you execute the tdpexecc do you run from the Exchange TDP catalog or
> form the BAClient Directory?
>
> The TSM Schedule is execute everything from the BAClient directory.
>
> Best Regards
> Christian Svensson
>
> Cell: +46-70-325 1577
> E-mail: Christian.Svensson AT cristie DOT se
> Skype: cristie.christian.svensson
> ________________________________________
> Från: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] f&#246;r Matthew
> Large [mlargedellteam AT GOOGLEMAIL DOT COM]
> Skickat: den 14 juli 2009 16:00
> Till: ADSM-L AT VM.MARIST DOT EDU
> Ämne: Re: Scheduled Exc backup failing on -1073741819
>
> Nothing in the event.log except the same ANS1512E dsmsched.log entry,
> nothing in dsierror.log, no crash files. Exchange reports nothing related
> at
> the time of the failure.
>
> 5.3.3 TDP for Exchange
> 5.5.0.4 TSM client
> on W2K3sp2
> The problem is that the backup runs absolutely fine from a manual trigger.
>
> Just got Del's post - how did I miss that!? (late night's, early mornings)
>
> Much appreciated,
> Matthew
>
>
> On Tue, Jul 14, 2009 at 1:19 PM, Richard Sims <rbs AT bu DOT edu> wrote:
>
> > The -1073741819 reported by the ANS1512E message could have been
> > better programmed for such high negative values, to more appropriately
> > and helpfully report it as C0000005, which is more readily findable as
> > a memory access problem.  Your posting doesn't cite your software
> > levels: this might be APAR IC49467.  Look for event log, dsierror.log,
> > and dsmcrash.log problem indications, and take a look at the Exchange
> > side log if necessary.
> >
> > You might also see if the backup can be invoked manually: If the same
> > problem occurs, you can trace it thereby.
> >
> >    Richard Sims
> >
>