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
: Improving NT client throughput
I have a bunch of Windows 2000 clients (file servers) whose backups are
really dragging. My server is TSM 3.7.3 on Solaris 2.7. The clients are
running TSM v 4.1.2.12. They have 2 Xeon 700Mhz CPUs and 512 MB RAM,
100Mb NICs on a gigabit backbone. Each one
I have a bunch of Windows 2000 clients (file servers) whose backups are
really dragging. My server is TSM 3.7.3 on Solaris 2.7. The clients are
running TSM v 4.1.2.12. They have 2 Xeon 700Mhz CPUs and 512 MB RAM,
100Mb NICs on a gigabit backbone. Each one of these clients has several
hundred
One additional item on the server can cause slowness with large amount of files on
client. on server do a: q db f=d
Look for these:
Cache Hit Pct.: 98.10
Cache Wait Pct.: 0.00
These two parameters from my server should be similar. If Cache Wait is above 0 there
is a problem. If Cache Hit