Hi Allen,

DP/SQL issues the "Waiting for Sql server..." message when it is
waiting for a SQL Server API to return for more than a few seconds.
DP/SQL cannot run a backup until that API call returns.

1. Take a look at the SQL Server log to see if it reveals anything.

2. Take a look at the Application Event Log to see if it complains.

3. If you have the space, try using the internal SQL Server tool for
   running a FULL backup.

4. Turn on DP/SQL tracing (add -TRACEFLAG=SERVICE -TRACEFILE=TRACE.TXT)
   to the command-line invocation of the backup.
   This will show you which SQL Server API is hanging.

If the steps above reveal nothing, you should call support.
Getting a trace to them will reveal where the hangup is.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/03/2009
10:24:22 AM:

> [image removed]
>
> Problems backing up a MSSQL database.
>
> Allen S. Rout
>
> to:
>
> ADSM-L
>
> 09/03/2009 10:25 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "Allen S. Rout"
>
> A client of mine is having some problems backing up a moderately sized
> MSSQL database.
>
> MSSQL:  2005 9.0.4035
> TDPSQL: 5.3.3.0
> TSMcli: 5.3.4.0
> TSMsrv: 5.5.3.0
>
>
> We've got a variety of DBs on this MSSQL instance, several smaller
> ones start moving data immediately and back up smoothly.  So we know
> we've got basic TSM commo working well.
>
> The problem child is moderately large: 126G.  When we request a full
> backup of it, the TDP gui smiles and waits, with message "Waiting for
> Sql server..." indefinitely.  Well, at least for two days. :)
>
> Of course, IDLETIMEOUT minutes after we kick that process off, the TSM
> server gives up; that ought not to be an issue, it should just start
> up again.
>
> On the MSSQL log side, we don't see anything edifying: there's a
> "starting this backup" notification, and then a "Hey! the backup
> application went away" when we close the TDP gui.
>
> We can do log backups from this database uneventfully, but we don't
> seem to be able to make a full.
>
> I've seen some messages in the archives talking about 'Waiting for SQL
> server', but they tend to be on the restore side.
>
>
> Any notions?  Usual suspects, tracing options, etc?  Where the problem
> stands right now, I anticipate a rousing game of Point The Finger if I
> hit the official support channels.  I am confident I can eventually
> win that game, but I don't relish spending the time.
>
>
>
> - Allen S. Rout