- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- BE 12.5 and D2D2503i Error reading cartridge Data ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2010 08:53 AM
тАО03-12-2010 08:53 AM
BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
This is my first post after a long search throught the forums, if I violate any rules my apologies beforehand!
We use an HP D2D2503i as backup target, which emulates an MSL2024 tape library. Connection is iSCSI with a Network of its own (only NIC, Switch (HP1810G-24), Tapelib)
Firmware version is: 101.038
The system is connected to the Server via an NC380T with iSCSI license
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.
The emulated tape drive is an HP utlrium LTO3-Drive (using symantec driver 5.1.37.0, the and BE-recommended Unknown Media changer driver) Block size and SCSI settings for the tape drive 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 inconsistent data by the D2D web-interface.
Since I was startled by that I turned on the verify option in BE and surprise surprise: On a random file I get 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 occurs at random during the verify run.
I ensured that:
- all remote agents have the latest versions.
- Symantec drivers are being used
- 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.
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
George
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-19-2010 12:34 AM
тАО03-19-2010 12:34 AM
Re: BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
regards and good look.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-19-2010 02:12 AM
тАО03-19-2010 02:12 AM
Re: BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
best, George
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2010 03:01 AM
тАО08-29-2010 03:01 AM
Re: BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 06:28 AM
тАО09-02-2010 06:28 AM
Re: BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
1) Do a firmware upgrade
2) Delete the RAID-set from the RAID-Controller's BIOS. As the config data and the D2D OS are stored on an USB flash drive, you wont harm the config of your system
3) Reboot tice
4) In the Web Interface klick Rebuild RAID (wait one day)
5) That was it for me!
What they figured out as the initial reason was, that probaly one disk failed, and druing the rebuild another ahd a bad sector!
And yes, do a firmware upgrade, it boosts performance incredibly...
best,
George
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2010 03:53 AM
тАО09-05-2010 03:53 AM
Re: BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2010 12:37 PM
тАО09-08-2010 12:37 PM
Re: BE 12.5 and D2D2503i Error reading cartridge Data on exporting virtual cartridge
As the RAID had to be rebuilded from Scratch all the data was lost. We had a dreadful night until the first full backup had completed...