Del,

It looks like our particular problem is with the machine itself.

I guess the origin of the question start because, is backing up the SQL
databases straight to tape the correct thing to do?  What is everyone
else doing?

Thanks,

Dave

>>> hoobler AT US.IBM DOT COM 12/9/2003 8:58:30 AM >>>
David,

There are many factors that could slow a backup down.
You should by trying to find out if this is a slow-down
in the network, TSM Server, tape mount wait, SQL Server, etc.

If you happen to be running Windows 2000 SP4, there is a known
problem that causes SQL Server backups to slow down and possibly
hang in certain situations. This was fixed in SQL 2000 SP3a.
This may not be the problem you are seeing, but I wanted to
point it out just in case you were running Windows 2000 SP4.

Thanks,

Del

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

> Simple question.  What is the optimal why to back up MS SQL
databases?
> Whats the ideal pool configuration etc?
>
> Right now I'm running into trouble with the way Tivoli was
originally
> figured for our systems.  The SQL tdp's sit on the client and back up
to
> a tape pool just for sql backups.  The tape pool is backed up to our
drm
> pool then.  The problem is our one sql database takes a long time to
> backup, and it pushing the schedules all off.
>
> The other weird thing is, the sql tdp for no apparent reason decided
to
> cut its throughput in half.  Needless to say the backups take twice
as
> long.  And the machine itself has not changed.