
Creating Configuration Files for Offhost Backup
64 NetBackup ServerFree Agent System Administrator’s Guide
Figure 14. Example mover.conf.storage_unit_name files (for two third-party copy devices)
Figure 14 shows two robots (robot0 and robot1). Robot0 has been assigned
two storage unit names, TLD_robot0 and TLD_robot00. Robot1 has been assigned
one storage unit name, TLD_robot1.
Figure 14 also shows two third-party copy devices, device-1 with a SCSI pass-through
device path of /dev/sg/c6t1l0, and device-2 with a SCSI pass-through device path
of /dev/sg/c6t4l0.
◆ To allow third-party copy device-1 to use robot0, create a file named
mover.conf.TLD_robot0. In the file, include the device path of device-1
(/dev/sg/c6t1l0).
◆ To allow third-party copy device-2 to use the same robot (robot0), create a file
named mover.conf.TLD_robot00. In the file, include the device path of
device-2 (/dev/sg/c6t4l0). Notice that the file name must refer to a different
storage unit, TLD_robot00, which is assigned to robot0.
◆ To allow third-party copy device-2 to use robot1, create a file named
mover.conf.TLD_robot1 that includes the device path of device-2
(/dev/sg/c6t4l0).
Third-party
copy device-1
/dev/sg/c6t1l0
Third-party
copy device-2
/dev/sg/c6t4l0
storage unit names:
TLD_robot0
TLD_robot00
storage unit name:
TLD_robot1
file name -> mover.conf.TLD_robot0
contains: /dev/sg/c6t1l0
SAN
Robots/storage units and
third-party copy devices on SAN:
Third-party copy devices in
mover.conf.storage_unit_name files:
robot0
robot1
file name -> mover.conf.TLD_robot00
contains: /dev/sg/c6t4l0
file name -> mover.conf.TLD_robot1
contains: /dev/sg/c6t4l0
NetBackup 4.0V ServerFree Agent System Administrator's Guide for Solaris
NetBackup 4.0V ServerFree Agent System Administrator's Guide for Solaris
Comentarios a estos manuales