2 weeks ago we got your last recommendation in this case. In the meantime several other persons encountered the same error with similar equipment. Is it possible that you give a sign of life? Maybe that you are thinking of our problem and give a workaround soon? We spent a lot of trust in your product, you got money from us cause we purchased this program (including support), followed your tips and recommends and fiddled around to get your BackupExec working to do what all of us expect from it - security. But without your help we feel alone with this problem. Do you understand this?
Hello, have same reproducable problems: backup stops before unloading the first tape of the job, drive goes offline.
Autoloader 1/9 with ultrium1 drive fully ok (LTT wellnessTest), latest firmware and drivers. Load and unload operations indicate no difficulties. Running Veritas backup exec 10.0 Built5484 on Win2003 Server Scsi Connection with Adaptec 29160 on 80 Mb/sec Service for "removable media" is deactivated
When doing server backup�s e.g. 430GB i have to supply 3-5 tapes (100GB uncompressed each) - ok
Eventviewer application and system tells me: time: source: event 00:36:55 adpu160m Das Ger�t \Device\Scsi\adpu160m1 (translated:) did not answer in time 00:37:00 Backup Exec Adamm Mover Error: Write Failure! Error = ERROR_IO_DEVICE 00:37:00 Backup Exec Adamm Mover Error: Write Not Ready Failure! Error = ERROR_DEVICE_NOT_CONNECTED 00:37:01 Backup Exec Storage device "HP 2" reported an error demanding write data onto medium. 00:37:21 Backup Exec Adamm Mover Error: GetDriveInfo Failure! Error = ERROR_DEVICE_NOT_CONNECTED
Seems to me: tapedrive or Autoloader gives the wrong media type to the software, software attempts to write more data to the drive and does not receive an information that drive is full
Unfortunately this SP4 only works on the 10.0 version of Veritas with build 5484 while my version of 10.0 is currently 5520. So this SP cannot be installed.
I am very dissapointed in the service Veritas Staff offers to their customers. As a reseller I am looking for other products out there, just because Veritas doesn't seem to be able to support there own products.
I called Symantec for support and it came down to them telling me it's a hardware issue after they thoroughly looked at some logs and our configuration. We're using version 10d also, so this service pack does not apply. We have a Quantum Superloader with a DLT1 drive and I ran Quantum's small utility to check the drive and when I did a destructive write, the drive reported a "drive error b718".
Needless to say, Quantum is sending me a new drive to swap out tomorrow, I'm crossing my fingers.
Thats a real cheap awnser, blame it on something else so you don't have to say your own software is defective...
I've also swapped tapedrives, from a DDS-4 to a DAT72 drive both from HP. The DAT72 was previously tested in a different server with the same controller and worked fine there (also Veritas backupexec installed).
I really hope this drive-swap workes for you though.
I had a similar problem. I will tell you my results, but you may not like it...
I tried 4 - count them 4! different scsi controllers, each with different chipsets and drivers. I tampered with SCSI settings until I could do it in my sleep. I had the manufacturer replace the tape drive. I tried 5 different versions of the driver - OEM and Veritas. I tried dozens of different tapes and tape manufacturers. I tried manufacturer diagnostics - checked ok. I tried NTBackup - checked ok.
After all of that there was no resolution to the problem.
I reinstalled v9 of BE. It worked fine...
I installed v10 of BE to another box with the tape drive (a desktop) It worked fine... I still do not know what the problem was, but I can confirm that it has worked fine on the desktop backing up all the targets with remote agents for many months.
The resolution to my problem was having the drive replaced. I am no longer getting those hardware errors. I am getting tape errors now, I'm thinking the faulty drive may have damaged some tapes, but won't know for sure until I run more diagnostics.
Honestly...I hope for you (Rick) that it solved your problem for good. My 2 cents? It's rather strange that all of a sudden several users complain about this specific error with each it's own different hardware... I use Veritas Backup v10 in an upgraded computer (working as file-server), it worked for almost one year without any problem, and then all of a sudden the error occured. After some searching I found this thread with exactly the same problem for several users... I tried almost everything (changed drivers, reinstalled card, reconfigured Backup Exec, ...), I'm willing to reinstall Backup Exec, but I'm not going to reinstall my server as I am almost convinced (yes, sometimes I can be really stubburn...) that it is due to the software. Unfortunately it is impossible to test the hardware somewhere else, because the file-server has to be 24 hours, 7 by 7 up and running. Same problem, little amounts of data -> no problem at all. Once above an half an hour of backing up, it gives me the error... The SP4 as mentioned before did not solve my problem either... So, I'm still waiting for a solution of Veritas (Symantec), because, again just my 2 cents, this problem is due to a problem/conflict/... within Backup Exec.
My bad luck.. I am facing a somewhat similar problem in a new server Proliant ML370G4 with Internal tape drive with builtin SCSI controller. The tape device is HP Ultrium 460 LTO2 device. I configured Veritas 10d and updated with all updates. Tried the backup with new ultrium cartridge.
Even the ntbackup is getting failed while throwing a hardware error.
in Event Logs ..Adamm Mover Error : Write Failure! and Write Retry Failures! and I/O device error are listed.
I downloaded the latest Library and tape tools and tested the drive.. All the tests passed without any error.
Only similarity in these two server are the SCSI adpater driver is shown as LSI Adapter Ultra 320 SCSI 2000 series w/1020/1030 in device manager.
In first case HP support says it may be a tape drive problem and for second server it may be a software issue..
Our problem seemed to have occured around the same time we updated all of the HP hardware/software through Insight Manager. I cannot confirm that though. I'm wondering if maybe this is the common thread for everyone's problem since it seems everyone is running an HP server (ours is a ML350).