SPJobLockType

Architecture: There are 8 Servers in all.. 1 Database Server 1 Mail Server 2 Web-FrontEnds 4 App Servers (out of which one is the Central Admin and also a Web Frontend) Observation: If you take a look at the Job Status in the Operations tab of the Central Admin, we can see that some jobs are running 6 instances, some 3 and some 1 instance. The number of instances is controlled by the SPJobLockType parameter that has to be passed to your job constructor. ( For a guide to creating custom jobs refer Andrew Connell's article http://www.andrewconnell.com/blog/articles/CreatingCustomSharePointTimerJobs.aspx ) There are 3 Locks available.. SPJobLockType.None -- if you set it none, the instance will run in all the available servers in the Farm (e.g. Application Server Timer Job) SPJobLockType.ContentDatabase – this will cause 3 instances to be running in each of the Web-Frontends. SPJobLockType.Job – this will cause only one instance of the job to run on any of the front-end ser...