Vint,
just to give you an idea that you're not alone, we have similar type servers of
which the largest contains 1.9 million tiff files (avg. 45 kb), your worst case
client scenario. To increment the file system will cost TSM about 2 1/2 hours.
Backuping the data itself will come to an average of 10mb/min, I've seen total
times of 3 hrs 46 mins to backup 25080 files for a total of 1.08gb to a
don't-hold-your-breath 9 hrs 41 mins to backup 92587 files.
The client node hardware consists of single CPU HP 6000 servers with 256kb
controller cache, 12 disks are configured as 1 RAID-5, this is all running on a
dedicated FDDI backbone. (system OS is NT4 SP6a, TSM client is V3.7.2.17).
TSM client tuning consisted of setting sensible max options like the
tcpwindowsize 63, tcpbuffsize 32 and tcpnodelay yes.
For the NT TSM server side, well pure misery after migration from 3.1.2.57 to
4.1.3 the db cache hit has dropped from 98 % to 83 % this impacted the backup
time big time but with some client and server re-tuning we're still within the
available backup window. We hope to get the db cache hit up a few percent with a
dump/ loadformat/load/audit but the audit abends, something that should be fixed
in V4.1.3.2.
In conclusion the things to get right where it concerns hardware, big RAIDS
(RAID5 or 10) at least 6 disks, lots of controller cache, try getting file
spaces on their own RAIDS on a seperate SCSI channel this way you can
efficiently run multiple TSM client nodes on 1 box (admittedly customer has to
comply in advance).
Get on to your own TSM or data network backbone, if running ethernet try to let
the big clients run in a quiet time slot.
On the TSM client and server side, the perfomance settings advized by Tivoli
seem to do the job, well, most of the time. And for sure get that % db cache hit
up to 98.
regards Walter Ridderhof.
-----------------------------------------------------------------
ATTENTION:
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
=========================================================================
|
