I/O Device Error 0x8007045D on Virtual Tape Drives

JuliusPIV

unread,

Jun 29, 2009, 10:06:01 AM6/29/09

to

On a Windows Server 2003 machine running DPM w/SP1, we're receiving the
following error on 2 of our virtual tape drives:

DPM encountered a critical error while performing an I/O operation on the
tape in Drive IBM ULTRIUM-TD1 SCSI Sequential Device (9040250003). (ID 30101
Details: The request could not be performed because of an I/O device error
(0x8007045D))

At first it was just one [virtual] device, so we disabled it, but within 2
hours or so, we received the same error on another [virtual] device. There
are 4 virtual tape drives, 2 of which were added within the last week. It is
the last two that have failed this morning. Everything was running fine
prior to this discovery early this morning. Since these are virtual, there's
no hardware to check (SCSI cables, terminators, reseating or replacing the
physical device itself) so we're not quite sure where to go.

A few searches revealed that others experienced similar issues, but they all
revolved around hardware or some physical device. Many of the results,
however, suggested the problem was with the tape drive firmware or device
driver. Along with that, several suggested creating the following key to
"ensure that [the] backup will span to next available whenever any IO device
error beyond of 30 GB on tape occurs. There by avoiding backup failures.":

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent]
"BufferQueueSize"=dword:00000001

Even though these are virtual drives, is a driver update necessary?
Is this a istuation where the registry key would do the trick?

We're looking for some documentation or advice on how to correctly
troubleshoot issues like these and what we should pay attention to. If
watson errors are required or unhandled exceptions from .xml files are
necessary, we're open to it.

--
Julius G. Perkins, IV
Enterprise Systems
Workstation Architect

Hitesh Sharma[MSFT]

unread,

Jun 30, 2009, 9:49:28 AM6/30/09

to

Hi,

Can you please try both the suggestions you have made:
1. Update drivers and 2. Try using the registry key mentioned.

--
Thanks,
Hitesh Sharma [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights.

Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm
"JuliusPIV" <Juli...@discussions.microsoft.com> wrote in message
news:88321666-1CB3-45EF...@microsoft.com...

Kh.@discussions.microsoft.com Archi Kh.

unread,

Aug 4, 2009, 4:41:01 AM8/4/09

to

Hi, all

I have the same situation on our env-nt (w2k3 sp2 x32, dpm 2007 sp1 x86, hp
msl 2024 lto3)
we used both of solututions : reg key BufferSize & TapeSize, updated lates
hardware drivers but nothing changed. Errors stil are.
Unfortunatly, we can't implement DPM as a productive DR solution.
Does MS have a real solution for this issue? we need it much more then ever!

Sachin Durge

unread,

Aug 4, 2009, 7:49:35 AM8/4/09

to

Can you change the tape drive drive to latest IBM driver or Inbox
ltotape.sys.
Seen some cases where ltotape.sys solved the problem.

Thanks,
Sachin Dugre[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights

"Archi Kh." <Archi Kh.@discussions.microsoft.com> wrote in message
news:10F9550A-85F4-4669...@microsoft.com...

Archi Kh.

unread,

Aug 5, 2009, 9:51:02 AM8/5/09

to

(( installed the ltotape.sys and have the same...

The back up to tape job failed for the following reason: (ID: 3311)

DPM encountered a critical error while performing an I/O operation on the

tape XXXXXXX-00000002 (GG3105) (Barcode - GG3105) in Drive Hewlett Packard
LTO Ultrium-3 drive. (ID: 30101)

Huber@discussions.microsoft.com Martin Huber

unread,

Aug 7, 2009, 6:07:14 AM8/7/09

to

Hi,

we have the same issue on a W2008 x64 with DPM2007 both with the latest
service packs an fixes, using a Tandberg StorageLibrary T40+ with a IBM LTO4
drive. The drivers we have installed are named on
http://technet.microsoft.com/en-us/dpm/cc678583.aspx#tandberg
but that didn't help either.

Sachin Durge

unread,

Aug 12, 2009, 2:23:05 AM8/12/09

to

I assume you are using DPM 2007 SP1. Did you tried below regkeys

Please add the following registry key to span after hitting I/O error while
writing data to tape

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent]

"TapeSize"=dword:00005000

00005000 is just a example, you can choose whatever value you want.
With this registry key set DPM will treat I/O errors(due to bad tape or
other issues) after offset 0x5000 as End Of media. by default DPM treat I/O
Errors after offset 30GB as End Of media.
-----------
Please add the below registry key to avoid job failures due to unexpected
driver behavior.

Registery change: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data

ProtectionManager\Agent] "BufferQueueSize"=dword:00000001

With this registry key DPM will issue one write to tape at a time, and avoid
driver issues with multiple asyncv writes. You might see backup/recovery
through put slowdown because of this(specially if you are using tape
encryption)

Thanks,
Sachin

This posting is provided "AS IS" with no warranties, and confers no rights

"Martin Huber" <Martin Hu...@discussions.microsoft.com> wrote in message
news:BE046E3A-BE16-48D9...@microsoft.com...

Martin Huber

unread,

Aug 12, 2009, 3:41:01 AM8/12/09

to

Hello Sachin,

thanks for answering so fast. Just one question: What value in GB the
0x0005000 stands for and what do you expect should we use for the native 800
GB Tapes?

Is there a recommendation?

Sachin Durge

unread,

Aug 12, 2009, 7:00:11 AM8/12/09

to

Its in MB, So in below DPM will treat IO Errors after 0x500MB as End of
media.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent]
"TapeSize"=dword:00005000

--

Thanks,
Sachin
This posting is provided "AS IS" with no warranties, and confers no rights

"Martin Huber" <Marti...@discussions.microsoft.com> wrote in message
news:0745E4B7-F6EE-4932...@microsoft.com...

uroskolar

unread,

Sep 18, 2009, 7:26:30 AM9/18/09

to

I am confused, you cannot assign a value to a key in registry. I may be wrong, but my understanding of registry is as follows.

I believe you have to create a value entity to assig it a numerical value (e.g. DWORD value), you cannot assign this simply to the key.

Like before, when speaking about BufferQueueSize.
The key was:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent]

And the value entity: BufferQueueSize, which is of DWALUE type.

The question is what's the correct value entity inside the key below:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent]

Which will carry the value 0x00000500?

I have huge problems with this one, and backups are as always, mission critical, so please help and provide me the missing information.

Posted as a reply to:

Re: I/O Device Error 0x8007045D on Virtual Tape Drives

Its in MB, So in below DPM will treat IO Errors after 0x500MB as End of
media.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent]
"TapeSize"=dword:00005000

--
Thanks,
Sachin
This posting is provided "AS IS" with no warranties, and confers no rights

"Martin Huber" <Marti...@discussions.microsoft.com> wrote in message
news:0745E4B7-F6EE-4932...@microsoft.com...

EggHeadCafe - Software Developer Portal of Choice
WCF Workflow Services Using External Data Exchange
http://www.eggheadcafe.com/tutorials/aspnet/3d49fa0d-a120-4977-842a-6dafb17b6d74/wcf-workflow-services-usi.aspx

Pranay Prabhakar [MSFT]

unread,

Oct 5, 2009, 5:46:30 AM10/5/09

to

TapeSize

Thanks,

"Uros Kolar" wrote in message news:200991872628...@hotmail.com...