AndreaR Contributor.
Contributor.
225 views

Error [65:73] "Bad message format" when importing media

Jump to solution

Hello,

I'm trying to import in DP 10.50 some LTO-2 backup tapes created with an old version of Omniback II. I'm able to scan them without any problem, but when I try importing them the process starts normally but, after reading the entire tape it stops with the following error:

[Critical] From: MSM@andrea-pc "QUANTUM:ULTRIUM 3_andrea-pc" Time: 02/10/2019 21:43:28
[65:73] Media Management daemon reports:
"Bad message format."

[Normal] From: MMA@andrea-pc "QUANTUM:ULTRIUM 3_andrea-pc" Time: 02/10/2019 21:43:28
ABORTED Media Agent "QUANTUM:ULTRIUM 3_andrea-pc"

Since the media has not been added to the media pool I cannot restore any file.

Maybe someone has had the same problem and would be so kind to help me?

Many thanks,

Andrea

0 Likes
1 Solution

Accepted Solutions
Knowledge Partner
Knowledge Partner

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello @AndreaR,

I send you a direct link in a private message. Install the 9.0 media kit, then the 9.09 patch bundle and the individual patches in sequence.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
8 Replies
Knowledge Partner
Knowledge Partner

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello @AndreaR,

This looks like something for support. Are you able to reach out to them?

In the meantime you could load the media to the drive and try TapeAnalyser to verify the header and catalog the media. Also restore of a particular file should be possible.

Get the device path from devbra -dev first.

devbra -dev
TapeAnalyser.exe -type 13 -device "TapeX:0:1:2C" -header
TapeAnalyser.exe -type 13 -device "TapeX:0:1:2C" -catalog
TapeAnalyser.exe -type 13 -device "TapeX:0:1:2C" -filename /folder1/file1.txt -newfilename C:\restore\file1.txt

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello @AndreaR,

Is the backup on the media contain spanned across multiple cartridges? Please try importing it in the right sequence starting with the first media.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
AndreaR Contributor.
Contributor.

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello,

 

first, thanks for your help.

This is what I've got:

C:\Program Files\OmniBack\bin\utilns>TapeAnalyser.exe -type 13 -device "Tape0:4:0:10:0C" -header
Opening medium Tape0:4:0:10:0C
=================================
=============== MEDIUM START BLOCK ===============
6e4e4253 41424344 0 0 0 0 1 MA_BLK_START MA_BLK_NULL 0 8192 236
medDateInitialized = 02/05/2006 09:52:45
medDateLastAccess = 18/09/2010 09:40:18
medDateLastWrite = 18/09/2010 09:40:18
medDateLastOverwrite = 18/09/2010 09:40:18
medNumWrites = 0
medNumOverwrites = 36
devInfoLength = 24
devInfoOffset = 360
medID = a3e4f878:44570e5a:3e56:0001
medLabel = NTWD_LTO_FULL_1
medLocation =
poolLabel = NTWD_LTO_FULL
devCapacity = 0
devCapacityHi = 0
medFmtVersion = 2
medDFType = 0
medDFSubType = 0

-----------------------------------------

DEVICE INFO STRUCTURE of MAStartBlock:

devType = 13
devBlkSize = 65536
woeStartPos = 0
woeEndPos = 0
segNum = 0

 

C:\Program Files\OmniBack\bin\utilns>TapeAnalyser.exe -type 13 -device "Tape0:0:4:0:10:0C" -catalog
Opening medium Tape0:0:4:0:10:0C
=================================

=================================
TASK: ANALYSE CATALOG
=================================
MAMED_OPEN: medium successfully opened!
=======================================
===========================================================
Medium info:
Device name: Tape0:0:4:0:10:0C
Magic Cookie: 6E4E4253
Medium ID: a3e4f878:44570e5a:3e56:0001
Medium Label: NTWD_LTO_FULL_1
Medium Pool: NTWD_LTO_FULL
Number of Writes: 0l
Device Capacity: 0l kBytes
===========================================================

