Fred -

Without an actual error message, extricated from TSM or MSSQL log/
error files, it's kinda difficult.  Somehow, someone has to dig that
out of this organizational stalemate.

You might want to look into IBM Technote 1194737 as one possible
technical avenue, perhaps inspiring further excavation.

   Richard Sims

On Sep 4, 2007, at 10:20 PM, Fred Johanson wrote:

Well, now we are at the point that MaxTransferSize is an MSSQL
parameter, but it is controlled by the TDP.  If that is the case,
how is it generated?  The only thing that I can come up with is
that the value generated is 4xLogBufSize.

Any hhhelp at navigating this rabbithole is greatly appreciated.

________________________________

From: ADSM: Dist Stor Manager on behalf of Richard Sims
Sent: Sat 9/1/2007 2:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] SQL TDP in MSCLuster



On Aug 31, 2007, at 9:18 PM, Fred Johanson wrote:

...The DBA is sure he has found the solution.  When he starts the
backup, this is the generated command:

BACKUP failed to complete the command USE master BACKUP DATABASE
[ProdDB] TO VIRTUAL_DEVICE=N'TDPSQL-000017B8-0000' WITH
BLOCKSIZE=512, MAXTRANSFERSIZE=1048576, NAME=N'full',
DESCRIPTION=N'TDPSQL-000017B8-0000 (TDP MS SQL V2)'

He's convinced the problem is with the MAXTRANSFERSIZE.  If I would
change that, everything would work.  But it's not a TSM parameter.
He says it doesn't appear in MSSQL either.  So where does this come
from?  Is it really the culprit?  Support hasn't been very
supportive so far, prefering to concentrate on the cluster.

Hi, Fred -

One wonders if the DBA did any research in his assigned area, in that
info on the MS SQL MaxTransferSize parameter is readily available, as
in http://support.microsoft.com/kb/873482 , where the value in play
looks nominal.

There have to be some messages somewhere saying why the backup
failed, as the basis for actual problem pursuit.

    Richard Sims