About the Linux tape drive device files
For tape drive device files, NetBackup uses the /dev/tape/by-path/xxxx-nst symbolic link files (-nst indicates the no rewind device file). The /dev/tape/by-path files are symbolic links to /dev/nstx device files. The Linux udev system creates the /dev/tape/by-path symlinks. These are persistent paths that always point to the same device. The/dev/nstx files can change associated devices, without updating NetBackup. Therefore, the /dev/nstx paths should not be used.
The Linux driver should create the /dev/nstx device files automatically. The Linux udev device management system should create the /dev/tape/by-path symbolic link files automatically. If the device files do not exist, see the Linux documentation for information about how to create them.
If you use device discovery in NetBackup, NetBackup looks for /dev/tape/by-path/xxxx-nst symbolic link files. NetBackup discovers the device files (and hence the devices) automatically. Alternatively, if you add a drive manually in NetBackup, you should enter the /dev/tape/by-path/xxxx-nst symbolic link pathname as the device file for that drive. If the /dev/nstx device paths are configured, restarting the NetBackup Device Manager (ltid) converts the paths to /dev/tape/by-path persistent paths.
The NetBackup avrd daemon establishes a default tape driver operating mode. If you change the default mode, NetBackup may not read and write tapes correctly, which results in data loss.