I would logon onto the system that is connected to the tape drive s and see if they are visible. Internal database backup failure DP 7. However, BackupExec does not detect the autoloader robotics library. That is set up OK. Any advise on how to proceed from here?

Uploader: Kataxe
Date Added: 11 December 2014
File Size: 25.17 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 70199
Price: Free* [*Free Regsitration Required]

I think some other things are chaning on this system – for instance RSM being enabled.

I have 2-scssi tried h Backupexec and reinstalling uninstall, reboot, install, reboot but h autoloader is still not detected by BackupExec.

Sorry I am new to DP, is this suppose to generate a log somewhere? Hi, Your problem looks to be an issue with the connectivity between the server and tape drive. GUI doesn’t respond after Device definition modification.

Good morning Paul, the Backup was successful. Is there a way to use the HP StoageWorks tools to troubleshoot?

Hp ultrium 2-scsi scsi sequential device drivers – Free Download –

By using this site, you accept the Terms of Use and Rules of Participation. In Windows Service stop and disable Removable Storage service. The database is corrupt. Retry your backup or just a scan of a tape. The opinions expressed above are the personal sequebtial of the authors, not of Micro Focus.


When I try to manually add a device, it only detects the tape drive. When you changed the cable and terminator, did it effect termination of the tape drive itself?

Disable your media changer in device manager Disable tape drive in device manager.

However, BackupExec does not detect the autoloader robotics library. BE still only sees the tape drive and one media within the autoloader. This tool has also managed to detect the barcode of all my loaded media.

On the Cell Manager what output do you get from: Ah, now if you’d mentioned that I would have suggested going to the device properties in DP and ultrlum Reload serial number. Hi guys, I am having a similar problem but the when I run devbra -dev, I don’t get any information, just a blank space.

I found an error dveice in BackupExec: Now re-run devbra -dev, should see addressing is now scsi in device path.

The G2 Autoloader may have been recently added and hp ultrium 2-scsi scsi sequential device not be in sewuential older version. Robert Fidler Springfield, Missouri.


Quality and Testing Security Security Research. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. HI Paul, it is directly connected to the Fileserver.

Are these direct connect tape drives or on a SAN?

HP Ultrium-1 SCSI Sequential Tape Device Free Driver Download (Official)

Good Luck — Hi Hp ultrium 2-scsi scsi sequential device, Based on your guide, you stated: Anyway, thanks a ulttrium Lou. If a SAN can any other system still see them ok? Problems were encountered during the configuration of your storage devices. It is important that you have the most recent device drivers for your version of BE. DP autoinitialised media with some data on it. Then when I install BackupExec 11d, it installed BackupExec default driver recommended and the tape drive was also detected in Device Manager.