IBM Support

Does AUTODETECT option work when defining paths to Storage Agents.

Question & Answer


Question

Can the AUTODETECT option be used to obtain the correct serial number for a drive path on a Storage Agent.

Answer

The AUTODETECT=YES option is not used to obtain the serial number associated with a device name on a remote Storage Agent Server, but should be used to obtain the serial numbers of drive paths on the local Tivoli Storage Manager Server.

To use a Storage Agent there is a requirement that for all drive paths defined for the Storage Agent, there must also be a drive path defined to the Tivoli Storage Manager Server for each drive. When a drive path is defined to the Tivoli Storage Manager Server, using the AUTODETECT=YES option the server will obtain the serial number from the drive using the device name provided. If the serial number for the drive is blank the server will update the drive definition serial number, this is the default. If the serial number in the drive definition is not blank then AUTODETECT defaults to NO.

There are two options for obtaining the correct device names for a drive attached to a storage agent:

1. The serial numbers of the drive paths must be matched up manually. Use the serial numbers associated with the drives on the Tivoli Storage Manager Server, and match them to the serial numbers associated with device names on the Storage Agent.

2. Use Tivoli Storage Manager SAN Device Mapping function to automatically update the device path information.

Related Information

[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"StgAgent","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"All Supported Versions","Edition":"Edition Independent","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
17 June 2018

UID

swg21697806