SONY TSL-A500C showing in Stand-alone-Drives and not in Robotic Libraries BACKUP EXEC 12.5
Updated: 21 May 2010 | 15 comments
After waiting for Backup Exec 12.5, Liveupdate, Running BE2213R322898_x64bit_324096 on a 64Bit Windows 2008 Server with either Windows drivers, Sony drivers, or the symantec Tape driver 27/7/07 5.1.34.0 for a Sony TSL-SA500C, we still can't get it to be recognised as a Robotic Library. Is there any way we can force it to work? We have even tried the autoload function on the drive itself. the Firmware on the drive is the latest L201. I have seen previous posts from last year, stating that this would be fixed with a driver, and it was a known problem, however I can't find any more followups anywhere...
discussion Filed Under:
Comments
Can you run through this
Can you run through this technote and post the results? Make sure the Backup Exec services have been stopped when you run it.
http://seer.entsupport.symantec.com/docs/322814.htm
If this response answers your concern, please mark it as a "solution"
Output Created, as requested
System Page Size: 4096
ByName: Tape
05:00:01:00 01 -- \\.\Tape0
INQ 00 "SONY TSL-A500C L201"
INQ cc ""
INQ dc ""
INQ 83 "SONY TSL-A500C 0004715237"
INQ 80 "0004715237"
TUR 00 00000
RES 00 00 00000
REL 00 00 00000
BUS SCSI(1)
MAX 0xffffffff bytes 0x11 pages
ByName: MediumChanger
ByName: Changer
ByPort: Scsi
ByGuid: Tape
05:00:01:00 01 00 \\?\scsi#sequential&ven_sony&prod_tsl-a500c#6&685b469&0&000100#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
ByGuid: Changer
ByGuid: ChangerIomega
ByGuid: CDRom
00:00:01:00 05 00 \\?\ide#cdrommatshita_dvd-ram_uj-860s________________1.00____#5&c1c2522&0&0.1.0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}
INQ 00 "MATSHITADVD-RAM UJ-860S 1.00"
INQ cc ""
INQ dc ""
INQ 80 ""
Have you run the device
Have you run the device wizard through Backup Exec? It gives you the option to configure a robotic library. This should show up as a stand-alone drive, and the robotic library. and you can drag your drive down to the library. Afterwards, restart your services.
I've just had to do the same thing on an HP autoloader.
If you find this is a solution, please mark it as such.
I have tried to run the
I have tried to run the device wizard through Backup Exec, however it will not let me drag down the Stand-alone Drive. I wish it was as simple as that.
I see no evidence of a
I see no evidence of a changer in the log you posted. Does the SCSI HBA have multi-LUN support enabled and can it see the changer? Does Windows Device manager show the changer?
If you find this is a solution for the thread, please mark it as such.
The Windows Device manager
The Windows Device manager shows up as a Sony AIT 50GB Autoloader Drive, and if you have a look at the output log, under Tape "ven_sony&prod_tsl-a500c" is listed there.
A tsl-a500c and tsl-sa500c are both autoloaders, not single tape drives.
SCSI ID
Hey buddy, could you check the SCSI ID of your tape drive/s and the Autoloader. Sounds like there might be a conflict.
Only the one tape
Only the one tape drive/Autoloader on the SCSI Cable. No conflicts there... Even changed SCSI ID, didn't make a difference.
Well as Larry said it does
Well as Larry said it does not appear that we are able to see the library in the discovery data.
ByGuid: Tape
05:00:01:00 01 00 \\?\scsi#sequential&ven_sony&prod_tsl-a500c#6&685b469&0&000100#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
ByGuid: Changer
If Backup Exec did see the changer it would be listed here. So I need you to do a couple more things for me so I can see what's happening.
1. Stop all the Backup Exec services.
2. Find tracer.exe (should be located in the same directory as discover.exe)
3. Run tracer.exe and make sure that it is capturing data (if it's coming up on screen it's capturing data)
4. Start all the Backup Exec services.
5. After all the services have started save the tracer output to a .bin file.
6. Follow the directions in this technote to collect all the server data for me, use the user defined selections to attach the tracer bin file.
http://seer.entsupport.symantec.com/docs/318474.htm (note: if vxgather does not look like the screenshots it will need to be updated using the instructions in the first paragraph) Make sure to select Backup Exec Base Logs and Hardware Logs(if available)
7. Enter in 111-111-111 for the case number
8. Upload the data to the FTP and let me know either on here or via private message when the data has been uploaded and I will review the information as soon as I am available to do so.
If this response answers your concern, please mark it as a "solution"
I had a chance to review the
I had a chance to review the logs this morning and from what I can tell the system does NOT see the medium changer.
The first thing that I checked was the SCSI DeviceMap located in the registry (This is part of the OS not Backup Exec). So I find it very hard to believe that device manager shows both the Medium Changer and the Tape drive. I also checked the SCSI Trace, again it only lists communication with the tape drive, nothing with the medium changer. Can you post a screenshot of what you are seeing in Device Manager?
Since the Sony TSA-A500C is a LUN based device I have to ask one of the questions that was previously posted, is multi-LUN enabled on the SCSI Card this device is attached to?
If this response answers your concern, please mark it as a "solution"
I've had another chance to
I've had another chance to shutdown the server, and check the settings on the SCSI Card. Yes, you were right about checking the multi-LUN, it wasn't enabled on the port, however the Multiloader WAS showing in the device list (as pictured below)... When I re-enabled multi-LUN for the port, and went through the whole process of uninstalling the tape drive with the software and letting it autodetect, it did not re-appear. Here is a screenshot without multi-Lun enabled. I'm really running out of ideas to solve this problem.
With the multi-lun enabled,
With the multi-lun enabled, can you run through the discover and vxgather process again? I'd like to compare the results.
If this response answers your concern, please mark it as a "solution"
I take it this issue hasn't been fixed before
I take it this issue hasn't been resolved in the past...
www.symantec.com/connect/forums/sony-tsl-a500c-showing-single-tape-device
I think we will be looking to invest in another drive.
new driver set fix?
I see they released a new driver set, maybe it fixes your issue?
http://support.veritas.com/docs/326626
http://support.veritas.com/docs/326004
If you find this is a solution for the thread, please mark it as such.
I had a similar issue to
I had a similar issue to this with the SCSI HBA being a RAID controller that didn't support Multi-LUNs. Make sure your HBA is not a RAID controller.
Would you like to reply?
Login or Register to post your comment.