I was wondering if those using the sql tdp might pass on what they have
found is a good configuration for your systems. I certainly understand
there are going to be differences in how environments are set up and may
find I would have to use a completely different configuration. Honestly
the last time I used it was version 2.2 but wanted to see if it would
solve a on and off again problem we have, and since the dba's don't seem
to care I wanted to dig it out and try to get it back in as a standard.

I was able to install version 5.5 and just kicked off a full backup of a
single 35gb database. I am running a basic command line backup and did
not code in any optional items. The rate started around 11,168,00 Kb/Sec
but seems to be very slowly steadily dropping little by little, now at
11,129.00. I was wondering if others have seen better throughput by
tweaking the configuration options. Do you run nightly full backups on
everything or just selected db's or other scenario. Again, I have not
used it for some time and would like to get input on what folks have
found is a good setup and backup standard so the dba's are 'happy'
(which is hard around here).

The server is running 4 cpu's, windows 2003, 4gb ram and sql2000 on a
100/FULL link. Previously we had set up a .cmd file on the client and
set up the schedule to call it. From what I have seen so far it looks
like this is still the method for scheduling backups.

Currently I am exporting data and having it sent over to a DR site. At
this point the data is sql dumps the dba's create. I am guessing I can
export the sql filespace and import it at the other site and at that
point someone can use the sqltdp to restore it to a sqlserver. Any
issues I should be concerned with or specific options I would need to
use when restoring the data?

Thanks for any input others might have. 
 
Geoff Gill 
TSM Administrator 
PeopleSoft Sr. Systems Administrator 
SAIC M/S-G1b 
(858)826-4062 
Email: geoffrey.l.gill AT saic DOT com