Selecting the appropriate device driver depends upon the type of device and the media management technique. Devices supported by TSM can use the TSM device driver, and other devices can use Windows device drivers. The way administrators set up the two competing device drivers determines which one acquires devices when TSM is started.
Devices may be used with Windows device drivers or with the manufacturer's device drivers, but the devices must have the following capabilities:
A file listing devices and their attributes can be created:
c:\program files\tivoli\tsm\utils
adsmdlst devlist.txt
notepad devlist.txt
Select from the following device driver setup procedures based upon the device environment.
The TSM device driver supports many manual and automated library devices. At many sites, the TSM device driver may be all that is required.
The TSM device driver is installed with the TSM server, but the device driver is unusable until the default behavior of the Windows device driver is controlled. By default, the Windows device driver tries to acquire all devices when Windows is started. If this happens, the TSM device driver is unable to acquire devices. Administrators must ensure that the TSM device driver acquires the devices that it needs by starting the TSM device driver before starting any Windows device driver.
To start the TSM device driver before starting any Windows device driver:
In the TSM Server Utilities...
In the Windows Control Panel...
Windows NT |
|
Windows 2000 | Administrators using TSM with Windows 2000 do not need to explicitly control the Windows device driver's acquisition of devices. When the TSM device driver is in boot mode, it automatically acquires all devices not specified in its Device Exclude List. |
Some devices are not supported by the TSM device driver, but they can still be used with TSM using the Windows device drivers. At sites where a mix of supported and unsupported devices are used, both the TSM and the Windows device drivers may be used together.
An example of this scenario is an environment where some data is backed up to an automated library device and some data is backed up to an Iomega Jaz drive. The automated library device requires the TSM device driver. However, the TSM device driver does not support Iomega Jaz drives so the Windows device driver is used to allow TSM to back up to the Iomega Jaz drive.
In the TSM Server Utilities...
Note: | See Obtaining Alias Names for Devices. Adding TSM device names to the Device Exclude List may require an additional server reboot to update the Device Information view. |
In the Windows Control Panel...
Windows NT |
|
Windows 2000 | Administrators using TSM with Windows 2000 do not need to explicitly control the Windows device driver's acquisition of devices. When the TSM device driver is in boot mode, it automatically acquires all devices not specified in its Device Exclude List. |
In some environments, administrators will want to use the same devices with both the TSM device driver and the Windows device driver. For example, this occurs when devices are used to back up data with TSM and then the same devices are used at other times to back up data with a different backup utility. This scenario requires a reboot of the system to switch between applications. The device drivers can be set up to give administrators the choice of starting either device driver.
Activate the TSM Device Driver...
Click to check the Enable Optical Device Support check box. The TSM device driver is automatically set to start at boot time and acquire all devices.
To use the Windows device driver:
Click to uncheck the Enable Optical Device Support check box. This ensures that the Windows device driver acquires devices.
Activate the Windows Device Driver...
Windows NT |
|
Windows 2000 | Administrators using TSM with Windows 2000 do not need to explicitly control the Windows device driver's acquisition of devices. When the TSM device driver is in boot mode, it automatically acquires all devices not specified in its Device Exclude List. |
By default, the Windows device driver acquires control of supported devices when the operating system is started. In an environment made up entirely of devices unsupported by the TSM device driver, administrators can use this default setting.