We migrated from backint 2.4.17.3 to Tivoli Data Protection for SAP just
after the first of the year; no other changes in the supporting
infrastructure. I'm seeing a 19 MB/sec drop in throughput. Has anyone else
run into this? Is this just a stupid tuning parm thing I missed? We're
running the same init<SID>.utl we ran prior to the upgrade.

Short overview of config -

SAP/R3 database on ESS, spread evenly over 3 fiber channels (not using SSD).
DB server is an S7A, AIX 4.3.3-06; TSM server is an S7A, AIX 4.3.3-06, TSM
3.7.4.0. Running five seperate strams, two on one gigabit ethernet, three on
the second gigbit ethernet. TSM configured to write the data directly to
tape, IBM LTO in a 3584 library -- using five of our ten drives. We are
using TDP/backint rl_compression; we are not using TSM client compression.

This is from the 2.4.17.3 run:
KI0020I: End of backint program at: Sun Dec 16 02:28:46 2001.
BKI0022I: Average transmission rate was 251.035 GB/h (71.406 MB/sec).
BKI2019I: Compression ratio for backup was 1.23.
BKI0021I: Elapsed time: 02 h 25 min 35 sec.

and this is from the 3.4.0.6 run:
BKI1215I: Average transmission rate was 184.671 GB/h (52.529 MB/sec).
BKI0020I: End of backint program at: Sun Jan 13 03:30:03 2002 .
BKI0021I: Elapsed time: 03 h 27 min 14 sec .
BKI0024I: Return code is: 0.

This is a weekly off-line backup. We also run nightly on-line backups, to
four tape drives. I'm seeing roughly the same hit, down from 60 MB/sec to 51
MB/sec. As can bee seen, I no longer get any benefit from running the
additional tape drive for the off-line backup.

So -- is this real, or is this a stupid config/tuning issue?

Tom Kauffman
NIBCO, Inc