Configuring multi-drive robotic libraries

Configuring Backup Exec to work with multiple drive robotic libraries is accomplished by making associations between the robotic library's media drives, robotic arm, and Backup Exec. Backup Exec supports serialized drives; manual configuration of serialized drives is not required.

Each drive in the robotic library and the robotic arm requires its own SCSI ID. Multi-drive robotic libraries require separate SCSI IDs for each device.

In addition to separate SCSI IDs, each drive in a multi-drive robotic library has unique drive element addresses. You must know each drive's element address to properly configure the robotic library to work with Backup Exec (refer to your robotic library documentation to determine the drive element address for each storage device).

After determining the drive considered to be the first drive in the robotic library (Storage Device 0), you will need to arrange the SCSI IDs to match the sequence of the drive element addresses.

In the following example, if your robotic library has two drives, the drive with the lowest drive element address should be assigned the lower SCSI ID

Table: Example configuration for a multi-drive robotic library

Data Transfer Element (Storage Devices)


Drive Element Address

Robotic Arm



Storage Device 0



Storage Device 1



More Information

Bar code rules in mixed media libraries