I would look into other activity currently going on within TSM at that
time...
I see things like that when (say) expiration is running at the same time a
client is backing up...
another time might be when reclamation is running and a client is
backing up
and/or some combination of such events... (backup, migration, reclamation,
expiration, ...)
I've never worried much about it myself (but I might be in error with my
thoughts...)
Dwight
-----Original Message-----
From: Matthias Feyerabend [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 13, 2001 9:57 AM
To: [EMAIL PROTECTED]
Subject: Lock acquisition failed
Hello,
we get reproducable errors on Windows2000 Server 4.2.1.7 running incr backup
from W2K fileserver:
ANR9999D dfutil.c(653): ThreadId<22> Lock acquisition (xLock) failed for
PoolId=1, cluster SrvId=0, Ck1=18, Ck2=1
Are these errors related to Server version, platform or to things like
bufpoolsize, logpoolsize?
Any answer appreciated.
Matthias Feyerabend
