Hi everyone!
This is my first post after a long search throught the forums, if I violate any rules my apologies beforehand!
We are using BE 12.5 SP3 with all avaliable patches as of Feb 28 2010.
BE runs on a Win Server 2008 x64 platform
We are backing up the server itself, another 2008x64 and a Win2003 file server.
We use an HP D2D2503i as backup target, which emulates an MSL20204 tape library. Connection is iSCSI with a Network of its own (only NIC, Switch, Tapelib)
The product is listed as being BE compatible by HP
The emulated tape drive is an HP utlrium LTO3-Drive (using symantec driver 5.1.37.0) Block sizte and SCSI settings have not been altered and are default values.
The system has already been working for quite some time now.
A few days ago, I tried to copy a virtual cartridge to a physical one and received an error about inconsisten data by the D2D webinterface.
Since I was startled by that I turned on the verify option in BE and surprise surprise: As soon as data from a remote server is about to be verified my backup job fails with the error
e00084c8 - "Backup-Gerät ist ausgefallen (eng: somthing like backup device is offline/not available)
In the event log I find the Errors:
33152 - Adamm mover error read failed
57665 - error during a read request (translated)
34113 - Backup job failed (translated)
The error only occurs when the verify of the first remote server is about to start!
I ensured that:
- all remote agents have the latest versions.
- Symantec drivers are being user
- smaller backups of remote servers run without problems - no problem with verify
- ethernet and IP connectivity is fine!
I also recreated the virtual cartridges
A few pieces of extra information:
The changer is partitioned in 6 partitions, with three slots for the first 5 partitions and one slot for the last (keeping it empty for restores)
Backup takes place according to a partition chosen by the day of week
I read through a heap of documentation but all I could find was information pertaining to physical devices. As my cvirtual tapelib claims it's healthy I'm inclined to believe that, especially as the error only occurs when the first verify of a remote server is about to start.
Does anyone of the inclined readers have an idea what might be the problem here? Management is slowly getting fussed about the whole issue, because I had to tell them that some other backups might also be toasted as we had verify off.
with many thanks in advance!
best regards
Georg
