07-08-2010 04:02 AM
09-16-2010 04:16 AM
Hi,
Run the Device Configuration Wizard in Backup Exec and reload the Symantec drivers.
For good measure, restart the services.
After that, just make sure that you job is pointing correctly to the device...it might still be looking at "old/non-existant" hardware giving you that error.
Laters!
09-16-2010 07:29 AM
The autoloader has the magazines connected to the LUN 1, the same than de connections on the server. However, the drive has the LUN 7 in the system's definition and in the server the LUN is 0. I change it and start a new copy. It seems that it works right.
Was it a possible focus of the problem?
Thanks!!
09-16-2010 07:36 AM
LUN 7 is normally always reserved for the SCSI card. If your autoloader had SCSI 7 assigned to it manually, it would definitely have caused a hardware address conflict, causing your issues.
11-28-2010 06:53 PM
Hi there,
We are in the process of getting a HP P411 SAS controller working with a HP StorageWorks 1/8 G2 autoloader running on a Windows 2003 Virtual Machine. The backup software is Backup Exec 2010 R2.
The issue is that BackupExec and the OS are seeing the autoloader as a stand alone device and not a robotic library.
Our P411 controller supports multiple LUNs so I am guessing the issue lies with VMware ESXi.
Has anyone got the HP P411 or a HBA with multiple LUN support working on an ESXi guest?
11-28-2010 07:07 PM
You should start a new discussion for your problem.
11-28-2010 07:56 PM
Will do...