From: esquel@sommarskog.se   
      
   Mark D Powell (Mark.Powell2@hp.com) writes:   
   > Recently my 64 bit SQL Server 2008 R2 RTM Enterprise Edition failover   
   > cluster running under Windows 2008 R2, the transaction log backup job   
   > has begun to fail every now and then with "was deadlocked on lock   
   > resources with another process and has been chosen as the deadlock   
   > victim"  Thirty minutes later when the next set of log backups run the   
   > task will run fine.   
   >   
   > This server is overdue to be migrated to a new cluster where it will can   
   > be patched, but I was wondering if anyone has seen this and knows of an   
   > article on the subject.   
      
   Supposedly, it is not the T-LOG backup itself that fails, but what fails   
   is when the log backup is recorded in msdb, which is not known for its   
   optimal indexing. This blog post with a script from my fellow MVP Geoff   
   Hiten should help you.   
      
   You should be able to deduce this from the error message, as it says   
   something like "the log backup itself was succesful".   
      
   Of course, if the entry is not written to msdb, this will make things a   
   little more difficult if you need to restore after a disaster.   
      
      
   --   
   Erland Sommarskog, Stockholm, esquel@sommarskog.se   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)