>Feb 25 16:28:41 clasp tldd[25220]: [ID 832037 daemon.error] scsi command 
>failed, may be timeout, scsi_pkt.us_reason = 7
>Feb 25 16:28:42 clasp tldd[25225]: [ID 832037 daemon.error] scsi command 
>failed, may be timeout, scsi_pkt.us_reason = 7
>Feb 25 16:28:44 clasp tldd[25270]: [ID 832037 daemon.error] scsi command 
>failed, may be timeout, scsi_pkt.us_reason = 7
>Feb 25 16:28:45 clasp tldd[25284]: [ID 832037 daemon.error] scsi command 
>failed, may be timeout, scsi_pkt.us_reason = 7
>Feb 25 16:28:46 clasp tldd[25292]: [ID 832037 daemon.error] scsi command 
>failed, may be timeout, scsi_pkt.us_reason = 7
>Feb 25 16:28:47 clasp tldd[25302]: [ID 832037 daemon.error] scsi command 
>failed, may be timeout, scsi_pkt.us_reason = 7


These messages come from tldd, the daemon controlling the robotic arm. Because 
you say that these messages appear when backups are running, I guess that the 
robotic arm is on the same bus as one or more tape drives.

I would suggest:
 -> Check cabling and termination of this SCSI bus.
 -> Make sure the library (robot arm) has unique SCSI id on the bus
    The librarie's SCSI id's can be set and seen on the lib's frontpanel
 -> If the robot is on a scsi bus with one or more tape drives, make sure that
    the "On bus" = On, on the lib's frontpanel. On bus = On means that the 
    robot arm shares a scsi connection with one or more drives.
    
Regards, Joost
-- 
Long may you run.