Opportunistic Locking Question


so perhaps in wrong place because didn't see w2k3 forum anymore, looked appropriate me given choices.

i've been recieving occasional errors in nightly copy lot of sources have indicated disabling opportunistic locking solve problem. copy initiated file server, actual copy seperate server destination being off site server. servers w2k3 (not r2) latest service packs , hotfixes. questions are:

1: disable opportunistic locking on file server initiates copy, source server, destination server, or combination thereof?

2: besides possible performance loss, there additional side effects, concerning users using same files @ same time on file server? opportunistic locking relates how files locked while being used seems possible me disableing may lead unexpected behavior when more 1 person trying edit same document or such things. or things stay same except performance decrease?

any on either item appreciated. thank you.
-luke

thanks info.  problem there causing disconnect between client writing backup file , target server.  if take route of disabling oplocks, suggest doing in on client side performance on target server not impacted clients.



Windows Server  >  File Services and Storage



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file