Some interesting things to report - First the good news - I was able to confirm that the server with the tape drive attached is fully functional and able to read and write tapes using a trial edition of Backup Exec 2012. It took me quite a while to nail this down as I had to use the generic microsof...
I sent the logs in last night - I verified that the tape drive works with a local install of Backup Exec (on the server with the tape drive) and will configure/test it on the remote server later today.
I would be happy to send the logs - where are there and where should I send them?
I am not sure I want to switch to a different back solution at this time - I have a fair number of tapes in the archive. However I can probably try something else to see if it's an issue with Retrospect.
Hi Anton - Partial Succes. I tried a number of different options/settings with the MS iSCSI initiator and was not successful. I tried mounting the tape and changer as one device and then separately. I reset the SCSI bus on the tape changer to SCSI ID 0 - so both the servers had the same mappings (Bu...
On source Windows 2008 R2 server: From Properties in the device manager Tape Drive shows as Tape drives -> Quantum LTO 3 Tape Drive -> Bus Number 0, Target Id 5, LUN 0 Medium Changer devices -> Quantum Superloader -> Bus Number 0, Target Id 5, LUN 1 On destination Windows SBS 2011 server Tape drives...
Hi! I have a quantum autoloader (Superloader3) attached to a physical Windows 2008 R2 server. I was able to install and use the tape redirector to export my autoloader and tape drive (they show up as two separate scsi devices). I installed the iSCSI initiator on a virtualized Windows server. I was a...