Hi,
We apologize for the inconvenience caused because of the delayed response. Please let us know if your issue / problem is resolved so that we can archive this post. However, if the issues still persist then refer to the steps mentioned below:
Refer to following technote and verify
http://support.veritas.com/docs/191187
http://support.veritas.com/docs/256134
Also try to
- Disable the device by navigating to "Devices" tab, highlight the device, right click and select "Enabled". This will disable the device.
- Next delete the device using the same procedure and selecting "delete".
-Restart all the Backup Exec services
- Ensure that SCSI ID 0 & 1 are not being used, as they are reserved for bootable devices
- "Changer" or "Loader" should be configured at a lower SCSI ID than the drive. (e.g. Changer = 2, Drive =3)
- Ensure that the device is visible in "Device Manager" in Windows
- Update the firmware of the device.
- Update firmware of the SCSI controller.
- Disable removable storage (RSM) service on that device. In most of the cases, it has been seen that VERITAS device driver does not work properly with RSM.
Following steps will guide you through the same 1. Right click My Computer from the Windows desktop and click Manage.
2. Expand Storage, expand Removable Storage.
3. Expand Physical Locations. Under Physical Locations, you should see your devices and drives.
4. Right click the desired drive to disable and click Properties.
5. Click the General tab. At the bottom of the General tab is a checkbox for Enable Library.
6. Remove this check mark to disable this device or drive in RSM.
We would also suggest, that you check system events for SCSI related events (7,9,11or 15) and in case you find any please refer to following technote/article for further information http://seer.support.veritas.com/docs/191158.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;154690
Additional Information
http://support.veritas.com/docs/191488
We hope this will help.
Please update us on the issue so that If the issue still persists we can troubleshoot the issue further.
If we do not receive your intimation within two business days, this post would be presumed to be answered and will be marked as assumed answered and archived.
Thanks.