BackupExec 12.5 on Intel Modular Server MFSYS25
9denis
July 19th, 2009
Hello,
We have Symantec BackupExec 12.5 installed on Intel Modular Server MFSYS25. The operating system is Windows Server 2003 64-bit. The tape drive that we use for backup is "HP StorageWorks Ultrium 1760" and it is connected via SAS port. The tape drives have Symantec Drivers installed. We have all the latest patches and service packs installed for Symantec BackupExec.
We are intermittently getting error while taking backup using Symantec BackupExec. The OS generates Event ID 11 and backup fails. The error source is "LSI_SAS" and the description says "The driver detected a controller error on \Device\RaidPort0".
Does anybody know of this error? Is there any known issue with this?
Thanks in Advance.
Regards,
Denis
Hi Denis, This error may
Hi Denis,
This error may occure if the tape library is connected RAID controller card.
Make sure that the library is connected to SCSI card only. Drivers which are installed for SCSI card should be OEM drivers.
Also check for the windows system event logs is it showing error as soon as backup fails
Probably Event ID would be 9, 11, 15 etc.
Ref. Link http://seer.entsupport.symantec.com/docs/280011.htm
Please check and confirm. If this remedy worked for you Kindly mark it as a SOLUTION
Abhijit
Thanks Abhijit for your
Thanks Abhijit for your valued reply.
Intel Modular Server comes with a common Storage Control Module, which has only 1 SAS Port. So, we have connected Tape drive with SAS Port to it. There is no option to connect a Tape Drive with SCSI port. Also, I have mentioned the error that gets registered in Event Log is Event ID 11. And it comes as soon as the backup fails.
Also, as per the recommendations in the document, we have fulfilled points no.1 & there is no option for point no.3. Today I will try to take backup after stopping RSM service.
Let me know if there is any other solution to this, as my backup fails almost everyday.
Regards,
Denis
Is there a provision to add a
Is there a provision to add a seperate SCSI card in that server?
Just check with that.
Please check and confirm. If this remedy worked for you Kindly mark it as a SOLUTION
Abhijit
There is no provision for
There is no provision for that.. Only SAS or iSCSI
Regards,
Denis
OK Now you have 2 options as
OK
Now you have 2 options as given below.
Option 1
Install BEWS 12.5 on another server / desktop, install SCSI card in that server and configure backup jobs on it.
Option 2
On the same server downgrade the BEWS to 11D and try to backup the data. For your information, in version 12.0 and 12.5 these are the limitations with this configurations.
Please check and confirm. If this remedy worked for you Kindly mark it as a SOLUTION
Abhijit
Backup Exec generally does
Backup Exec generally does not support any device attached to a RAID controller. There are a few exceptions to this rule though, the following technote goes over this. http://seer.entsupport.symantec.com/docs/325573.htm.
You will either need to move the device to a standard controller without raid, or to one of the controllers listed on that technote.
If this response answers your concern, please mark it as a "solution"
I'm are having the same
I'm are having the same problem. I'm getting controller errors (event 11) and resets (event 129) from the LSI_SAS driver. Our configuration is:
1 - Intel Modular Server 2.5" chassis
2 - 5520VI compute modules w/ mezzanine cards (Windows 2008 Standard 64-bit)
2 - Storage control modules
2 - Gigabit switch modules
3 - Power supplies
7 - Seagate 300GB SAS 2.5" hard drives
1 - Dell LT04 half height tape drive
The tape drive is connected to storage controller module 1 and is accessible from the first server. I've got technical support cases going with both Symantec and Intel. I've got the latest updates for Backup Exec 12.5. The tape drive has the latest firmware according to Dell's web site. I've also upgraded to Intel's 3.6 firmware for the modular server. I also have the latest MPIO drivers. Symantec seems to be pointing the finger at the storage controller driver. I'm in the process of providing Intel information for escalation. Please, post the solution if you get a resolution.
Thanks,
Matt
Symantec basically reviewed
Symantec basically reviewed the system configuration and claimed it's a hardware issue. I tend to agree with them. However, Intel supposely it looking in to the issue but they noted several times that this is OEM hardware and make no guarantees of it working.
Here's the device information on my tape drive:
Vendor: IBM
Product ID: ULTRIUM-HH4
Firmware: 89D1
Drive Type: LTO 64K (64K,10,0,E,HU)
Denis,
Could you post the information from your tape drive?
An update on this issue. It
An update on this issue. It now appears to be solved. The solution provided by Intel was to upgrade the LSI SAS firmware to v1.25.05. It's been working great since that was done. If you are having this issue call Intel as ask them for the new firmware.
Matt
Would you like to reply?
Login or Register to post your comment.