=======================================
Starting Analysis of medium
=================================

========================== DEFAULT ERROR REPORT ===========================
?15♥ ☺[12:1]♥ ☻[2002]♥ ♣1570173057♥ OMNI_BLKDMP♥ andrea-pc♥ ☺[90:52]♥ Tape0:0:4:0:10:0C♥ Details unknown.♥ Tape0:0:4:0:10:0C♥===========
==========================================

========================== DEFAULT ERROR REPORT ===========================
?15♥ ☺[12:1]♥ ☻[2002]♥ ♣1570173057♥ OMNI_BLKDMP♥ andrea-pc♥ ☺[90:53]♥ Tape0:0:4:0:10:0C♥ IPC Module Not Initialized♥ Tape0:0:4:0:10:0C♥=
====================================================

 

There seems to be some sort of error with -catalog, may be the cause of the problem?

The tape is the first of a set, it is clearly marked as such.

Thanks again,

Andrea

0 Likes
Knowledge Partner
Knowledge Partner

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello @AndreaR,

Call it fortune, but I had the same issues with A.10.50 and a few older LTO3/LTO4 tapes. The import aborted in the same way. I decided to do a test installation of Data Protector A.09.09_117 and the import worked well there (same hardware, OS, drivers).

I hope you have a old media kit available to do the same while I try to move this to support.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
AndreaR Contributor.
Contributor.

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello,

thanks for your help.

Unfortunately I don't have the older version. Is there a way for me to get it as a trial?

Thanks,

Andrea

 

0 Likes
Knowledge Partner
Knowledge Partner

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello @AndreaR,

I send you a direct link in a private message. Install the 9.0 media kit, then the 9.09 patch bundle and the individual patches in sequence.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
AndreaR Contributor.
Contributor.

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello,

thank you again for your help.

After downloading the older version I had a bit of a problem because it kept complaining about the SSL certificate not being ok, but after generating a new one I was able to use the GUI to import a tape and it worked.

I've tested other tapes and they all imported without issues.

So I think there is something wrong with the current version 10.50.

Best regards,

Andrea

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Error [65:73] "Bad message format" when importing media

Jump to solution

Hello @AndreaR,

Yes, there is something broken and I'm currently working with support to get this resolved. From the debugs I can see the media is correctly read, but the media is not properly added to the IDB afterwards. This is where it fails.

[ 99] 2019-10-04 14:09:43.349 ("w:\src\idb\src\facade\cadapter\legacy_wrapper.cpp":1391)
[ 99] <<=== (3) } /* DbOpen_facade */
[ 99]
[ 30] CmnSetDatabaseUUID:0 0 CA09EAC7-BBE3-404B-9CCC-11D2B733BDA0
[ 10] >>>>> Database re-opened after inactivity <<<<<

[ 10] 2019-10-04 14:09:43.349 ("/sm/mmd/mmd.c $Rev$ $Date:: $:":1781)
[ 30] [DblMarkLocker] lockQb=000000C6927C0000, 6772-1570185238@server.domain.com

[ 31] 2019-10-04 14:09:43.349 ("/db/lock.c $Rev$ $Date:: $:":979)
[ 10] Processing message MSG_ADDMEDIUM from MSM()@server.domain.com [handle:1,pid:6772,mtime:1570185238].

[ 5] 2019-10-04 14:09:43.349 ("/sm/mmd/mmdquery.c $Rev$ $Date:: $:":2703)
[ 5] [MARK 3] in MsgAddMedium:2703
Code: 1009
Info:


[ 5] 2019-10-04 14:09:43.349 ("/lib/cmn/error.c $Rev$ $Date:: $:":1173)
[ 5] [CLEAR 3]
Marked: ("/sm/mmd/mmdquery.c $Rev$ $Date:: $:":2703)
Code is:1009

You have two options now:

  1. Upgrade to 10.50 after the import. This will retain everything in IDB.
  2. Use Copy Catalog to File on 9.x and import the MCF on 10.50. 

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.