Error 4462: The media was not prepared for boot with HP's One-Button Disaster Recovery (OBDR) soluti

[DavidALines]

I am running a brand new server 2003 R2 patched server. The server is a ML350 G5

With
Data protector 3.50 sp2
bare metal disaster recovery
exchange agent
open file agent

I am doing a full backup of the server including data protector express, system files, and data files.

I have checked under options, advanced options,
create dr bootable media
update dr information on selected server

I am using a HP LTO Ultrium 3 tape drive with HP tapes.

I have done several complete backups to different tapes and get this error every time

If I try and create a disaster recovery CD I get the error
No disaster recovery image could be located

Why is this so difficult?

[ChrisFowler]

Yep same problem here.

[D Lancaster]

What OS are you running?

[DavidALines]

brand new server 2003 R2 patched server

[D Lancaster]

32 Bit or 64 Bit?

[DavidALines]

Sorry - 32 bit.

[D Lancaster]

Hmm. Should work. It appears that it's hanging up getting the boot informaion from the internal SCSI or SATA array. I'll have to do some research.

DL

[D Lancaster · Accepted solution]

David,

Can you do a test for me?

Try to create the DR CD again. If it fails, capture all the files in the folder C:\Program Files\HP\Data Protector Express\log and zip them up and email them to me at ltt.team@hp.com with a subject line of "Files for Dave Lancaster"

Thanks.

[DavidALines]

I have attached the file drwntmp.zip to am email to you with a subject of
threadid=1195134
Thank you

[D Wong]

Hi David:

To understand why you are getting Error 4462, you need to attach the entire contents of the Data Protector Express log directory. Please attach your winzip log directory to this thread.

The dptrace.* files will show additional information on why you are not able to create an OBDR boot tract on your tape cartridge.

[DavidALines]

Here is the log directory minus the 226MB detail log file of the backups

[D Wong]

Hi David:

Your log directory attachment to the this thread seems to be unreadable.

Could you try again to attach log directory.

[DavidALines]

This is a compressed file, (ZIP) I have downloaded the file onto my computer from the HP site. It works perfectly. I could upload the file again but there is nothing wrong with it. It contains 48 files and I did not want to upload these individually. XP opens compressed files natively. Or you could use Winzip.

[D Wong]

Hi David:

Still cannot read you attached log files.

Try collecting your log file information by running the attached Data Protector Express collection tool on your Windows 32-bit machine.

The collected data logs will be stored in C:\ path location.

Please attach the output of the data collection information to this thread.

[D Wong]

Hi David:

I noticed an issue with my attachment to the above thread.

Please download the collection tool from the below public ftp site.

ftp://lines:Marvels1@15.192.32.69/

When you have finished collecting the data output copy the information to the above ftp site.

e.g.

> ftp 15.192.32.69
> login: lines
> password: Marvels1
> bin
> put dpwinsup.zip
> quit

[DavidALines]

I take it you got my email with the logs so I do not need to do this?

[D Wong]

Please use the ftp site capture tool. I cannot read your attachment to the thread.

[DavidALines]

OK - It appears I am getting confused and I apologise. I have emailed these details to

Devakumar D
Technical Conssultant II


Because I thought you and he were the same person - It looks like two people are trying to help me and although I really really appreciate it I can see this will get confusing. I have emailed Devakumar all the information YOU have requested. I am sorry

Can the two of you decide who is going to be my point of contact.

Once again I am sorry for this confusion.

[Kevin Simisi]

Hi there

Did you ever resolve this problem, can you add it to this forum.

Thanks

Kevin

[DavidALines]

Never been resolved no matter how many things I try.

I have been advised to reformat the server and reinstall DPE - NOT going to happen. I'm looking at shadow protect to do the same job.

[SBS Group]

I'm having the same error on a brand new ML310 with a USB attached DAT72.
I have 2 questions

1) How to I tell if the Bare Metal Disaster Recovery software is installed as it didn't appear as an option on the Data Protector express CD I have
2) Has anyone got a solution to this problem yet

Thank You
Doug

[SBS Group]

I've logged a support call with HP for this will let everyone know if they provide a solution that works.

[DavidALines]

Doug,

Sorry about my initial response to you - have you found answers to your questions. I now have a successful backup

AFTER 6 MONTHS

I had given up hope and admittedly I went on holiday and training courses and it was a very slow process.

ANYWAY

If you need help I feel I might be able to help. (which means I will pass on the knowledge I have gleaned from real HP engineers)

[SBS Group]

Hi David, yes I've managed to get it resolved with HP, only took 5 days. I'm not that happy with the answer I got but it works.
The resolution I was provided with was to change a registry setting because the DR software was having problems with the Language and Keyboard layout I had chosen when I first setup my server.

The response from HP is included here if anyone else is interested.

I have analyzed the DPtrace logs and have noticed the following alerts
07/23/2008 3:12:28 PM Wrg: Unable to open key DRSYSTEM\ControlSet001\Control\Keyboard Layouts\00001409 (2)

Based on that, I suspect may have a problem with incorrect entries in the registry for the keyboard layout

This means that DPX cant find the key in the Windows registry on the system that they are trying to perform the DR backup of.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layouts\00001409

It is looking in that location based on the information it finds in the following key
HKEY_USERS\.DEFAULT\Keyboard Layout\Preload

That key will have an entry with a value â 00001409â .

You may be able to resolve the problem by changing the value to a key that exists. For example, on the DPX server in my lab, I have the value â 00000409â in the HKEY_USERS\.DEFAULT\Keyboard Layout\Preload key, which will make DPX look for the key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layouts\00000409 which does exist.

Keep in mind that this is not a problem with DPX. Itâ s a problem in the registry.You may choose to use a tool that checks and corrects problems in the registry rather than manually editing it, and they should definitely have a working backup and restore process in place before editing the registry. We cant guarantee this workaround will resolve the problem, and problems can be caused by incorrectly editing the registry.

I disagree with the comment above about it not being a problem with DPX but a registry issue.

Doug

[DavidALines]

I have to tell you that is the exact same "final" issue I had with my installation. In the logs it would always complain about

Error 85: Registry Operation Failure

An unexpected error occurred while accessing the registry. Check the dptrace.txt file for more information.

I changed the preload from 00001409 to 00000409 and the error went away. Didn't even have to restart the server!