Hi,
I have the same situation here for no apparent reason.
I do weekly backups using TDP SQL. Three big databases on the same client
behave differently on the same day. The MIS db is 180GB and takes about
3hrs. The TRN db is 120GB and takes 2hrs to complete. The BAL db is 80GB and
take 1.30hrs. This happens for two weeks. Then for no apparent reason the
TRN db requires 5hrs to complete while the MIS db still takes 3hrs and the
BAL db 1.30hrs.
So the TRN db backup just slows down for two or three weeks. Then with no
change it gets back to normal. I have checked network connections, routing
configuration, database reorganisation - all is fine.

Any input would be welcome.

Yiannakis


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
David Benigni
Sent: 09 December 2003 04:58
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SQL TDP configurations


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.

Any thoughts would be great.  TIA.

David Benigni