This is what Linux multipath does - gives you a single device based on multiple paths to the device. Each path to a device would use standard scsi disk naming (/dev/sd*) but the multipath device uses a name (e.g. if using "friendly names") like /dev/mapper/mpath* and you set your processes to use that device instead of any of the underlying /dev/sd* devices. If one of the underlying paths goes away your processes still work because they can get to the disk via the other sd path.
If you do a web search for "multipath tutorial" you'll find various hits like this one:
http://thegeekdiary.com/beginners-gu...-multipathing/
Of course on rereading it appears you're talking about tape rather than disk and I've not done anything like that with tape. For our tape libraries we only have one path to tape for each drive and were told multipathing isn't possible. For your VTL I don't know the answer. I did find hits talking about multipathing for IBM and TSM:
https://adsm.org/forum/index.php?thr...ltipath.16459/ (For AIX?)
https://www.ibm.com/support/knowledg...4multipath.htm
Another hit I found mentions tape for standard Linux multipathing (device mapper multipath) but has no examples other than the disk multipathing I'm familiar with.