Hi,

Does anybody else have problems with backups which have the
resourceutilization option set to greater than one ?

When the option first became available, we experimented with different
values. However, we found that the controlling thread would frequently go
into IDLEWAIT for long periods of time. If the IDLEWAIT state exceeds the
server IDLEWAIT timeout, then the session is terminated. We have seen this
result in a backup showing as 'completed' with all associated stats, but not
actually completing. If the filespaces are viewed, the backup shows as not
completed.

We circumvented this problem by always setting the resourceutilization to
one.

Now, with the release of the version 5 server & client, there is the
functionality for a multi-threaded restore. This requires MAXNUMMP and
RESOURCEUTILIZATION to be set to greater than one, to allow a restore to use
more than one tape and thus reap the performance benefits.

However, even with a version 5.1.1.4 server and version 5.1.1 client, we
still see the controlling thread timeout of a multi-thread backup. Our
IDLEWAIT parameter is set to 45 mins.

The resourceutlization parameter is now of some considerable use when doing
restores, but does not seem to function correctly when backing up.

Has anybody else seen this and if so, have you found a fix.

Thanks


  regards,

-=Dave=-
--
+44 (0)20 7608 7140

Accountants' minds are always in NumLock!


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________