We're using TSM Server v3.7.1.0 on Windows NT and a number of clients
running v3.7.1 of the TSM client on Windows NT. The clients and server have
a lot of spare capacity so I thought I'd maximise the use of the available
resources by upping the resourceutilization setting in the DSM.OPT file.

With the resourceutilization set to 10 I started to see some really strange
things happening. Out of 800Mb of data on the server which was unchanged,
about 300Mb was backed up. This happened on repeated incremental backups,
but the individual files which were unnecessarily backed up seemed to be
unpredictable. During the backup, there were 7 or 8 sessions created with
the server.

This problem occured on any of the clients on which I set the
resourceutilization to 10. When I set the value back to 2, everything works
as expected.

Has anyone else seen this? Can anybody explain it?

Neil Schofield


The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Kelda Group plc and its subsidiaries, UK
Registered in England and Wales No 2366627